continuous integration and continuous deployment tools

testing, the current code is a version that can be deployed directly (artifact). All files of this version are packaged ( tar filename.tar * ) archived and sent to the production server.The production server will package the files, unpack them into a local directory, point the symbolic Link (symlink) of the running path to the directory, and then restart the app. The deployment tools in this area are ansib

1 overviewContinuous integration (continuous integration) is a software development practice.2 main environment and tools Git code management System (for example: Gitosc) Linux operating system (UBUNTU) Jenkins System Software installation package The SDK for Jenkins ' Python language Python an

[LNMP automation integration] use jenkins for PHP continuous integration-automated code inspection, analysis, and Singleton testing continuous integration to solve problems Uniform test code release Code automated testing Multi-host automatic

integration was successful, when the icon is red, it indicates that the last integration failed, and when it is yellow, it indicates that continuous integration is in progress. The following icon shows the problem with the last integration: There is also a kind of is to us

time when the test fails or an error occurs. Constantly test and fix integration issues to avoid cramming. Alert issues and conflict codes. All code changes can be tested in a timely manner. Provide developers with timely feedback on the functionality, quality, and impact of their writing code. Frequent code checks encourage developers to write modular and concise code. The project is kept in a running state at all times.

　Part 1. Implementation 0. Functions of continuous integration tools Reduce Risks? No Improve quality? No Quick feedback? Yes! The tool itself cannot reduce project risks and improve code quality. the only thing the tool can do is to give you quick feedback. the behavior after you receive feedback is the key to reducing risks and improving the quality (not checki

In this article, I will only talk about "continuous integration ". Some people say that Agility must have continuous integration, while others say that continuous integration is agile. If you do not know about

Agile requirement analysis, Agile Project Management, and agile software development have become a hot topic. In today's complex and changing business projects, it seems that "agile" has become the best choice. Indeed, no matter from theory or countless cases, most of the software projects in today's business environment are suitable. Just as the appearance of a good language affects a software developer's five, ten, or even longer career. The emergence and popularization of an excellent softw

continuous integration can be used in most companies today or in the same way. Some will choose some open source tools, such as Cruisecontrol,hudson,luntbuild and so on, some will buy a better service, stronger features of the commercial products, such as teamcity,quickbuild and so on, And some will choose their own implementation, such as Cron+ant/maven/make and

integration systemThus, a complete build system must include: An automated build process that includes automated compilation, distribution, deployment, and testing. A code repository that requires version control software to guarantee the maintainability of the Code and as a repository for the build process. A continuous

Transferred from: Http://www.infoq.com/cn/news/2011/05/ci-dependency-management Http://kb.cnblogs.com/page/101101/ In the previous article branch policy (continued), we discussed multi-component applications.ProgramContinuous integration policy, that is, to create your own exclusive for relatively independent componentsCodeLibrary, and then continuous integrati