|
||||||||
|
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.
I can reproduce this easily now, is that, pushing --force to a PR that's being tested already in Jenkins.
A simple test is just have a dummy project, which just a build script that is a sleep 60.
Then create a PR, wait until jenkins runs the job to build it, while is at it, do a git rebase --force HEAD^ to the project and push --force to the PR branch and boom!
If configurations are really a problem or not needs to be confirmed still, I'll do that as soon as possible.