[JIRA] (JENKINS-57364) jenkins cannot provision new agent with openstack-cloud-plugin
Title: Message Title agatha chen commented on JENKINS-57364 Re: jenkins cannot provision new agent with openstack-cloud-plugin Oliver Gondža I'm not sure where should I get the full log of openstack cloud plugin, could you describe the way or the path where log files are stored? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199144.155729319.680.1557725400223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55103) Oops after update to 2.150.1 LTS on main page
Title: Message Title Florian Eidenhammer closed an issue as Incomplete Disabling all linked plugins to the matrix-project plugin solved the problem. I enabled the plugins again until the problem appeared again. Problem was an HP ALM plugin. Jenkins / JENKINS-55103 Oops after update to 2.150.1 LTS on main page Change By: Florian Eidenhammer Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196153.1544429539000.678.1557725280362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title anand acharya commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. Hi I also got similar issue just few days back for email extension plugin 2.66. Please resolve this issue asap. Email was triggered for: Unstable (Test Failures) Sending email for trigger: Unstable (Test Failures) ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:1098) at hudson.model.Run.execute(Run.java:1863) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.674.1557724140187%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated JENKINS-57111 PR merged. Will be release in the next couple weeks to weekly build. Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.671.1557722760237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56910) Can no longer search for branch names of parallel() branches
Title: Message Title Jared Patterson commented on JENKINS-56910 Re: Can no longer search for branch names of parallel() branches Any chance we can get the parallel name added back to the raw logs, very useful when debugging grepping through log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198583.1554468108000.666.1557696240120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Get Delta-Report in Pipeline
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Get Delta-Report in Pipeline
You can either use the available token (see https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#token-macro-support) or directly work with the created object of the { { publishIssues} } step. Would that work for you?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.656.1557688380126%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Get Delta-Report in Pipeline
Title: Message Title
Ulli Hafner commented on JENKINS-57312
Re: Get Delta-Report in Pipeline
You can either use the available token (see https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#token-macro-support) or directly work with the created object of the {publishIssues} step. Would that work for you?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.653.1557688320122%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57378
Re: warnings-ng commands show up as General Build Step in pipeline views
And you don't want them to appear there? Or what exactly should be done? These are actually steps...I have for instnace instance :{noformat}Step Arguments StatusStart of Pipeline - (4 min 25 sec in block) SuccessAllocate node : Start - (4 min 25 sec in block) Console Output SuccessAllocate node : Body : Start - (4 min 24 sec in block) SuccessStage : Start - (7.8 sec in block) Checkout Console Output SuccessCheckout - (7.7 sec in block) SuccessCheck out from version control - (7.6 sec in self) Console Output SuccessStage : Start - (4 min 16 sec in block) Build and Analysis Console Output SuccessBuild and Analysis - (4 min 16 sec in block) SuccessProvide Maven environment : Start - (3 min 11 sec in block) Console Output SuccessProvide Maven environment : Body : Start - (3 min 6 sec in block) SuccessShell Script - (3 min 6 sec in self) mvn -V -e clean verify -Dmaven.test.failure.ignore Console Output SuccessRecord compiler warnings and static analysis results - (22 sec in self) Console Output SuccessRecord compiler warnings and static analysis results - (8.5 sec in self) Console Output SuccessArchive JUnit-formatted test results - (3.8 sec in self) **/target/*-reports/TEST-*.xml Console Output SuccessRecord compiler warnings and static analysis results - (30 sec in self) Console Output Success{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.651.1557688080188%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Ulli Hafner commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views And you don't want them to appear there? Or what exactly should be done? These are actually steps... I have for instnace: Step Arguments Status Start of Pipeline - (4 min 25 sec in block) Success Allocate node : Start - (4 min 25 sec in block) Console Output Success Allocate node : Body : Start - (4 min 24 sec in block) Success Stage : Start - (7.8 sec in block) Checkout Console Output Success Checkout - (7.7 sec in block) Success Check out from version control - (7.6 sec in self) Console Output Success Stage : Start - (4 min 16 sec in block) Build and Analysis Console Output Success Build and Analysis - (4 min 16 sec in block) Success Provide Maven environment : Start - (3 min 11 sec in block) Console Output Success Provide Maven environment : Body : Start - (3 min 6 sec in block) Success Shell Script - (3 min 6 sec in self) mvn -V -e clean verify -Dmaven.test.failure.ignore Console Output Success Record compiler warnings and static analysis results - (22 sec in self) Console Output Success Record compiler warnings and static analysis results - (8.5 sec in self) Console Output Success Archive JUnit-formatted test results - (3.8 sec in self) **/target/*-reports/TEST-*.xml Console Output Success Record compiler warnings and static analysis results - (30 sec in self) Console Output Success Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57402) Let diagrams interact with Details table
Title: Message Title Ulli Hafner commented on JENKINS-57402 Re: Let diagrams interact with Details table There is a link on the build page that navigates to the new and fixed issues. Since FIXED and NEW warnings use a totally different rendering I'm not sure if it makes sense to reload the whole page on the selection of the chart. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199186.1557486983000.647.1557687660184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57400) Add option to filter warnings
Title: Message Title Ulli Hafner resolved as Fixed https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#filtering-issues Jenkins / JENKINS-57400 Add option to filter warnings Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199184.1557485001000.645.1557687180192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57391) Id for Snipped Generator Page
Title: Message Title Ulli Hafner edited a comment on JENKINS-57391 Re: Id for Snipped Generator Page Seems that adding an ID is not so easy for those select controls. I solved this problem in a general way now by adding the dependency to the [Form Element Path Plugin| | https://wiki.jenkins.io/display/JENKINS/Form+Element+Path+Plugin].See https://github.com/jenkinsci/warnings-ng-plugin/commit/ff78ca50858b37be92278037c26a5b03933ea248. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199173.1557437154000.636.1557674940406%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57391) Id for Snipped Generator Page
Title: Message Title Ulli Hafner edited a comment on JENKINS-57391 Re: Id for Snipped Generator Page Seems that adding an ID is not so easy for those select controls. I solved this problem in a general way now by adding the dependency to the [Form Element Path Plugin||https://wiki.jenkins.io/display/JENKINS/Form+Element+Path+Plugin]. See https://github.com/jenkinsci/warnings-ng-plugin/commit/ff78ca50858b37be92278037c26a5b03933ea248. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199173.1557437154000.634.1557674940352%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57391) Id for Snipped Generator Page
Title: Message Title Ulli Hafner updated JENKINS-57391 Seems that adding an ID is not so easy for those select controls. I solved this problem in a general way now by adding the dependency to the [Form Element Path Plugin||https://wiki.jenkins.io/display/JENKINS/Form+Element+Path+Plugin]. Jenkins / JENKINS-57391 Id for Snipped Generator Page Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199173.1557437154000.632.1557674940328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57379) EclipseParser fails to extract full message when message includes array brackets
Title: Message Title Ulli Hafner updated JENKINS-57379 Jenkins / JENKINS-57379 EclipseParser fails to extract full message when message includes array brackets Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199160.1557353883000.630.1557671400289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57419) Cannot upgrade Debian package when not set to start on boot
Title: Message Title Pepijn Schmitz created an issue Jenkins / JENKINS-57419 Cannot upgrade Debian package when not set to start on boot Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2019-05-12 13:10 Environment: Ubuntu 16.04.6 LTS Labels: debian ubuntu installer package Priority: Minor Reporter: Pepijn Schmitz Trying to upgrade Jenkins, which has been installed on Ubuntu as a deb package from pkg.jenkins.io, results in the following error if Jenkins has been set to to not run standalone in /etc/default/jenkins: Setting up jenkins (2.164.3) ... Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. invoke-rc.d: initscript jenkins, action "start" failed. * jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-05-12 15:00:08 CEST; 37ms ago Docs: man:systemd-sysv-generator(8) Process: 22350 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE) May 12 15:00:08 server07.pepsoft.org systemd[1]: Starting LSB: Start Jenkins at boot time... May 12 15:00:08 server07.pepsoft.org jenkins[22350]: Not configured to run standalone May 12 15:00:08 server07.pepsoft.org systemd[1]: jenkins.service: Control process exited,
[JIRA] (JENKINS-46710) Error: java.lang.ClassNotFoundException: hudson.remoting.Launcher
Title: Message Title Ilia Meerovich commented on JENKINS-46710 Re: Error: java.lang.ClassNotFoundException: hudson.remoting.Launcher reproduced Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185056.1504777376000.626.1557655860032%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46710) Error: java.lang.ClassNotFoundException: hudson.remoting.Launcher
Title: Message Title Ilia Meerovich commented on JENKINS-46710 Re: Error: java.lang.ClassNotFoundException: hudson.remoting.Launcher reproduced Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185056.1504777376000.617.1557655810312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25704) Scheduled triggering stops working until restart
Title: Message Title David Resnick commented on JENKINS-25704 Re: Scheduled triggering stops working until restart HARISHKUMAR TR I think someone has to be convinced to take it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159277.141647497.615.1557643980876%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Rick commented on JENKINS-57412 Re: Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Glad to know this. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.593.1557642180122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
