Thanks Jose Sa. I have a GitHub organization folder with a multibranch pipeline that is showing the issue consistently.
Your near term alternatives include:
- Use a multibranch project created separate from the GitHub organization folder
- Retain the second fetch globally so that the second fetch provides tags even though the first fetch incorrectly does not provide tags
- Define the organization folder so that it retrieves tags. That should then be used by the multibranch projects
It appears that a difference in tag retrieval configuration between the first and second fetch is not being detected by the code that removes the (potentially) redundant fetch.
Problem is also only visible on the initial creation of a workspace. Later updates of an existing workspace do not have the issue. Since most of us are moving to ephemeral agents, it will be more and more common that the job is always performing initial creation of a workspace.
I'm also able to consistently show the failure in a multibranch project that uses the GitHub provider and is configured to not fetch tags in the multibranch definition. My two cases that consistently pass are using the git provider and have tag fetching enabled. I suspect the issue is that the setting inside the job definition to fetch tags is being ignored or overridden on the first fetch and not ignored on the second fetch.