How do I go from “here’s the zip” to a good release strategy?
I can write code, resolve dependencies, and get my program to run on my computer; I have no idea where to go from here though. How do I get the software ready for distribution?
Dynamic choice of compilers?
An application has the following logic:
How often should we launch SONAR analysis?
I successfully installed Jenkins and then Sonar to go with continuous integration. The firsts reports are not that good in term of rules violations ,comments, code duplication …
Does continuous integration involve automatic merging between branches?
When setting up a continous integration environment, does it always entail having the build server pull code and merge between branches?
Is it a good practice to capture build artifacts in Artifactory that Jenkins produces?
We use Jenkins to run continuous integration builds. The output of these builds might be EAR files, WAR files, or just a collection of files that are TAR’d up.
What software models are appropriate for daily builds and continuous integration?
On reading the joel test and about daily builds, a discussion with a few tech-lead friends of mine in various companies revealed that they never did daily builds or continuous integration because according to them:
What are the practical examples of code exploration techniques?
Code Exploration (CE) is quite a new term and I wonder if there already any successful examples of implementing this techniques in terms of Continuous Integration principles?
Branching and CI Builds with Agile
We follow many agile processes, including automated tests, continuous integration, sprint reviews, etc… We’re currently having a debate about how often we should branch release builds.
How should I select continuous integration tool? [closed]
Closed 9 years ago.
How do I get from a highly manual process of development and deploy to continuous integration?
We have a development process which is completely manual. No unit tests, interface tests are manual, and merging and integration are as well. How could we go from this state to implementing continuous integration with full (or at least close to full) automation of build and test? We have a pretty intense development cycle, and are not currently using agile, so switching to agile with CI in one move would be a very complicated and expensive investment. How can we take it slowly, and still moving constantly towards a CI environment?