Re: Git based builds; one commit at a time

Or just use Gerrit and the Gerrit trigger plugin :-) On 31 December 2014 14:59:28 GMT+00:00, Mark Waite wrote: >If that's the case, you should probably consider the pre-tested commit >plugin that is part of the Cloudbees commercial offering. > >On Wed, Dec 31, 2014 at 7:48 AM, Steve K > >wrote:

Re: Git based builds; one commit at a time

Am 31.12.2014 um 15:59 schrieb Mark Waite: > If that's the case, you should probably consider the pre-tested commit > plugin that is part of the Cloudbees commercial offering. Or use a branch based development approach and some lines of script code to let Jenkins do the pull - merge - build - tes

Re: Git based builds; one commit at a time

If that's the case, you should probably consider the pre-tested commit plugin that is part of the Cloudbees commercial offering. On Wed, Dec 31, 2014 at 7:48 AM, Steve K wrote: > Jason, Yes. True. Development wants to ensure no commits are received > (added to the repo) unless they pass all the

Re: Git based builds; one commit at a time

Jason, Yes. True. Development wants to ensure no commits are received (added to the repo) unless they pass all the tests -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an

RE: Git based builds; one commit at a time

> -Original Message- > From: Rob Mandeville > Sent: Wednesday, December 31, 2014 8:57 > [reformatted to make sense...] >> From: Steve K >> Sent: Tuesday, December 30, 2014 3:21 PM >> >> Let's say that, since my most recent build, there have been >> three (3) new commits. >> Rather than h

Re: Git based builds; one commit at a time

ia HTTP to the job’s /api/xml page. > > 2. Get the history of the repository or branch > > 3. Find all the commits done after the last commit built > > 4. In order, launch the runner for each of those commits. > > > > --Rob > > > >

RE: Git based builds; one commit at a time

ps.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Steve K Sent: Tuesday, December 30, 2014 3:21 PM To: jenkinsci-users@googlegroups.com Subject: Git based builds; one commit at a time Let's say that, since my most recent build, there have been three (3) new commits. Rather than having one

Re: Git based builds; one commit at a time

Am 30.12.2014 um 21:21 schrieb Steve K: > Let's say that, since my most recent build, there have been three (3) > new commits. > Rather than having one build that includes all three commits, I would > like to have three separate builds; one for each of the three in sequence. > > Is anyone doing so

Git based builds; one commit at a time

Let's say that, since my most recent build, there have been three (3) new commits. Rather than having one build that includes all three commits, I would like to have three separate builds; one for each of the three in sequence. Is anyone doing something like that? If so, how are you doing it?