Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using same string for branch and tag fails. #337

Open
moshavnik opened this issue Jun 21, 2023 · 1 comment
Open

using same string for branch and tag fails. #337

moshavnik opened this issue Jun 21, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@moshavnik
Copy link

moshavnik commented Jun 21, 2023

Jenkins and plugins versions report

Environment
Paste the output here

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

  1. create a repo in gitlab.
  2. 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.
  3. create a branch called "some_version".
  4. check that jenkins "sees" the branch and runs it's jenkinsfile.
  5. 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...

@moshavnik moshavnik added the bug Something isn't working label Jun 21, 2023
@rhit-gawronja
Copy link
Contributor

I have been looking into this issue for a while I was wondering if you are still running into this problem on current versions of Jenkins

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants