Re: Jenkins CI Windows Attempting Failsafe Tests

This happens quite often and indicates an infrastructure problem. Normally it disappears after a while... > Am 18.04.2019 um 22:55 schrieb 'Craig Barber' via Jenkins Developers > : > > We're running into an issue where the Jenkins CI is trying to run failsafe > tests and failing: > https://ci

Jenkins CI Windows Attempting Failsafe Tests

We're running into an issue where the Jenkins CI is trying to run failsafe tests and failing: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgoogle-kubernetes-engine-plugin/detail/PR-50/1/pipeline Anyone have an idea what might be causing this? -- Craig Barber Software Engineer Cloud

Re: Plugin idea: publish the analysis result (reading from the jxlint xml format)

> Am 18.04.2019 um 08:41 schrieb Jérémie Bresson : > > I know this thread is old, but I took time to work again on this idea. > > Since then, the code was reorganized into: > * Jenkins' warnings next generation plug-in > . > * Analysis Parsers L

Re: Migrate a token stored in plain text to one that uses Secret

> The plain text tokens are already potentially compromised and need to > be regenerated and stored encrypted anyways. This is specific to each > plugin on how to go about regenerating keys and whatnot. > Yes, when you put it like that it makes more sense not to worry about migration. Thank you a

Re: Migrate a token stored in plain text to one that uses Secret

On Thu, Apr 18, 2019 at 8:57 AM Mez Pahlan wrote: > I could ignore it, for sure. But that was the reason I received a security > bug that I'm looking to fix. That the tokens in my plugin were being stored > in plain text. If I leave them in plain text what am I actually fixing? I'm > fixing for

Re: Migrate a token stored in plain text to one that uses Secret

> On 18. Apr 2019, at 15:50, Jesse Glick wrote: > > On Thu, Apr 18, 2019 at 2:53 AM Mez Pahlan wrote: >> What's the best way to migrate those over without asking the user to go into >> each of their jobs updating it? > > There is not any good way that I know of. I would just ignore it. Thi

Re: Migrate a token stored in plain text to one that uses Secret

> > There is not any good way that I know of. I would just ignore it. > I could ignore it, for sure. But that was the reason I received a security bug that I'm looking to fix. That the tokens in my plugin were being stored in plain text. If I leave them in plain text what am I actually fixing? I'm

Re: Migrate a token stored in plain text to one that uses Secret

On Thu, Apr 18, 2019 at 2:53 AM Mez Pahlan wrote: > What's the best way to migrate those over without asking the user to go into > each of their jobs updating it? There is not any good way that I know of. I would just ignore it. -- You received this message because you are subscribed to the Go

Re: Any idea what could cause Jenkins console output to be mixed like this in a pipeline job?

On Wed, Apr 17, 2019 at 3:53 PM Martin Weber wrote: > Could this cause JENKINS-55215? Unlikely. That is just using the normal `ProcStarter.stdout(TaskListener)` which should not need any special `flush` call, either before or after https://github.com/jenkinsci/jenkins/pull/3961 -- You received

Re: Migrate a token stored in plain text to one that uses Secret

Maybe you can try and report the job to the old data monitor somehow? That way an admin can batch save the affected jobs, I think :) /B Den tors 18 apr. 2019 kl 12:44 skrev Slide : > Did you mark the old field as transient in your code? If you mark it as > transient and have a readResolve, it sh

Re: Migrate a token stored in plain text to one that uses Secret

Did you mark the old field as transient in your code? If you mark it as transient and have a readResolve, it shouldn't get resaved once the upgrade happens. On Wed, Apr 17, 2019 at 11:53 PM Mez Pahlan wrote: > Morning > > I'm trying to migrate a plugin that used to use plain text for handling >