[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Arnaud Héritier commented on JENKINS-62054 Re: Support action is displayed even if the user does not have the rights Obviously there is a problem Pierre Beitz It's a not a security issue from my POV (Daniel Beck) because you cannot generate anything but I agree with you that we should fix it. Not sure about the fix you propose and why the permissions set in actions by Allan BURDAJEWICZ don't not work. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205951.158783968.17963.1587916380210%40Atlassian.JIRA.
[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Arnaud Héritier commented on JENKINS-62054 Re: Support action is displayed even if the user does not have the rights Pierre Beitz Could it be with some specific settings and/or a specific security scheme ? It's surprising (I didn't test) because the actions are supposed to to require the permission SupportPlugin.CREATE_BUNDLE https://github.com/jenkinsci/support-core-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/support/actions/SupportAbstractItemAction/action.jelly#L5 https://github.com/jenkinsci/support-core-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/support/actions/SupportComputerAction/action.jelly#L5 https://github.com/jenkinsci/support-core-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/support/actions/SupportRunAction/action.jelly#L5 Also on our products when I don't have an admin permission I do not see them (but we are probably not using the lastest version of support-core). cc Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205951.158783968.17926.1587901200193%40Atlassian.JIRA.
[JIRA] (JENKINS-58343) Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183
Title: Message Title Arnaud Héritier commented on JENKINS-58343 Re: Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183 Was fixed in release 2.13 (requires scm plugins updates too) https://github.com/jenkinsci/subversion-plugin/releases/tag/subversion-2.13.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200456.1562236576000.4154.1579770720644%40Atlassian.JIRA.
[JIRA] (JENKINS-58343) Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183
Title: Message Title Arnaud Héritier resolved as Fixed Fixed by https://github.com/jenkinsci/subversion-plugin/pull/239 AFAIU Jenkins / JENKINS-58343 Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183 Change By: Arnaud Héritier Status: Open Resolved Resolution: Fixed Released As: 2.13 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-58343) Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183
Title: Message Title Arnaud Héritier assigned an issue to Stefan Spieker Jenkins / JENKINS-58343 Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183 Change By: Arnaud Héritier Assignee: Stefan Spieker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200456.1562236576000.4158.1579770720719%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Arnaud Héritier updated JENKINS-60805 Fixed in support-core 2.67 Jenkins / JENKINS-60805 NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Change By: Arnaud Héritier Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Arnaud Héritier commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents support-core PR to restore the previous API: https://github.com/jenkinsci/support-core-plugin/pull/207 support-core SNAPSHOT if you want to test it instead of downgrading: https://ci.jenkins.io/job/Plugins/job/support-core-plugin/job/PR-207/1/artifact/org/jenkins-ci/plugins/support-core/2.67-rc812.5f943f6894c1/support-core-2.67-rc812.5f943f6894c1.hpi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.1248.1579281960298%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Arnaud Héritier commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents The PR proposed by Evaristo Gutierrez is fixing the issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.1244.1579281360337%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Arnaud Héritier started work on JENKINS-60805 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.1014.1579258500257%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Arnaud Héritier commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Allan BURDAJEWICZ it seems that it's regression due to https://github.com/jenkinsci/support-core-plugin/commit/4a3c12403766f8e28386df1d2bd9757e3ec2fae7 ( JENKINS-59342 ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204135.1579238976000.1008.1579258200344%40Atlassian.JIRA.
[JIRA] (JENKINS-60327) Tests are failing in windows using jenkins-test-harness-2.56
Title: Message Title Arnaud Héritier commented on JENKINS-60327 Re: Tests are failing in windows using jenkins-test-harness-2.56 it's already tested on windows by default. Thus I suppose that we don't yet have the issue because we use an older version jenkins-test-harness Emilio Escobar ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203335.1575022375000.9345.1575029460045%40Atlassian.JIRA.
[JIRA] (JENKINS-60327) Tests are failing in windows using jenkins-test-harness-2.56
Title: Message Title Arnaud Héritier commented on JENKINS-60327 Re: Tests are failing in windows using jenkins-test-harness-2.56 it's already tested on windows by default. Thus I suppose that we don't yet have the issue because we use an older version jenkins-test-harness Emilio Escobar ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203335.1575022375000.9343.1575029410187%40Atlassian.JIRA.
[JIRA] (JENKINS-60327) Tests are failing in windows using jenkins-test-harness-2.56
Title: Message Title Arnaud Héritier commented on JENKINS-60327 Re: Tests are failing in windows using jenkins-test-harness-2.56 Let's start by testing the plugin on windows ? https://github.com/jenkinsci/support-core-plugin/pull/202 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203335.1575022375000.9314.1575025860161%40Atlassian.JIRA.
[JIRA] (JENKINS-60281) Generating a support bundle with no about.md is useless
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-60281 Generating a support bundle with no about.md is useless Issue Type: Bug Assignee: Unassigned Components: cloudbees-jenkins-advisor-plugin Created: 2019-11-26 10:06 Priority: Major Reporter: Arnaud Héritier Related to JENKINS-57512, the problem comes from support-core as advisor is reusing/duplicating the same logic. A bundle with no about.md file is useless because our probes are using a lot of informations which are in this file (the product version ...) Maybe we could make the about component mandatory at least in Advisor if it is not in support-core Add Comment
[JIRA] (JENKINS-57512) Make About Jenkins always included in a bundle
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-57512 Make About Jenkins always included in a bundle Change By: Arnaud Héritier Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199414.1558044714000.7031.1574762700408%40Atlassian.JIRA.
[JIRA] (JENKINS-57512) Make About Jenkins always included in a bundle
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-57512 Make About Jenkins always included in a bundle Change By: Arnaud Héritier Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199414.1558044714000.7028.1574762580364%40Atlassian.JIRA.
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier updated JENKINS-59714 Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202423.1570628855000.9876.1573035240455%40Atlassian.JIRA.
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier closed an issue as Fixed Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202423.1570628855000.9880.1573035240528%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated JENKINS-59696 Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.9878.1573035240489%40Atlassian.JIRA.
[JIRA] (JENKINS-59775) Support Core dynamic loading is failing to load Master Log Record component
Title: Message Title Arnaud Héritier commented on JENKINS-59775 Re: Support Core dynamic loading is failing to load Master Log Record component I confirm that it's a problem with 2.190.x (reproduced today. No logs in the bundle until your restart (ref JENKINS-60073 to close as duplicated if confirmed) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202499.1571053707000.9845.1573033800164%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: support-core and thus advisor require to restart the instance to be activated I confirm. I tested with 2.138.4 and 2.190.2 and the problem isn't here. With 2.190.2 I hit JENKINS-60073 / JENKINS-59775 which is annoying but not critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.9843.1573033740168%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated JENKINS-59696 Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Status: In Review Resolved Resolution: Fixed Released As: support-core-2.63 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.9839.1573033620384%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated JENKINS-59696 Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.9841.1573033620416%40Atlassian.JIRA.
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Arnaud Héritier commented on JENKINS-60073 Re: support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Probably duplicates JENKINS-59775 To be confirmed by some experts cc Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202908.1573032472000.9835.1573032900260%40Atlassian.JIRA.
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Arnaud Héritier commented on JENKINS-60073 Re: support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission After a restart it is ok. No error and the logs are here Archive: jenkins-home/support/support_2019-11-06_09.30.25.zip Length DateTimeName - -- - 6093 11-06-2019 10:30 nodes/master/logs/jenkins.log 5264 11-06-2019 10:30 nodes/master/logs/all_memory_buffer.log 6144 11-06-2019 10:13 nodes/master/logs/all_2019-11-06_09.11.09.log 5264 11-06-2019 10:30 nodes/master/logs/all_2019-11-06_09.28.42.log 459 11-06-2019 10:30 other-logs/health-checker.log 87 11-06-2019 10:07 other-logs/Download metadata.log.1 87 11-06-2019 10:28 other-logs/Download metadata.log 89 11-06-2019 09:57 other-logs/Download metadata.log.2 89 11-06-2019 10:13 other-logs/Bundle Upload.log.1 40 11-06-2019 10:30 other-logs/Bundle Upload.log 6766 11-06-2019 10:30 about.md 556 11-06-2019 10:30 identity.md 3813 11-06-2019 10:30 nodes.md 1648 11-06-2019 10:30 plugins/active.txt 0 11-06-2019 10:30 plugins/disabled.txt 0 11-06-2019 10:30 plugins/failed.txt 28 11-06-2019 10:30 plugins/backup.txt 10259 11-06-2019 10:30 docker/Dockerfile 5087 11-06-2019 10:30 nodes/master/checksums.md5 184 11-06-2019 10:30 admin-monitors.md 75 11-06-2019 10:30 buildqueue.md 3386 11-06-2019 10:30 nodes/master/environment.txt 567 11-06-2019 10:30 nodes/master/file-descriptors.txt 604 11-06-2019 10:30 load-stats/no-label/sec10.csv 220 11-06-2019 10:30 load-stats/no-label/min.csv 172 11-06-2019 10:30 load-stats/no-label/hour.csv 1679 11-06-2019 10:30 load-stats/no-label/gnuplot 604 11-06-2019 10:30 load-stats/overall/sec10.csv 220 11-06-2019 10:30 load-stats/overall/min.csv 172 11-06-2019 10:30 load-stats/overall/hour.csv 1679 11-06-2019 10:30 load-stats/overall/gnuplot 836 11-06-2019 10:30 load-stats/label/master/sec10.csv 248 11-06-2019 10:30 load-stats/label/master/min.csv 172 11-06-2019 10:30 load-stats/label/master/hour.csv 1679 11-06-2019 10:30 load-stats/label/master/gnuplot 102 11-06-2019 10:30 loggers.md 76939 11-06-2019 10:30 nodes/master/metrics.json 1860 11-06-2019 10:30 nodes/master/networkInterface.md 728 11-06-2019 10:30 node-monitors.md 74 11-06-2019 10:30 reverse-proxy.md 0 11-06-2019 10:30 running-builds.txt 3620 11-06-2019 10:30 nodes/master/system.properties 269 11-06-2019 10:30 update-center.md 0 11-06-2019 10:30 nodes/master/pipeline-timings.txt 0 11-06-2019 10:30 nodes/master/pipeline-thread-dump.txt 40783 11-06-2019 10:30 nodes/master/thread-dump.txt 2632 11-06-2019 10:30 manifest.md - --- 191277 47 files
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Arnaud Héritier assigned an issue to Unassigned Jenkins / JENKINS-60073 support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Change By: Arnaud Héritier Assignee: Emilio Escobar Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202908.1573032472000.9808.1573032540113%40Atlassian.JIRA.
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-60073 support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-11-06 09:27 Priority: Minor Reporter: Arnaud Héritier Scenario: 1/ Install and configure Jenkins LTS 2.190.2 2/ Configure the experimental update center ( https://updates.jenkins.io/experimental/update-center.json ) to get access to support-core 2.63-alpha 3/ Install Health Advisor by CloudBees plugin 3.0 from the UC. It will install support-core 2.63-alpha 4/ Look at the logs: Failed to instantiate Key[type=com.cloudbees.jenkins.support.impl.JenkinsLogs, annotation=[none]]; skipping this component hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission at hudson.security.ACL.checkPermission(ACL.java:73) at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47) at jenkins.model.Jenkins.getLog(Jenkins.java:2501) at com.cloudbees.jenkins.support.impl.JenkinsLogs.(JenkinsLogs.java:50) at com.cloudbees.jenkins.support.impl.JenkinsLogs$$FastClassByGuice$$adeef6a3.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89) at
[JIRA] (JENKINS-59917) Jenkins Health Advisor by CloudBees for offline instances
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59917 Jenkins Health Advisor by CloudBees for offline instances Change By: Arnaud Héritier Summary: Jenkins Health Advisor by CloudBees for offline instances Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202716.1571915942000.4562.1572360660199%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: support-core and thus advisor require to restart the instance to be activated If you are facing this issue and cannot restart your instance, disable the logger which is generating these logs up until you can restart. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.1781.1572017521074%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Attachment: Screenshot 2019-10-25 17.28.38.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.1779.1572017521019%40Atlassian.JIRA.
[JIRA] (JENKINS-59936) The Advisor Global Configuration page hangs in case the backend doesn't answer
Title: Message Title Arnaud Héritier commented on JENKINS-59936 Re: The Advisor Global Configuration page hangs in case the backend doesn't answer I see what is wrong. Thanks for reporting it Pierre Beitz I will try to propose a fix soon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202738.1572011346000.1611.1572011640119%40Atlassian.JIRA.
[JIRA] (JENKINS-59936) The Advisor Global Configuration page hangs in case the backend doesn't answer
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59936 The Advisor Global Configuration page hangs in case the backend doesn't answer Change By: Arnaud Héritier Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202738.1572011346000.1609.1572011580437%40Atlassian.JIRA.
[JIRA] (JENKINS-59917) Jenkins Health Advisor for offline instances
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59917 Jenkins Health Advisor for offline instances Issue Type: New Feature Assignee: Unassigned Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-24 11:19 Priority: Minor Reporter: Arnaud Héritier The current architecture of Jenkins Health Advisor by CloudBees is relying on a server maintained and regularly update by the CloudBees Support team. When an instance isn't connected to internet it cannot send a support bundle for being analysed automatically. A solution not too much expensive could be to provide a front-end with a form where we ask the email to use and the support bundle to analyse (to be generated manually on the offline infrastructure). Even if this is a server improvement, I am tracking it here on the plugin side to give the visibility to the community Add Comment
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier updated JENKINS-59714 Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: support-core-2.63 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202423.1570628855000.237.1571915640844%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Improve UX and users feedbacks
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Improve UX and users feedbacks Change By: Arnaud Héritier Summary: Give more details in the connection success panel Improve UX and users feedbacks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8936.1571248380406%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 3.0 is out Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8814.1571235060150%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Monitors: Connection statusLast upload status Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8813.1571235002055%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated JENKINS-59707 3.0 is out Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8808.1571234830314%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: advisor-config-last-upload-error.png Attachment: advisor-monitor-error.png Attachment: advisor-config-current-status-error.png Attachment: advisor-config-last-upload-success.png Attachment: advisor-config-current-status-success.png Attachment: advisor-config-last-upload-skipped.png Attachment: advsior-config-last-upload-none.png Attachment: advisor-config-current-status-invalid.png Attachment: advisor-monitor-configure-it.png Add Comment
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 3.0 is out Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.8806.1571234760097%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated JENKINS-59695 3.0 is out Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.8801.1571234700622%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-3.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8767.1571231162010%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.8764.1571231101832%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor-plugin- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.8760.1571231101687%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8766.1571231101886%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier commented on JENKINS-59767 Re: Replace the comma separated list for CC by a list of emails https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/55 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8508.1571212260051%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier assigned an issue to Unassigned Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Assignee: Arnaud Héritier Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8506.1571212200214%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8507.1571212200233%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Summary: support-core requires and thus advisor require to restart the instance to be activated Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8503.1571211060262%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 support-core requires to restart the instance to be activated Change By: Arnaud Héritier Summary: Jenkins Health Advisor support-core requires to restart the instance to be activated Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8501.1571210400374%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8500.1571210400360%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated I did a lot of manual tests and the problem is always when support-core isn't yet installed. The problem isn't directly in advisor Ryan Campbell Otherwise we will have to see with Allan BURDAJEWICZ if we can isolate/fix the issue in support-core. The only thing I could try to do at the advisor level is to catch this error and ask to the administrator to restart the instance. For now the user is seeing this generic error in the Advisor config panel: And this warning monitor (note to myself: they should be unified ...) Note, that as soon the support-core is installed but the instance not restarted the logs are polluted with these errors Oct 16, 2019 8:49:05 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Oct 16, 2019 8:49:08 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier stopped work on JENKINS-59696 Change By: Arnaud Héritier Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8497.1571209982133%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Attachment: Screenshot 2019-10-16 09.00.42.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8494.1571209320747%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Attachment: Screenshot 2019-10-16 08.57.20.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8490.1571209200250%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Component/s: support-core-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8488.1571208180308%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated JENKINS-59707 Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Status: Open Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.12 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8206.1571155500312%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel I did these improvements. It will be enough for now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8204.1571155440192%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: Screenshot 2019-10-15 18.01.19.png Attachment: Screenshot 2019-10-15 18.00.37.png Attachment: Screenshot 2019-10-15 18.00.01.png Attachment: Screenshot 2019-10-15 17.59.39.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Ryan Campbell I don't think we want to expose the # of probes or Advisor version. I think we just want to say something like "Connection successful" for the Server: Ok. It's what we have today. I will keep it. It was to show that even if the plugin doesn't evolve much, on the server side we are regularly updating it I really like showing the previous upload vs. next. Where is that data coming from? The previous information we have it already. It's recorded in the configuration each time we send a bundle (I don't like to store it here but I don't know if we can do better). It was already displayed for some time but I'm trying to make it more visible. I would love to display the next upload but I'm not able to find a such info in a AsyncPeriodicWork. I have to dig more... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.7751.1571135520271%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated As seen above and with Allan BURDAJEWICZ tests, the problem is perhaps in support-core and not in advisor ( JENKINS-59775 ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.7018.1571056020103%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Attachment: Screenshot 2019-10-14 12.26.24.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.6933.1571048820108%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier commented on JENKINS-59767 Re: Replace the comma separated list for CC by a list of emails I should give something like Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.6934.1571048820199%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Issue Type: Improvement Assignee: Arnaud Héritier Attachments: Screenshot 2019-10-13 22.32.02.png, Screenshot 2019-10-13 22.33.42.png Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-13 20:34 Priority: Minor Reporter: Arnaud Héritier Instead of I would prefer to have the ability to add the emails 1 by one and having them configured as a list. Like we can see for branches in the git plugin to add/remove them Add Comment
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier started work on JENKINS-59767 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.6745.1570998900280%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.12 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6741.1570997880128%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier commented on JENKINS-59697 Re: Add an Apply button and enhance the UX https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6273.1570832040057%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier started work on JENKINS-59697 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6267.1570831560333%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6268.1570831560351%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier In addition of the Save button (like many others plugins) to be able to apply the configuration change without leaving the configuration screen .Improving the validation logic to make the setup easier Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6249.1570827780072%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Summary: Add an Apply button and enhance the UX Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6248.1570827720062%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated Allan BURDAJEWICZ could we discuss about this ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.6101.1570812960053%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Maybe something like cc Ryan Campbell (it's just an idea) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.5254.1570742820052%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: Screenshot 2019-10-10 23.24.15.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.5253.1570742700064%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated JENKINS-59695 Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-plugin-2.12 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.4817.1570711500253%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated In fact doing 3/ with the current master code and not the patched one works too Should I conclude that to install a plugin without restarting the master the best strategy is to upload it manually instead of installing it from the UC? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3908.1570632780088%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated Pierre Beitz also found something similar done by Stephen Connolly a year ago: https://github.com/jenkinsci/metrics-plugin/blame/bb4a572004bb708136a57d2d359a930c934786b1/src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java#L708-L721 https://issues.jenkins-ci.org/browse/JENKINS-28983 https://issues.jenkins-ci.org/browse/JENKINS-52072 But my tests are with 2.138 thus we should have the required fix in core And strangely I find ~ no plugin using @Extension(dynamicLoadable = YesNoMaybe.YES) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3898.1570631580065%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated 3/ Jenkins 2.138.4 installed from scratch with suggested plugins. *I upload from the UI a patched version of the plugin* with all extensions and marked as loadable dynamically and it works. I can trigger an upload from the console. No issue. https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/50 But is it a test which is relevant compared to installations 1/ and 2/ done from the UC ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3893.1570630680218%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title
Arnaud Héritier edited a comment on JENKINS-59696
Re: Jenkins Health Advisor requires to restart the instance to be activated
More tests:1/ Jenkins 2.138.4 installed from scratch with suggested plugins. *" Install without Restart "* adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing:{noformat}Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Started Bundle UploadOct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logErrorSEVERE: ERROR: Could not save support bundlejava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logSEVERE: ERROR: Unable to generate support bundleOct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Finished Bundle Upload. 8 msOct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated 2/ Jenkins 2.138.4 installed from scratch with suggested plugins. "Download now and install after restart" but adds Variant, Metrics and Support core plugins but all of them are "Downloaded Successfully. Will be activated during the next boot". We cannot use any of them before the next restart Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3867.1570626540089%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title
Arnaud Héritier edited a comment on JENKINS-59696
Re: Jenkins Health Advisor requires to restart the instance to be activated
More tests:1/ Jenkins 2.138.4 installed from scratch with suggested plugins. Install without Restart adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing:{noformat}Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Started Bundle UploadOct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logErrorSEVERE: ERROR: Could not save support bundlejava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logSEVERE: ERROR: Unable to generate support bundleOct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Finished Bundle Upload. 8 msOct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated More tests: 1/ Jenkins 2.138.4 installed from scratch with suggested plugins. Install without Restart adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing: Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Bundle Upload Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logError SEVERE: ERROR: Could not save support bundle java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748) Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload log SEVERE: ERROR: Unable to generate support bundle Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Bundle Upload. 8 ms Oct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier started work on JENKINS-59696 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3583.1570570860087%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Issue Type: New Feature Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 21:18 Priority: Minor Reporter: Arnaud Héritier The idea is to replace the message Jenkins Healthy Advisor by CloudBees has been successfully connected. By something like You are connected to Jenkins Healthy Advisor by CloudBees. Server v2.40 (2019-10-14) with 238 probes. The idea is to give more details about the server side. In the future we might also publish it's release notes publicly and add a link. It gives to our users an idea of our updates.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated I took a clean 2.138.4, installed the plugin with `Install without restart` and the plugin isn't in the Manage Jenkins page I have the warning `Changes will take effect when you restart Jenkins` Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3575.1570569000447%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59697 Add an Apply button Issue Type: New Feature Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 08:29 Priority: Minor Reporter: Arnaud Héritier In addition of the Save button (like many others plugins) to be able to apply the configuration change without leaving the configuration screen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3176.1570521660313%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Issue Type: Improvement Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 07:59 Priority: Minor Reporter: Arnaud Héritier Right now the plugin requires to have the master restarted otherwise (often?) it doesn't start to send bundles. We want to verify if we could fix this issue (it's painful to have to restart an instance to install a plugin) I suppose the issue could come from the instanciation/activation of the AsyncPeriodicWork task https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/advisor/BundleUpload.java Is there any good practices to follow ? Any sample of such AsyncPeriodicWork extensions which aren't requiring to restart the master ? Add Comment
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Summary: JCasC support for Jenkins Health Advisor by CloudBees plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.3174.1570521060555%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor by CloudBees
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor by CloudBees Issue Type: Task Assignee: Francisco Fernández Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 07:48 Priority: Minor Reporter: Arnaud Héritier As reported by Oleg Nenashev this plugin doesn't yet support JCasC. Configurations options are The ToS validation The primary email The CC emails The list of support-core components to use The ability to deactivate the monitor which is reminding to configure the plugin Add Comment
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59554 Avoid capturing an automatic bundle immediately after startup Change By: Arnaud Héritier Released As: support-core-2.62 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202186.1569530151000.2252.1570435440362%40Atlassian.JIRA.
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Arnaud Héritier updated JENKINS-59454 Jenkins / JENKINS-59454 Increase Advisor bundle generation delay to 30mins Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202047.1568943413000.908.1570181820239%40Atlassian.JIRA.
[JIRA] (JENKINS-59618) Upgrade parent pom + configure plugin metadata
Title: Message Title Arnaud Héritier updated JENKINS-59618 Jenkins / JENKINS-59618 Upgrade parent pom + configure plugin metadata Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202259.1569961496000.904.1570181760798%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Arnaud Héritier updated JENKINS-59644 Jenkins / JENKINS-59644 Upgrade Jenkins core pre-requisite to 2.138.4 Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202334.1570111402000.900.1570181760736%40Atlassian.JIRA.
[JIRA] (JENKINS-59614) New icon for Jenkins Health Advisor by CloudBees
Title: Message Title Arnaud Héritier updated JENKINS-59614 Jenkins / JENKINS-59614 New icon for Jenkins Health Advisor by CloudBees Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202255.156995264.905.1570181760819%40Atlassian.JIRA.
[JIRA] (JENKINS-59613) Rename the plugin "Jenkins Health Advisor by CloudBees"
Title: Message Title Arnaud Héritier updated JENKINS-59613 Jenkins / JENKINS-59613 Rename the plugin "Jenkins Health Advisor by CloudBees" Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202254.1569951438000.906.1570181760832%40Atlassian.JIRA.
[JIRA] (JENKINS-59629) Not validating the TOS is confusing
Title: Message Title Arnaud Héritier updated JENKINS-59629 Jenkins / JENKINS-59629 Not validating the TOS is confusing Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202310.1570035924000.903.1570181760784%40Atlassian.JIRA.
[JIRA] (JENKINS-59647) Upgrade support-core dependency to 2.62
Title: Message Title Arnaud Héritier updated JENKINS-59647 Jenkins / JENKINS-59647 Upgrade support-core dependency to 2.62 Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202337.1570118067000.899.1570181760717%40Atlassian.JIRA.
[JIRA] (JENKINS-59648) UX improvements
Title: Message Title Arnaud Héritier updated JENKINS-59648 Jenkins / JENKINS-59648 UX improvements Change By: Arnaud Héritier Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202338.1570118477000.898.1570181760626%40Atlassian.JIRA.
[JIRA] (JENKINS-59647) Upgrade support-core dependency to 2.62
Title: Message Title Arnaud Héritier updated JENKINS-59647 Jenkins / JENKINS-59647 Upgrade support-core dependency to 2.62 Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202337.1570118067000.897.1570178460116%40Atlassian.JIRA.
