[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite edited a comment on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime I'm unable to duplicate the problem. Refer to the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-56326/Jenkinsfile] in my JENKINS-56326 [bug repro branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-56326/README.md] to see the code that I used to attempt to duplicate it. The duplication performs the following steps:# Commit a change to the JENKINS-56326 branch# Launch a multibranch Pipeline job to build that change# Job performs a checkout, reports the SHA1 of the checkout, sleeps 90 seconds, performs another checkout in a separate workspace, then reports SHA1 of checkout in new workspace# While job is running (during the 90 second sleep), the "increment" target that launched the job originally sleeps 53 seconds, commits to the master branch, and pushes that commitThe check for duplication was performed with command line git in multiple environments, including Windows and several different Linux machines. The check was also performed with JGit.I am closing this as "cannot reproduce". If you can provide more details so that I can duplicate the problem, please reopen it. Refer to the preceding comment for one possible reason for that error message from command line git. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite updated JENKINS-56326 Jenkins / JENKINS-56326 Git fetch in a later Pipeline stage fails when master received new revisions in the meantime Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite edited a comment on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime I'm unable to duplicate the problem. Refer to the [ Jenkinsfile |https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-56326/Jenkinsfile] in my JENKINS-56326 [ bug repro branch |https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-56326/README.md] to see the code that I used to attempt to duplicate it. The duplication performs the following steps:# Commit a change to the JENKINS-56326 branch# Launch a multibranch Pipeline job to build that change# Job performs a checkout, reports the SHA1 of the checkout, sleeps 90 seconds, performs another checkout in a separate workspace, then reports SHA1 of checkout in new workspace# While job is running (during the 90 second sleep), the "increment" target that launched the job originally sleeps 53 seconds, commits to the master branch, and pushes that commitThe check for duplication was performed with command line git in multiple environments, including Windows and several different Linux machines. The check was also performed with JGit.I am closing this as "cannot reproduce". If you can provide more details so that I can duplicate the problem, please reopen it. Refer to the preceding comment for one possible reason for that error message from command line git. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite commented on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime I'm unable to duplicate the problem. Refer to the Jenkinsfile in my JENKINS-56326 bug repro branch to see the code that I used to attempt to duplicate it. The duplication performs the following steps: Commit a change to the JENKINS-56326 branch Launch a multibranch Pipeline job to build that change Job performs a checkout, reports the SHA1 of the checkout, sleeps 90 seconds, performs another checkout in a separate workspace, then reports SHA1 of checkout in new workspace While job is running (during the 90 second sleep), the "increment" target that launched the job originally sleeps 53 seconds, commits to the master branch, and pushes that commit The check for duplication was performed with command line git in multiple environments, including Windows and several different Linux machines. The check was also performed with JGit. I am closing this as "cannot reproduce". If you can provide more details so that I can duplicate the problem, please reopen it. Refer to the preceding comment for one possible reason for that error message from command line git. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56326 Git fetch in a later Pipeline stage fails when master received new revisions in the meantime Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3* Dump:* [^jenkins_dump.txt]* Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56441) Jenkins worker not released
Title: Message Title laurent gil updated an issue Jenkins / JENKINS-56441 Jenkins worker not released Change By: laurent gil Attachment: jenkins_dump.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title laurent gil edited a comment on JENKINS-31536 Re: Jobs hanging in Build Executor even if it is finished Since roughlty 3 weeks our Jenkins instance started to have finished jobs which don't release the worker. They appear to be running but when we go to the job console there is a jenkins message saying 'SUCCESS' or 'FAILURE'. Since 2 days this issue occurs several time a day. This morning i tried to rollback to the latest LTS version but without success. You will find the thread dump attached.Any help will be appreciated as our users are strated to complain and we really don't know how to sort it out.*Jenkins Version:* 2.150.3* Dump:* [^jenkins_dump.txt]* Plugins:* [^jenkins-plugins.txt]*^Java version:^* ^openjdk version "1.8.0_201" build "1.8.0_201_b09" 64-Bit Server VM (build 25.201-b09, mixed mode)^ Regards Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55871) Update without losing plugins settings
Title: Message Title Daniel Spilker resolved as Not A Defect This is a question for the Jenkins users mailing list (see https://jenkins.io/mailing-lists/) or Stack Overflow (see https://stackoverflow.com/questions/tagged/jenkins). Jenkins / JENKINS-55871 Update without losing plugins settings Change By: Daniel Spilker Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56320) Job DSL 1.71 unable to process DSLs
Title: Message Title Daniel Spilker assigned an issue to Joe Roberts I can not reproduce the problem using the offical Jenkins 2.150.3 docker image and Job DSL 1.72. Can you provide a reproducer? Jenkins / JENKINS-56320 Job DSL 1.71 unable to process DSLs Change By: Daniel Spilker Assignee: Daniel Spilker Joe Roberts Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56427) Phabricator plugin DSL missing workDir parameter
Title: Message Title
Daniel Spilker resolved as Not A Defect
This is already supported by the Dynamic DSL:
job('example') {
wrappers {
phabricatorBuildWrapper {
createCommit(true)
applyToMaster(true)
skipForcedClean(false)
createBranch(false)
patchWithForceFlag(true)
skipApplyPatch(false)
scmType('git')
workDir('test')
}
}
}
Jenkins / JENKINS-56427
Phabricator plugin DSL missing workDir parameter
Change By:
Daniel Spilker
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed
[JIRA] (JENKINS-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite commented on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime If the error occurs on agent D and it is the same host as agent C, are those two agents using a shared directory for their workspace? The command line git message that it cannot lock a ref might indicate that two different processes are operating in the same directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-54119 ESlint rules are not applied on the client Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy started work on JENKINS-54119 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51451) BugBash session for Evergreen client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51451 BugBash session for Evergreen client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51449) Testing of P1 cases for evergreen client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51449 Testing of P1 cases for evergreen client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50534) git-plugin quality audit for Evergreen
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-50534 git-plugin quality audit for Evergreen Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51425) Define quality bar for client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51425 Define quality bar for client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32544) Commit message line breaks are stripped out in Changes page.
Title: Message Title Christopher Simons edited a comment on JENKINS-32544 Re: Commit message line breaks are stripped out in Changes page. Fixed in [PR #375|https://github.com/jenkinsci/git-plugin/pull/375] , though still unmerged 3 years later for unknown reasons .A screen shot of the fixed rendering is attached (file "32544-FIXED.png"): Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53934) Support ListViewColumn to display status of 'master'-branch in subview
Title: Message Title Robert Scholte commented on JENKINS-53934 Re: Support ListViewColumn to display status of 'master'-branch in subview Is it worth investing energy in the suggested solution? IIRC Stephen Connolly has a different idea to solve this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53934) Support ListViewColumn to display status of 'master'-branch in subview
Title: Message Title Robert Scholte commented on JENKINS-53934 Re: Support ListViewColumn to display status of 'master'-branch in subview Is it worth investing energy in the suggested solution? IIRC Stephen Connolly has a different idea to solve this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Ioannis Moutsatsos commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Thank you for your feedback Saheta B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Initially we thought that this is an issue with active choice parameter plugin, but later we realized that this is only related to parameter separator and not active choice parameter plugin. So we can remove that tag. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56494) hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Title: Message Title
Steve Hill updated an issue
Jenkins / JENKINS-56494
hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Change By:
Steve Hill
Goal: More operational insight into Jenkins Starting up a newly-downloaded Jenkins 2.150.3 with the FINE level enabled currently logs this misleading stacktrace about 20 times:{noformat}23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinder23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinderjava.lang.Throwable: nullat hudson.ExtensionList.load(ExtensionList.java:378) ~[?:?]at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318) ~[?:?]at hudson.ExtensionList.getComponents(ExtensionList.java:183) ~[?:?]at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1114) ~[?:?] at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:177) ~[?:?] at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_181] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]{noformat}In looking [at the code ][ | https://github.com/jenkinsci/jenkins/blob/jenkins-2.150.3/core/src/main/java/hudson/ExtensionList.java#L378], a new Throwable is created when this message is logged. If we left that out, we'd get the nice DEBUG message without the concerning stacktrace.
Add Comment
[JIRA] (JENKINS-56494) hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Title: Message Title
Steve Hill updated an issue
Jenkins / JENKINS-56494
hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Change By:
Steve Hill
Goal: More operational insight into Jenkins Starting up a newly-downloaded Jenkins 2.150.3 with the FINE level enabled currently logs this misleading stacktrace about 20 times:{noformat}23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinder23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinderjava.lang.Throwable: nullat hudson.ExtensionList.load(ExtensionList.java:378) ~[?:?]at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318) ~[?:?]at hudson.ExtensionList.getComponents(ExtensionList.java:183) ~[?:?]at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1114) ~[?:?] at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:177) ~[?:?] at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_181] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]{noformat} In looking [at the code](https://github.com/jenkinsci/jenkins/blob/jenkins-2.150.3/core/src/main/java/hudson/ExtensionList.java#L378), a new Throwable is created when this message is logged. If we left that out, we'd get the nice DEBUG message without the concerning stacktrace.
Add Comment
[JIRA] (JENKINS-56494) hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Title: Message Title
Steve Hill updated an issue
Jenkins / JENKINS-56494
hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Change By:
Steve Hill
Goal: More operational insight into Jenkins Starting up a newly-downloaded Jenkins 2.150.3 with the FINE level enabled currently logs this misleading stacktrace about 20 times:{noformat}23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinder23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinderjava.lang.Throwable: nullat hudson.ExtensionList.load(ExtensionList.java:378) ~[?:?]at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318) ~[?:?]at hudson.ExtensionList.getComponents(ExtensionList.java:183) ~[?:?]at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1114) ~[?:?] at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:177) ~[?:?] at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_181] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]{noformat}In looking [at the code] ( [ https://github.com/jenkinsci/jenkins/blob/jenkins-2.150.3/core/src/main/java/hudson/ExtensionList.java#L378 ) ] , a new Throwable is created when this message is logged. If we left that out, we'd get the nice DEBUG message without the concerning stacktrace.
Add Comment
[JIRA] (JENKINS-56494) hudson.ExtensionList logs stacktrace unnecessarily on FINE level
Title: Message Title Steve Hill created an issue Jenkins / JENKINS-56494 hudson.ExtensionList logs stacktrace unnecessarily on FINE level Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-09 16:24 Environment: Jenkins 2.150.3 JVM Version 1.8.0_181-b02 Apache Tomcat 8.5.38 Tomcat started with all logging bridged to log4j2 via -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager Tomcat enables DEBUG (FINE) logging for everything Priority: Minor Reporter: Steve Hill Goal: More operational insight into Jenkins Starting up a newly-downloaded Jenkins 2.150.3 with the FINE level enabled currently logs this misleading stacktrace about 20 times: 23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinder23:15:27.375 [pool-7-thread-9] DEBUG hudson.ExtensionList - Loading ExtensionList: class hudson.ExtensionFinder java.lang.Throwable: null at hudson.ExtensionList.load(ExtensionList.java:378) ~[?:?] at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318) ~[?:?] at hudson.ExtensionList.getComponents(ExtensionList.java:183) ~[?:?] at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1114) ~[?:?] at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) ~[?:?] at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) ~[?:?] at
[JIRA] (JENKINS-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Benoit Le Gall updated JENKINS-55794 Jenkins / JENKINS-55794 Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN Change By: Benoit Le Gall Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Benoit Le Gall updated JENKINS-55794 Jenkins / JENKINS-55794 Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN Change By: Benoit Le Gall Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/rabbitmq-publisher-plugin/releases/tag/rabbitmq-publisher-1.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Benoit Le Gall closed an issue as Fixed Jenkins / JENKINS-55794 Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN Change By: Benoit Le Gall Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-101) Login Test Failed
Title: Message Title Murray Jones updated an issue test / TEST-101 Login Test Failed Change By: Murray Jones Attachment: VMCE_V8.pdf Attachment: VMCE_V9.pdf Attachment: VTNE.pdf Attachment: Wonderlic.pdf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52497) Jenkins cannot build with error - groovy
Title: Message Title Ioannis Moutsatsos commented on JENKINS-52497 Re: Jenkins cannot build with error - groovy Tomas Pavelka any updates? Is this really due to the Active Choice parameter. Otherwise, please provide a test case we can troubleshoot. Best regards Ioannis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title Ioannis Moutsatsos commented on JENKINS-53540 Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter This behavior is already present in AC Reactive Reference. Return a 'Formatted HTML' parameter (not an Input Text Box) of type and insure that under advanced options you select 'Omit value filed' You can even provide a default value that can be further edited by the user. Something like this would work: return "" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54006) No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter
Title: Message Title Ioannis Moutsatsos commented on JENKINS-54006 Re: No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter Have you tried to go into the advanced options of the AC Reactive Reference and check the Omit value field option? Otherwise the default 'null' value is passed into the build Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54006) No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-54006 No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter Change By: Ioannis Moutsatsos Attachment: image-2019-03-09-09-58-36-226.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55007) How do I have more then one parameter on a single line for parameterized jobs?
Title: Message Title Ioannis Moutsatsos commented on JENKINS-55007 Re: How do I have more then one parameter on a single line for parameterized jobs? Hi ANSHUK ROY You could use an Active Choice reactive reference to return formatted HTML. You could then have multiple input fields and other control inputs (checkboxes, calendar, colors etc) returned by a single parameter. You may need to deconvolute this complex value later though, as it will return the various values simply as a comma separated list Hope this helps Best regards Ioannis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Why is this issue even tagged with Active Choices plugin? I don't see what the issue is with AC? I have removed the AC plugin tag until the relevance is demonstrated Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Ioannis Moutsatsos Component/s: active-choices-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Ioannis Moutsatsos commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Why is this issue even tagged with Active Choices plugin? I don't see what the issue is with AC? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz started work on JENKINS-55462 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Ioannis Moutsatsos commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Hi Madhavi. I must say that most issues with AC reactive parameters boil down to the values of referenced parameters. Depending on the state of your build form referenced parameter values could change (or even be null) and of course that would affect the success or failure of the AC reactive script. Do you have a fallback script? This is always a good way to troubleshoot. You can have a fallback script that reports the values of referenced parameters so at least you know what the script input is. Finally, you can debug your AC reactive script by running it from the script console and hard-coding some of the input values to observe it behavior Hope this is helpful Best regards Ioannis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_COMMIT no longer set in git plugin 4.0.0-rc
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-56176 GIT_COMMIT no longer set in git plugin 4.0.0-rc Change By: Mark Waite Summary: GIT_REVISION macro replaced with GIT_COMMIT but without support for length no longer set in git plugin 4.0.0-rc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title Mark Waite updated JENKINS-56390 Jenkins / JENKINS-56390 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56390) Duplicate ChangeLog on Jenkins builds for concurrent builds
Title: Message Title Mark Waite updated JENKINS-56390 Jenkins / JENKINS-56390 Duplicate ChangeLog on Jenkins builds for concurrent builds Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56493) Platform labeler should handle Linux machines without lsb_release
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-56493 Platform labeler should handle Linux machines without lsb_release Issue Type: Improvement Assignee: Unassigned Components: platformlabeler-plugin Created: 2019-03-09 14:03 Priority: Minor Reporter: Mark Waite The platform labeler plugin relies on the lsb_release command to determine Linux operating system details. When the lsb_release command is not installed, it reports spurious information. It should use additional methods to determine Linux operating system information when the lsb_release command is not available. Add Comment
[JIRA] (JENKINS-53571) Configuration-as-Code compatibility
Title: Message Title René Scheibe assigned an issue to Unassigned Jenkins / JENKINS-53571 Configuration-as-Code compatibility Change By: René Scheibe Assignee: Nick Grealy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56462) pipelineJob does not support trim option for stringParam
Title: Message Title
Daniel Spilker resolved as Not A Defect
The trim option is already supported by the Dynamic DSL:
pipelineJob('example') {
parameters {
stringParam {
name('EXAMPLE')
defaultValue('test')
description('an example')
trim(true)
}
}
}
Jenkins / JENKINS-56462
pipelineJob does not support trim option for stringParam
Change By:
Daniel Spilker
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-56492) Fix Javadoc failures on Java11
Title: Message Title Ramon Leon updated JENKINS-56492 Jenkins / JENKINS-56492 Fix Javadoc failures on Java11 Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56492) Fix Javadoc failures on Java11
Title: Message Title Ramon Leon commented on JENKINS-56492 Re: Fix Javadoc failures on Java11 Pull request with the fix: https://github.com/jenkinsci/acceptance-test-harness/pull/490 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41392) disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Title: Message Title
Amir Barkal commented on JENKINS-41392
Re: disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Joining Op's request, our use case is very similar: Using the same Jenkinsfile for different jobs with declarative syntax. This can be implemented by either having the options{} block accept a when{} clause, or (preferably) by having all the options support configurable parameters. IMO this ticket should be reopened with a definition of done like Op's subject.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56492) Fix Javadoc failures on Java11
Title: Message Title Ramon Leon started work on JENKINS-56492 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56492) Fix Javadoc failures on Java11
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-56492 Fix Javadoc failures on Java11 Issue Type: Bug Assignee: Ramon Leon Components: acceptance-test-harness Created: 2019-03-09 08:41 Labels: java11 java11-devtools-compatibility Priority: Major Reporter: Ramon Leon There are two tests failing when running on Java 11 related with javadoc-plugin: plugins.JavadocPluginTest.publish_javadoc_from_matrix_job plugins.JavadocPluginTest.publish_javadoc_from_freestyle_job These failures are related to JENKINS-32619 because Java11 is not using frames anymore for rendering the javadoc. javadoc-plugin has been fixed to modify the landing page when linking the javadoc, but we still need to fix the tests of this plugin on ATH. Depending on the java version and the javadoc-plugin version used, the way of asserting the javadoc is generated is different.
