I suggest to use the pipeline-graph-view
Looks nice, but doesn’t replace the stage view right? you have to go into the job itself first.
Either way, you’ve been a huge help and I’m slowly getting closer to replicating this old matrix job!
One quick question about parameters; do i need to define them in the jenkinsfile as well as in the job ui? if i add options to the choices param in the ui, my jenkinsfile script does not get updated with the other values, and if i remove the UI choice parameter, the build page doesnt show it at all
There’s a global option to show the pipeline-graph on a job pages (though just in a condensed view).
It’s not a 100% replacement but I personally prefer it over the stage view.
You should maintain parameters either in the UI or in the Jenkinsfile.
Parameters you define in your Jenkinsfile will become active only after running the pipeline once and then they are also visible in the UI. So if you add a parameter in the Jenkinsfile on the first run after adding the new parameter is not yet available.
Changes done via the UI are overwritten when you have parameters in the Jenkinsfile. And the UI is not able to modify the Jenkinsfile, how should it do so when the file is in a repository.
Sorry, I’m writing the jenkinsfile code in the UI, its not in a repo 
The issue I am having with the git paramter in the pipeline script is i can’t see tags, only branches.
gitParameter branchFilter: 'origin/(.*)', tagFilter: 'origin/(*)', defaultValue: 'develop', quickFilterEnabled: true, sortMode: 'DESCENDING_SMART', name: 'BRANCH', type: 'PT_BRANCH'
ive never had to use branch filters before, but i need to here for some reason, otherwise it tried to checkout origin/origin/develop instead of origin/develop. and yea, no tags shown at all
correct syntax here?
tagFilter: 'origin/(*)'
is this a regex then maybe you need
tagFilter: 'origin/(.*)'
No dice 
Tried just * as well, no luck
EDIT - fixed it, needed PT_BRANCH to be PT_BRANCH_TAG
1 Like