I started to do that. But first, you reminded me to check that plugin to
ensure it was up to date. It wasn't. But updating it didn't fix the
issue. Rather than monkey with my team jenkins I loaded up a docker run
jenkins locally - and installed the plugin from plugin manager (not the
pre-release
Bjorn I like that explanation. If this behaviour is "as designed" then I
just need to adjust my expectations.
I suspect that my Ansible playbooks are not relaunching the agent processes
when changes happen. The agent options are specified through the JCasC yaml
in the master/controller, and I susp
You could install a pre-release version of the pipeline stage view plugin
and help with the testing to confirm that the pre-release build resolves
the issue.
Build is
at
https://ci.jenkins.io/job/Plugins/job/pipeline-stage-view-plugin/job/master/lastSuccessfulBuild/artifact/org/jenkins-ci/plug
