>> Is there some way for me to find out *why* Jenkins thought the default named
>> workspace was already in use? Our scripts make assumptions about the
>> workspace location and if Jenkins appends something ("@2") to the name of
>> the folder it won't work.
It's very strange that Jenkins thoug
I just upgraded Jenkins from 2.159 to 2.160, and then found that I could not
log on to the web interface.
Clicking "login" prompted me for my credentials as expected, and then returned
me to the Jenkins web page, but not logged in.
Clearing cookies and cache, and using a different browser, did n
To: Jenkins Users
Subject: Re: Logins (CAS plugin) not working after upgrading to 2.160 (security)
We documented this issue and a workaround at
https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+the+SECURITY-901+fix
> On 17. Jan 2019, at 16:32, matthew.web...@diamond.ac.uk wrote:
>
>> is there a plugin to limit the number of Jenkins jobs (more precisely
>> pipeline jobs) currently running on Jenkins in total (master+slaves)?
I don't think it quite does what you want, but you might want to take a look at
https://github.com/jenkinsci/throttle-concurrent-builds-plugin/blob/mas
We use freestyle jobs which allow concurrent builds. Sometime we have 10+
builds running at the same time, distributed across a number of agents. We use
the https://wiki.jenkins.io/display/JENKINS/Throttle+Concurrent+Builds+Plugin
as well.
Some of our agents are slower than others. Unfortunatel
We're using Jenkins v2.117 with the
https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger plugin.
We also use the https://wiki.jenkins.io/display/JENKINS/Role+Strategy+Plugin
plugin.
When I log in to Jenkins, I can see the "Query and Trigger Gerrit Patches" on
the left side of the screen.
Howe
>> When I log in to Jenkins, I can see the "Query and Trigger Gerrit Patches"
>> on the left side of the screen.
>> However, other people cannot see this useful option.
>> What permission do I need to set so that people can use the "Query and
>> Trigger Gerrit Patches" facility?
To answer my own
> Master/slave concept has been on Jenkins since the start, despite the
> cultural reinforcement of slavery-related terms.
> Maybe a JEP could follow the trend to more harmonious terms:
In Jenkins 2, slaves (also sometimes known as nodes), were renamed to agents.
--
This e-mail and any attac
You might want to wait for someone else to confirm this, but for us at least:
You’re correct, that the front page login is unrelated to the tokens.
We revoked all legacy tokens without problems. We had a couple of
infrastructure accounts using tokens, which we knew about (and set up new-style
tok
We recently upgraded Jenkins from 2.146 to 2.147 (which is the newest release
at the time of writing).
Since then, Jenkins has displayed a message in the WebUI:
"Because of a security vulnerability discovered earlier, we need to change the
encryption key used to protect secrets in your configura
that.
> Any scripting messing with this file could be a possible culprit.
>
> I recommend not executing this. I'm not sure whether the format of secrets we
> implemented ~2 years ago is still compatible with the re-keying.
>
> > On 19. Oct 2018, at 18:26, matthew.web...@d
11 matches
Mail list logo
