Question

I am new to jenkins and maybe do not understand the CI-topic yet completly. Considering my research i found that if i do CI, i will always have stable build. Now this somehow confuses me, since i did not found anything about it in jenkins. My understanding of this is, that i have a repo. Jenkins is based on this repo, after every commit my project gets checked out by jenkins and will be build. But what if a commit actually breaks the build? This would mean my repo is broken aswell. Now i am searching for a way to solve this Problem. My basic idea for this atm is, that i have 2 repos. (i am using subversion)

1. Repo: This one gets all the commits from the developers. Jenkins builds the project based on this one.

2. Repo: Whenever the project gets build successful the commit gos into this Repo. I am not sure how to do this part, since i dont find anything related to this in my post-build steps in my project configuration in jenkins.

Have you an idea on how i could realize this configuration?

Was it helpful?

Solution

Jenkins does not have any built-in support for a "pre-tested commit", which is what it seems like you are looking for. See https://wiki.jenkins-ci.org/display/JENKINS/Designing+pre-tested+commit and https://issues.jenkins-ci.org/browse/JENKINS-1682. If you were using git as your version control system, it looks like there has been some effort there (see http://jenkins-ci.org/content/pre-tested-commits-git).

If you are looking for a system that does this out of the box, you might want to check out TeamCity and its "pre-tested commit" feature. This is not a free product, however.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top