You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
controller - centos 6.4
agent - irrelevant (issue is related to plugin implementation on controller)
Reproduction steps
create a repo in gitlab.
create a multibranch pipeline on jenkins, pointing to the repo from step 1. configure the job to "see" all branches and all tags, and run the Jenkinsfile in the root folder.
create a branch called "some_version".
check that jenkins "sees" the branch and runs it's jenkinsfile.
create a tag called "some_version".
Expected Results
the tag should appear under tags in the job created before, and should run just like any other tag.
Actual Results
the job fails to "see" the tag, and nothing happens.
Anything else?
looking in the file system on the controller, I see that both branches and tag are created as folders under the job itself. I guess that's why using the same string for both tags and branch doesn't work.
suggestion - add another level of separation in the folders (branches/tags/merge_requests) and it will solve it...
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
controller - centos 6.4
agent - irrelevant (issue is related to plugin implementation on controller)
Reproduction steps
Expected Results
the tag should appear under tags in the job created before, and should run just like any other tag.
Actual Results
the job fails to "see" the tag, and nothing happens.
Anything else?
looking in the file system on the controller, I see that both branches and tag are created as folders under the job itself. I guess that's why using the same string for both tags and branch doesn't work.
suggestion - add another level of separation in the folders (branches/tags/merge_requests) and it will solve it...
The text was updated successfully, but these errors were encountered: