When testing out the pipeline/blueocean setup, it appears that it is very geared towards branches in git, rather than tags. Most git processes I know of, such as git flow, utilise tags for version numbering.
I'm using the blueocean docker to do the evaluation.
There are a couple of issues I have seen that I don't see any documentation to address:
Blueocean is geared towards branches instead of tags. I'm not sure what the workflow/process this was based on is, I couldn't really find out from the documentation. Git flow uses tags to build out releases, but does use branches for features, so it would only half work with blueocean. I would prefer it if tags were supported.
There is no way that I have found to use the declarative pipeline and only execute a build when a new tag is pushed. Contrasted with gitlab-ci, where you can easily filter out to only build on tags. In fact, with the declarative pipeline, there doesn't appear to be any way to skip builds based on any set criteria
For some reason, tags are stripped out of the SCM build step. Most CI tools I have used/tested do a full clone of the git repo down. I also make the assumption when writing build scripts that I will be in an environment as close as just being within the git repo itself. As this is not the case, I have to worry about 2 environments instead of one.
While I support having tags stripped out for users that don't want it, I don't believe this is a sensible default.
Probably an existing ticket, but you can't edit pipelines in blueocean, just adding a default style git repo, you get a nice error:
Which is caused by an error on the url: http://blueocean:8080/blue/rest/organizations/jenkins/pipelines/myrepo/scm/content?path=Jenkinsfile&branch=master