We have recently upgraded to Stash 3.2.4, which resulted in some odd behaviour with pull-requests.
I suspect the problem is a result of the rather radical changes to Pull Request handling.
The problem:
A new build of my Pull Request job is not triggered with a change in a Pull Request and is also not triggered, when pushing the 'Trigger build' button.
Steps to reproduce:
Create a Pull Request
Push the 'Trigger Build' button inside the PR
Observer the request to jenkins that is created.
Expected result:
The supplied url to jenkins should contain
the url to the repository
the stash-branch to represent the PR (refs/pull-requests/${PR-number}/from)
optionally the sha1 to represent the PR
Such a URL would cause my Pull Request job to run on the supplied change
Actual result:
The supplied url contains:
the url to the repository
the stash-branch this PR originates from
the sha1 of the last commit in the branch the PR originates from
This does not do anything, as i have no job building the originating branch
If i manually build the PR job in jenkins it will run just fine and publish the result to the pull request.
We have recently upgraded to Stash 3.2.4, which resulted in some odd behaviour with pull-requests. I suspect the problem is a result of the rather radical changes to Pull Request handling.
The problem: A new build of my Pull Request job is not triggered with a change in a Pull Request and is also not triggered, when pushing the 'Trigger build' button.
Steps to reproduce:
Expected result: The supplied url to jenkins should contain
Actual result: The supplied url contains:
If i manually build the PR job in jenkins it will run just fine and publish the result to the pull request.