-
Bug
-
Resolution: Unresolved
-
Major
-
None
PS: Im not sure if it is only for Multibranch Pipelines, but thats my current workflow, and the only one Im aware of.
Setting Refspec on the Configuration level:
Making sure that the refspec is honored:
But still when the branch runs, tags are fetched, but not the declared refspec:
I believe this a regression, since this has worked for me in the past.
[JENKINS-72731] Refspec does not work for Multibranch Pipelines
Assignee | Original: Mark Waite [ markewaite ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Not A Defect [ 7 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Assignee | New: Mark Waite [ markewaite ] |
I place the refspec configuration inside the Jenkinsfile rather than placing it on the multibranch Pipeline definition in my test jobs. The refspec inside the Jenkinsfile works as expected. Here are some examples of that configuration:
I assume that "origin/develop" is a single branch on the remote repository. If it is a single branch, then I don't see how a multibranch Pipeline provides any benefit. It will find at most a single branch named "develop" and that single branch will result in a single job named "develop" in the multibranch Pipeline folder.
If "origin/develop" is not a single branch on the remote repository, then I believe you need a different syntax to match all branches that are beneath the "develop" folder. The syntax for all branches in the develop folder is