![]() |
|
|
|
|
Change By:
|
Frank Lee
(13/Jun/14 7:09 AM)
|
|
Description:
|
Problem:
A job keeps triggering when it should not.
Background:
2 separate jobs are configured to be triggered on the same Github repository depending on branch that pushed to.
When pushing to the 1st branch, "origin/test/branch1", the 1st job is triggered. Good.
When pushing to the 2nd branch, "origin/test/branch2", the 2nd job triggers. Good.
But the 1st job is triggered again. Bad. There's only been 2 pushes.
The repository is very large, so the git clone takes a few minutes for both jobs.
The problem consistently occurs when pushing to the 1st branch, THEN immediately pushing to the 2nd branch. The 1st job is triggered and git cloning. And the 2nd job is triggered and queued. BUT another 1st job is triggered and queued.
Seems to happen when it's still downloading during the clone.
That extra triggered job is causing us grief, because it's used for deployments.
This is reproducible consistently with this script:
----------------------------
#!/bin/bash
pushd mydirectory
git checkout develop
echo ${1}d >> d.txt
git add .
git commit -m "${1}d"
git push
git checkout test/branch1
git pull --no-edit upstream develop
git push
git checkout test/branch2
git pull --no-edit upstream test/branch1
git push
popd
----------------------------
And run it as:
# ./script 1
# ./script 2
etc...
Jenkins v1.558
Git Client v1.9.0
Git plugin v2.2.1
GitHub API v1.44
Github OAuth v0.14
GitHub Pull Request Builder 1.12
GitHub plugin v1.8
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
