I don't see a way to do that using hooks or polling. As far as I can tell, the git plugin assumes that a SHA1 only needs to be built once.
If the typical case is that you push the staging branch and staging and develop are the same SHA1, could you add a build step to one of the branches which runs the same job again with a parameter that is the value of the other branch? The build step would somehow need to be conditional so that you don't always run the job twice on every commit to either branch. Managing two jobs sounds simpler to me than trying to manage the subtle challenges hiding in that configuration running two different configurations from the same job. Mark Waite On Wed, Aug 27, 2014 at 8:31 AM, Nicolas Goy <nico...@goyman.com> wrote: > I have two branches, develop and staging. > > When I push changes to the develop branch, a build is triggered and this > works fine. > > Now, if I merge develop into staging and push the staging branch, jenkins > git plugin says there is no change because the commit id of the staging > branch matches the commit id of the develop branch. > > I'd am using the conditional plugin and I check for the branch name. I'd > like to have one test suite for the develop branch and a slightly different > suite for the staging branch. > > How can I do that without duplicating the project within jenkins? > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- 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. For more options, visit https://groups.google.com/d/optout.
