I think the git plugin sets GIT_BRANCH environment variable, so you could e.g.
write it to a .properties file and use parameterized trigger to pass it to
another build.
-- Sami
Allen Bierbaum kirjoitti 20.8.2012 kello 18.16:
> On Sun, Aug 19, 2012 at 1:11 PM, Sami Tikka wrote:
>> I think it
On Sun, Aug 19, 2012 at 1:11 PM, Sami Tikka wrote:
> I think it depends on how you have configured the two jobs. Jenkins does not
> carry any sort of hidden message about git branch from build to another build.
>
That was the key piece of information I needed. I think I need to use
the paramete
I think it depends on how you have configured the two jobs. Jenkins does not
carry any sort of hidden message about git branch from build to another build.
Maybe you could share the job configurations with the list? Could you put them
up on pastebin or gist for us to see? You can get the job con
in trigger of downstream is not building same
branch
I had the same thought but was hoping for something more concrete to
track down or fix.
Just to be clear then, if a build using git triggers a downstream
build using "Build other projects" as a post build action then the
downstream bu
I had the same thought but was hoping for something more concrete to
track down or fix.
Just to be clear then, if a build using git triggers a downstream
build using "Build other projects" as a post build action then the
downstream build should build the same branch as the upstream?
-Allen
On S
Maybe something has changed? Someone upgraded some Jenkins plugin or installed
a new one or changed something in the job configuration.
I happen to know if you install the Workspace Cleanup plugin and configure a
job to use it, it deletes the workspace and that somehow causes git plugin to
get
