[JIRA] (JENKINS-27512) Support icons for folders
Title: Message Title Daniel Spilker commented on JENKINS-27512 Re: Support icons for folders Roman Donchenko yes, but then there is only one icon, which is the default icon. So, there no icon to choose from. And thus no reason to add DSL for configuration. Or am I missing something? 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.161314.1426786361000.1567.1562223360183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51202) choiceParam not listed in JobDSL API viewer
Title: Message Title Daniel Spilker updated JENKINS-51202 Jenkins / JENKINS-51202 choiceParam not listed in JobDSL API viewer Change By: Daniel Spilker Status: Reopened 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.190518.1525788096000.1563.156760862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58335) Parameterized Remote Trigger plugin print too much logs in Console Output
Title: Message Title daniel zhang created an issue Jenkins / JENKINS-58335 Parameterized Remote Trigger plugin print too much logs in Console Output Issue Type: Improvement Assignee: KaiHsiang Chang Components: parameterized-remote-trigger-plugin Created: 2019-07-04 06:32 Environment: plugin version: 3.0.8 Priority: Minor Reporter: daniel zhang The plugin auto print too much logs in console output and when remote trigger begin builds it will print below warning info firstly [WARNING] The attribute "number" was not found. Unexpected response: [WARNING] The attribute "url" was not found. Unexpected response: Add Comment
[JIRA] (JENKINS-58333) Implement Param Validation in Plugin Service
Title: Message Title Jack Shen started work on JENKINS-58333 Change By: Jack Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200445.1562219609000.1559.1562220180202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58334) Add Webpack Config For watch-build
Title: Message Title Jack Shen created an issue Jenkins / JENKINS-58334 Add Webpack Config For watch-build Issue Type: Improvement Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-04 06:02 Labels: gsoc-2019 Priority: Minor Reporter: Jack Shen 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 vi
[JIRA] (JENKINS-58333) Implement Param Validation in Plugin Service
Title: Message Title Jack Shen updated an issue Jenkins / JENKINS-58333 Implement Param Validation in Plugin Service Change By: Jack Shen Issue Type: Improvement New Feature Labels: gsoc-2019 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.200445.1562219609000.1557.1562219880171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57744) Unify timezone when input date
Title: Message Title Jack Shen resolved as Fixed Jenkins / JENKINS-57744 Unify timezone when input date Change By: Jack Shen Status: In Progress 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.199689.1559142427000.1556.1562219820093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58333) Implement Param Validation in Plugin Service
Title: Message Title Jack Shen created an issue Jenkins / JENKINS-58333 Implement Param Validation in Plugin Service Issue Type: Improvement Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-04 05:53 Priority: Minor Reporter: Jack Shen 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.200445.1562219609000.1555.1562219640162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58332) Fix broken promotion duration display
Title: Message Title Tommy Tynjä updated an issue Jenkins / JENKINS-58332 Fix broken promotion duration display Change By: Tommy Tynjä Environment: delivery pipeline plugin 1.3.2 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.200444.156221941.1554.1562219460279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58332) Fix broken promotion duration display
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-58332 Fix broken promotion duration display Issue Type: Bug Assignee: Tommy Tynjä Components: delivery-pipeline-plugin Created: 2019-07-04 05:50 Priority: Minor Reporter: Tommy Tynjä The promotion duration is displayed as NaN because an undefined property was referenced. Reported with a proposed solution in: https://github.com/Diabol/delivery-pipeline-plugin/pull/302 Add Comment This message was sent by Atlassian Jira (v7.11.2#
[JIRA] (JENKINS-58331) Plugin not working with latest RocketChat API
Title: Message Title Martin Reinhardt created an issue Jenkins / JENKINS-58331 Plugin not working with latest RocketChat API Issue Type: Bug Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2019-07-04 04:05 Priority: Blocker Reporter: Martin Reinhardt The Request are timing out, see here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-58330 ChangTest Change By: Joseph Petersen Component/s: _unsorted Component/s: accurev-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200441.1562209278000.1545.1562210100189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Joseph Petersen assigned an issue to Unassigned Jenkins / JENKINS-58330 ChangTest Change By: Joseph Petersen Assignee: Joseph Petersen 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.200441.1562209278000.1547.1562210100219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Chang Yao updated JENKINS-58330 Jenkins / JENKINS-58330 ChangTest Change By: Chang Yao Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200441.1562209278000.1543.1562209380185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Chang Yao created an issue Jenkins / JENKINS-58330 ChangTest Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2019-07-04 03:01 Priority: Minor Reporter: Chang Yao 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.200441.1562209278000.1537.1562209320506%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Chang Yao started work on JENKINS-58330 Change By: Chang Yao Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200441.1562209278000.1539.1562209320541%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Chang Yao updated JENKINS-58330 Jenkins / JENKINS-58330 ChangTest Change By: Chang Yao Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200441.1562209278000.1541.1562209320575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58072) no notification with successful test connection
Title: Message Title Martin Reinhardt updated JENKINS-58072 Jenkins / JENKINS-58072 no notification with successful test connection Change By: Martin Reinhardt 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.200096.156086886.1527.1562208780458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38840) log parser plugin fails on slave node
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-38840 log parser plugin fails on slave node Change By: Martin Reinhardt Assignee: Manuel Recena Soto Martin Reinhardt 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.175248.1475920173000.1530.1562208780499%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57465) Add support for fields in RocketChat attachments
Title: Message Title Martin Reinhardt commented on JENKINS-57465 Re: Add support for fields in RocketChat attachments feel free to sent a PR 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.199325.1557849075000.1521.1562208720218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57465) Add support for fields in RocketChat attachments
Title: Message Title Martin Reinhardt assigned an issue to Brian Jackson Jenkins / JENKINS-57465 Add support for fields in RocketChat attachments Change By: Martin Reinhardt Assignee: Martin Reinhardt Brian Jackson 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.199325.1557849075000.1523.1562208720250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33085) Log Parser Plugin Not Honoring Regex Patterns that Span Multiple Lines in Console Output
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-33085 Log Parser Plugin Not Honoring Regex Patterns that Span Multiple Lines in Console Output Change By: Martin Reinhardt Assignee: Manuel Recena Soto Martin Reinhardt 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.168442.1456158603000.1497.1562208692728%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35265) Parameter showGraphs: true has no effect using Pipeline job
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-35265 Parameter showGraphs: true has no effect using Pipeline job Change By: Martin Reinhardt Assignee: Manuel Recena Soto Martin Reinhardt 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.170968.1464786107000.1491.1562208680898%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Martin Reinhardt Assignee: Manuel Recena Soto Martin Reinhardt 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.168062.1455052339000.1502.1562208692806%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step I see the issue, but how would you pass the login info the step? If we add this feature you also need to pass the login info here.. 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.200423.1562147249000.1484.1562208600365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt assigned an issue to Maxime KILT Jenkins / JENKINS-58315 Allow to customize serverUrl while using rocketSend step Change By: Martin Reinhardt Assignee: Martin Reinhardt Maxime KILT 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.200423.1562147249000.1488.1562208600420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt started work on JENKINS-58315 Change By: Martin Reinhardt Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1486.1562208600392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58329) Added environment variable parsing in file path for App Center Plugin
Title: Message Title Jiuyang Wang created an issue Jenkins / JENKINS-58329 Added environment variable parsing in file path for App Center Plugin Issue Type: Improvement Assignee: Jiuyang Wang Components: appcenter-plugin Created: 2019-07-04 02:13 Priority: Trivial Reporter: Jiuyang Wang A minor commit to enable using environment variable in file path for our daily business. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58191) Get information about security and available updates from CLI w/o installing plugins
Title: Message Title Natasha Stopa started work on JENKINS-58191 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200246.1561482441000.1481.1562203680101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58228) CLI usage doesn't work if typo in args
Title: Message Title Natasha Stopa started work on JENKINS-58228 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200288.156159164.1479.1562198400153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58228) CLI usage doesn't work if typo in args
Title: Message Title Natasha Stopa updated JENKINS-58228 Jenkins / JENKINS-58228 CLI usage doesn't work if typo in args Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200288.156159164.1480.1562198400335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16240) Problem with NOT_BUILT build result
Title: Message Title Metin Savignano edited a comment on JENKINS-16240 Re: Problem with NOT_BUILT build result [~montej]: I don't see how setting this in a pre-build step could help. The problem is that NOT_BUILT is recognized even though only one step in the build has failed. See also [my findings documented here|https://issues.jenkins-ci.org/browse/JENKINS-55816?focusedCommentId=359080&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-359080]. 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.147053.1357137003000.1467.1562192100281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Thanks Pavel Roskin. That's what I was thinking of trying. At least you can test that it works. Would you like to submit a PR for that? If you do, be sure to @mention me (@jeffret-b on GitHub). I'm looking into an ATH test that is supposed to duplicate this issue but I haven't been able to get it configured correctly yet. 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.197354.1549278137000.1452.1562192041244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16240) Problem with NOT_BUILT build result
Title: Message Title Metin Savignano commented on JENKINS-16240 Re: Problem with NOT_BUILT build result Montej Shah: I don't see how a pre-build could help. The problem is that NOT_BUILT is recognized even though only one step in the build has failed. See also my findings documented here. 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.147053.1357137003000.1454.1562192041274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Martin Weber commented on JENKINS-57502 Re: Cmake arguments sometimes are added to path in parallel build Sorry, cannot reproduce the error with Jenkins ver. 2.150.3 and cmake plugin 2.8.1. Does the problem still persist? If so, remove the sourceDir: ".", specification from the script and re-try. If sourceDir is not specified, the workspace-root is used by default. 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.199365.1557999255000.1428.1562183220080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-58328 Add repository browser support (e.g. Fisheye) to pipeline jobs Change By: Mark Waite 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.200437.1562180075000.1426.1562182680182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title Mark Waite updated JENKINS-58328 Jenkins / JENKINS-58328 Add repository browser support (e.g. Fisheye) to pipeline jobs Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200437.1562180075000.1424.1562182620697%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title Mark Waite updated JENKINS-58328 The git step is an intentionally simplified short form of the more general purpose checkout step. It does not include most of the options available from the checkout step, including the repository browser support options. The git step documentation says: Note that this step is shorthand for the generic SCM step: checkout([$class: 'GitSCM', branches: [[name: '*/master']], userRemoteConfigs: [[url: 'http://git-server/user/repository.git']]]) The Pipeline Syntax page in your Jenkins installation will allow you to use the Jenkins UI to define the checkout step. Once defined using the helper in the Pipeline Syntax page, you can paste that text into the job definition. Jenkins / JENKINS-58328 Add repository browser support (e.g. Fisheye) to pipeline jobs Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Matt Sicker commented on JENKINS-55203 Re: Jenkins EC2 plugin prints private key contents in Jenkins log I backported the public security fix to create 1.42.1 and 1.41.1 due to some configuration changes in 1.43 that make it forward incompatible. 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.196273.1544798485000.1418.1562182500093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-55203 Jenkins EC2 plugin prints private key contents in Jenkins log Change By: Matt Sicker Released As: Amazon EC2 plug ec2 - in v1 1 .44 , 1.42.1, 1.41.1 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.196273.1544798485000.1416.1562182440245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54218) Job DSL API in groovy for Office 365 Connector
Title: Message Title Maria Olivero commented on JENKINS-54218 Re: Job DSL API in groovy for Office 365 Connector Any updates on this, its been 8 months 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.194857.1540375036000.1414.1562181120191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58322 Re: IgnoreError step Devin Nusbaum for the declarative input step seems there is not a good solution to catch the ABORT and transform it in another thing, I'll continue playing with it to find a solution. 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.200430.1562161555000.1411.1562180640324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title
Matthew Mallard updated an issue
Jenkins / JENKINS-58328
Add repository browser support (e.g. Fisheye) to pipeline jobs
Change By:
Matthew Mallard
When configuring a freestyle job you have the ability to add a repository browser when selecting Git under source code management. This functionality would be beneficial in pipeline jobs. Example: ?? pipeline {stage ('Checkout develop branch') {steps {git branch: "develop",credentialsId: 'buildit',url: 'ssh://git@my.server.local:7999/project/repo.git'fisheyeUrl: 'https://fisheyeInstance/browse/repo'}} } ??
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.200437.1562180075000.1409.1562180220267%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title
Matthew Mallard updated an issue
Jenkins / JENKINS-58328
Add repository browser support (e.g. Fisheye) to pipeline jobs
Change By:
Matthew Mallard
When configuring a freestyle job you have the ability to add a repository browser when selecting Git under source code management. This functionality would be beneficial in pipeline jobs. Example: ?? pipeline {stage ('Checkout develop branch') {steps {git branch: "develop",credentialsId: 'buildit',url: 'ssh://git@my.server.local:7999/project/repo.git'fisheyeUrl: 'https://fisheyeInstance/browse/repo'}} } ??
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.200437.1562180075000.1407.1562180220229%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title
Matthew Mallard updated an issue
Jenkins / JENKINS-58328
Add repository browser support (e.g. Fisheye) to pipeline jobs
Change By:
Matthew Mallard
When configuring a freestyle job you have the ability to add a repository browser when selecting Git under source code management. This functionality would be beneficial in pipeline jobs. Example: {quote} pipeline {stage ('Checkout develop branch') {steps {git branch: "develop",credentialsId: 'buildit',url: 'ssh://git@my.server.local:7999/project/repo.git'fisheyeUrl: 'https://fisheyeInstance/browse/repo'}} } {quote}
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.200437.1562180075000.1405.1562180160141%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58328) Add repository browser support (e.g. Fisheye) to pipeline jobs
Title: Message Title
Matthew Mallard created an issue
Jenkins / JENKINS-58328
Add repository browser support (e.g. Fisheye) to pipeline jobs
Issue Type:
New Feature
Assignee:
Mark Waite
Components:
git-plugin, pipeline
Created:
2019-07-03 18:54
Priority:
Minor
Reporter:
Matthew Mallard
When configuring a freestyle job you have the ability to add a repository browser when selecting Git under source code management. This functionality would be beneficial in pipeline jobs. Example:
pipeline { stage ('Checkout develop branch') { steps
Unknown macro: { git branch}
} }
Add Comment
[JIRA] (JENKINS-52059) checkout scm step does not populate environment with GIT_*** variables in non-multibranch pipelines
Title: Message Title Amaretto Slim commented on JENKINS-52059 Re: checkout scm step does not populate environment with GIT_*** variables in non-multibranch pipelines Bump 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.191655.1529486575000.1399.1562179801160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52059) checkout scm step does not populate environment with GIT_*** variables in non-multibranch pipelines
Title: Message Title Amaretto Slim updated an issue Jenkins / JENKINS-52059 checkout scm step does not populate environment with GIT_*** variables in non-multibranch pipelines Change By: Amaretto Slim Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191655.1529486575000.1397.1562179801128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title
kyle ian commented on JENKINS-57899
Re: Jira site configuration lost after a reboot
Working off Justin Holzer's workaround, the below worked for me in script console – I also tried this as a file in $JENKINS_HOME/ref/init.groovy.d to get loaded on boot, and it appeared to blow away the site record entirely, so I don't recommend trying that. Opted for new JiraSite to overwrite existing due to lack of setUrl method.
import hudson.plugins.jira.*
jiraSites = JiraGlobalConfiguration.get().getSites()
jiraSites[0] = new JiraSite("https://my-jira-site.atlassian.net/")
jiraSites[0].setCredentialsId("some-credential-id")
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.199864.1559853126000.1390.1562179020329%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58304) Create Java Docs
Title: Message Title Natasha Stopa started work on JENKINS-58304 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200412.156208470.1388.1562178480070%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Mez Pahlan started work on JENKINS-58311 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200419.1562139986000.1387.1562176860285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan closed an issue as Fixed Jenkins / JENKINS-58327 Specify usage instructions Change By: Mez Pahlan 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.200436.1562174694000.1385.1562176800298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Mez Pahlan commented on JENKINS-58311 Re: NotSerializableException when uploading apk with appcenter-plugin Hi Peter Oost thank you for being an early tester for this plugin. I'm not immediately sure why this is happening so will have to take a deeper look into it. I'll update this issue with my findings. Could you let me know your Jenkins setup in the mean time? Single Master or Master + Slave nodes? And are you running Linux / Mac / Windows on these. Many 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.200419.1562139986000.1383.1562176740181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan commented on JENKINS-58327 Re: Specify usage instructions Added usage instructions into the README that will be part of the next release but also the same instructions in the wiki so that users are not waiting. https://wiki.jenkins.io/display/JENKINS/App+Center+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200436.1562174694000.1379.1562176560262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan updated JENKINS-58327 Jenkins / JENKINS-58327 Specify usage instructions Change By: Mez Pahlan Status: In Review 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.200436.1562174694000.1380.1562176560275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan updated JENKINS-58327 Jenkins / JENKINS-58327 Specify usage instructions Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200436.1562174694000.1377.1562175840225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32673) Build Pipeline - Ability to Disable Retry option on a Job
Title: Message Title Ploutarchos Spyridonos commented on JENKINS-32673 Re: Build Pipeline - Ability to Disable Retry option on a Job It would be nice if we can have the ability to disable the button within the job's configuration. This is an example of how the Rebuilder plugin does it: https://wiki.jenkins.io/display/JENKINS/Rebuild+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167825.1453980288000.1370.1562175780265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32673) Build Pipeline - Ability to Disable Retry option on a Job
Title: Message Title Ploutarchos Spyridonos updated an issue Jenkins / JENKINS-32673 Build Pipeline - Ability to Disable Retry option on a Job Change By: Ploutarchos Spyridonos Attachment: example-of-rebuilder-plugin.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167825.1453980288000.1363.1562175720303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan started work on JENKINS-58327 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200436.1562174694000.1361.1562175000178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan commented on JENKINS-55013 Re: support for App Center Hi Adi Ben-Dahan, you're very welcome. I'm looking for early adopters and appreciate the feedback. To save polluting this issue I've created a new issue under JENKINS-58327. Could you follow along there please. 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.196049.1543936697000.1346.1562174882160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan closed an issue as Fixed Jenkins / JENKINS-55013 support for App Center Change By: Mez Pahlan 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.196049.1543936697000.1348.1562174882233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58327) Specify usage instructions
Title: Message Title Mez Pahlan created an issue Jenkins / JENKINS-58327 Specify usage instructions Issue Type: New Feature Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-07-03 17:24 Priority: Minor Reporter: Mez Pahlan Specify quick usage instructions in README and wiki. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-58322 Re: IgnoreError step you are right, this thing does not make sense, it is the same . I did not see it because *catchError* is not available to select in the *Declarative Directive Generator*, you only can select *wramError* 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.200430.1562161555000.1332.1562174340097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58322 Jenkins / JENKINS-58322 IgnoreError step Change By: Ivan Fernandez Calvo Status: In Review Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200430.1562161555000.1329.1562174100304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58322 Re: IgnoreError step you are right, this thing does not make sense, it is the same 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.200430.1562161555000.1328.1562174100292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53772) scoverage report - failed to copy
Title: Message Title Aniket Kulkarni commented on JENKINS-53772 Re: scoverage report - failed to copy HI team, are there any updates on the resolution of this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194281.1537912695000.1326.1562173380434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Christian Molson edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I have a very similar issue, updated all plugins and Jenkins on July 2nd 2019. Here is the stack trace: java.lang.NoSuchFieldError: SIZE at org.jruby.ext.posix.HeapStruct.(HeapStruct.java:52) at org.jruby.ext.posix.LinuxPOSIX.allocateStat(LinuxPOSIX.java:44) at org.jruby.ext.posix.LinuxPOSIX.stat(LinuxPOSIX.java:87) at com.atlassian.ant.tasks.PermissionsUtils.getPermissions(PermissionsUtils.java:21) at com.atlassian.ant.tasks.CopyWithPerms.doFileOperations(CopyWithPerms.java:75) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy$1CopyImpl.doFileOperations(LocalCopy.java:60) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:568) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy.copyAndGetNumbers(LocalCopy.java:83) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:71) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:41) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) It seems that the update of JNA in 2.181 may have caused this for us based on this commit changing SIZE to NATIVE.POINTER_SIZE : [https://github.com/java-native-access/jna/commit/869bb33984a2cf701f9343ea40cca27ffec4be88#diff-d5b04c438e96aeec3c0fdad0596087ee] To get it back up right away I've rolled back to 2.180 for now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Christian Molson commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I have a very similar issue, updated all plugins and Jenkins on July 2nd 2019. Here is the stack trace: java.lang.NoSuchFieldError: SIZE at org.jruby.ext.posix.HeapStruct.(HeapStruct.java:52) at org.jruby.ext.posix.LinuxPOSIX.allocateStat(LinuxPOSIX.java:44) at org.jruby.ext.posix.LinuxPOSIX.stat(LinuxPOSIX.java:87) at com.atlassian.ant.tasks.PermissionsUtils.getPermissions(PermissionsUtils.java:21) at com.atlassian.ant.tasks.CopyWithPerms.doFileOperations(CopyWithPerms.java:75) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy$1CopyImpl.doFileOperations(LocalCopy.java:60) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:568) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy.copyAndGetNumbers(LocalCopy.java:83) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:71) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:41) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) It seems that the update of JNA in 2.181 caused this for us based on this commit: https://github.com/java-native-access/jna/commit/869bb33984a2cf701f9343ea40cca27ffec4be88#diff-d5b04c438e96aeec3c0fdad0596087ee To get it back up right away I've rolled back to 2.180 for now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-32673) Build Pipeline - Ability to Disable Retry option on a Job
Title: Message Title VENKAT KOTHAPALLI updated an issue Jenkins / JENKINS-32673 Build Pipeline - Ability to Disable Retry option on a Job Change By: VENKAT KOTHAPALLI Priority: Major Critical 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.167825.1453980288000.1311.1562171760533%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44001) Jenkins crash with ClosedChannelException
Title: Message Title Todd Densmore edited a comment on JENKINS-44001 Re: Jenkins crash with ClosedChannelException I am experiencing this issue too. My pipeline fails using Kaniko on Kubernetes. Looks like this might have to do with pod resource limits... [https://medium.com/@garunski/closedchannelexception-in-jenkins-with-kubernetes-plugin-a7788f1c62a9] 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.181536.1493771965000.1286.1562171520529%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44001) Jenkins crash with ClosedChannelException
Title: Message Title Todd Densmore commented on JENKINS-44001 Re: Jenkins crash with ClosedChannelException I am experiencing this issue too. My pipeline fails using Kaniko on Kubernetes. 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.181536.1493771965000.1261.1562171340587%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58326) UI Test Capture Plugin is not publishing results on jenkins dashboard
Title: Message Title Anvesh Thada updated an issue Jenkins / JENKINS-58326 UI Test Capture Plugin is not publishing results on jenkins dashboard Change By: Anvesh Thada Attachment: UITestCasePluginDashBoard.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200435.1562170578000.1259.1562170680058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58326) UI Test Capture Plugin is not publishing results on jenkins dashboard
Title: Message Title Anvesh Thada created an issue Jenkins / JENKINS-58326 UI Test Capture Plugin is not publishing results on jenkins dashboard Issue Type: Bug Assignee: Unassigned Attachments: CapturedImage.png, teststream.txt, UITestCapturePluginConfiguration_Jenkins.png Components: ui-samples-plugin Created: 2019-07-03 16:16 Priority: Major Reporter: Anvesh Thada UI Test Capture Plugin is not publishing results on jenkins dashboard after configuring it properly through guidelines given in jenkins wiki page(https://wiki.jenkins.io/display/JENKINS/UI+Test+Capture+Plugin). attached the teststream.txt which is generated through code and also the jenkins configuration for UI Test Capture plugin. Add Comment
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Heiko Nardmann edited a comment on JENKINS-57945 Re: p4 sync corrupts symlinks I have the same problem.Jenkins v2.107.3.P4 plugin v1.10.0. Does v1.10.1 fix that problem? See [https://github.com/jenkinsci/p4-plugin/blob/master/RELEASE.md]. 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.199921.1560203497000.1255.1562168580128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Heiko Nardmann commented on JENKINS-57945 Re: p4 sync corrupts symlinks I have the same problem. Jenkins v2.107.3. P4 plugin v1.10.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.1253.1562168400229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title Bing Shiao commented on JENKINS-54475 Re: p4sync hangs at "p4 sync -f -q" After changing populate method from forceClean to autoClean, I don't see this problem anymore; not sure if it's related or just coincident. populate: forceClean(have: true ...) populate: autoClean(delete: true ...) 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.195241.1541458128000.1249.1562167680209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Tom Kiemes commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes Javier Delgado sorry to bother, but was this developed just for Bitbucket or also for GitHub? I am using version 0.4.0 of "GitHub Commit Skip SCM Behaviour" plugin on a Jenkins connected to GitHub Enterprise and my configuration looks as follows: GitHub Organisation project Build strategies (in this order; not sure if the order is important here): Change requests Regular branches Skip build trigger if commit message contains Pattern : skip The documentation still states, that "The filtering is only performed for change request events, so push events to non-pull requests will be always run". But the same sentence is still in the doc for BitBucket and as far as I understand the discussion, this is working? Any help would be appreciated. Best regards, Tom 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 htt
[JIRA] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Baptiste Mathus updated JENKINS-25046 Jenkins / JENKINS-25046 Cookie header too long, causing a 413 HTTP error Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.158544.1412778026000.1199.1562166486298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Baptiste Mathus assigned an issue to Josh Soref Jenkins / JENKINS-25046 Cookie header too long, causing a 413 HTTP error Change By: Baptiste Mathus Assignee: Josh Soref 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.158544.1412778026000.1113.1562166484989%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Baptiste Mathus started work on JENKINS-25046 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.158544.1412778026000.1156.1562166485779%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title Tomas Kyjovsky updated an issue Jenkins / JENKINS-58325 Some pipeline stages keep running after pipeline build was aborted Change By: Tomas Kyjovsky Environment: Jenkins 2.121.3Pipeline 2.5 Pipeline Model API Durable Task Plugin 1. 3.7 29 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.200434.156216522.1110.1562165880453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52374) Issue with unclosed LDAP connections
Title: Message Title Jeremy Cornett commented on JENKINS-52374 Re: Issue with unclosed LDAP connections Yes, I can confirm this was working on Java 8. Specifically, on 6/4/2019, I upgrade our Jenkins instance from docker jenkins/jenkins:2.164.1 to jenkins/jenkins:2.164.1-jdk11 with active-directory:2.8 to active-directory:2.13. Immediately thereafter, our Jenkins instance started crashing. It took a number of weeks for me diagnose this problem properly, and I subsequently tried upgrading to newer versions of Jenkins and the active-directory plugin. We are now using docker jenkins/jenkins:2.176.1-jdk11 and active-directory:2.16. I finally resolved the issue in our instance by abandoning StartTLS and using LDAPS, as outlined in the plugin documentation. Memory settings, the VM I was using had 2 cores and 12 GB of RAM initially. I thought the problem was a memory issue, so on 6/11/2019, I changed the VM to 4 cores and 16 GB of RAM, but that didn't make a discernible difference. I found that when I monitored top on the VM (CentOS 7.6), memory usage would never go above 4 GB of RAM, but the virtual memory would grow and grow over time. The highest I saw VIRT was about 28 GB. Eventually, I installed the plugin monitoring:1.77.0. This allowed me to see the number of open files and threads, which also allowed me to see threads were Waiting and had similar information as what is on this ticket. When I then disabled StartTLS, the symptom went away completely. 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.192168.1530728155000.1106.1562165880379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title Tomas Kyjovsky assigned an issue to Lucie Votypkova Jenkins / JENKINS-58325 Some pipeline stages keep running after pipeline build was aborted Change By: Tomas Kyjovsky Assignee: Lucie Votypkova 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.200434.156216522.1103.1562165760133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title Tomas K commented on JENKINS-58325 Re: Some pipeline stages keep running after pipeline build was aborted I'm attaching a redacted version of the build console output. There are some error messages like "sh: /home/jenkins/workspace/ ... @tmp/durable-93e804c1/jenkins-result.txt.tmp: No such file or directory" which suggest it could have something to do with the durable task stuff. There is a StackOverflowError at the end of the log showing repeated calls of: org.jenkinsci.plugins.workflow.actions.ErrorAction.isUnserializableException(ErrorAction.java:75) 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.200434.156216522.1101.1562165580053%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title Tomas K created an issue Jenkins / JENKINS-58325 Some pipeline stages keep running after pipeline build was aborted Issue Type: Bug Assignee: Unassigned Attachments: consoleText_redacted.txt Components: pipeline Created: 2019-07-03 14:47 Environment: Jenkins 2.121.3 Pipeline 2.5 Pipeline Model API 1.3.7 Priority: Major Reporter: Tomas K After a pipeline build has been aborted some of its stages are not stopped but keep running. The top-level view of the build is marked as "aborted" however in the Build Steps view some of the stages are still shown as running, and these executions are also visible in the "Build Executor Status" panel on the left side - both global and agent-specific view. So far I have observed 2 such occurences. Add Comment
[JIRA] (JENKINS-58325) Some pipeline stages keep running after pipeline build was aborted
Title: Message Title Tomas K updated an issue Jenkins / JENKINS-58325 Some pipeline stages keep running after pipeline build was aborted Change By: Tomas K Attachment: consoleText_redacted.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200434.156216522.1100.1562165280155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title
Nick Jones edited a comment on JENKINS-55624
Re: Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
I see the same behavior, and it appears to be specific to Freestyle jobs using Git as an SCM; Mercurial and Subversion still present the full list of credentials to choose from. Accordingly, I've added {{git-plugin}} to the Component/s list here.Also, creating a new user and adding credentials are not necessary as part of reproducing this. It is enough to have an existing Freestyle job that uses an existing "username with password" credential for the Git SCM configuration on the job. Simply switching the global build authorization strategy from "Run as SYSTEM" to "Run as Specific User" (and specifying a user, of course) causes the credentials list when configuring a job to be empty. Jobs that were already created (prior to this switch) will have a "{{ - current - }}" option in the list, and will still build (i.e., checkout) properly, but new jobs will only have "{{ - none - }}" and thus will fail.
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.196797.1547654507000.1095.1562164320701%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title
Nick Jones edited a comment on JENKINS-55624
Re: Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
I see the same behavior, and it appears to be specific to Freestyle jobs using Git as an SCM; Mercurial and Subversion still present the full list of credentials to choose from. Accordingly, I've added {{git-plugin}} to the Component/s list here.Also, creating a new user and adding credentials are not necessary as part of reproducing this. It is enough to have an existing Freestyle job that uses an existing "username with password" credential for the Git SCM configuration on the job. Simply switching the global build authorization strategy from "Run as SYSTEM" to "Run as Specific User" (and specifying a user, of course) causes the credentials list when configuring a job to be empty. Jobs that were already created (prior to this switch) will have a " {{ - current - }} " option in the list, and will still build (i.e., checkout) properly, but new jobs will only have " {{ - none - }} " and thus will fail.
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.196797.1547654507000.1093.1562164320627%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title Nick Jones commented on JENKINS-55624 Re: Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set I see the same behavior, and it appears to be specific to Freestyle jobs using Git as an SCM; Mercurial and Subversion still present the full list of credentials to choose from. Accordingly, I've added git-plugin to the Component/s list here. Also, creating a new user and adding credentials are not necessary as part of reproducing this. It is enough to have an existing Freestyle job that uses an existing "username with password" credential for the Git SCM configuration on the job. Simply switching the global build authorization strategy from "Run as SYSTEM" to "Run as Specific User" (and specifying a user, of course) causes the credentials list when configuring a job to be empty. Jobs that were already created (prior to this switch) will have a "- current " option in the list, and will still build (i.e., checkout) properly, but new jobs will only have " none -" and thus will fail. 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.196797.1547654507000.1087.1562164260156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Tzach Yarimi commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Fajran Rusadi is your service creating jobs inside the multibranch folders? Can you please share some code for doing that? 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.181165.1492753177000.986.1562164202165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Ante Kevrić updated an issue Jenkins / JENKINS-58324 HTML report do not show from Jenkins page (html error 404 on page js file) Change By: Ante Kevrić Summary: HTML report do not show from Jenkins page (html error 404 on page js filese file ) 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.200432.1562163785000.984.1562163900112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: Nick Jones Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196797.1547654507000.980.1562163840779%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js filese)
Title: Message Title Ante Kevrić created an issue Jenkins / JENKINS-58324 HTML report do not show from Jenkins page (html error 404 on page js filese) Issue Type: Bug Assignee: Richard Bywater Attachments: file stucture IBM RPT 9_5.PNG, html report in browser served by web server_ibm_rpt_95.PNG, sources_network_ibm_rpt_95.PNG Components: htmlpublisher-plugin Created: 2019-07-03 14:23 Environment: Jenkins 2.165 (master) HTML Publisher plugin 1.18 Win10 64bit (slave) IBM Rational Performance Tester 9.5 Chrome 64 and MS IE11 Labels: htmlpublisher HTML webpage Priority: Major Reporter: Ante Kevrić We have problem when viewing created and published http performance tests reports: its not working when served from Jenkins web server. ... "plugin is using the "Page Title" field as the base path for putting in the report's index.html and the file is not present there" In dev tools (Chrome) when loading page we see: "HTTP ERROR 404" on several files. But physically files are there. So, if we want to open published report directly e.g. from Jenkins as web page then http report won’t show (we see only blank page with title na link on zip) but if then http report is downloaded locally (zi
[JIRA] (JENKINS-18377) Improve the performance when listing many jobs (GSoC 2019, coding phase 2)
Title: Message Title Jesse Glick commented on JENKINS-18377 Re: Improve the performance when listing many jobs (GSoC 2019, coding phase 2) When loading the "Overview" to list all jobs, the loading time is over 60 seconds. Certainly it is good to optimize particular bottlenecks as we find them, but in tandem I would suggest changing the rendering of the dashboard to be progressive so that server-side bottlenecks do not completely prevent display nor block the user from initiating unrelated actions (like clicking on the sidebar). JENKINS-25075 suggests doing this for individual *ListView/column.jelly cells, though you could just as easily render whole rows lazily, ameliorating a bunch of performance problems at once. 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.149684.1371493826000.947.1562162460713%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title
Devin Nusbaum commented on JENKINS-58322
Re: IgnoreError step
Ivan Fernandez Calvo Thanks for the RFE. I'm not quite sure what ignoreErrors is doing in your example, it looks like a block scope step because it is in options, but by your description it sounds like a basic step like unstable? If I understand correctly, maybe better to just add option to the unstable step, so it could be used like this:
unstable(message: "Release candidate was not uploaded", setBuildResult: false)
If you mean for ignoreErrors to act like catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'), I think you could just put that in options today, like this (untested):
options {
catchError(message: 'Release Candidate was not uploaded', buildResult: 'SUCCESS', stageResult: 'UNSTABLE')
}
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.200430.1562161555000.944.1562162160201%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58323) Be able to creating groups in jenkins server which integrated with LDAP for autentication
Title: Message Title venu k created an issue Jenkins / JENKINS-58323 Be able to creating groups in jenkins server which integrated with LDAP for autentication Issue Type: Task Assignee: Unassigned Components: jenkins-flowdock Created: 2019-07-03 13:53 Environment: UAT Priority: Blocker Reporter: venu k We have requirement to create groups in jenkins server( which is having integrated with LDAP/AD). every time asking Active directory management team to add users to group or creating group, we want to create groups in Jenkins( that server is already authenticating with AD/LDAP) Add Comment
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-58322 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200430.1562161555000.939.1562162041269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58322 Jenkins / JENKINS-58322 IgnoreError step Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200430.1562161555000.940.1562162041330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58322) IgnoreError step
Title: Message Title
Ivan Fernandez Calvo created an issue
Jenkins / JENKINS-58322
IgnoreError step
Issue Type:
New Feature
Assignee:
Ivan Fernandez Calvo
Components:
workflow-basic-steps-plugin
Created:
2019-07-03 13:45
Priority:
Minor
Reporter:
Ivan Fernandez Calvo
On the issue https://issues.jenkins-ci.org/browse/JENKINS-45579 Devin Nusbaum has added a couple of really nice steps WarnErrorStep and CatchErrorStep, this improvement is a continuation of his work (mostly copy) to add another user case, when you need to ignore the failure of a stage but you want to mar the build as successful and it is not possible to use CatchErrorStep or you want to simplify your stage code, something like the following stage that it is waiting for an input on declarative where you can not use CatchErrorStep for the input, ignoreErrors option would mark the build as SUCCESS and the stage as UNSTABLE.
stage('Release Candidate') {
agent any
options {
ignoreErrors('Release Candidate was not uploaded')
}
input {
message 'Should we upload the Release Candidate version?'
ok 'Yes, we should.'
}
when {
beforeAgent true
beforeInput true
anyOf {
tag "rc-\\d+\\.\\d+\\.\\d+*"
}
}
steps {
echo "My Release Candidate process"
}
}
[JIRA] (JENKINS-58314) Job-dsl support for organizationFolder: DslFactory
Title: Message Title Daniel Spilker updated JENKINS-58314 Jenkins / JENKINS-58314 Job-dsl support for organizationFolder: DslFactory Change By: Daniel Spilker Status: Open Fixed but Unreleased Resolution: Duplicate 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.200422.1562143038000.937.1562161080963%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
