If anyone's interested. Updating my jenkins instance on the server fixed the css issue I was on about last week. If anything, this encouraged me to install it on my laptop so I could muck about with what I wanted without risking breaking somethng for my team - so that's always good ;-)
On Sat, Oct 3, 2020 at 5:54 PM Kari Cowan <[email protected]> wrote: > 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), and it worked fine. The log pops up in front and you can > read it. > > So going that route, I can't replicate the bug I found on my team system. > It's running Jenkins 2.235.5, though I see that Jenkins 2.249.1 is > available (that's the version my docker v is running). I should probably > update to that version first and see if that fixes it. > > > > On Sat, Oct 3, 2020 at 1:32 PM Mark Waite <[email protected]> > wrote: > >> 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/plugins/pipeline-stage-view/pipeline-stage-view/2.16-rc318.6592e15c43fc/pipeline-stage-view-2.16-rc318.6592e15c43fc.hpi >> and >> https://ci.jenkins.io/job/Plugins/job/pipeline-stage-view-plugin/job/master/lastSuccessfulBuild/artifact/org/jenkins-ci/plugins/pipeline-stage-view/pipeline-rest-api/2.16-rc318.6592e15c43fc/pipeline-rest-api-2.16-rc318.6592e15c43fc.hpi >> . >> >> The bug report that tracks it is at >> https://issues.jenkins-ci.org/browse/JENKINS-63556 >> >> Mark Waite >> >> On Saturday, October 3, 2020 at 1:59:26 PM UTC-6 Kari Atari wrote: >> >>> When viewing logs from a pipeline job, the popup window is transparent >>> and underneath the header bar. I'm pretty sure I could hack the CSS to >>> make it right, but think next time I upgrade versions I could lose that >>> change. Any way to deal with it that I am not aware of? >>> >>> [image: Screen Shot 2020-10-03 at 12.52.18 PM.png] >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/adb7f060-4412-424f-a810-d37f4cadc12fn%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/adb7f060-4412-424f-a810-d37f4cadc12fn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAE7w4hhVmDmBoYfAmnR5HqbbB64t0BGk8H9yTOZ4r5JwiFKUzg%40mail.gmail.com.
