Most helpful Answer There is a plugin called SCM Sync configuration plugin. Original Answer Have a look at my answer to a similar question. The basic idea is to use the filesystem-scm-plugin to detect changes to the xml-files. Your second part would be committing the changes to SVN. EDIT: If you find a way to … Read more
Update: Jenkins is the most up to date version of Hudson. Everyone should be using Jenkins now. I’ll be updating the links accordingly. Hudson is free and extremely easy to configure and will easily run on a VM. Partly from an old post of mine: We use it to Deploy Windows services Deploy web services … Read more
You can use Parameterized Trigger Plugin which will let you pass parameters from one task to another. You need also add this parameter you passed from upstream in downstream.
I have done it the following way. I am not sure if that is the right way, but it seems to be working. You need to get the Jenkins Groovy plugin installed and do the following script. import hudson.model.*; import hudson.util.*; import hudson.scm.*; import hudson.plugins.accurev.* def thr = Thread.currentThread(); def build = thr?.executable; def changeSet= … Read more
Perhaps GitHub’s support for deploy keys is what you’re looking for? To quote that page: When should I use a deploy key? Simple, when you have a server that needs pull access to a single private repo. This key is attached directly to the repository instead of to a personal user account. If that’s what … Read more
First things first, hover the mouse over the grey area below. Not part of the answer, but absolutely has to be said: If you have a shell script that does “checkout, build, deploy” all by itself, then why are you using Jenkins? You are foregoing all the features of Jenkins that make it what it … Read more
Your understanding is correct, an artifact in the Jenkins sense is the result of a build – the intended output of the build process. A common convention is to put the result of a build into a build, target or bin directory. The Jenkins archiver can use globs (target/*.jar) to easily pick up the right … Read more
I have found a solution giving me access to the regular keychains for my Jenkins user. Find this plist: /Library/LaunchDaemons/org.jenkins-ci.plist then: Add the UserName element with a value of jenkins. Add a SessionCreate element with a value true to the plist file. This gives access to the normal keychains for the user you specified in … Read more
The OP Josh Smith managed to sort it out: I’d actually needed to add the SSH key from /var/lib/hudson/.ssh/id_rsa.pub for the user (me) into the Gerrit GUI. Then from there it worked like a charm. The username must be the username in Gerrit (the admin account). My original advice is below: What is the user … Read more
I did a similar thing a few months ago, and it turned out this simple format was enough for Hudson to accept it as a test protocol: <testsuite tests=”3″> <testcase classname=”foo1″ name=”ASuccessfulTest”/> <testcase classname=”foo2″ name=”AnotherSuccessfulTest”/> <testcase classname=”foo3″ name=”AFailingTest”> <failure type=”NotEnoughFoo”> details about failure </failure> </testcase> </testsuite> This question has answers with more details: Spec. for … Read more