![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Attachments:
|
jenkins.log |
|
Components:
|
git-client-plugin, github-api-plugin |
|
Created:
|
03/Feb/15 8:37 AM
|
|
Description:
|
We are trying to analyse this situation for quite some time now - but we honestly have no clue.
This situation is sometimes triggered because of force pushes to branches.
Sometimes it happens because of other branches being merged into master.
A workaround is to create a new branch and a new pull request. As soon as the job is executed on this new pull request (which holds the identical commits) the job executes just fine.
Soometimes is also helps to not touch the branch for days and simply retrigger the execution.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Thomas Müller
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
