[JIRA] [ghprb] (JENKINS-18713) push --force loses build statuses

2013-07-17 Thread jagua...@gmail.com (JIRA)












































 
Iulian Dragos
 edited a comment on  JENKINS-18713


push --force loses build statuses
















I just noticed that this only happens when using GitHub notifications. If I go back to polling, things look good.



























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/groups/opt_out.




[JIRA] [ghprb] (JENKINS-18713) push --force loses build statuses

2013-07-17 Thread jagua...@gmail.com (JIRA)














































Iulian Dragos
 commented on  JENKINS-18713


push --force loses build statuses















I just notice that this only happens when using GitHub notifications. If I go back to polling, things look good.



























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/groups/opt_out.




[JIRA] [ghprb] (JENKINS-18713) push --force loses build statuses

2013-07-11 Thread jagua...@gmail.com (JIRA)














































Iulian Dragos
 created  JENKINS-18713


push --force loses build statuses















Issue Type:


Bug



Affects Versions:


current



Assignee:


Honza Brázdil



Components:


ghprb



Created:


11/Jul/13 3:15 PM



Description:


I force-pushed to my branch for which I had an open pull request. The plugin didn't pick up my change. When I asked `retest this please`, the build was triggered but no status was added to my commits. It looks like the old shas were used.

Here's the parameters I got:


sha1:origin/pr/464/merge
ghprbActualCommit: 285f72ae5b7b6c9460ccb6fc922789dba4cef2ad
ghprbPullId: 464
ghprbTargetBranch: master


The actual commit is the previous one (before my push --force). As a result, the pull request (and all its commits) has no build status.




Project:


Jenkins



Priority:


Major



Reporter:


Iulian Dragos

























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/groups/opt_out.