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 something like that? If so, how are you doing it?
Not exactly something like that, but similar, I think. We develop
everything on change branches, where each branch is directly related to
one ticket in our tracking system. Jenkins is our gatekeeper for merging
those branches back to master (or the maintenance branch for a specific
release). So we use some scripting in our Jenkins jobs to clone/pull the
repo, merge one branch (given as parameter), run build and tests and
commit and push the result only if everything was OK. In case of failure
in any of these steps, the developer is informed by email and the merge
result is thrown away.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 1596666 (Ansage) 1149
*Email*: d...@recommind.com <mailto:d...@recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
--
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 email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54A399F4.7020707%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
