[JIRA] (JENKINS-58424) Error occurred while uploading to Azure - Fail to upload archive to blob
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-58424 Error occurred while uploading to Azure - Fail to upload archive to blob Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.0.3 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.200551.1562760578000.7805.1562824140250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58424) Error occurred while uploading to Azure - Fail to upload archive to blob
Title: Message Title Jie Shen commented on JENKINS-58424 Re: Error occurred while uploading to Azure - Fail to upload archive to blob Thanks for reporting this issue. Fix has been released as 1.0.3. 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.200551.1562760578000.7803.1562824080114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title tanmoy roy commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed Team, Any update on 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.199631.1558935625000.7796.1562821800201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57698) Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem
Title: Message Title tanmoy roy commented on JENKINS-57698 Re: Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem hi Rolando-Mihai Vlad, Some how i was not able to followup with the steps u provided. Request u to please share the .hpi if possible. 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.199636.155895364.7793.1562821740395%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58435) Latest update fails with No Artifactory server configured for null; Duplicate upload server in config
Title: Message Title nag bhushan created an issue Jenkins / JENKINS-58435 Latest update fails with No Artifactory server configured for null; Duplicate upload server in config Issue Type: Bug Assignee: Eyal Ben Moshe Attachments: cred.JPG, job-config.JPG, old-working-config.JPG Components: artifactory-plugin Created: 2019-07-11 05:03 Environment: Jenkins ver: 2.184 Artifactory plugin version: 3.3.2; All other dependent plugin versions are latest. On Ubuntu 16.04.6 LTS xenial Connecting to latest jfrog artifactory. Labels: artifactory-plugin artifactory-plugin_development Priority: Major Reporter: nag bhushan I updated my jenkins to latest (2.184) and installed the artifactory plugin to try out the upload of built binaries from a fresh project. Getting these errors in my job console log: Jenkins Artifactory Plugin version: 3.3.2*09:52:17* No Artifactory server configured for null. Please check your configuration.09:52:17 FATAL: No Artifactory server configured for null. Please check your configuration.09:52:17 java.io.IOException: No Artifactory server configured for null. Please check your configuration.09:52:17 at org.jfrog.hudson.util.RepositoriesUtils.validateServerConfig(RepositoriesUtils.java:191)09:52:17 at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator.setUp(ArtifactoryGenericConfigurator.java:291)09:52:17 at
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title Steve Springett commented on JENKINS-58373 Re: Restore "all" gates to version 5 Pull requests are accepted 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.200494.1562587793000.7789.1562816040176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
Title: Message Title Jeremy Whiting commented on JENKINS-24155 Re: Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot Louis Heche Oleg Nenashev Cesos Barbarino Can one of you do the following. To help narrow down the possible leak areas it will be useful to capture process memory usage and JVM heap usage. Start your master process as normal. Then start 2 tools on the system and redirect the output to separate files. Both tools have low system resource usage. Memory stats can be captured using pidstat. Specifically to capture resident set size. $ pidstat -r -p 8 > /tmp/pidstat-capture.txt JVM heap size and GC behavior. Specifically the percentage of reclaimed heap space after a full collection. $ jstat -gcutil -t -h12 8s > /tmp/jstat-capture.txt Please attach the generated files to 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.156631.1407424853000.7784.1562815321379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Steve Springett commented on JENKINS-58381 Re: Trend graph not appearing I was able to reproduce. The trend graph does not display on pipeline jobs, but does display on other jobs. Will need to investigate. 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.200503.1562595115000.7739.1562815140166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-58381 Trend graph not appearing Change By: Steve Springett Assignee: Steve Springett 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.200503.1562595115000.7741.1562815140193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58424) Error occurred while uploading to Azure - Fail to upload archive to blob
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58424 Error occurred while uploading to Azure - Fail to upload archive to blob Change By: Jie Shen Assignee: Azure DevOps Jie 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.200551.1562760578000.7737.1562810460257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58402) On Windows slaves, any call of dependency check tool results in "The input line is too long" error
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-58402 On Windows slaves, any call of dependency check tool results in "The input line is too long" error Change By: Steve Springett Assignee: Steve Springett 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.200527.1562668975000.7734.1562810400539%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58402) On Windows slaves, any call of dependency check tool results in "The input line is too long" error
Title: Message Title Steve Springett commented on JENKINS-58402 Re: On Windows slaves, any call of dependency check tool results in "The input line is too long" error You can try enabling logging for hudson.* The execution is handled by Jenkins itself, specifically hudson.Launcher.ProcStarter BTW, I've also had issues running 5.1.0, but 5.0.0 works fine in my environment. It might be an issue with the dependency-check script itself, which would be outside of the Jenkins plugin control. 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.200527.1562668975000.7732.1562810400193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58375) Dependency check results rendering error
Title: Message Title Steve Springett closed an issue as Not A Defect This is an issue in the velocity XML template in dependency-check core. You'll need to open a ticket there. Jenkins / JENKINS-58375 Dependency check results rendering error Change By: Steve Springett Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200496.1562589011000.7730.1562809860270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-58387 Quality gates not working as expected Change By: Steve Springett Assignee: Steve Springett 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.200511.1562600834000.7728.1562809140177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title Steve Springett commented on JENKINS-58387 Re: Quality gates not working as expected "When there are two high and seven medium issues, the status is Success" That's interesting and certainly a bug. Let me to and replicate 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.200511.1562600834000.7726.1562809140141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58386) Add v4 xml parser
Title: Message Title Steve Springett closed an issue as Won't Do Jenkins / JENKINS-58386 Add v4 xml parser Change By: Steve Springett Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200510.1562600049000.7720.1562808840347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58400) Fix GitLabBuildStatusNotifier
Title: Message Title Parichay Barpanda commented on JENKINS-58400 Re: Fix GitLabBuildStatusNotifier Fixed enqueue error in 2cc7de2 of https://github.com/baymac/gitlab-branch-source-plugin/pull/22. 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.200525.1562664652000.7715.1562808120042%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55797) Performance: Remove the grantedRoles map from RoleBasedAuthorizationStrategy
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-55797 Performance: Remove the grantedRoles map from RoleBasedAuthorizationStrategy Change By: Parichay Barpanda Sprint: GSoC - 2019. Coding Phase 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.197186.1548590838000.7714.1562808000235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58370) Initial branch indexing log is not formatted
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58370 Initial branch indexing log is not formatted Change By: Parichay Barpanda Sprint: GSoC - 2019. Coding Phase 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.200487.1562460446000.7709.1562807940103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58377) Add instructions for multibranch pipeline jobs
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58377 Add instructions for multibranch pipeline jobs Change By: Parichay Barpanda Sprint: GSoC - 2019. Coding Phase 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.200498.1562590092000.7710.1562807940154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Shah Chowdhury commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. 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.196204.1544601655000.7704.1562806440251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title Shah Chowdhury commented on JENKINS-54763 Re: Branch name disappear after plugin upgrade (>= 2.26) We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. 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.195569.1542867431000.7702.1562806380163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58418) Job named foo.bar and foo_bar causes crash when saving view
Title: Message Title Timothy Bingaman updated JENKINS-58418 Thanks for the PR! Looks good, merged. Jenkins / JENKINS-58418 Job named foo.bar and foo_bar causes crash when saving view Change By: Timothy Bingaman 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.200545.1562743078000.7698.1562802960323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Jesse Glick commented on JENKINS-57631 Re: No credentials found for id I think this is referring to KubectlBuildWrapper on freestyle projects, with the authorize-project plugin enabled. You would need to ensure that the user associated with the project has permission to use those credentials. I do not think this area is tested at all. Sounds similar to JENKINS-48437. Is there a particular way to reproduce from scratch, in a fresh Jenkins installation (say using the mock-security-realm 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.199561.1558603884000.7695.1562801160150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43234) Invalid symlink causing repeated error in log
Title: Message Title James Vaughan commented on JENKINS-43234 Re: Invalid symlink causing repeated error in log I'm running into this same issue, exactly as John described it, except with 10 seconds between errors while jobs are running rather than 2-3 seconds. I'm happy to provide any info that makes it easier to fix this. 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.180356.1490885811000.7691.1562798820128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer commented on JENKINS-57631 Re: No credentials found for id I can reproduce it now: If i configure "Access Control for Builds" under "Global Security", the credentials vanish in the job configuration. If i remove everything under "Access Control for Builds" they reappear. 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.199561.1558603884000.7688.1562797560121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58110) Move "writeFailedPluginsToFile" out of PluginManager
Title: Message Title Natasha Stopa started work on JENKINS-58110 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.200153.1561003808000.7686.1562795940167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58110) Move "writeFailedPluginsToFile" out of PluginManager
Title: Message Title Natasha Stopa commented on JENKINS-58110 Re: Move "writeFailedPluginsToFile" out of PluginManager Removed writing to file in: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/29 Still need to add additional options on how to output failed plugins. 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.200153.1561003808000.7684.1562795880152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58126) Make Parsing for Plugin Manager CLI More Robust
Title: Message Title Natasha Stopa commented on JENKINS-58126 Re: Make Parsing for Plugin Manager CLI More Robust Kept parsing to be on ":", but added checks for blank lines and comments. Partially fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/27, but url input still broken. Fixed again in: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/28 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.200171.156105741.7682.1562795820043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58126) Make Parsing for Plugin Manager CLI More Robust
Title: Message Title Natasha Stopa started work on JENKINS-58126 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.200171.156105741.7681.1562795700086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58241) Support comments to skip line
Title: Message Title Natasha Stopa commented on JENKINS-58241 Re: Support comments to skip line Fixed in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/27 Tested in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/28 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.200304.1561664297000.7676.1562795640249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa started work on JENKINS-58216 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.200276.156156802.7677.1562795640262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa commented on JENKINS-58216 Re: Issues with Failed Download Output File in Docker Fixed in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/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.200276.156156802.7679.1562795640295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58389) Add support for REF environment variable
Title: Message Title Natasha Stopa commented on JENKINS-58389 Re: Add support for REF environment variable Fixed in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/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.200513.1562607059000.7669.1562795520215%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58389) Add support for REF environment variable
Title: Message Title Natasha Stopa started work on JENKINS-58389 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.200513.1562607059000.7670.1562795520259%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58241) Support comments to skip line
Title: Message Title Natasha Stopa started work on JENKINS-58241 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.200304.1561664297000.7672.1562795520298%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58364) Default jenkins.war path only supports *NIX style paths
Title: Message Title Natasha Stopa commented on JENKINS-58364 Re: Default jenkins.war path only supports *NIX style paths Fixed in PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/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.200479.1562342423000.7668.1562795460116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58434) ComputerListener onRemoved
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-58434 ComputerListener onRemoved Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-07-10 21:18 Priority: Minor Reporter: Kanstantsin Shautsou Need a way to close file tied to node. Current ComputerListener has only nofications related to Node (offline/online Computer actions)> Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer edited a comment on JENKINS-57631 Re: No credentials found for id Update: Transfered jenkins again now everything is fine. After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards.!image-2019-07-10-21-53-04-753.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.199561.1558603884000.7663.1562790660242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title Tobias Herrmann Hinz commented on JENKINS-54683 Re: Pods entering error state due to ConnectionRefusalException: Unknown client name see @JENKINS-58409 - facing the same 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.195475.1542484359000.7656.1562790360292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-57631 No credentials found for id Change By: Benjamin Brummer Attachment: image-2019-07-10-21-53-04-753.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.199561.1558603884000.7650.1562788440227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer commented on JENKINS-57631 Re: No credentials found for id After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards. 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.199561.1558603884000.7652.1562788440256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53372) Update Groovy to v2.5.x
Title: Message Title Christian Bongiorno commented on JENKINS-53372 Re: Update Groovy to v2.5.x We are up to 2.5.11 - 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.193459.1535728527000.7643.1562787180177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Jesse Glick commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field I have [the sandbox] disabled, but still from time to time face security (sandbox) related exceptions and I suspect […] that the root cause of all these strange Groovy behaviors are due to the fact that at some point sandbox has been plugged in No. Pipeline script is compiled with either one or two syntax transformers: A CPS transformer, which is always enabled, though it skips methods marked @NonCPS. This permits a build to survive a Jenkins restart. A sandbox transformer, if selected. (Actually it is even a bit more complicated than that: there is a generic sandbox transformer in the script-security plugin which can be applied to any Groovy scripting in Jenkins; and then the workflow-cps plugin includes a hybrid transformer which mixes the CPS transformer with the sandbox transformer.) tl;dr: if you run Pipeline script (including JFR) you are not running plain Groovy, and so there are corner cases where standard language features do not work as expected. Note that, like the sandbox, the CPS transform is pointless for JFR because there is no server to restart; if the JFR JVM dies, your build is dead and that is that. So it would be great to make JFR run your script as plain Groovy. It is not enough to just disable the CPS transformer, though, since the entire execution model of workflow-cps is built to assume this transform. We would need to develop a separate execution engine that just delegates to the default Groovy runtime while offering Pipeline steps and global variables in the binding. Would make JFR faster, smaller, and more usable. There is other stuff that does not add any value in JFR, like the durable-task plugin; it would be simpler and better for sh in JFR to just run the specified command and keep the stdout / stderr file descriptors open using plain old java.lang.Process (or hudson.Proc), like freestyle projects do in hudson.tasks.Shell. Add Comment
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title
Dicom J edited a comment on JENKINS-58414
Re: Property of object, which extends Map, couldn't be accessed
[~jglick], @ notation works, both internally as `def myFooBar() \{ this.@foobar }` and externally as `m.@foobar`.Again, thanks a lot!!!
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.200541.1562704486000.7637.1562785740131%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title
Dicom J commented on JENKINS-58414
Re: Property of object, which extends Map, couldn't be accessed
Jesse Glick, @ notation works, both internally `def myFooBar() { this.@foobar }` and externally as `m.@foobar`. Again, thanks a lot!!!
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.200541.1562704486000.7635.1562785680175%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58433) Plot plugin doesn't display data points from previous builds in case of multiple .properties files
Title: Message Title Jatin Mehta created an issue Jenkins / JENKINS-58433 Plot plugin doesn't display data points from previous builds in case of multiple .properties files Issue Type: Bug Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2019-07-10 18:59 Environment: Plot plugin 2.1.1, Jenkins ver. 2.176.1, Chrome Priority: Major Reporter: Jatin Mehta If a single properties file is provided, previous builds data points are shown. Below is the snippet plot csvFileName: '$WORKSPACE/Throughput_all_plots.csv', group: 'Throughput_Plots', keepRecords: true, //latest data point propertiesSeries: [[file: 'DRThroughputTestReport.properties', label: 'DR_Throughput']], numBuilds: '10', style: 'line', title: 'Throughput_Plot', yaxis: 'RedoLogThroughput(MBps)', yaxisMaximum: '20', yaxisMinimum: '0' But in case of two of them, it only shows current build's data point plot csvFileName: '$WORKSPACE/Throughput_all_plots.csv', group: 'Throughput_Plots', keepRecords: true, propertiesSeries: [[file: 'DRThroughputTestReport.properties', label:
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title Dicom J edited a comment on JENKINS-58414 Re: Property of object, which extends Map, couldn't be accessed [~jglick], thanks , will try 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.200541.1562704486000.7626.1562784900310%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36779) Upgrade Guava or properly isolate core Guava dependency from plugins
Title: Message Title Jesse Glick commented on JENKINS-36779 Re: Upgrade Guava or properly isolate core Guava dependency from plugins See artifact-manager-s3 #83 for an example (again based on the jclouds library, but not using jclouds-plugin) of a case where the bundled Guava made it impossible to do an otherwise straightforward refactoring. 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.172818.1468885385000.7628.1562784900349%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-54683 Pods entering error state due to ConnectionRefusalException: Unknown client name Change By: Carlos Sanchez Summary: Pods entering error statedue to ConnectionRefusalException: Unknown client name 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.195475.1542484359000.7619.1562784690850%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58409) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-58409 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name Change By: Carlos Sanchez Status: Open Closed 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.200536.1562697471000.7621.1562784691530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title Dicom J commented on JENKINS-58414 Re: Property of object, which extends Map, couldn't be accessed Jesse Glick, 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.200541.1562704486000.7611.1562784420172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Jesse Glick, I have never said that I have enabled sandbox anywhere. Actually I have it disabled, but still from time to time face security (sandbox) related exceptions and I suspect (sorry, I shouldn't do that, it's not my business) that the root cause of all these strange Groovy behaviors are due to the fact that at some point sandbox has been plugged in. maybe my suspicions are wrong, again it's not my business, but as I said I have to deal with it. Regarding JFR, I found it as very useful tool in development of pipelines and shared libraries as: 1. Many people run it locally from docker against theirs local codebases of the same project/product. Everybody has it's own Jenkins running without interfering with others. 2. I personally can run it from command line, actually from my vim's command line, it's how I've got used to do actual programming. 3. I personally, don't like to deal with UIs. Also my/our Jenkinsfile comprises just 1 line of code to call the code from shared library, which loads source code base for target project from scm and then looks for *.groovy cicd related modules within that code base and dynamically loads them, looks for required interface inside, and plug them in, in which way actual pipeline is built dynamically (where closures are heavily used). So I really like that JFR exists, in many other products headless part goes first and UI is just an extension of UX. So many thanks to those who've come up with JFR... 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
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Liam Newman assigned an issue to Daniel Spilker Jenkins / JENKINS-39682 Generated Multibranch Pipeline Job does not index branches Change By: Liam Newman Assignee: Stephen Connolly Daniel Spilker 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.176259.1478899646000.7587.1562784300916%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Chris Carr, Jose Valverde I'd like to setup a webex with one of you to investigate further. Can one of you comment in this case then send an email to supp...@perforce.com so I can arrange that. Note: 1.0.2 just shipped today but as far as I know it has no credential related fixes. Thanks in advance. Karl 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.199083.1556813511000.7605.1562784301287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Matt Sicker updated JENKINS-50181 Released in 1.17.1. Jenkins / JENKINS-50181 ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Change By: Matt Sicker Status: Fixed but Unreleased Resolved Released As: ssh-credentials-1.17.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.189200.1521076967000.7547.1562783460743%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Ryan Felder edited a comment on JENKINS-57695 Re: Jira issue not created when jenkins build failed I am also experiencing this, but it is inconsistent.Sometimes I do receive the NullPointerExceptionSometimes a job fails and there is no indication in the logs that anything failed to occur, but a Jira ticket is not created. Sometimes tickets are created as expected. This inconsistent behaviour occurs on projects that have been copied from one another, with no apparent difference in configuration.I am presently tweaking issue type and severity values to see if I can get consistent behaviour but have not found a magic combination yet. I am using Jenkins 2.176.1, Jira Plugin 3.0.8, and I am trying to integrate with a hosted Jira Cloud site. 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.199631.1558935625000.7501.1562783040230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58432) Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL)
Title: Message Title Ariel M created an issue Jenkins / JENKINS-58432 Sonar Quality Gate fails due to wrong call to Json (double backslashes in the URL) Issue Type: Bug Assignee: Rafael Ramos Components: sonar-quality-gates-plugin Created: 2019-07-10 18:14 Priority: Critical Reporter: Ariel M I have Jenkins where all jobs fail in Sonar Quality Gate for the same reason: [Bitbucket] Build result notified hudson.remoting.ProxyException: net.sf.json.JSONException: Invalid JSON String and few lines after it, the next info: Caused: hudson.remoting.ProxyException: java.lang.IllegalStateException: Unable to parse response from http://illin5566.corp.amdocs.com:19090//api/ce/task? id=AWvbAMmYTj8ZIUmGCNc1: I can't understand why I'm getting two backslashes instead of one after the port. I couldn't figure out where it's coming. Below is query is working fine. http://illin5566.corp.amdocs.com:19090/api/ce/task?id=AWvafAKkTj8ZIUmGCNaW Add Comment
[JIRA] (JENKINS-58427) Warnings from parallel build stages are always aggregated
Title: Message Title Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-58427 Warnings from parallel build stages are always aggregated Change By: Ulli Hafner Status: Open Closed 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.200556.1562770948000.7482.1562780880195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title
Jesse Glick commented on JENKINS-58407
Re: Fail to call a Closure stored as a class attribute/field
the real value of pipelines for me is actual ability to program pipelines, put common part into share library etc.
Other than for the sake of compatibility when migrating an existing corpus of Pipeline script from a Jenkins server, there is no real reason for a Jenkinsfile in JFR to be anything more than
node {
checkout scm
sh 'bash run.sh'
}
with all the details being handled by some external programs. This is because the purpose of Pipeline script is to script Jenkins—allocate nodes, publish test or analysis results in visual form, trigger builds of other jobs, accept user input, model structure for Blue Ocean, etc.—none of which is possible inside JFR as currently conceived. (Well, if you had bundled a cloud plugin such as kubernetes, you may be able to script node allocation, in which case parallel + podTemplate + container + node would be an alternative idiom to a direct kubectl run.)
not sure what are actual selling points for sandboxes
The only reason I can think of to enable the sandbox in JFR is to help test behavior of scripts which you also plan to run in a Jenkins server. At any rate, JENKINS-58414 does not sound specific to the sandbox.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-58414) Property of object, which extends Map, couldn't be accessed
Title: Message Title Jesse Glick commented on JENKINS-58414 Re: Property of object, which extends Map, couldn't be accessed As a workaround, check if @ notation (explicit field access) helps. 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.200541.1562704486000.7476.1562779080257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title
Oleg Nenashev commented on JENKINS-58407
Re: Fail to call a Closure stored as a class attribute/field
> Of course using the sandbox at all in JFR is pointless (provides no actual protection), and so I would hope that JFR disables it. There is an opt-out flag for it ("--no-sandbox" flag)
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.200534.1562691597000.7473.1562778060258%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Matt Sicker updated JENKINS-50181 Fixed in PR https://github.com/jenkinsci/ssh-credentials-plugin/pull/33 which was just merged. Jenkins / JENKINS-50181 ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Change By: Matt Sicker 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.189200.1521076967000.7463.1562777880847%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Jesse Glick, thanks for explicit workaround, will follow 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.200534.1562691597000.7458.1562776500247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Devin Nusbaum, exactly, and I'm perfectly fine with that. regarding sandboxes and security in general, IMHO, it's almost nobody needs feature which costs a lot, since it breaks a lot of things. As it lames groovy (just opened another fundamental bug https://issues.jenkins-ci.org/browse/JENKINS-58414, most likely related to your case in bullet #1, Jesse Glick I think this one would be interesting for you) what doesn't allow me to do actual programming job on my CICD pipeline, then at the end I'll have nothing to secure (put in that sandbox), what's the point ? the real value of pipelines for me is actual ability to program pipelines, put common part into share library etc, not secure it, as there're a lot of means for that, e.g. private networks with vpn access, etc. I'm not in Jenkins As A Service business, not sure what are actual selling points for sandboxes. But again if simple groovy stuff doesn't work for me then all other 1K plugins and features are useless/irrelevant and I'd rather go and find other means to fulfill my CI/CD requirements... 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.200534.1562691597000.7454.1562775960215%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58431) Icon for disabled jobs and aborted builds should be different
Title: Message Title Chris Frolik created an issue Jenkins / JENKINS-58431 Icon for disabled jobs and aborted builds should be different Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-10 16:20 Priority: Minor Reporter: Chris Frolik The icons for "aborted build" and "disabled job" are the exact same icon, making them impossible to distinguish. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Jesse Glick commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field I don't think it's a good idea to try to whitelist that method It is not; indeed that method is blacklisted. Of course using the sandbox at all in JFR is pointless (provides no actual protection), and so I would hope that JFR disables it. For the case of the sandbox being used, it is a bug in SandboxInterceptor that Jenkins does not recognize what method is actually being called; there are many such bugs (this one would perhaps be in script-security-plugin). I'm checking to see if there is some way we can detect that jenkinsfile-runner is being used and use that in addition to Main.isUnitTest Better to just fix JENKINS-55764 already than to introduce hacks into other (supported!) components to work around it. Anyway, the root issue here is that JENKINS-31314 is issuing a false positive for what looks like a fairly straightforward case that did not happen to be covered by any of our existing tests. (We have some involving closure calls, but apparently not this precise variant.) Dicom J to give you some background, the Jenkins Groovy interpreter (essentially) is seeing st.aPointerToClosure() and mistakenly assumes that it is about to call a method named aPointerToClosure defined on the type SomeStruct. In fact the byzantine Groovy call dispatch mechanism winds up calling Closure.call instead. The likely workaround is simple enough—be explicit, rather than relying on exotic syntax: st.aPointerToClosure.call() Add Comment
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Igor Kostenko commented on JENKINS-36776 Re: Support Windows Server Containers It is much easier to use docker client for running jobs and deal with corresponding issues (like interrupting job would not stop running container) than to setup Kubernetes cluster just for 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.172815.1468881746000.7385.1562774880929%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Devin Nusbaum commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Dicom J To be clear, I do not think that code is safe in general, as enabling it inside of the sandbox would require whitelisting method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object, which might allow the sandbox to be bypassed (it is on the sandbox blacklist here), but I am not sure if that is relevant in jenkinsfile-runner's security model. My point is just that as far as what JENKINS-31314 is trying to detect, I do not think your code should be triggering a warning. 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.200534.1562691597000.7382.1562774820209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin PS if you use that Throttle Concurrent Builds patch and find that it helps, please comment on the PR. I've been using it successfully for over 6 months and trying to get it merged/released (including asking for the privileges to merge/release it myself) but so far have received no response. 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.194284.1537930113000.7380.1562774760247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Jesse Glick commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Ulad Muraveika good catch. Could you file an issue for this in the WEBSITE project? Of course if you have the time to do it, we welcome PRs updating documentation. (In the case of code samples, this means testing that the proposed syntax actually works in current releases.) 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.160147.1421607875000.7240.1562774703255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Devin Nusbaum, I can live with that message, as you qualified that code as safe to use , since it's a fundamental thing (storing this closure to be called a bit further) around which entire pipeline is built... 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.200534.1562691597000.7237.1562774460132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin I'm not surprised Throttle Concurrent Builds is on the scene of the crime here, but I don't want to jump to any conclusions yet without knowing more details about your configuration. It may or may not be related to the Pipeline race being described here. As an aside, if you're using Throttle Concurrent Builds with categories and Pipeline, you really should be using my patch from throttle-concurrent-builds-plugin#57, which improves CPU usage drastically and also has some correctness benefits. But that may or may not be related to this bug. 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.194284.1537930113000.7235.1562774400299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58258) Record network traffic on ATH
Title: Message Title Jesse Glick updated JENKINS-58258 Jenkins / JENKINS-58258 Record network traffic on ATH Change By: Jesse Glick 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.200322.1561745789000.7229.1562774280328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58258) Record network traffic on ATH
Title: Message Title Jesse Glick started work on JENKINS-58258 Change By: Jesse Glick 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.200322.1561745789000.7227.1562774280301%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Oleg Nenashev commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field There is a bunch of places where isUnitTest is used apparently: https://github.com/search?q=org%3Ajenkinsci+%22main.isUnitTest%22=Code Many of them represent a debug mode (with asserts like in Pipeline CPS), but some actually include the behavior changes. Will need a careful review while removing the flag 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.200534.1562691597000.7225.1562774040160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Devin Nusbaum commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Dicom J There are two problems in this ticket: Your code triggers a warning even though your code itself is not problematic in terms of what JENKINS-31314 is trying to detect, i.e. it is a false positive. What should be a harmless warning printed to the logs is actually causing an exception to be thrown because jenkinsfile-runner activates the flag that gates the strict behavior, breaking your Pipeline. For now I am only concerned about the second point. Even once that is fixed, the warning message will be printed in your logs, it just won't stop the Pipeline from executing. 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.200534.1562691597000.7221.1562773920125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Oleg Nenashev, you guys can figure out your self. Just I'd like to mention that I have tried to apply Main.isUnitTest = false in that place Devin Nusbaum pointed out, it helped, so it works (doesn't throw any exceptions) but anyways it prints that warning, not sure it entirely helped and so only this opt-in flag could mitigate such behavior ... java.lang.IllegalStateException: expected to call SomeStruct.aPointerToClosure but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ But as I said, you are the smart ones 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.200534.1562691597000.7218.1562773620276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Raphael Höser commented on JENKINS-36776 Re: Support Windows Server Containers Guillaume Egles I don't know whether you really need direct docker support, but we moved onto using Kubernetes in our setup - you just need a windows based jnlp container which you insert as "jnlp" into your pod and then you can have windows based kubernetes pods. That way you need one Linux Kube Master Node in your cluster and after that you can mix and match windows and linux containers in seperate pods as you need for your builds. Note for high scalings: Avoid running Linux Containers on Windows nodes, since this is possible with current builds, but the windows process scheduler doesn't handle high core counts well (up to 16 works totally fine). 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.172815.1468881746000.7158.1562773381150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro created an issue Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 2019-07-10 15:40 Labels: plugin Priority: Major Reporter: Johann Moro In one pipeline job, run the same FitNesse tests and generate 2 xml files. So for instance: FitNesse tests on Linux generates fitnesse_linux.xml FitNesse tests on Windows generates fitnesse_windows.xml The way the tests are generated is as follows (same for windows) java -jar ./fitnesse-standalone.jar -c "MySuite?suite=xml" -b fitnesse_windows.xml Now in the pipeline job, the tests are published in this way: step([$class: 'FitnesseResultsRecorder',
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Oleg Nenashev commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field My suggestion is... Disable the strict behavior by default in JFR Introduce an opt-in flag to enable the strict behavior. jenkinsfile Runner test framework may require enabling it by default Fix any regressions which are coming from NOT using isUnitTest = true 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.200534.1562691597000.7151.1562773140232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Oleg Nenashev commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Devin Nusbaum Dicom J Jenkinsfile Runner is in the pre-release state. We can afford any kind of breaking changes there if needed. IMHO no need to apply hacks on the Pipeline side. If you just provide any public API to define whether a strict behavior should be used, I can configure Pipeline in JFR and cut a new release 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.200534.1562691597000.7148.1562772840567%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58407 Fail to call a Closure stored as a class attribute/field Change By: Oleg Nenashev Component/s: jenkinsfile-runner 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.200534.1562691597000.7138.1562772180163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58429) Remove dependency on Matrix Auth from Ownership plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58429 Remove dependency on Matrix Auth from Ownership plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-07-10 15:13 Priority: Minor Reporter: Oleg Nenashev There is a plan to rework Matrix Auth with some breaking changes. Me might be interested to remove the dependency to avoid the issues in the future Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-58428) Remove dependency on Matrix Auth from Role Strategy plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58428 Remove dependency on Matrix Auth from Role Strategy plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-07-10 15:12 Priority: Minor Reporter: Oleg Nenashev There is a plan to rework Matrix Auth with some breaking changes. Me might be interested to remove the dependency to avoid the issues in the future Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-58429) Remove dependency on Matrix Auth from Ownership plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58429 Remove dependency on Matrix Auth from Ownership plugin Change By: Oleg Nenashev Component/s: ownership-plugin Component/s: role-strategy-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.200558.1562771592000.7120.1562771640167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58427) Warnings from parallel build stages are always aggregated
Title: Message Title
Wolfgang Issovits created an issue
Jenkins / JENKINS-58427
Warnings from parallel build stages are always aggregated
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-07-10 15:02
Environment:
Jenkins ver. 2.121.3 Warnings NG Plugin: 5.1.0
Priority:
Minor
Reporter:
Wolfgang Issovits
When using the clang tool for parsing warnings in the console of a parallel pipeline (10 build stages which all generate warnings) the number of warnings are always summed up. It seems that the stage scans always the full console at the point of execution. Note: I am using a scripted pipeline. Is this a known issue or am I doing something wrong? Example code (project_x / project_x_name is different for every parallel stage):
def clangIssues= scanForIssues id: "${project_x}", name: "${project_x_name}", tool: clang(id: "project_x", name: "project_x_name"), aggregateResults: false
publishIssues: issues: [clangIssues], id: "${project_x}", name: "${project_x_name}"
[JIRA] (JENKINS-58405) Backward compatibility of the yaml field merge
Title: Message Title Vincent Latombe updated JENKINS-58405 Jenkins / JENKINS-58405 Backward compatibility of the yaml field merge Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: 1.15.9, 1.17.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.200530.1562684455000.7115.1562770920306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Yes I see (it's hard coded), I just tried to make silly suggestions, but seems like you don't need them (have better ones in mind). Also it looks like it might be just an intermediate solution introduced by the following commit https://github.com/jenkinsci/jenkinsfile-runner/commit/f72641df3f31588c750226ea33c4a4178d8ed39a "JENKINS-54424 - Remove Jenkins Test Harness Dependency & replace by local code". Maybe an owner of that code (Oleg Nenashev), had something in mind, but it's never properly followed up since then, never mind... Anyways, thank you very much, seems like I've blindly picked the right person. I'm really impressed about you taking care of it on so short notice... 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.200534.1562691597000.7113.1562770680109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Devin Nusbaum commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field For now, there is no way to do that. I'm checking to see if there is some way we can detect that jenkinsfile-runner is being used and use that in addition to Main.isUnitTest so that jenkinsfile-runner does not get the strict behavior. 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.200534.1562691597000.7109.1562769960247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta edited a comment on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration [~kamil02], I don't have admin access to restart Jenkins master. Besides, thats only a temporary workaround. If this was a permanent solution, it shouldn't have cropped up for a new project (or same project with its name changed for that matter). It is still a bug. Will try to come up with a more consistent way to produce 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.164818.1441065243000.7097.1562769660434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Devin Nusbaum, Can this value Main.isUnitTest = true for runner come and so be controlled from some external configuration or at least environment variable ? 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.200534.1562691597000.7094.1562769601829%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Jatin Mehta commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration I don't have admin access to restart Jenkins master. Besides, thats only a temporary workaround. If this was a permanent solution, it shouldn't have cropped up for a new project (or same project with its name changed for that matter). It is still a bug. Will try to come up with a more consistent way to produce 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.164818.1441065243000.7082.1562769600942%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Dicom J commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Ok, so how do I make jenkinsfile-runner not to set this into true, as I can see it's hardcoded in there ? since runner doc (https://github.com/jenkinsci/jenkinsfile-runner#jenkinsfile-runner) states that it could be used for Use Jenkins in Function-as-a-Service context My goal is to use it as a function and not mixing with testing of Jenkins itself... 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.200534.1562691597000.7079.1562769300291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Ulad Muraveika commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Guys, it will be cool if you update documentation on https://jenkins.io/doc/pipeline/examples/ page, because bug was fixed and doc right now is confusing novice users >Due to limitations in Workflow - i.e., JENKINS-26481 - it's not really possible to use Groovy closures or syntax that depends on closures, so you can't do the Groovy standard of using .collectEntries on a list and generating the steps as values for the resulting entries. You also can't use the standard Java syntax for For loops - i.e., "for (String s: strings)" - and instead have to use old school counter-based for loops. 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.160147.1421607875000.6944.1562769243301%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Just FYI, we use this to create on-deman Selenium clusters. The test pod has a container for the Selenium hub, and then we spawn a whole bunch of browsers. The browsers are garbage collected by k8s after the test finishes and the test pod is cleaned up by kubernetes-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.200414.1562098146000.6940.1562768880497%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49732) java.util.LinkedHashMap$Entry not serializable in Pipeline
Title: Message Title
Ulad Muraveika edited a comment on JENKINS-49732
Re: java.util.LinkedHashMap$Entry not serializable in Pipeline
Hi [~abayer],It will be very helpful, if you explain why your workaround with groovy closure will work, because I've tried to debug similar code and can see {{java.util.LinkedHashMap$Entry}} variables as well.Does serialization works in different way for variables in closures?My answer: yes, it is working different and it can be used as workaround per fixed https://issues.jenkins-ci.org/browse/JENKINS-26481 Thanks in advance!
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.188674.1519637279000.6938.1562768880454%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Yeah, I think I can put together a simple Jenkinsfile to demonstrate this. I'll post it here when I have one. 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.200414.1562098146000.6932.1562768701163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58407) Fail to call a Closure stored as a class attribute/field
Title: Message Title Devin Nusbaum commented on JENKINS-58407 Re: Fail to call a Closure stored as a class attribute/field Ah, that explains it, jenkinsfile-runner actually sets Main.isUnitTest = true when it runs a Jenkinsfile, because it is based on the Jenkins Test Harness, see here. Also see JENKINS-55764. 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.200534.1562691597000.6930.1562768100119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Jesse Glick commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Deiwin Sarjas do you have a simple way to reproduce this issue, such as a self-contained demo repository? In particular it is not obvious to me how your build pod is creating resources (I suppose using a service account?) and finding its own name/UID to link to. This seems like a rather unusual use case, certainly not one we normally test. We would ideally be able to write a functional test in kubernetes-plugin that fails in master (in the expected way—derivative resource remains after build completion) but passes when the client dependency is updated to include this proposed fix. 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.200414.1562098146000.6928.1562767980153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
