how to stay efficient when a build is almost always broken
I work in a middle sized team which shares the same source code and while have a continues integration in place, but as all of us has to work in the same branch, the build is almost always broken.
Handling compiler bugs in Continuous Integration
I believe that warnings should be treated as errors. If you start ignoring warnings you’ll start missing “important” warnings among the “unimportant” ones. So my Continuous Integration system fails a build if there are warnings.
How is it possible to build the whole codebase from source at Google scale?
The first answer to an old, recently active question linked to a video which talks about how Google repository is done.
Who should support and maintain development infrastructure?
I am interested to know what other peoples’ experiences are with managing development infrastructure are. I am talking about things like the build server, the central git repo etc etc. Any infrastructure which end users would probably not even know existed, but which are essential for the development team.
Simple explanation of Continuous Integration
How would you define Continuous Integration and what specific components does a CI server contain?
In which cases build artifacts will be different in different environments
We are working on automation of deployment using Jenkins. We have different environments – DEV, UAT, PROD. In SVN, we are tagging each release and placing same binaries in DEV, UAT, PROD. The artifacts already contains config files w.r.t each environment but I am not understanding why we are storing binaries in environment folder again. Are there any scenarios where deployment might be different for different environments.
Continuous Integration with Bamboo and Maven, Managing Version Numbers?
I am currently developing a product that is broken up into a few main parts: A Server, an Android client, a Desktop client, and a class library for providing common data structures. Currently my team is using Maven (with a private Nexus repo) and TeamCity to do continuous integration, but we’re having a ton of problems with builds failing due to version numbering issues. Our current solution involves using the Auto-Increment Versions Plugin for Maven, but any time we make any changes to our pom files we have to manually update the version of the pom file since the version of the pom in Git is now out of date.
Continuous Integration with Bamboo and Maven, Managing Version Numbers?
I am currently developing a product that is broken up into a few main parts: A Server, an Android client, a Desktop client, and a class library for providing common data structures. Currently my team is using Maven (with a private Nexus repo) and TeamCity to do continuous integration, but we’re having a ton of problems with builds failing due to version numbering issues. Our current solution involves using the Auto-Increment Versions Plugin for Maven, but any time we make any changes to our pom files we have to manually update the version of the pom file since the version of the pom in Git is now out of date.
Who fixes broken tests? [duplicate]
This question already has answers here: Should a programmer fix someone else’s failed build? [closed] (16 answers) Closed 11 years ago. Our small team has made the curious observation that diagnosing and fixing broken automated tests is a useful activity; in particular, if the CI build indicates that developer A’s last check-in broke some tests, […]
Who fixes broken tests? [duplicate]
This question already has answers here: Should a programmer fix someone else’s failed build? [closed] (16 answers) Closed 11 years ago. Our small team has made the curious observation that diagnosing and fixing broken automated tests is a useful activity; in particular, if the CI build indicates that developer A’s last check-in broke some tests, […]