Re: In jenkins test harness (only) node() {} commands crash the executor

[Jesse Glick]

On Wed, Jul 15, 2020 at 4:25 PM Michael Carter
 wrote:
> if I do an exclude on jenkins-core:jar and pipeline-model-definition it goes 
> away... well all versions of gauva go away.

Try excluding only from `pipeline-model-definition`.

Without seeing your POM it is hard to help here, this is all just
general advice.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0rhqHL4BneDQV4YPp5vDvjZ%3DgeYePg7UhC4G2bKSZx9Q%40mail.gmail.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

So my ignorance might be showing but I think I tracked down where the 
27.1-jre is coming from as if I do an exclude on jenkins-core:jar and 
pipeline-model-definition it goes away... well all versions of gauva go 
away.

I'm guessing it's part of this?

  2.235.1
  bom-2.235.x

  
io.jenkins.tools.bom
${jenkins.bom}
${jenkins.bomver}
import
pom
  




On Wednesday, July 15, 2020 at 4:09:23 PM UTC-4, Michael Carter wrote:
>
> jenkins-core:jar appears to be the one... 
>
> On Wednesday, July 15, 2020 at 3:00:23 PM UTC-4, Jesse Glick wrote:
>>
>> On Wed, Jul 15, 2020 at 2:09 PM Michael Carter 
>>  wrote: 
>> > ... and that did the trick: 
>> > 
>> >  
>> >   com.google.guava 
>> >   guava 
>> >   11.0.1 
>> >   test 
>> >  
>>
>> Not recommended. Better to find out which other dependency was pulling 
>> it a newer version of Guava and add an `` to suppress that. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ab24f231-539c-492c-9de7-df1a044d0d6bo%40googlegroups.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

jenkins-core:jar appears to be the one... 

On Wednesday, July 15, 2020 at 3:00:23 PM UTC-4, Jesse Glick wrote:
>
> On Wed, Jul 15, 2020 at 2:09 PM Michael Carter 
> > wrote: 
> > ... and that did the trick: 
> > 
> >  
> >   com.google.guava 
> >   guava 
> >   11.0.1 
> >   test 
> >  
>
> Not recommended. Better to find out which other dependency was pulling 
> it a newer version of Guava and add an `` to suppress that. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/af72e673-8f91-4f7b-9f7e-288f7bbec467o%40googlegroups.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Jesse Glick]

On Wed, Jul 15, 2020 at 2:09 PM Michael Carter
 wrote:
> ... and that did the trick:
>
> 
>   com.google.guava
>   guava
>   11.0.1
>   test
> 

Not recommended. Better to find out which other dependency was pulling
it a newer version of Guava and add an `` to suppress that.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1Jd6dp0MfL%3Dogiv0CJgzokhgfb0iXsXutrG9MqoP9YJg%40mail.gmail.com.

Re: JENKINS-48900 - Show "Full Name" on Assign Roles page

[Jesse Glick]

On Wed, Jul 15, 2020 at 1:49 PM Oleg Nenashev  wrote:
> Passing true would create a user account if it is missing.

Does not _save_ a user account, merely ensures that a `User` object is
created in memory if it were not already on disk, which it very well
might not be. The Javadoc is perhaps misleading.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr38avQDyWpFPdPkQDs2u_HRn4V-gGTKEPA2mAtA6NG2qg%40mail.gmail.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

... and that did the trick:


  com.google.guava
  guava
  11.0.1
  test



Output:
  62.511 [jobname-PipelineManualFailTest #1] [Pipeline] node
  62.763 [jobname-PipelineManualFailTest #1] Running on Jenkins in 
workspace/jobname
  62.964 [jobname-PipelineManualFailTest #1] [Pipeline] {
  63.568 [jobname-PipelineManualFailTest #1] [Pipeline] stage
  63.668 [jobname-PipelineManualFailTest #1] [Pipeline] { (Example Build)
  64.121 [jobname-PipelineManualFailTest #1] [Pipeline] sh


Guess that's what had me all turned around when I saw the guava jar coming 
from the jenkins-core I just assumed it was the correct one I should be 
using.

Thanks for all the help everyone!

On Wednesday, July 15, 2020 at 2:05:15 PM UTC-4, Michael Carter wrote:
>
> +- org.jenkins-ci.main:jenkins-core:jar:2.235.1:provided
> |  +- com.google.guava:guava:jar:27.1-jre:provided
>
> Guess that's my problem... somehow when I upgraded the pom.xml to pull the 
> 2.235.1/2.222.4 it must have broke then.
>
> At least this gives me a place to start looking.
>
> On Wednesday, July 15, 2020 at 1:42:56 PM UTC-4, Jesse Glick wrote:
>>
>> On Wed, Jul 15, 2020 at 9:17 AM Michael Carter 
>>  wrote: 
>> > so it can pick up version 27.1-jre of guava from the war. 
>>
>> From `jenkins.war`? As mentioned, that bundles 11, not 27. Keep 
>> editing `pom.xml` until 
>>
>> $ mvn dependency:tree | fgrep guava 
>> [INFO] |  +- com.google.guava:guava:jar:11.0.1:provided 
>>
>> > problem is backtracking what I added from it last working is near 
>> impossible at this point. 
>>
>> git bisect 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c2bc8121-ae41-404c-98f0-3c4f67171877o%40googlegroups.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

+- org.jenkins-ci.main:jenkins-core:jar:2.235.1:provided
|  +- com.google.guava:guava:jar:27.1-jre:provided

Guess that's my problem... somehow when I upgraded the pom.xml to pull the 
2.235.1/2.222.4 it must have broke then.

At least this gives me a place to start looking.

On Wednesday, July 15, 2020 at 1:42:56 PM UTC-4, Jesse Glick wrote:
>
> On Wed, Jul 15, 2020 at 9:17 AM Michael Carter 
> > wrote: 
> > so it can pick up version 27.1-jre of guava from the war. 
>
> From `jenkins.war`? As mentioned, that bundles 11, not 27. Keep 
> editing `pom.xml` until 
>
> $ mvn dependency:tree | fgrep guava 
> [INFO] |  +- com.google.guava:guava:jar:11.0.1:provided 
>
> > problem is backtracking what I added from it last working is near 
> impossible at this point. 
>
> git bisect 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a3f4739f-f9a1-40ed-bc5b-903a14c2beaao%40googlegroups.com.

Re: JENKINS-48900 - Show "Full Name" on Assign Roles page

[Oleg Nenashev]

Passing true would create a user account if it is missing. I do not think
it is a good idea for Role Strategy UI which already supports missing SIDs.

On Wed, Jul 15, 2020, 19:40 Jesse Glick  wrote:

> On Wed, Jul 15, 2020 at 11:02 AM Oleg Nenashev 
> wrote:
> > hudson.model.user.getById(String id, false).getFullName() would be the
> best approach.
>
> Rather pass true.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/fQ8aOxAIwPw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1MLXgyrqCVTYViF47k%2BPjarPmeBYCQM9L%3DydXT3PZ-cg%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDmAM96rBa8zJJisu6xvN_%3DQwB3WUUcmnO066JHjJW6DQ%40mail.gmail.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Jesse Glick]

On Wed, Jul 15, 2020 at 9:17 AM Michael Carter
 wrote:
> so it can pick up version 27.1-jre of guava from the war.

>From `jenkins.war`? As mentioned, that bundles 11, not 27. Keep
editing `pom.xml` until

$ mvn dependency:tree | fgrep guava
[INFO] |  +- com.google.guava:guava:jar:11.0.1:provided

> problem is backtracking what I added from it last working is near impossible 
> at this point.

git bisect

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0yGuc%2ByC2oCe1Z_HOd9tj0gnx16866dUXwX2YLwNFynA%40mail.gmail.com.

Re: JENKINS-48900 - Show "Full Name" on Assign Roles page

[Jesse Glick]

On Wed, Jul 15, 2020 at 11:02 AM Oleg Nenashev  wrote:
> hudson.model.user.getById(String id, false).getFullName() would be the best 
> approach.

Rather pass true.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1MLXgyrqCVTYViF47k%2BPjarPmeBYCQM9L%3DydXT3PZ-cg%40mail.gmail.com.

Jenkins Governance Meeting on Jul 15, 2020

[Oleg Nenashev]

Hi all,

In a few hours we will have a regular Jenkins Governance meeting update.
Current agenda is provided below, we will do the meeting in Zoom:
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09. If you
would like to add any topic for a discussion, please suggest it in this
Google Doc

.


   -

   News!
   -

  New Code of Conduct is published:
  https://www.jenkins.io/project/conduct/
  -

  // Other news?
  -

   Terminology updates (Alex)
   -

  https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8
  -

  Vote: Selecting 10 options for voting
  -

   Jenkins CDF graduation status report (Oleg)
   -


  
https://groups.google.com/forum/#!msg/jenkinsci-dev/I3sUP2SB2JI/LDS99sOtBQAJ
  -

  Multiple updates in user and maintainer documentation: Weekly release
  documentation, list of adopters, GitHub Landing, etc.
  -

  Official request was submitted to CDF TOC, added to the TOC meeting
  agenda on Jul 21
  -

   Core Infrastructure Initiative updates (Oleg)
   -


  
https://groups.google.com/forum/#!msg/jenkinsci-dev/n1qH1K5_td0/a3SoeMGzBQAJ
  -

   Downloads Page rework (Oleg)
   -

  Approving the page update:
  https://github.com/jenkins-infra/jenkins.io/pull/3517
  -

   Roadmap review
   -

  https://groups.google.com/forum/#!topic/jenkinsci-dev/Ez7nZxlxSWk
  -

  https://www.jenkins.io/project/roadmap/
  -

  Contributor meetup on Jul 10
  -

 Video recording: https://www.youtube.com/watch?v=ldWBY5BdQ5I
 -

 Slides: https://bit.ly/jenkins-meetup-roadmap
 -

  Pending/Recent updates
  -

 https://github.com/jenkinsci/jep/pull/293
 -


 
https://github.com/jenkins-infra/jenkins.io/pulls?q=is%3Apr+is%3Aopen+label%3Aroadmap
 -

  VOTE: Ready to publish?


Best regards,
Oleg Nenashev

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBN-kB8hpO9Vcv%2B7d1_i2YhsNCZzicMfnHkoVCbW2Y6Mw%40mail.gmail.com.

Re: JENKINS-48900 - Show "Full Name" on Assign Roles page

[Oleg Nenashev]

Hi,

hudson.model.user.getById(String id, false).getFullName() would be the best 
approach.
It uses direct access to user profiles inside Jenkins. 
https://javadoc.jenkins-ci.org/hudson/model/User.html

Best regards,
Oleg

On Tuesday, July 14, 2020 at 2:21:12 PM UTC+2, Tidhar Klein Orbach wrote:
>
> Hi
>
> I looked on https://issues.jenkins-ci.org/browse/JENKINS-48900 and the 
> relevant code in role strategy plugin.
>
> I have found that RoleMap 
> 
>  
> uses org.acegisecurity.userdetails.UserDetails to get the user details.
> I see that UserDetails interface has getUserName() which is used for the 
> "sid" in the role-strategy-plugin. But there is no getDisaplyName  in the 
> interface.
> It does exist  in some of its implemented classes (for example 
> ActiveDirectoryUserDetail)
>
> any suggestions how to get the full name if exists?
>
> thanks,
> Tidhar
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/96aeb71a-c61a-4d8c-b977-d0c11e601634o%40googlegroups.com.

Re: Terminology Updates

[Robert Sandell]

Good suggestions overall so far, so I can't really contribute to more
suggestions.

Just that Blocklist reminds me too much of Blockchain, so I want to add my
veto to that term :)

/B

Den fre 10 juli 2020 kl 20:31 skrev 'Martin Schmude' via Jenkins Developers
:

> My proposals for "master":
>
>
>- central
>- main
>
> Besides this I'm find with "Jenkins server" or simply "server".
>
> James Nord schrieb am Dienstag, 30. Juni 2020 um 22:06:29 UTC+2:
>
>> how about monolith 樂 for the 'master'
>>
>> it may be modular in terms of plugins and architecture but it's not micro
>> services.
>> whilst some parts (fingerprint storage, artifact storage) are pluggable
>> we still have the one big thing.
>>
>> other equally bizarre / useful suggestions include:
>>
>> * comptroller
>> * orchestrator (may have already been suggested apologies if it has)
>> * sneer (it's the collective noun for butlers) it would be good if used
>> for the master node to disuade stop people using it
>> * trustee
>> * 'legacy_unsafe' (for the master node/executor label)
>> * "M" (as in James bond, head of all the agents)
>> * case officer (handles agents)
>> * director (tells the agents what to do)
>> * "C" the head of MI6 (not "M" as the bond movie make you believe)
>>
>>
>> /James
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/9c289226-7882-4c9d-a816-6e813ef9c7b4n%40googlegroups.com
> 
> .
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.

E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0RDS5vUFbxuZ0dX0nmyHNPa_oi3x79D5vEtL99CEo2dg%40mail.gmail.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

Tried excluding the 27.1-jre version out of one of the apis I'm using so it 
can pick up version 27.1-jre of guava from the war.   Didn't work.

Tried adding directly:


  com.google.guava
  guava
  27.1-jre
  test



Didn't work either.   I think the thread is crashing.  Any way to turn on 
more debugging?   Doing -X on maven doesn't put the jenkins harness into 
debug mode or anything.

As for did the test stop working without code change.   Not to that test 
but I as doing a lot of work in other areas before re-testing pipeline so 
probably something I did... problem is backtracking what I added from it 
last working is near impossible at this point.

On Wednesday, July 15, 2020 at 8:13:55 AM UTC-4, Jesse Glick wrote:
>
> On Wed, Jul 15, 2020 at 7:42 AM Michael Carter 
> > wrote: 
> > java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>  
>
> >  at 
> org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(Futures.java:90)
>  
>
> >  … 
> > 
> > Not sure what I did to cause the problem 
>
> Somehow pulled in an incompatible version of `guava`. Jenkins bundles 
> 11.x, and without a lot of advanced acrobatics¹ you cannot override 
> this. If your plugin bundles some third-party libraries, they may be 
> depending on a newer version of Guava and Maven picks that version for 
> tests, breaking everything. Check 
>
> mvn dependency:tree 
>
> and use an `` as necessary. Unless the third-party library 
> actually _requires_ newer Guava features, in which case you have 
> problems. 
>
>
> Also, did your tests stop working with no code changes? If `master` 
> was blue/green until now, check whether your `Jenkinsfile` is using, 
> say, 
>
> buildPlugin(configurations: recommendedConfigurations()) 
>
> which is nondeterministic. If tests broke inside a PR (I would 
> recommend a PR for all nontrivial changes, even if you are a sole 
> maintainer, just for trackability and CI), link to that from any post 
> to the mailing list. 
>
>
> ¹Read: 
> https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/#pluginfirstclassloader-and-its-discontents
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/67873b52-020b-4d56-b3c7-17522c1a57b8o%40googlegroups.com.

Re: In jenkins test harness (only) node() {} commands crash the executor

[Jesse Glick]

On Wed, Jul 15, 2020 at 7:42 AM Michael Carter
 wrote:
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>  at 
> org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(Futures.java:90)
>  …
>
> Not sure what I did to cause the problem

Somehow pulled in an incompatible version of `guava`. Jenkins bundles
11.x, and without a lot of advanced acrobatics¹ you cannot override
this. If your plugin bundles some third-party libraries, they may be
depending on a newer version of Guava and Maven picks that version for
tests, breaking everything. Check

mvn dependency:tree

and use an `` as necessary. Unless the third-party library
actually _requires_ newer Guava features, in which case you have
problems.


Also, did your tests stop working with no code changes? If `master`
was blue/green until now, check whether your `Jenkinsfile` is using,
say,

buildPlugin(configurations: recommendedConfigurations())

which is nondeterministic. If tests broke inside a PR (I would
recommend a PR for all nontrivial changes, even if you are a sole
maintainer, just for trackability and CI), link to that from any post
to the mailing list.


¹Read: 
https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/#pluginfirstclassloader-and-its-discontents

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1SG%3D%2BuPiiT3LURfW88oSBZU%3D3X09YCLi6ia4XwFuED3A%40mail.gmail.com.

In jenkins test harness (only) node() {} commands crash the executor

[Michael Carter]

Last of the thorns in my side before I release this code internally today.  
 All my tests via pipeline suddenly stopped working a week ago.   One thing 
I did try was having a few minute pause at the beginning of this command so 
I could log in via the http console.   Then tired creating the job via the 
UI and same results.  As soon as the node part start it crashes the 
executor and all jobs just spin.  

Any echo commands and such on the job run fine.   As long as there is no 
node() {} command

Script running
node() {
  echo "hello"
}


  44.247 [jobname-enableTest #1] [Pipeline] Start of Pipeline
  47.466 [jobname-enableTest #1] [Pipeline] node
  49.717 [id=47] SEVERE hudson.model.Executor#finish1: Executor threw an 
exception
java.lang.NoSuchMethodError: com.google.common.util.concurrent.MoreExecutors
.sameThreadExecutor()Lcom/google/common/util/concurrent/
ListeningExecutorService;
 at org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(
Futures.java:90)
 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.runInCpsVmThread(
CpsFlowExecution.java:900)
 at org.jenkinsci.plugins.workflow.cps.CpsBodyInvoker.start(CpsBodyInvoker.
java:153)
 at org.jenkinsci.plugins.workflow.cps.CpsBodyInvoker.start(CpsBodyInvoker.
java:56)
 at org.jenkinsci.plugins.workflow.support.steps.
ExecutorStepExecution$PlaceholderTask$PlaceholderExecutable.run(
ExecutorStepExecution.java:844)
 at hudson.model.ResourceController.execute(ResourceController.java:97)
 at hudson.model.Executor.run(Executor.java:428)

Not sure what I did to cause the problem but I'm sure this is just some 
library I'm missing as it seems to be the root of all my issues so far.  
 Just not sure where to look or where to start.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3ac8d5d6-bf08-40d5-ad44-8dceeca1eaa3o%40googlegroups.com.

Re: How to override the plugin version seen by plugin manager area

[Daniel Beck]

> On 14. Jul 2020, at 18:39, Jesse Glick  wrote:
> 
> Would not recommend it unless there is a
> compelling need.

Recent releases of Jenkins also show release dates in the plugin manager, the 
release dates are shown on the plugins site and in tooltips on the archives 
page, so I would be surprised if there is such a need while following our 
recommended practices.

I also wouldn't be surprised if this behavior breaks some parts of our 
automation.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D4CA2D97-9DCC-4979-B4DD-3212EBF1E491%40beckweb.net.