Minor I have a pipeline Job, which is checking out several svn repos.
When this job is run, the changeset reflects the changes. However, it sometimes gets called by a different job (very simple freestyle; we call it the trigger job). Whenever that happens, the changeset of the called job is entirely empty. (If there are changes in the repo where the Jenkinsfile of the called job resides, these changes are in the changeset, but not the changes of any repo the Jenkinsfile checks out.)
[JENKINS-73591] Changeset empty when pipeline Job is called by another Job
| Description |
Original:
I have a pipeline Job, which is checking out several svn repos.
When this job is run, the changeset reflects the changes. However, it sometimes gets called by a different job (very simple freestyle; we call it the trigger job). Whenever that happens, the changeset of the called job is entirely empty. (If there are changes in the repo where the pipeline Jenkinsfiles of the called job resides, these changes are in the changeset, but not the changes of any repo the Jenkinsfile checks out.) |
New:
I have a pipeline Job, which is checking out several svn repos.
When this job is run, the changeset reflects the changes. However, it sometimes gets called by a different job (very simple freestyle; we call it the trigger job). Whenever that happens, the changeset of the called job is entirely empty. (If there are changes in the repo where the Jenkinsfile of the called job resides, these changes are in the changeset, but not the changes of any repo the Jenkinsfile checks out.) |
Osaid
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
| Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |