Re: How does one fix this CSS issue in Jenkins?

[Kari Cowan]

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  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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/adb7f060-4412-424f-a810-d37f4cadc12fn%40googlegroups.com
> 
> .
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAE7w4hgwXP%3DKcfBdbi-88fDUAfOBX0g6FsyvqTJ08vpuzDUiwQ%40mail.gmail.com.

Re: How do you set java options for ssh agents

[Tim Black]

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 suspect CasC does nothing to detect agent
config changes and relaunch remote agent processes. Thus I have to reboot
them..

I should probably add my own Ansible task to relaunch agent processes..

On Mon, Sep 28, 2020, 04:08 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> I think this is  simply because the agent process survives the master
> restart (that is actually a feature) so if agent settings change, you need
> to disconnect and connect the agent (or otherwise restart the agent process
> to pick up the changes).
>
> timb...@gmail.com schrieb am Freitag, 25. September 2020 um 20:03:25
> UTC+2:
>
>> Thanks. I believe you were saying stop/start because you're using Docker
>> container. In your Docker example, stopping and restarting the Docker
>> container is analogous to rebooting (power cycling, or sudo rebooting) the
>> physical or virtual machine hosting the Jenkins service.
>>
>> In this thread I'm saying that restarting the Jenkins service (which
>> resides within a container or vm that is NOT being restarted/rebooted) IS
>> sufficient to apply MOST CasC settings, however, NOT the ssh agent
>> jvmOptions. It's not a blocking problem, bc I can get the desired effect by
>> rebooting master/controller and agent machines. But it's a mystery I'd like
>> to understand better, bc as I scale this cluster and rll out new
>> configuration changes to it, I'm going to need to understand these
>> mechanics.
>>
>> Would this be an appropriate thread for jenkins-developers group? Is
>> there another forum you could recommend to ask detailed questions about
>> JCasC? (I'm on the gitter channel but it's quite hit and miss due to the
>> format)
>>
>> On Friday, September 25, 2020 at 8:56:43 AM UTC-7 kuisat...@gmail.com
>> wrote:
>>
>>> Restart Jenkins using the CLI(
>>> https://www.jenkins.io/doc/book/managing/cli/) it is the same make it
>>> from the UI. When I said stop/start, I mean stop/start the Jankins
>>> daemon/service/Docker container/Whatever. The reason it is because IIRC
>>> JCasC runs on the start time of the Jenkins process, and also IIRC if you
>>> make changes on the JCasC config file and reload the configuration, or
>>> restart from UI the JCasC configuration is not recreated because the stage
>>> where it is run is not running on those restart ways. Probably someone with
>>> the deepest acknowledge of JCasC can add more context.
>>> It is easy to check, run a Jenkins Docker container configured with
>>> JCasC (e.g.
>>> https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-63703)
>>> then connect to the container and modify the JENKINS_HOME/jenkins.yaml file
>>> and restart from UI or CLI, the JCasC changes will not apply if you stop
>>> the Docker container and start it again the changes are applied.
>>>
>>> El vie., 25 sept. 2020 a las 17:33, Tim Black ()
>>> escribió:
>>>
 Thanks. What's the difference between "restart Jenkins from UI" and
 "stop the Jenkins instance and start it again"? In the latter, how are you
 implying that Jenkins gets stopped and restarted, through the CLI? Just
 trying to understand what you're saying - it sounds like you're implying
 CasC settings aren't applied when you restart jenkins through the GUI, but
 they are when you restart through the CLI..

 I don't think this explanation is relevant to my use case bc I *never* 
 restart
 jenkins through the GUI. In the workflow I outlined above, I am running an
 ansible playbook on my jenkins cluster, over and over, and each time if
 there is a config change, it restarts the jenkins service through the CLI
 using a jenkins admin credentials (using an active-directory user
 actually). This appears to *not *have the desired effect of applying
 the new agent jvmOptions upon next connection of the agent, whereas when I
 simply reboot the entire machines (master/controller and agents), the new
 jvmOptions are used in the SSHLauncher). Note that *I do not have this
 same problem with other CasC settings, only ssh agents.*

 On Friday, September 25, 2020 at 3:05:59 AM UTC-7 kuisat...@gmail.com
 wrote:

> ok, I think I know what happens, I saw it before using Docker and
> JCasC, if you make changes on the JCasC and restart Jenkins from UI the
> changes are not applied because JCasC is not executed on that restart, but
> if you stop the Jenkins instance and start it again the changes are 
> applied
> IIRC is how it works.
>
> El miércoles, 23 de septiembre de 2020 a las 23:37:18 UTC+2, Ivan
> Fernandez Calvo escribió:
>
>> I will configure a test environment with JCa

Re: How does one fix this CSS issue in Jenkins?

[Mark Waite]

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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/adb7f060-4412-424f-a810-d37f4cadc12fn%40googlegroups.com.