Hi Daniel,
I am looking for something better. The SHA1 and branch name displayed on
the job would be incorrect. Since I am looking at the source of the
git plugin I am moving this discussion to the developers mailing list.
Ivan
October, 21 at 6:16 Daniel Serodio wrote:
> You could add a shell script step and "git checkout ${BRANCH}" instead
> of relying on the Git plugin for this.
>
> Regards,
> Daniel Serodio
>
> On Monday, October 20, 2014 8:12:53 AM UTC-2, Ivan Kanis wrote:
>
> Hello,
>
> We are using a job with multiple git branches and it's working
> very
> well. I am agreeably surprised that it does multiple builds when
> two
> branches have changed with a push.
>
> However when we run the build manually we cannot specify which
> branch to
> build. It defaults to the last branch built which is not
> necessarily the
> one we want.
>
> How could we specify this? I can't think of anything.
>
> Ivan
>
> --
> We look at the present through a rear-view mirror. We march
> backwards
> into the future.
> -- Marshall McLuhan
>
>
>
--
We didn't pay the Internet bill and it's been cut off.
-- BOFH excuse #31
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
