[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada assigned an issue to Oleg Nenashev Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Change By: P Mdada Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203161.1574059881000.3067.1574147640147%40Atlassian.JIRA.
[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada updated an issue Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Change By: P Mdada Priority: Blocker Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203161.1574059881000.3065.1574147460110%40Atlassian.JIRA.
[JIRA] (JENKINS-49567) Automatically support docker networks in pipelines with multiple containers
Title: Message Title Vivek Anand commented on JENKINS-49567 Re: Automatically support docker networks in pipelines with multiple containers I was looking for the exact same thing, but then we could use the docker.withRun to start a container(pause container) and then join all the other containers to the pause container network. This gives us the benefit of not having to remember to delete the network and is similar to how AWS fargate or Kubernetes does the networking to provide inter container communciation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188477.151865502.3058.1574146980337%40Atlassian.JIRA.
[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Roy Lu commented on JENKINS-60174 Re: To be able to inform test version executed Hi Sergio Cuenca, There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run? Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong. BR, Roy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3056.1574146200151%40Atlassian.JIRA.
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Mark Waite edited a comment on JENKINS-43818 Re: Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin No fix is planned for this issue by me. I don't recognize your reference to JENKINS-14276.patch. Instructions for building the Git plugin are included in its [CONTRIBUTING|https://github.com/jenkinsci/git-plugin/blob/master/CONTRIBUTING.adoc#contributing-to-the-git-plugin] file. Instructions for building the git client plugin are included in its [CONTRIBUTING|https://github.com/jenkinsci/git-client-plugin/blob/master/CONTRIBUTING.adoc#contributing-to-the-git-client-plugin] file. After looking at the history of JENKINS-14276 and its related bugs, I doubt any patches from that bug or its related bugs will help with this issue. This issue is requesting parameter expansion for pipeline jobs which use lightweight checkout to obtain the Jenkinsfile. I doubt those changes from 2015 will help with lightweight checkout in pipelines. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181336.1493119364000.3050.1574144700300%40Atlassian.JIRA.
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Mark Waite commented on JENKINS-43818 Re: Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin No fix is planned for this issue by me. I don't recognize your reference to JENKINS-14276.patch. Instructions for building the Git plugin are included in its CONTRIBUTING file. Instructions for building the git client plugin are included in its CONTRIBUTING file. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181336.1493119364000.3044.1574144400163%40Atlassian.JIRA.
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Mark Waite updated JENKINS-43818 Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181336.1493119364000.3038.1574144281249%40Atlassian.JIRA.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Fabrice Pipart commented on JENKINS-50429 Re: Shell command are really slower than before Hi! As far as I'm concerned, this issue has been solved. You can have a look at the mentioned Pull Request(s) mentioned above if you're interested to implement a similar fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189484.1522154059000.3019.1574143820702%40Atlassian.JIRA.
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Arun Subbaramu commented on JENKINS-43818 Re: Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Is the fix for this issue planned anytime soon or if the issue is not fixed how do we fix the the issue by applying this patch [^JENKINS-14276.patch] Any pointers greatly appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181336.1493119364000.3012.1574140740235%40Atlassian.JIRA.
[JIRA] (JENKINS-59900) Jenkins web interfece down
Title: Message Title Владислав Ненашев commented on JENKINS-59900 Re: Jenkins web interfece down I got a similar problem on another instance[^Legacy_jstackjava1] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202647.1571826147000.3000.1574137320105%40Atlassian.JIRA.
[JIRA] (JENKINS-59900) Jenkins web interfece down
Title: Message Title Владислав Ненашев updated an issue Jenkins / JENKINS-59900 Jenkins web interfece down Change By: Владислав Ненашев Attachment: Legacy_jstackjava1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202647.1571826147000.3001.1574137320152%40Atlassian.JIRA.
[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Roy Lu assigned an issue to Roy Lu Jenkins / JENKINS-60174 To be able to inform test version executed Change By: Roy Lu Assignee: Maria Narcisa Galan Roy Lu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.2999.1574129400374%40Atlassian.JIRA.
[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder
Title: Message Title Roy Lu assigned an issue to Roy Lu Jenkins / JENKINS-60175 To be able to define test cases in hierarchy folder Change By: Roy Lu Assignee: Maria Narcisa Galan Roy Lu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2996.1574129400321%40Atlassian.JIRA.
[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder
Title: Message Title Roy Lu edited a comment on JENKINS-60175 Re: To be able to define test cases in hierarchy folder Hi [~scuenca],1. Are you saying the tests were uploaded to Root/Automated tests/ and either to Root/Automated/Module 1, Root/Automated/Module 2, Root/Automated/Module 3?2. As I remember Currently only one path you can define in Jenkins plugin. For example here's Root/Automated tests/. IF If you want to define multiple patchs, while which folder would you like the different tests being uploaded to? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2993.1574129340215%40Atlassian.JIRA.
[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder
Title: Message Title Roy Lu commented on JENKINS-60175 Re: To be able to define test cases in hierarchy folder Hi Sergio Cuenca, 1. Are you saying the tests were uploaded to Root/Automated tests/ and either to Root/Automated/Module 1, Root/Automated/Module 2, Root/Automated/Module 3? 2. As I remember only one path you can define in Jenkins plugin. For example here's Root/Automated tests/. IF you want to define multiple patchs, while folder would you like the different tests being uploaded to? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2990.1574129281199%40Atlassian.JIRA.
[JIRA] (JENKINS-60207) JVM crash on Jenkins 2.190.2 with OpenJDK 8.0_222-b10
Title: Message Title Jurgen Bergmann created an issue Jenkins / JENKINS-60207 JVM crash on Jenkins 2.190.2 with OpenJDK 8.0_222-b10 Issue Type: Bug Assignee: Unassigned Attachments: hs_err_pid1936.log, Jenkins master plugin report.pdf Components: core Created: 2019-11-19 01:55 Environment: Jenkins: 2.190.2 JVM: OpenJDK 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10 OS: Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-69-generic x86_64) see list of plugins in description Priority: Major Reporter: Jurgen Bergmann We had now twice a JVM crash after moving our jenkins master to a new workstation. The last crash happen on Saturday in the following environment: Jenkins: 2.190.2 JVM: OpenJDK 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10 OS: Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-69-generic x86_64) The previous jvm crash occurred on Wed 10/30: Jenkins: 2.190.1 JVM: OpenJDK 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10 OS: Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-69-generic x86_64) The last crash had the following info: A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f819a906076, pid=1936, tid=0x7f817e33a700 # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
[JIRA] (JENKINS-58147) Support Different Formats for Listing Plugins to be Downloaded
Title: Message Title Natasha Stopa updated JENKINS-58147 Tool now accepts yaml format. Jenkins / JENKINS-58147 Support Different Formats for Listing Plugins to be Downloaded Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58147) Support Different Formats for Listing Plugins to be Downloaded
Title: Message Title Natasha Stopa updated JENKINS-58147 Jenkins / JENKINS-58147 Support Different Formats for Listing Plugins to be Downloaded Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200192.1561139309000.2984.1574122320290%40Atlassian.JIRA.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title Falko Modler commented on JENKINS-43758 Re: Parameters disappear from pipeline job after running the job Annother super annoyed user here (sorry to say that, but that's just the truth). We are setting up most of our jobs via JCasC (which wraps JobDSL) and every single time we execute our JCasC yaml files, all properties that are defined by the respective pipeline scripts are lost: parameters, triggers, sidebar links etc. Losing parameters of jobs that are triggered not by human project members but by other systems/scripts (e.g. Pull Request Notifier for Bitbucket Server) is especially painful. Those jobs frequently triggered by human project members will sooner or later re-receive their parameters because someone will just click "Build Now" eventually but those jobs triggered from outside will just never run (rejected because of "unknown" parameters?). Every single time we execute our JCasC scripts we have to go through a list of jobs and "fix" them by clicking "Build Now". Yes, we could write a script for that but some jobs don't have parameters. Instead they need to have their scm-polling re-initialized. Since some of those jobs run for many hours, so we need to abort them right away. Writing a script for all those cases feels like investing too much time on the wrong end of the problem. I am willing to contribute a fix but where to start? What is the right approach? Should we start with an opt-in to preserve (instead of wipe) parameters, triggers etc.? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60205) Optional dependencies should be considered when resolving version
Title: Message Title Alex Earl commented on JENKINS-60205 Re: Optional dependencies should be considered when resolving version I believe this is happening because matrix-project is an optional dependency of the git plugin and the plugin-installation-manager doesn't not deal with optional dependencies (from what I can gather). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203176.157410471.2959.1574117220234%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Mark Waite stopped work on JENKINS-60203 Change By: Mark Waite Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2953.1574113920359%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Mark Waite updated JENKINS-60203 Jenkins / JENKINS-60203 Git client plugin 3.0 fails to load trilead class Change By: Mark Waite Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2951.1574113920332%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Ok it looks like something which is configured on the multibranch configuration is causing this error. I removed now all advanced options apart from Advanced sub-modules behaviours from a copy of the original jobs and it works. I will have a look tomorrow, what is causing this error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2946.1574113620195%40Atlassian.JIRA.
[JIRA] (JENKINS-59968) Variable expansion in string cause exception for pipelines
Title: Message Title Devin Nusbaum commented on JENKINS-59968 Re: Variable expansion in string cause exception for pipelines What version of script-security are you running? My best guess is that you are managing dependencies manually and have an old version of script-security installed. scripts-security includes groovy-sandbox as a dependency, and it is the library that defines the method from the NoSuchMethodError. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202772.1572337231000.2948.1574113620221%40Atlassian.JIRA.
[JIRA] (JENKINS-60027) Use correct separator character for Windows
Title: Message Title Mez Pahlan updated JENKINS-60027 Jenkins / JENKINS-60027 Use correct separator character for Windows Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Resolution: Fixed Done Released As: 0.8.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202852.1572697791000.2944.1574113321661%40Atlassian.JIRA.
[JIRA] (JENKINS-59942) Add stats badges to README
Title: Message Title Mez Pahlan updated JENKINS-59942 Jenkins / JENKINS-59942 Add stats badges to README Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Resolution: Fixed Done Released As: 0.8.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202746.1572077923000.2943.1574113321639%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan updated JENKINS-59694 Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Resolution: Fixed Done Released As: 0.8.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202393.1570520886000.2935.1574113321428%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan updated JENKINS-60197 Jenkins / JENKINS-60197 Support macOS applications upload Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Resolution: Fixed Done Released As: 0.8.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2932.1574113321382%40Atlassian.JIRA.
[JIRA] (JENKINS-58490) Support symbol file upload
Title: Message Title Mez Pahlan updated JENKINS-58490 Jenkins / JENKINS-58490 Support symbol file upload Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Resolution: Fixed Done Released As: 0.8.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200628.1563184462000.2941.1574113321581%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules I attempted to duplicate the problem using a multibranch pipeline and was unsuccessful. My guess is that the issue is either somehow specific to the multibranch pipeline configuration you are using or is connected to an existing workspace from a prior build of the same job which is being reused by the pipeline job. If you run the same multibranch pipeline job in parallel, does the failure happen on all the jobs running in parallel, or only on the first job that was started? When multiple jobs run in parallel, Jenkins allocates a new workspace for the parallel jobs so that they will not collide with running jobs,. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2927.1574112840203%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title René Scheibe commented on JENKINS-56569 Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set Above I also linked JENKINS-45228 which is about git LFS at merge time. (This here is about git LFS at checkout time). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198184.1552593939000.2928.1574112840218%40Atlassian.JIRA.
[JIRA] (JENKINS-60206) When using Fall-back user confuration for Active Directory plugin crashes
Title: Message Title James Hanley created an issue Jenkins / JENKINS-60206 When using Fall-back user confuration for Active Directory plugin crashes Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-11-18 21:32 Labels: plugin configuration security Priority: Critical Reporter: James Hanley When testing the base case of configuring Active Directory without a binding and using fall-back user, system crashes. java.lang.NullPointerException at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:223) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-60163) Support pagination by providing Next Page link
Title: Message Title Owen Wood commented on JENKINS-60163 Re: Support pagination by providing Next Page link Baptiste Mathus Basically, there are no navigation links. Users are unable to navigate to a "Next" or "Previous" page when there are more results than a single page. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203115.157370392.2921.1574112720325%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title René Scheibe commented on JENKINS-56569 Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set Right, that's a breaking change so to speak. If GIT_LFS_SKIP_SMUDGE=1 is always set to disable any enabled smudge filter and git lfs pull is only performed when the "Git LFS pull after checkout" behaviour is specified, users that currently have the smudge filter enabled via a system/global/local git config would have to change their job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198184.1552593939000.2918.1574112546414%40Atlassian.JIRA.
[JIRA] (JENKINS-53430) Capture logged in username and IP Address Audit Trail Plugin
Title: Message Title Pierre Beitz commented on JENKINS-53430 Re: Capture logged in username and IP Address Audit Trail Plugin Trey Owens as far as I can tell, the current implementation is using the user if available (ie if somebody is logged) falling back to the IP if it's not possible My understanding is that you'd like to see both logged, am I correct? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193623.153616120.2915.1574112120194%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan commented on JENKINS-60197 Re: Support macOS applications upload I think I've added sufficient test coverage for this. But if there is any issue do let me know. I'll be doing a release tonight. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2910.1574112000164%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Looks like this is somehow project type related. The log above is from a multibranch pipeline. If i use a freestyle project the submodules are handled without a problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2911.1574112000186%40Atlassian.JIRA.
[JIRA] (JENKINS-20438) Make it an option to show failed builds in trend graph
Title: Message Title ankush goyal commented on JENKINS-20438 Re: Make it an option to show failed builds in trend graph Nalin Makar i have toggle ON the option "Show failed builds in trend graph", still not able to see the failed build in TestNG result Trend graph Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151959.1383735882000.2905.1574111340350%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Em Jot commented on JENKINS-60197 Re: Support macOS applications upload Great, let me know if you want me to test it Mez Pahlan. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2902.1574109420151%40Atlassian.JIRA.
[JIRA] (JENKINS-60158) ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter
Title: Message Title Damian Szczepanik resolved as Fixed Jenkins / JENKINS-60158 ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter Change By: Damian Szczepanik Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203024.1573655768000.2900.1574109000347%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Serhii Shepel commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Liam Newman could you please provide some info regarding usage and possibilities for the bindings... I can see a bunch of test cases here: (https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/335e44ff6d19cfd43f58be210d9af81e4491cdec/pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/MatrixTest.java), but a bit more details would be nice... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.2898.1574108884868%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Alexander Komarov edited a comment on JENKINS-59790
Re: Container cannot connect to node because it doesn't exist
For those of us that do want to use *JNLP* rather than *Attach* mode, here is a quick and dirty workaround that has proven to stabilize docker launching under heavy load (in my case, a matrix job spawning 70 containers simultaneously). All it does is re-run the JNLP script a few times in case the master wasn't ready. Without this, I was left with a ton of stopped containers and no resources.I simply change the *ENTRYPOINT* in my images from the default (*/usr/local/bin/jenkins-agent* script from [jenkins/jnlp-slave)|https://hub.docker.com/r/jenkinsci/jnlp-slave/] to this script: {code:java}#!/bin/bashACTUAL_ENTRYPOINT=/usr/local/bin/jenkins-slave# sleep between retries, if needed (s)SLEEP= ${JNLP_RETRY_SLEEP:- 5 } # Try to reconnect this many timesTRIES= ${JNLP_RETRY_COUNT:- 3 } # Stop retrying after this many seconds regardlessMAXTIME= ${JNLP_RETRY_MAXTIME:- 60 } # Do not retry if we're running bash to debug in this container# more than 1 arg is probably jenkins jnlp startif [ $# -eq 1 ] ; then exec $*fiSTART=$(date +%s)while [ $TRIES -gt 0 ] && [ $(($(date +%s) - $START)) -lt $MAXTIME ] && ! $ACTUAL_ENTRYPOINT "$@" ; do CODE=$? echo "$ACTUAL_ENTRYPOINT exited [$CODE], waiting $SLEEP seconds and retrying" sleep $SLEEP TRIES=$(($TRIES - 1))doneecho "Exiting [$CODE] with $TRIES remaining tries and $(($(date +%s) - $START)) seconds elapsed"exit $CODE{code}and my Dockerfile looks like this:{code:java}FROM jenkins/jnlp-slave # directly or indirectlyCMD [ "/bin/bash" ]ENTRYPOINT [ "entrypoint" ]{code}(My images have bash... for alpine you may want to change the shebang to /bin/sh) For the record, network stability has been an issue for me with *Attach*. Since I'm using classic Swarm, the topology is too complex and the connection is sometimes lost:{noformat}Master -> Swarm Manager -> Docker Host -> Container{noformat}With JNLP, it's simply:{noformat}Container -> Master{noformat} [~oleg_nenashev], perhaps it may be worthwhile to integrate some (better than the above) retry logic in [jenkins-agent script|https://github.com/jenkinsci/docker-jnlp-slave/blob/master/jenkins-agent] or even slave.jar itself? (possibly after identifying the "unknown name" error from the master). Happy to make a PR with some guidance.
Add Comment
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Alexander Komarov edited a comment on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Thanks [~pjdarton] for the reminder. I also added rudimentary configuration for sleep/etc via environment variables. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.2861.1574107860679%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Alexander Komarov commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Thanks pjdarton for the reminder. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.2849.1574107740229%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Alexander Komarov edited a comment on JENKINS-59790
Re: Container cannot connect to node because it doesn't exist
For those of us that do want to use *JNLP* rather than *Attach* mode, here is a quick and dirty workaround that has proven to stabilize docker launching under heavy load (in my case, a matrix job spawning 70 containers simultaneously). All it does is re-run the JNLP script a few times in case the master wasn't ready. Without this, I was left with a ton of stopped containers and no resources.I simply change the *ENTRYPOINT* in my images from the default (*/usr/local/bin/jenkins-agent* script from [jenkins/jnlp-slave)|https://hub.docker.com/r/jenkinsci/jnlp-slave/] to this script: {code:java}#!/bin/bashACTUAL_ENTRYPOINT=/usr/local/bin/jenkins-slave# sleep between retries, if needed (s)SLEEP=5 # Try to reconnect this many timesTRIES=3# Stop retrying after this many seconds regardlessMAXTIME=60# Do not retry if we're running bash to debug in this container# more than 1 arg is probably jenkins jnlp startif [ $# -eq 1 ] ; then exec $*fiSTART=$(date +%s)while [ $TRIES -gt 0 ] && [ $(($(date +%s) - $START)) -lt $MAXTIME ] && ! $ACTUAL_ENTRYPOINT "$ * @ " ; do CODE=$? echo "$ACTUAL_ENTRYPOINT exited [$CODE], waiting $SLEEP seconds and retrying" sleep $SLEEP TRIES=$(($TRIES - 1))doneecho "Exiting [$CODE] with $TRIES remaining tries and $(($(date +%s) - $START)) seconds elapsed"exit $CODE{code}and my Dockerfile looks like this:{code:java}FROM jenkins/jnlp-slave # directly or indirectlyCMD [ "/bin/bash" ]ENTRYPOINT [ "entrypoint" ]{code}(My images have bash... for alpine you may want to change the shebang to /bin/sh) For the record, network stability has been an issue for me with *Attach*. Since I'm using classic Swarm, the topology is too complex and the connection is sometimes lost:{noformat}Master -> Swarm Manager -> Docker Host -> Container{noformat}With JNLP, it's simply:{noformat}Container -> Master{noformat} [~oleg_nenashev], perhaps it may be worthwhile to integrate some (better than the above) retry logic in [jenkins-agent script|https://github.com/jenkinsci/docker-jnlp-slave/blob/master/jenkins-agent] or even slave.jar itself? (possibly after identifying the "unknown name" error from the master). Happy to make a PR with some guidance.
Add Comment
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Mark Waite commented on JENKINS-60203 Re: Git client plugin 3.0 fails to load trilead class Java 1.8.0_101 is almost 4 years old (January 2016). The current version is Java 1.8.0_232. There were significant changes in Java 1.8.0 in the 150 / 160 timeframe. I don't know if those changes will affect this issue or not. I'm not aware of any Jenkins developers that test with a Java 8 version which is that old. Even if it does not resolve this issue, you're likely to have a better experience with Jenkins if you're running a current Java version (either OpenJDK or AdoptOpenJDK). Since you're running the most recent command line git on your Windows Server, I assume you're also able to update to the latest AdoptOpenJDK or OpenJDK version. Are you able to duplicate the same problem on another computer? Can you provide the detailed configuration you used to duplicate the problem? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2840.1574107380128%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60204 git plugin 4.0.0 can not handle submodules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2836.1574106960226%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title
Mark Waite edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not handle submodules
The message seems to match with a [stackoverflow question|https://stackoverflow.com/questions/40987847/unable-to-find-current-origin-master-revision-in-submodule-path], though I'm not sure how to apply the recommended solution from stackoverflow in the case of the git plugin. The git plugin does not allow user control of the specific git commands and does not provide direct access to {{git pull}}The message in the stack trace is:{noformat}hudson.plugins.git.GitException: Command "git submodule update --remote impl/tool_protec" returned status code 1:stdout: stderr: fatal: Needed a single revisionUnable to find current origin/development revision in submodule path 'impl/tool_protec'{noformat}Can you provide enough details so that someone else can duplicate the problem you're seeing? I use submodules in many different tests and they all work as expected with both git plugin 3.12 and 4.0. I'm sure that means there is something missing from my set of tests, but I don't know what that is until I can duplicate the problem you're seeing.If you'd like to provide a test case as a pull request to my repository jenkins-bugs repository on the [JENKINS-60204 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-60204/README.md] , you're welcome to do that . Otherwise, detailed steps and configuration settings that will duplicate the problem will be sufficient.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Larry charbonneau commented on JENKINS-60203 Re: Git client plugin 3.0 fails to load trilead class Java on server: 1.8.0_101 (Oracle) Windows Server 2016 Git on server: 2.24.0.windows.2 Have Git client Plugin 3.0 installed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2834.1574106780243%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules The message seems to match with a stackoverflow question, though I'm not sure how to apply the recommended solution from stackoverflow in the case of the git plugin. The git plugin does not allow user control of the specific git commands and does not provide direct access to git pull The message in the stack trace is: hudson.plugins.git.GitException: Command "git submodule update --remote impl/tool_protec" returned status code 1: stdout: stderr: fatal: Needed a single revision Unable to find current origin/development revision in submodule path 'impl/tool_protec' Can you provide enough details so that someone else can duplicate the problem you're seeing? I use submodules in many different tests and they all work as expected with both git plugin 3.12 and 4.0. I'm sure that means there is something missing from my set of tests, but I don't know what that is until I can duplicate the problem you're seeing. If you'd like to provide a test case as a pull request to my repository jenkins-bugs repository on the JENKINS-60204 branch. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-60205) Optional dependencies should be considered when resolving version
Title: Message Title Martin d'Anjou created an issue Jenkins / JENKINS-60205 Optional dependencies should be considered when resolving version Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-11-18 19:18 Labels: plugin-manager Priority: Minor Reporter: Martin d'Anjou The following yaml file results in a bad dependency version for the git plugin: plugins: - artifactId: configuration-as-code source: version: 1.32 - artifactId: git source: version: 4.0.0 - artifactId: workflow-aggregator source: version: 2.6 - artifactId: ssh-slaves source: version: 1.31.0 - artifactId: build-user-vars source: version: 1.5 When Jenkins starts, the following happens: 2019-11-18 15:14:50.418+ [id=33]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Jenkins Git plugin v4.0.0 (git) java.io.IOException: Jenkins Git plugin version 4.0.0 failed to load. - Matrix Project Plugin version 1.4 is older than required. To fix, install version 1.14 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:922) at hudson.PluginManager$2$1$1.run(PluginManager.java:545) at
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Jatin Bedi commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen +1. Any updates on this would be appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.2822.1574104560382%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60203 Git client plugin 3.0 fails to load trilead class Change By: Mark Waite Summary: Git Plugin 4 client plugin 3 .0 is not working fails to load trilead class Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2819.1574104500154%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not handle submodules Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-11-18 18:58 Environment: Jenkins 2.190.2 git-plugin 4.0.0 Priority: Major Reporter: Benjamin Brummer git-plugin 3.12 works without any problem. > git submodule update --remote impl/tool_protec # timeout=10 Error when executing always post condition: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:266) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:263) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite commented on JENKINS-60203 Re: Git Plugin 4.0 is not working Have you installed git client plugin 3.0.0 when you installed git plugin 4.0.0? I assume yes, but since incomplete configuration information is provided in the report, I can't be sure. I assume you're running one of the versions of Java 8 that is available for Windows. Which Java version is it? Which Java provider (Oracle, OpenJDK, AdoptOpenJDK, Amazon Corretto, etc.)? If it is an older Java 8 version, can you try a more recent Java version on a different machine to see if it resolves the issue? If it is a Java 11 version, can you try a Java 8 version on a different machine to see if it resolves the issue? I doubt that the Windows Server version is relevant, but just in case, what is the Windows Server version? I doubt that the Windows Server feature release is relevant, but just in case, what Windows Server feature release are you using? I regularly test agents with Windows 10.0.1903 and have tested previously with Windows 10.0.1809. Incomplete information and screenshots of text are making it more difficult for me to help with this report. Can you provide more detailed configuration information? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Larry charbonneau commented on JENKINS-60203 Re: Git Plugin 4.0 is not working We have the Trilead API Plugin installed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2812.1574102580228%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Larry charbonneau updated an issue Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Change By: Larry charbonneau Attachment: image-2019-11-18-12-42-48-665.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2811.1574102580214%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite updated JENKINS-60203 Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Change By: Mark Waite Status: In Review Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2804.1574102280416%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite updated JENKINS-60203 Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Change By: Mark Waite Resolution: Not A Defect Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2806.1574102280449%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2798.1574102220457%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite commented on JENKINS-60203 Re: Git Plugin 4.0 is not working You'll need to install the "trilead-api" plugin on your Jenkins instance. The trilead-api plugin was extracted from Jenkins core in Jenkins 2.190. Plugins cannot make the trilead-api plugin an explicit dependency without breaking their use on Jenkins versions before 2.190. The git plugin and git client plugin must continue to support Jenkins users on versions prior to 2.190. Thankfully, many users already have the trilead-api plugin installed, so they do not see any problem even with 2.190. Install the trilead-api plugin on your Jenkins instance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2796.1574102220428%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite updated JENKINS-60203 Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2802.1574102220546%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Mark Waite started work on JENKINS-60203 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.2800.1574102220507%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan updated JENKINS-60197 Jenkins / JENKINS-60197 Support macOS applications upload Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2794.1574102040484%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan updated JENKINS-60197 Jenkins / JENKINS-60197 Support macOS applications upload Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2792.1574102040419%40Atlassian.JIRA.
[JIRA] (JENKINS-59977) P4 Plugin creates invalid AppleDouble files
Title: Message Title Joel Brown commented on JENKINS-59977 Re: P4 Plugin creates invalid AppleDouble files This is a P4Java bug and has been reproduced. Perforce internal job number is job100626. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202781.1572367041000.2790.1574101800171%40Atlassian.JIRA.
[JIRA] (JENKINS-59977) P4 Plugin creates invalid AppleDouble files
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-59977 P4 Plugin creates invalid AppleDouble files Change By: Joel Brown Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202781.1572367041000.2786.1574101680264%40Atlassian.JIRA.
[JIRA] (JENKINS-55322) Jenkins' message about JENKINS_HOME is too vague, on the verge of being misleading.
Title: Message Title Mike Tschudi updated an issue Jenkins / JENKINS-55322 Jenkins' message about JENKINS_HOME is too vague, on the verge of being misleading. Change By: Mike Tschudi Comment: I couldn't figure out what was causing the filling up, so I configured my jobs to discard builds older than 4 days and restarted Jenkins; now the warning is gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196410.1545640998000.2783.1574100900210%40Atlassian.JIRA.
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Peter Carenza updated an issue Jenkins / JENKINS-52966 Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Change By: Peter Carenza Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192947.1533846304000.2754.1574100362104%40Atlassian.JIRA.
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Peter Carenza updated an issue Jenkins / JENKINS-52966 Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Change By: Peter Carenza Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192947.1533846304000.2725.1574100301602%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan commented on JENKINS-60197 Re: Support macOS applications upload So it looks like whilst we don't officially support MacOS files we don't restrict them either. At least from the point of view of uploading the app. It's only when we try and upload debug symbols do we face an issue. In other words, this might be easy enough to implement! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2718.1574098980908%40Atlassian.JIRA.
[JIRA] (JENKINS-60203) Git Plugin 4.0 is not working
Title: Message Title Larry charbonneau created an issue Jenkins / JENKINS-60203 Git Plugin 4.0 is not working Issue Type: Bug Assignee: Mark Waite Attachments: image-2019-11-18-11-42-11-178.png, image-2019-11-18-11-42-32-578.png Components: git-plugin Created: 2019-11-18 17:42 Environment: Jenkins (2.190.2) running on Windows Server Git Plugin 4.0 Firefox Browser Labels: plugin git Priority: Minor Reporter: Larry charbonneau We have been running Jenkins and pulling using Git. Updated Git plugin from 3.12.1 to version 4.0.0. We now see these two errors when attempting to pull using Git. Add Comment
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Josh Brozen commented on JENKINS-60008 Re: Build fails due to Distribution Group in AppCenter not having Correct Permissions Mez Pahlan - I honestly think Microsoft should fill the gap and figure out distribution groups strategy - it seems very backwards right now (also so that it is in feature parity with HockeyApp - why provide a Distribution Group access to the app to only force the build process to then set the specific distribution again?) In terms of the Jenkins plug-in, can you please (at least) output to console log whatever Distribution Groups failed to gain access to the build via distribution? I don't even know if that should mark the Jenkins build as a "failure" - it just failed to distribute but the job was successful and did actually upload the build to AppCenter (it just didn't get distributed properly due to an issue with AppCenter). Thanks and please let me know if you have any other questions. -Josh Brozen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202825.1572558119000.2716.1574098920136%40Atlassian.JIRA.
[JIRA] (JENKINS-60202) Error when --Jenkins-update-manager value has trailing slash
Title: Message Title leemeador created an issue Jenkins / JENKINS-60202 Error when --Jenkins-update-manager value has trailing slash Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-11-18 17:36 Labels: plugin-manager Priority: Minor Reporter: leemeador Command line like this: java -jar jenkins-plugin-manager-1.0.1.jar -f plugins.txt --verbose --plugin-download-directory ~/plugins --no-download --list --war /usr/lib/jenkins/jenkins.war --jenkins-update-center https://jenkins-updates.cloudbees.com/ fails with stack trace containing java.io.FileNotFoundException: https://jenkins-updates.cloudbees.com//update-center.json Remove the trailing slash from the desired update center and it accepts the supplied update center. (This is the workaround) Add Comment
[JIRA] (JENKINS-55322) Jenkins' message about JENKINS_HOME is too vague, on the verge of being misleading.
Title: Message Title Mike Tschudi commented on JENKINS-55322 Re: Jenkins' message about JENKINS_HOME is too vague, on the verge of being misleading. I couldn't figure out what was causing the filling up, so I configured my jobs to discard builds older than 4 days and restarted Jenkins; now the warning is gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196410.1545640998000.2711.1574098320232%40Atlassian.JIRA.
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Mez Pahlan started work on JENKINS-60197 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.2709.1574097960172%40Atlassian.JIRA.
[JIRA] (JENKINS-58490) Support symbol file upload
Title: Message Title Mez Pahlan updated JENKINS-58490 Jenkins / JENKINS-58490 Support symbol file upload Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200628.1563184462000.2704.1574097842367%40Atlassian.JIRA.
[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes
Title: Message Title Steve Teti commented on JENKINS-56770 Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes I can confirm that the latest master (83a8c0a) fixed this issue for me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198414.155366818.2693.1574097360384%40Atlassian.JIRA.
[JIRA] (JENKINS-59764) Connection timeout is not honored
Title: Message Title pjdarton updated JENKINS-59764 PR has been merged. Will be FITNR. Jenkins / JENKINS-59764 Connection timeout is not honored Change By: pjdarton Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Liam Newman commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline You can pull 1.5.0-beta1 from the experimental update site now to take a look at matrix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.2653.1574094962079%40Atlassian.JIRA.
[JIRA] (JENKINS-60201) On parametric selection based on products
Title: Message Title z cloud assigned an issue to z cloud Jenkins / JENKINS-60201 On parametric selection based on products Change By: z cloud Assignee: z cloud Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203172.1574094097000.2641.1574094360122%40Atlassian.JIRA.
[JIRA] (JENKINS-60201) On parametric selection based on products
Title: Message Title z cloud assigned an issue to Unassigned Jenkins / JENKINS-60201 On parametric selection based on products Change By: z cloud Assignee: z cloud Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203172.1574094097000.2642.1574094360178%40Atlassian.JIRA.
[JIRA] (JENKINS-60201) On parametric selection based on products
Title: Message Title z cloud updated an issue Jenkins / JENKINS-60201 On parametric selection based on products Change By: z cloud Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203172.1574094097000.2634.1574094180210%40Atlassian.JIRA.
[JIRA] (JENKINS-60201) On parametric selection based on products
Title: Message Title z cloud updated an issue Jenkins / JENKINS-60201 On parametric selection based on products Change By: z cloud Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203172.1574094097000.2633.1574094180155%40Atlassian.JIRA.
[JIRA] (JENKINS-60201) On parametric selection based on products
Title: Message Title z cloud created an issue Jenkins / JENKINS-60201 On parametric selection based on products Issue Type: Bug Assignee: Unassigned Attachments: image-2019-11-19-00-13-26-271.png, image-2019-11-19-00-17-47-979.png Components: extensible-choice-parameter-plugin Created: 2019-11-18 16:21 Priority: Minor Reporter: z cloud 1、Can I add the option of repo to the item page, because I only want to use a library of the Artifactory to get the version of the artifact.Otherwise, the scope of the voucher is too large to get permission. In addition, can you add global voucher function to Jenkins system configuration so that it can be configured not only through items. 2、Can we cascade and select artifactid to simplify item configuration and avoid creating too many items. Add Comment
[JIRA] (JENKINS-60200) More control over cache
Title: Message Title poh koh created an issue Jenkins / JENKINS-60200 More control over cache Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin Created: 2019-11-18 16:05 Priority: Minor Reporter: poh koh The plugin caches (https://github.com/jenkinsci/github-oauth-plugin/pull/100) some user's information for a period of time. If Github is using SSO for a specific organization, it's possible that user authenticates with Github but has an expired SSO. In such a scenario, the plugin will not be able to receive the list of teams under this organization. This information is then cached for one hour. If the teams are being used in managing permissions, the users will effectively lose all these permissions during this period of time without any way of fixing it (except for restarting jenkins). I hope there can be a way to better manage this cache (option to control the cache time, etc.). Better, if it's possible, to refresh the cache if the user is trying to perform a reauthentication. Add Comment
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title pjdarton commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Note: $@ not $* FYI "$*" will glob all CLI arguments into one argument, which is pretty-much guaranteed to break things (it'll break things if more than one argument was provided), whereas $* would only break things if folks provided arguments containing whitespace. "$@" is the best option when you want to "pass through all arguments as they were provided". TL;DR: Whitespace in arguments is very easy to get wrong Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Alexander Komarov edited a comment on JENKINS-59790
Re: Container cannot connect to node because it doesn't exist
For those of us that do want to use *JNLP* rather than *Attach* mode, here is a quick and dirty workaround that has proven to stabilize docker launching under heavy load (in my case, a matrix job spawning 70 containers simultaneously). All it does is re-run the JNLP script a few times in case the master wasn't ready. Without this, I was left with a ton of stopped containers and no resources.I simply change the *ENTRYPOINT* in my images from the default (*/usr/local/bin/jenkins-agent* script from [jenkins/jnlp-slave)|https://hub.docker.com/r/jenkinsci/jnlp-slave/] to this script: {code:java}#!/bin/bashACTUAL_ENTRYPOINT=/usr/local/bin/jenkins-slave# sleep between retries, if needed (s)SLEEP=5 # Try to reconnect this many timesTRIES=3# Stop retrying after this many seconds regardlessMAXTIME=60# Do not retry if we're running bash to debug in this container# more than 1 arg is probably jenkins jnlp startif [ $# -eq 1 ] ; then exec $*fiSTART=$(date +%s)while [ $TRIES -gt 0 ] && [ $(($(date +%s) - $START)) -lt $MAXTIME ] && ! $ACTUAL_ENTRYPOINT " $* " ; do CODE=$? echo "$ACTUAL_ENTRYPOINT exited [$CODE], waiting $SLEEP seconds and retrying" sleep $SLEEP TRIES=$(($TRIES - 1))doneecho "Exiting [$CODE] with $TRIES remaining tries and $(($(date +%s) - $START)) seconds elapsed"exit $CODE{code}and my Dockerfile looks like this:{code:java}FROM jenkins/jnlp-slave # directly or indirectlyCMD [ "/bin/bash" ]ENTRYPOINT [ "entrypoint" ]{code}(My images have bash... for alpine you may want to change the shebang to /bin/sh) For the record, network stability has been an issue for me with *Attach*. Since I'm using classic Swarm, the topology is too complex and the connection is sometimes lost:{noformat}Master -> Swarm Manager -> Docker Host -> Container{noformat}With JNLP, it's simply:{noformat}Container -> Master{noformat} [~oleg_nenashev], perhaps it may be worthwhile to integrate some (better than the above) retry logic in [jenkins-agent script|https://github.com/jenkinsci/docker-jnlp-slave/blob/master/jenkins-agent] or even slave.jar itself? (possibly after identifying the "unknown name" error from the master). Happy to make a PR with some guidance.
Add Comment
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Alexander Komarov commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Completely agree, pjdarton. The above was meant to be an example of a quick-and-easy fix for my use, not a polished product. Once we get into command-line args territory there is an increase in complexity (like shifting bash args). Currently (with the script behavior hardcoded) I can simply substitute my images in both k8s and docker jenkins plugins, without manually configuring entrypoint command-line args in the UI (using implicit defaults). So basically we agree that this logic would ideally be part of the jnlp image components. Fair point about spaces, I'll edit my code above. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.2600.1574090160258%40Atlassian.JIRA.
[JIRA] (JENKINS-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Daniel Hoerner commented on JENKINS-39107 Re: expose "Stream Codeline" as an environment variable there any news about that? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175527.1476879748000.2594.1574089380244%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
pjdarton commented on JENKINS-59790
Re: Container cannot connect to node because it doesn't exist
Personally, I approve of adding retry logic to pretty-much anything network related. The SSH connection mechanism from Master -> Slave-Node has lots of (configurable) retry logic so there is "prior art" to having this. There's a lot of chicken/egg issues when it comes to starting Jenkins slaves and so it makes a lot of sense to ensure that no aspect of this delicate negotiation process requires things to happen in a specific order. e.g. in the docker-plugin's case, it wants to know the container-ID of the container (which is only available once the "run container" command has returned) to write into the slave node instance before returning it to Jenkins, so it has to start the container before Jenkins gets it ... but if the slave container starts up very quickly then Jenkins might well receive and reject its connection request before Jenkins adds the node to its list of permitted slaves. A retry mechanism would allow an easy workaround for this ... as well as helping with situations where the network between the master and slave is less than perfect. FYI the script I use for starting Windows VMs with the vSphere-plugin (linked to from the vSphere plugin's wiki page) that connect via JNLP contains a lot of retry logic and that's proved its worth many times over. What I would recommend, however, is that the number of retries and the delay between retries be made configurable. ...and I'd also recommend that
$ACTUAL_ENTRYPOINT $*
should be changed to
${ACTUAL_ENTRYPOINT} "$@"
so whitespace in arguments gets preserved (something that'd be less of an issue if this retry logic was incorporated in the core /usr/local/bin/jenkins-slave script).
Add Comment
[JIRA] (JENKINS-58682) Global YAML Merge Strategy is not respected
Title: Message Title Vincent Latombe closed an issue as Fixed Jenkins / JENKINS-58682 Global YAML Merge Strategy is not respected Change By: Vincent Latombe Status: Open Closed Resolution: Fixed Released As: 1.21.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200965.1564154658000.2548.1574085000923%40Atlassian.JIRA.
[JIRA] (JENKINS-58682) Global YAML Merge Strategy is not respected
Title: Message Title Vincent Latombe commented on JENKINS-58682 Re: Global YAML Merge Strategy is not respected And it was added through https://github.com/jenkinsci/kubernetes-plugin/pull/638 (1.21.2 and later). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200965.1564154658000.2542.1574084940409%40Atlassian.JIRA.
[JIRA] (JENKINS-58682) Global YAML Merge Strategy is not respected
Title: Message Title Vincent Latombe commented on JENKINS-58682 Re: Global YAML Merge Strategy is not respected however, changing the YAML merge strategy configuration at the cloud level seems to have no effect. Indeed, there is NO global flag to control YAML merge strategy. A pod template controls how it merged with its parent. What is missing here is support of this field for declarative. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200965.1564154658000.2533.1574084880331%40Atlassian.JIRA.
[JIRA] (JENKINS-58682) Global YAML Merge Strategy is not respected
Title: Message Title Vincent Latombe commented on JENKINS-58682 Re: Global YAML Merge Strategy is not respected Allan BURDAJEWICZ what you reproduced is expected, this is the current override behaviour. See https://github.com/jenkinsci/kubernetes-plugin/pull/623/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200965.1564154658000.2528.1574083920654%40Atlassian.JIRA.
[JIRA] (JENKINS-45871) Failed test sets all steps to unstable
Title: Message Title Andrei Gheorghiu reopened an issue The implementation for this is awkward. The junit step does indeed set the stage status to UNSTABLE, but it also quickly sets the whole build status to UNSTABLE. As Jenkins build status can only be changed down (UNSTABLE can not be reverted/changed to SUCCESSFUL, but only to FAILED), this implementation limits functionality. Can the junit plugin only change the status for the stage it is called in? When changing the whole build status to UNSTABLE, the fact that it also changed the stage status is not visible anyway. Jenkins / JENKINS-45871 Failed test sets all steps to unstable Change By: Andrei Gheorghiu Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Dirk Heinrichs commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger Any news on this? We still cannot access promotion logs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.2472.1574081760660%40Atlassian.JIRA.
[JIRA] (JENKINS-56391) Whitespace entered during role assignments is handled inconsistently
Title: Message Title Martin Bickel commented on JENKINS-56391 Re: Whitespace entered during role assignments is handled inconsistently As I was bitten by this problem myself, I've fixed it. Pullrequest is at https://github.com/jenkinsci/role-strategy-plugin/pulls Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197980.1551713695000.2459.1574080500326%40Atlassian.JIRA.
[JIRA] (JENKINS-56391) Whitespace entered during role assignments is handled inconsistently
Title: Message Title Martin Bickel edited a comment on JENKINS-56391 Re: Whitespace entered during role assignments is handled inconsistently As I was bitten by this problem myself, I've fixed it.Pullrequest is at [https://github.com/jenkinsci/role-strategy-plugin/ pulls pull/112 ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197980.1551713695000.2462.1574080500385%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title olli hauer created an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-11-18 12:29 Environment: Jenkins: 2.205 Apache 2.4.41 as reverse proxy Priority: Minor Reporter: olli hauer After the upgrade from 2.204 to 2.205 jenkins redirects to http(s)://127.0.0.1/ after login. Add Comment
