Checkout configuration in declarative multi branch pipeline

Using Jenkins Ask a question
1

We have a multibranch declarative pipeline, using gitea plugin as the SCM.

When a new node is allocated, Jenkins does a complex series of git commands to create the workspace. This includes git fetch --no-tags, but we’d really like tags on the repo (so we can properly version artefacts with the release tag, if it is present).

Current workaround is to put an explicit git fetch --tags in the relevant steps.

Is there a better way to modify the default checkout behaviour for a declarative pipeline?

Jenkins setup: (old and needs updating, I know)
Jenkins 2.426.3
Gitea 1.4.7
Git 4.7.0
Branch 2.1178

2

If you are using a Gitea Organization Folder, then you can add the additional clone behavior that will fetch tags.

My screen looks like this:

screenshot
screenshot732×2065 55.5 KB

3

Thanks Mark, that has solved it for us.