The git plugin is able to work from either a detached head or a named local branch. Detached head is the default.
Making a named branch is one of the additional behaviors that can be added from the job definition. Mark Waite On Mar 30, 2014 7:14 AM, "dev123" <[email protected]> wrote: > Jenkins1.549 > Git plugin 1.5.0 > > I have a job in jenkins where I specify the following branch to build: > origin/myfeature. I also have another job that is configured to build > origin/master. > > Using strategy: Default > Last Built Revision: Revision 1966b44e903862343c98c46f4a94d5a603a9a58f > (origin/myfeature) > Fetching changes from 1 remote Git repository > Fetching upstream changes from origin > Commencing build of Revision 0643d142b4dfa95cbc77fd4cda11306302fd866c > (origin/myfeature) > Checking out Revision 0643d142b4dfa95cbc77fd4cda11306302fd866c > (origin/myfeature) > > But do I need to prefix my branchId with "origin"? It seems to me that the > get plugin always does: > > 1) Fetch latest changes > 2) Checkout the specified branch on origin > > It does not look like it stores local branches but instead builds from a > "Detached Head". Is that correct? > > > -- > 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. > -- 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.
