![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Assignee:
|
Honza Brázdil
|
|
Components:
|
ghprb-plugin |
|
Created:
|
06/Feb/15 5:26 PM
|
|
Description:
|
After updating from version 1.16-5 to 1.16-8 early February, I noticed that pull request from GitHub were building master instead of the PR content.
Feel free to browse build history at Ehcache on cloudbees
See logs from last valid PR build:
The line git rev-parse origin/pr/277/merge^{commit} indicates that the PR was built.
Then all build after 477 look as follows (this one for example):
There are two git rev-parse lines but they both look at master instead of the PR. And you can see that what is checked out (954e6f0ffc324a384f4fae14bc9419a301020a3f) is different than what is announced at the top (c86d869f7fadf3e35e4ba23c08dae31dc57c8a3d).
I have downgraded the plugin back to version 1.16-5, and the latest build at this time is now a valid PR build once more.
|
|
Environment:
|
Cloudbees Jenkins: https://ehcache.ci.cloudbees.com
ghprb-plugin: 1.16-8
Git plugin 2.3.4
GitHub API plugin 1.59
GitHub plugin 1.10
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
git
github
pull_request
|
|
Priority:
|
Blocker
|
|
Reporter:
|
Louis Jacomet
|
|
|
|
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.