[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Ali Narenji commented on JENKINS-55066 Re: Docker plugin erroneously terminates containers shortly after they start Is there any workaround on the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196118.1544159082000.24783.1560229740121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57949) EC2 plugin not found by install-plugins.sh
Title: Message Title Pablo Gomes Ludermir created an issue Jenkins / JENKINS-57949 EC2 plugin not found by install-plugins.sh Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-06-11 04:16 Priority: Minor Reporter: Pablo Gomes Ludermir I am installing the ec2-plugin (https://github.com/jenkinsci/ec2-plugin) using the install-plugins.sh (in a Dockerfile). The plugins.txt file that I supply to the install script has the plugin listed as "ec2:1.4.3". The plugin is located at http://mirrors.jenkins-ci.org/plugins/ec2/1.43/ec2.hpi (as expected by the plugins.txt). When the install-plugins.sh script looks for it, it attempts to download from a different location. Here are the relevant log messages from the Jenkins installation: Downloading plugin: ec2 from https://updates.jenkins.io/download/plugins/ec2/1.4.3/ec2.hpi ... 03:13:20 Failed in the last attempt (curl -sSfL --connect-timeout 20 --retry 3 --retry-delay 0 --retry-max-time 60 https://updates.jenkins.io/download/plugins/ec2/1.4.3/ec2.hpi -o /usr/share/jenkins/ref/plugins/ec2.jpi) Downloading plugin: ec2-plugin from https://updates.jenkins.io/download/plugins/ec2-plugin/1.4.3/ec2-plugin.hpi ... 03:13:35 Failed in the last attempt (curl -sSfL --connect-timeout 20 --retry 3 --retry-delay 0 --retry-max-time 60 https://updates.jenkins.io/download/plugins/ec2-plugin/1.4.3/ec2-plugin.hpi -o /usr/share/jenkins/ref/plugins/ec2-plugin.jpi) Failed to download plugin: ec2 or ec2-plugin ... Some plugins failed to download! Not downloaded: ec2
[JIRA] (JENKINS-57932) Unstash pipeline step hangs intermittently
Title: Message Title Enrico Mills commented on JENKINS-57932 Re: Unstash pipeline step hangs intermittently Thanks, Jie Shen. Just to be clear, I removed the base prefix entirely after running one pipeline job and the issue still persists. Do you think the base prefix (or my lack of one) is causing the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199906.1560157275000.24743.1560222180542%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57932) Unstash pipeline step hangs intermittently
Title: Message Title Jie Shen commented on JENKINS-57932 Re: Unstash pipeline step hangs intermittently Enrico Mills for now the plugin does not support environment variables for prefix. I will add a check to avoid the confusing error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199906.1560157275000.24741.1560221820100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57947) Managing credentials in JCasC yaml
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57947 Managing credentials in JCasC yaml Change By: Parichay Barpanda Summary: Managing credentials in config as code JCasC yaml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199924.1560215713000.24739.1560221220065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57948) Use regex to compare name field in jcasc
Title: Message Title Parichay Barpanda updated JENKINS-57948 Jenkins / JENKINS-57948 Use regex to compare name field in jcasc Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199925.1560215792000.24730.1560216180089%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57948) Use regex to compare name field in jcasc
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57948 Use regex to compare name field in jcasc Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-11 01:16 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57948) Use regex to compare name field in jcasc
Title: Message Title Parichay Barpanda started work on JENKINS-57948 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199925.1560215792000.24729.1560215820197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57947) Managing credentials in config as code yaml
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57947 Managing credentials in config as code yaml Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-11 01:15 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda The credentials field is being populated using plain text from the config yaml. Need to use a method to securely add credentials. Maybe use a environment variable and populate the environment via REST API. Add Comment
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Parichay Barpanda stopped work on JENKINS-57760 Change By: Parichay Barpanda Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199706.1559207961000.24727.1560215760166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57793) Creates addition empty connection cfg. after applying JCasC
Title: Message Title Owen Mehegan commented on JENKINS-57793 Re: Creates addition empty connection cfg. after applying JCasC Nicolas De Loof do you have any thoughts about why this would happen? The GitLab plugin has not been modified at all to support CasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199742.1559312157000.24723.1560208740212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47561) Pipelines wait indefinitely for kubernetes slaves to come back online
Title: Message Title Rishi Thakkar reopened an issue I still see this issue in the newest version of the plugin. The pod runs out of ephemeral storage and the JNLP agent dies. Then, the build step gets stuck indefinitely. Jenkins / JENKINS-47561 Pipelines wait indefinitely for kubernetes slaves to come back online Change By: Rishi Thakkar Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186028.1508518293000.24720.1560207960436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54540) Pods stuck in error state is not cleaned up
Title: Message Title Rishi Thakkar commented on JENKINS-54540 Re: Pods stuck in error state is not cleaned up I see this issue as well when podRetention is set to never. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195312.1541679013000.24717.1560206820220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57946) No notification when Jenkins fails to check out a pipeline script
Title: Message Title A B created an issue Jenkins / JENKINS-57946 No notification when Jenkins fails to check out a pipeline script Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-06-10 22:36 Priority: Major Reporter: A B Jenkins SCM pipeline doesn't provide any action for when the pipeline script can't be fetched. I only just found out a job (which used to work fine) had been failing for months just because it wasn't able to access its pipeline script from the SCM. It fails the #1 feature of a CI system: notify me when things go wrong. This is a dealbreaker IMHO in terms of making pipeline jobs usable, and violates basic error handling practices (don't ignore errors). There should be way to define notification actions for when the "checking out the pipeline script" step fails. This was using Jenkins 2.138.2 with Pipeline 2.6. Add Comment
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Michael Rose commented on JENKINS-57945 Re: p4 sync corrupts symlinks This issue only started happening after we updated p4 plugin from 1.9.6 to 10.0.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.24712.1560204900105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-57945
p4 sync corrupts symlinks
Change By:
Michael Rose
The "checkout scm" pipeline task when used for the p4plugin intermittently corrupts symlinks. Instead of create a symlink, it seems that the "p4 sync" is create a text file and the content of the file is the destination that the symlink would point to.{quote}*$ ls -l /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf*-r--r--r-- 1 jenkins-agent jenkins 23 Jun 10 09:51 /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf [mrose@bld0010 ~] $ cat /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf no_integ/coverity.conf{quote}When the "checkout scm" works, the output looks like this{quote}*$ ls -l /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf*lrwxrwxrwx. 1 jenkins-agent jenkins 22 May 27 03:08 /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf -> no_integ/coverity.conf{quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-57945
p4 sync corrupts symlinks
Change By:
Michael Rose
The "checkout scm" pipeline task when used for the p4plugin intermittently corrupts symlinks. Instead of create a symlink, it seems that the "p4 sync" is create a text file and the content of the file is the destination that the symlink would point to.{quote}*$ ls -l /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf* -r--r--r-- 1 jenkins-agent jenkins 23 Jun 10 09:51 /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf * $ cat /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf * no_integ/coverity.conf{quote}When the "checkout scm" works, the output looks like this{quote}*$ ls -l /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf* lrwxrwxrwx. 1 jenkins-agent jenkins 22 May 27 03:08 /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf -> no_integ/coverity.conf{quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Michael Rose created an issue Jenkins / JENKINS-57945 p4 sync corrupts symlinks Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 2019-06-10 21:51 Environment: Jenkins ver. 2.138.2 p4 plugin 1.10.0 Priority: Major Reporter: Michael Rose The "checkout scm" pipeline task when used for the p4plugin intermittently corrupts symlinks. Instead of create a symlink, it seems that the "p4 sync" is create a text file and the content of the file is the destination that the symlink would point to. $ ls -l /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf rrr- 1 jenkins-agent jenkins 23 Jun 10 09:51 /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf [mrose@bld0010 ~]$ cat /jenkins/workspace/e_dev-KK246RZWMFT6CWJS6OTBGLMLTACX7NHSGHICXOVCAFVC6S2TK3RA/coverity.conf no_integ/coverity.conf When the "checkout scm" works, the output looks like this $ ls -l /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf lrwxrwxrwx. 1 jenkins-agent jenkins 22 May 27 03:08 /jenkins/workspace/dev-ZKMEBZTMPZSI7NMLJWXPTTFRX3Z67EZAASPHONVQ32DG2EV3MQDQ/coverity.conf -> no_integ/coverity.conf
[JIRA] (JENKINS-55198) java.nio.channels.ClosedChannelException
Title: Message Title Rishi Thakkar commented on JENKINS-55198 Re: java.nio.channels.ClosedChannelException I see a similar issue except it happens randomly at the end of a stage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196266.1544781514000.24702.1560203280169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title Mark Waite edited a comment on JENKINS-54008 Re: Loading library fails - Error fetching remote repo 'origin' [~ilatypov] , thanks for your comments. You said:bq. I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil.I don't want to be evil. I don't want to do things that are evil. However, I don't understand what you envision should happen as an alternative to what happened with this ticket. With this ticket:# [~emchi] reported a problem and provided a stack trace which showed the problem# I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem# I asked some further clarifying questions but received no responses to those clarifying questions or to my original investigation # [~zazzletian] reported a different problem which included a different error message inside a stack trace# I asked [~zazzletian] to submit a different bug report so that independent issues have distinct bug reports,# [~zazzletian] agreed that it was a separate bug report# A month after receiving no answers from [~emchi] on the original questions, I closed the bug because I could not reproduce itThe Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue. It is used by core and many different plugins. It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug. Resolving an issue as "Cannot reproduce" does not hide the issue. It does not prevent the issue from being reopened. It does not prevent someone from reopening it and assigning it to themselves to resolve.If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means. If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug.Can you explain further what you think should have happened in this case and how those different steps would have been better? Add Comment
[JIRA] (JENKINS-57943) Rename package
Title: Message Title Parichay Barpanda updated JENKINS-57943 Jenkins / JENKINS-57943 Rename package Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199919.156020204.24694.1560202800430%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57944) project_name tag set incorrectly
Title: Message Title
Mandy Prescott-Courville created an issue
Jenkins / JENKINS-57944
project_name tag set incorrectly
Issue Type:
Bug
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-06-10 21:39
Environment:
Operating System: Windows 7 Oracle JRE - 1.8.0_201 Jenkins - 2.164.2 InfluxDB plugin - 1.17 Chrome web browser
Priority:
Minor
Reporter:
Mandy Prescott-Courville
Since upgrading from InfluxDB plugin version 1.14 to 1.17 the jenkins_data measurement is now prefixing the project_name tag with an underscore. From a quick look at the source code it appears that when the "replaceDashWithUnderscore" parameter is false (which is the default) then the code assumes you must have a custom prefix and prepends the project_name tag with customPrefix + "_". If your Jenkins job doesn't have a custom prefix you end up with an underscore prefixed to the project name. Looks like the code needs to be changed to something like: String projectTagName; if (this.replaceDashWithUnderscore) { projectTagName = renderedProjectName; } else if (customPrefix != null) { projectTagName = customPrefix + "_" + build.getParent().getName(); } else { projectTagName = build.getParent().getName(); }
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title Mark Waite edited a comment on JENKINS-54008 Re: Loading library fails - Error fetching remote repo 'origin' [~ilatypov] , thanks for your comments. You said:bq. I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil.I don't want to be evil. I don't want to do things that are evil. However, I don't understand what you envision should happen as an alternative to what happened with this ticket. With this ticket:# [~emchi] reported a problem and provided a stack trace which showed the problem# I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem# I asked some further clarifying questions but received no responses to those clarifying questions# [~zazzletian] reported a different problem which included a different error message inside a stack trace# I asked [~zazzletian]to submit a different bug report so that independent issues have distinct bug reports,# [~zazzletian] agreed that it was a separate bug report# A month after receiving no answers from [~emchi] on the original questions, I closed the bug because I could not reproduce itThe Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue. It is used by core and many different plugins. It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug. Resolving an issue as "Cannot reproduce" does not hide the issue. It does not prevent the issue from being reopened. It does not prevent someone from reopening it and assigning it to themselves to resolve.If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means. If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug.Can you explain further what you think should have happened in this case and how those different steps would have been better? Add Comment This message was
[JIRA] (JENKINS-57943) Rename package
Title: Message Title Parichay Barpanda started work on JENKINS-57943 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199919.156020204.24686.1560202080304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57943) Rename package
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57943 Rename package Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-06-10 21:27 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda As discussed with Marky in the gitter chat. The package name for server configuration which was previously `gitlabserver` is now renamed into `gitlabserverconfig`. Add Comment
[JIRA] (JENKINS-46582) stash / unstash pipeline step is not preserving files timestamp
Title: Message Title Spenser Gilliland commented on JENKINS-46582 Re: stash / unstash pipeline step is not preserving files timestamp Hi, just wanted to say that I'm seeing the same issue. Please let me know of any workaround for this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184906.1504242686000.24684.1560201300102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh updated JENKINS-57933 Jenkins / JENKINS-57933 Landing page for build with parameters requires refresh in order to display build flow graph Change By: Gustaf Lundh Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24674.1560200460338%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh commented on JENKINS-57933 Re: Landing page for build with parameters requires refresh in order to display build flow graph In 1.9.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24678.1560200460453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh closed an issue as Fixed Jenkins / JENKINS-57933 Landing page for build with parameters requires refresh in order to display build flow graph Change By: Gustaf Lundh Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24676.1560200460370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh updated JENKINS-57933 Jenkins / JENKINS-57933 Landing page for build with parameters requires refresh in order to display build flow graph Change By: Gustaf Lundh Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24672.1560200100299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57803) Add README to GitHub repository
Title: Message Title Parichay Barpanda updated JENKINS-57803 Jenkins / JENKINS-57803 Add README to GitHub repository Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199754.1559329605000.24664.1560199620295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-57886 Add JCasC config test Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199850.1559832725000.24666.1560199620330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh updated JENKINS-57933 Jenkins / JENKINS-57933 Landing page for build with parameters requires refresh in order to display build flow graph Change By: Gustaf Lundh Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24663.1560199260213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Gustaf Lundh started work on JENKINS-57933 Change By: Gustaf Lundh Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199907.1560159185000.24661.1560198780172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40695) Allow lightweight or remote checkout for Groovy libraries
Title: Message Title Cesar Martinez commented on JENKINS-40695 Re: Allow lightweight or remote checkout for Groovy libraries Similar use case here; I am trying to identify the files changed on my last (git scm) changeset, and perform some greps on them, but they are on a different node. Would it be possible to get an ETA for this? (in case it will be implemented) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177398.1482869335000.24659.1560195300816%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title Mark Waite commented on JENKINS-54008 Re: Loading library fails - Error fetching remote repo 'origin' Ilguiz Latypov , thanks for your comments. You said: I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil. I don't want to be evil. I don't want to do things that are evil. However, I don't understand what you envision should happen as an alternative to what happened with this ticket. With this ticket: m f reported a problem and provided a stack trace which showed the problem I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem I asked some further clarifying questions but received no responses to those clarifying questions Tian Wang reported a different problem which included a different error message inside a stack trace I asked Tian Wangto submit a different bug report so that independent issues have distinct bug reports, Tian Wang agreed that it was a separate bug report A month after receiving no answers from m f on the original questions, I closed the bug because I could not reproduce it The Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue. It is used by core and many different plugins. It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug. Resolving an issue as "Cannot reproduce" does not hide the issue. It does not prevent the issue from being reopened. It does not prevent someone from reopening it and assigning it to themselves to resolve. If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means. If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug. Can you explain further what you think should have happened in this case and how those different steps would have been better? Add Comment
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title Brian Grogan commented on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo I have the same issue with one of the jobs on my Jenkins installation. Error Output from the Console Log > git fetch --tags --progress git@git-server:organization/project.git +refs/heads/:refs/remotes/origin/ ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress git@git-server:organization/project.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: /home/jenkins/workspace/project-name@tmp/ssh8085679836267327653.sh: 6: /home/jenkins/workspace/project-name@tmp/ssh8085679836267327653.sh: ssh: not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Much like John Elion above, when I make a clone of the affected job, the cloned job has the same issue as the original job. If I create an entirely new job, and fill in the configuration values manually, the new job works fine. Somehow, the cloned job is "inheriting" the buggy behavior from its parent. My jobs are the FreeStyle type, and they use the Build Parameters configuration option. On my Jenkins installation, I use the Git plug-in, the Git Client plug-in, and the GitLab plug-in. The Jenkins master and all of the Jenkins slaves run Ubuntu Linux. So far, the only solution to this issue I can find is to manually re-create the affected job (no cloning). Software Versions Jenkins: 2.178 Jenkins Master: Ubuntu 16.04.5 Jenkins Slaves: Ubuntu 16.04.5 Git Plug-in: 3.9.3 Git Client Plug-in: 2.7.7 GitLab Plug-in: 1.5.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title
Paul Borchers updated an issue
Jenkins / JENKINS-57942
Found multiple extensions which provide method originPullRequestDiscoveryTrait
Change By:
Paul Borchers
I'm getting an error "Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait" when I try to use the originPullRequestDiscoveryTrait. I think it could be fixed by adding the @Symbol to [OriginPullRequestDiscoveryTrait.java|#L132].] That's what was done for [BranchDiscoveryTrait.java|https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/BranchDiscoveryTrait.java]. job-dsl usage{quote}{{organizationFolder('Org') {}} {{ organizations {}} {{ github {}} {{ repoOwner('Owner')}} {{ traits {}} {{ originPullRequestDiscoveryTrait()}} \{{ } }} \{{ } }} \{{ } }} {{}}}{quote} Stacktrace...{quote}javaposse.jobdsl.dsl.DslException: Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait, org.jenkinsci.plugins.github_branch_source.OriginPullRequestDiscoveryTrait]] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105){quote}
Add Comment
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title
Paul Borchers updated an issue
Jenkins / JENKINS-57942
Found multiple extensions which provide method originPullRequestDiscoveryTrait
Change By:
Paul Borchers
I'm getting an error "Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait" when I try to use the originPullRequestDiscoveryTrait. I think it could be fixed by adding the @Symbol to [OriginPullRequestDiscoveryTrait.java| [https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/OriginPullRequestDiscoveryTrait.java #L132].] That's what was done for [BranchDiscoveryTrait.java|https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/BranchDiscoveryTrait.java]. job-dsl usage{quote}{{organizationFolder('Org') {}}{{ organizations {}}{{ github {}}{{ repoOwner('Owner')}}{{ traits {}}{{ originPullRequestDiscoveryTrait()}} \ {{ }}} \ {{ }}} \ {{ }}}{{}}}{quote} Stacktrace...{quote}javaposse.jobdsl.dsl.DslException: Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait, org.jenkinsci.plugins.github_branch_source.OriginPullRequestDiscoveryTrait]] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105){quote}
Add Comment
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title
Paul Borchers created an issue
Jenkins / JENKINS-57942
Found multiple extensions which provide method originPullRequestDiscoveryTrait
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2019-06-10 17:23
Environment:
Jenkins version = 2.164.3(docker jenkins/jenkins:lts) Jobdsl version = job-dsl-1.74
Priority:
Major
Reporter:
Paul Borchers
I'm getting an error "Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait" when I try to use the originPullRequestDiscoveryTrait. I think it could be fixed by adding the @Symbol to OriginPullRequestDiscoveryTrait.java That's what was done for BranchDiscoveryTrait.java. job-dsl usage
organizationFolder('Org') { organizations { github { repoOwner('Owner') traits { originPullRequestDiscoveryTrait() {{ }}} {{ }}} {{ }}} }
Stacktrace...
javaposse.jobdsl.dsl.DslException: Found multiple extensions which provide method originPullRequestDiscoveryTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.OriginPullRequestDiscoveryTrait, org.jenkinsci.plugins.github_branch_source.OriginPullRequestDiscoveryTrait]] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at
[JIRA] (JENKINS-56531) org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null
Title: Message Title Adam Brousseau edited a comment on JENKINS-56531 Re: org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null I think this is resolved in 3.2.4 via [ HAP-1167 |https://www.jfrog.com/jira/browse/HAP-1167] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198140.1552421627000.24622.1560185400095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56531) org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null
Title: Message Title Adam Brousseau commented on JENKINS-56531 Re: org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null I think this is resolved in 3.2.4 via [HAP-1167|https://www.jfrog.com/jira/browse/HAP-1167] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198140.1552421627000.24618.1560185340216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56531) org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null
Title: Message Title Adam Brousseau edited a comment on JENKINS-56531 Re: org.jfrog.hudson.pipeline.common.types.ArtifactoryServer getCredentialsId() returns null I think this is resolved in 3.2.4 via [[ HAP-1167 |https://www.jfrog.com/jira/browse/HAP-1167]|[https://www.jfrog.com/jira/browse/HAP-1167]] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198140.1552421627000.24620.1560185340245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan edited a comment on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished Hi [~sophistifunk] -- I can confirm that some completed stages are still showing as transparent, in Blue Ocean 1.17.I think that some parallel stages that had a _single_ stage were previously not showing correctly sometimes, and that seems to have improved.But a stage that has parallel stages that each have _sequential_ stages in them are still showing as transparent when complete, though as before, it paints correctly as soon as the pipeline finishes.For example:---ab---c|---de---fIf d completes, it shows as transparent (incorrect). I'm also now seeing that if " e does show " is active, it sometimes doesn't have the blue animation showing as active (which is correct) . Things may have gotten worse. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194330.153804945.24608.1560184380514%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'
Title: Message Title Ilguiz Latypov commented on JENKINS-54008 Re: Loading library fails - Error fetching remote repo 'origin' I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil. The git plugin seems an utmost importance component of Jenkins. Closing issues or suggesting that reporters re-submit part of them as separate bugs always throws me off as if maintainers are not really to own the code. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194621.1539241642000.24602.1560183420225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Jesse Glick updated JENKINS-46076 Jenkins / JENKINS-46076 Test flake in CpsThreadTest.stop Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.24597.1560183303322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan edited a comment on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished Hi [~sophistifunk] -- I can confirm that some completed stages are still showing as transparent, in Blue Ocean 1.17.I think that some parallel stages that had a single _single_ stage were previously not showing correctly sometimes, and that seems better to have improved .But a stage that has parallel stages that each have _sequential_ stages in them are still showing as transparent when complete, though as before, it paints correctly as soon as the pipeline finishes.For example:---ab---c|---de---fIf d completes, it shows as transparent (incorrect). e does show as active (which is correct). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194330.153804945.24591.1560182820174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan edited a comment on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished Hi [~sophistifunk] -- I can confirm that some completed stages are still showing as parallel transparent , in Blue Ocean 1.17.I think that some parallel stages that had a single stage were previously not showing correctly sometimes, and that seems better.But a stage that has parallel stages that each have _sequential_ stages in them are still showing as transparent when complete, though as before, it paints correctly as soon as the pipeline finishes.For example:---ab---c|---de---fIf d completes, it shows as transparent (incorrect). e does show as active (which is correct). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194330.153804945.24586.1560182760206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57259) Installation fails due to 404 in structs/1.19
Title: Message Title Jason Boehle edited a comment on JENKINS-57259 Re: Installation fails due to 404 in structs/1.19 And again: `Failed to download plugin: ssh-credentials or ssh-credentials-plugin` . ssh-credentials Last released: 38 minutes ago. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199024.1556639914000.24580.1560182700299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57259) Installation fails due to 404 in structs/1.19
Title: Message Title Jason Boehle commented on JENKINS-57259 Re: Installation fails due to 404 in structs/1.19 And again: `Failed to download plugin: ssh-credentials or ssh-credentials-plugin` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199024.1556639914000.24574.1560182640840%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup
Title: Message Title
Rudolf-Walter Kiss-Szakacs commented on JENKINS-57862
Re: A wrong configuration of CasC yaml kill Jenkins startup
[Originally posted on the associated GitHub issue, replicating here for visibility.] I have personally worked around this by applying CasC configs through a job, and disabling CasC for Jenkins startup by pointing it to an empty file. That is, I have a job that does a SCM checkout, and then runs something like this as a system-groovy script (from the groovy plugin):
import jenkins.model.GlobalConfiguration
import io.jenkins.plugins.casc.ConfigurationAsCode
import io.jenkins.plugins.casc.CasCGlobalConfig
def workspacePath = build.environment.WORKSPACE
def jcascConfig = GlobalConfiguration.all().get(CasCGlobalConfig.class)
try {
jcascConfig.setConfigurationPath(workspacePath)
jcascConfig.save()
ConfigurationAsCode.get().configure()
} finally {
jcascConfig.setConfigurationPath("${workspacePath}/empty.yaml")
jcascConfig.save()
}
(Note that below CasC version 1.20, you need to have at least one setting in empty.yaml, a completely empty file generates a null pointer exception.)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199824.1559748979000.24567.1560181200340%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Alexander Komarov commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 Temporary workaround for those blocked: -Dhudson.remoting.ClassFilter=com.cx.restclient.dto.ScanResults Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.24562.1560180600183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57941) Artifactory credentials default deployer credentials won't allow selection
Title: Message Title Jeff Koenig created an issue Jenkins / JENKINS-57941 Artifactory credentials default deployer credentials won't allow selection Issue Type: Bug Assignee: Eyal Ben Moshe Attachments: artifactory_3_2_2_settings.png, artifactory_3_2_4.png Components: artifactory-plugin Created: 2019-06-10 15:20 Environment: Jenkins: 2.179 Artifactory plugin: 3.2.3 - 3.2.4 Credentials plugin: 2.2.0 Labels: artifactory artifactory-plugin Priority: Minor Reporter: Jeff Koenig Selecting credentials for the "Default Deployer Credentials" is broken in the artifactory plugin 3.2.3 and 3.2.4. I've confirmed rolling back to artifactory 3.2.2 resolves the issue To Reproduce: Goto Jenkins "Configure System" page Find Artifactory Settings Select "Use the Credentials Plugin" Attempt to add or select credentials At this point you'll find that you cannot select existing credentials from the drop down, and adding new credentials will also not work. Further more, any existing jobs depending on this will fail with an
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Govind Sureka commented on JENKINS-57334 Re: "Run on planned host" from Build section not working Please provide solution to this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199108.1557111748000.24556.156018275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47770) Sometimes the node() step allocates a workspace that is already in use by another executor on the same slave.
Title: Message Title Neil Hemingway commented on JENKINS-47770 Re: Sometimes the node() step allocates a workspace that is already in use by another executor on the same slave. We're also being hit by this issue. Is there a log category that would help in diagnosis that I can enable? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186265.150953934.24550.1560179100181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57940) readJSON from pipeline-utility-steps-plugin swallows keys named 'class'
Title: Message Title Ian Driver created an issue Jenkins / JENKINS-57940 readJSON from pipeline-utility-steps-plugin swallows keys named 'class' Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2019-06-10 14:56 Environment: org.jenkins-ci.main:jenkins-war:2.150.3 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.codehaus.groovy:groovy-all:2.4.12 org.kohsuke.stapler:stapler-groovy:1.256 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 org.jenkins-ci.modules:windows-slave-installer:1.9.2 commons-digester:commons-digester:2.1 org.kohsuke:libpam4j:1.11 commons-io:commons-io:2.4 com.github.jnr:jnr-posix:3.0.45 org.kohsuke:trilead-putty-extension:1.2 org.jenkins-ci.modules:instance-identity:2.2 commons-codec:commons-codec:1.9 org.kohsuke:asm6:6.2 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.ui:jquery-detached:1.2 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 com.github.jnr:jnr-ffi:2.1.8 com.github.jnr:jnr-constants:0.9.9 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.slf4j:log4j-over-slf4j:1.7.25 org.jenkins-ci:version-number:1.4 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 org.kohsuke.stapler:stapler:1.256 org.jenkins-ci:jmdns:3.4.0-jenkins-3 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.apache.ant:ant:1.9.2 com.sun.solaris:embedded_su4j:1.1 com.github.jnr:jffi:1.2.17 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.apache.commons:commons-compress:1.10 commons-beanutils:commons-beanutils:1.8.3 org.jvnet.localizer:localizer:1.24 org.fusesource.jansi:jansi:1.11 org.jenkins-ci.modules:sshd:2.4 org.jenkins-ci.main:jenkins-core:2.150.3 org.springframework:spring-beans:2.5.6.SEC03 net.java.sezpoz:sezpoz:1.13 javax.xml.stream:stax-api:1.0-2 org.jenkins-ci:winstone:5.1 org.slf4j:slf4j-jdk14:1.7.25 org.jvnet.hudson:activation:1.1.1-hudson-1 commons-jelly:commons-jelly-tags-fmt:1.0 net.i2p.crypto:eddsa:0.2.0 jfree:jfreechart:1.0.9 org.kohsuke.stapler:stapler-jelly:1.256 oro:oro:2.0.8
[JIRA] (JENKINS-57408) MSBuild plugin "Install automatically" function not working
Title: Message Title Steven Lee commented on JENKINS-57408 Re: MSBuild plugin "Install automatically" function not working Is there a date estimate on when this bug will get worked on? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199211.1557518699000.24545.1560178200089%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Pat O'Shea edited a comment on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage Same issue here:Jenkins version - 2.164.3Workspace cleanup plugin - 0.37 Windows agent/slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194924.1540578037000.24536.1560177780421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57939) Nested PodTemplate erroneous behaviour
Title: Message Title
Christopher Webb updated an issue
Jenkins / JENKINS-57939
Nested PodTemplate erroneous behaviour
Change By:
Christopher Webb
See the following: {code:java}podTemplate(label: 'x', inheritFrom: 'JenkinsDeployer', nodeUsageMode: 'EXCLUSIVE') {node('x') {echo env.environmentpodTemplate(label: 'y', inheritFrom: 'JenkinsLiveDeployer', nodeUsageMode: 'EXCLUSIVE') {node('y') {echo env.environment}}}}{code} Assuming there are pod templates for a 'JenkinsDeployer' which have a set of environment variables and then a pod template for 'JenkinsLiveDeployer', which has a different set of environment variables, then I would expect to see a different value for each echo statement. Right now, assuming environment on each pod template are respectively pre-production and and production, the actual result of the code snippet above is: {code:java}// node starting'pre-production'// node starting'pre-production'{code} whereas the expected value should be:{code:java}// node starting'pre-production'// node starting'production'{code} This should be the same behaviour as doing the following but it is **not** : {code:java}node('label') { echo env.environment node('live-label') {echo env.environment }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-57939) Nested PodTemplate erroneous behaviour
Title: Message Title
Christopher Webb updated an issue
Jenkins / JENKINS-57939
Nested PodTemplate erroneous behaviour
Change By:
Christopher Webb
See the following: {code:java}podTemplate(label: 'x', inheritFrom: 'JenkinsDeployer', nodeUsageMode: 'EXCLUSIVE') {node('x') {echo env.environmentpodTemplate(label: 'y', inheritFrom: 'JenkinsLiveDeployer', nodeUsageMode: 'EXCLUSIVE') {node('y') {echo env.environment}}}}{code} Assuming there are pod templates for a 'JenkinsDeployer' which have a set of environment variables and then a pod template for 'JenkinsLiveDeployer', which has a different set of environment variables, then I would expect to see a different value for each echo statement. Right now, assuming environment on each pod template are respectively pre-production and and production, the actual result of the code snippet above is: {code:java}// node starting'pre-production'// node starting'pre-production'{code} whereas the expected value should be:{code:java}// node starting'pre-production'// node starting'production'{code} This should be the same behaviour as doing: {code:java}node('label') { echo env.environment node('live-label') {echo env.environment }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are
[JIRA] (JENKINS-57939) Nested PodTemplate erroneous behaviour
Title: Message Title
Christopher Webb created an issue
Jenkins / JENKINS-57939
Nested PodTemplate erroneous behaviour
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-06-10 14:22
Priority:
Minor
Reporter:
Christopher Webb
See the following:
podTemplate(label: 'x', inheritFrom: 'JenkinsDeployer', nodeUsageMode: 'EXCLUSIVE') {
node('x') {
echo env.environment
podTemplate(label: 'y', inheritFrom: 'JenkinsLiveDeployer', nodeUsageMode: 'EXCLUSIVE') {
node('y') {
echo env.environment
}
}
}
}
Assuming there are pod templates for a 'JenkinsDeployer' which have a set of environment variables and then a pod template for 'JenkinsLiveDeployer', which has a different set of environment variables, then I would expect to see a different value for each echo statement. Right now, assuming environment on each pod template are respectively pre-production and and production, the actual result of the code snippet above is:
// node starting
'pre-production'
// node starting
'pre-production'
[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Pat O'Shea commented on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage Same issue here: Jenkins version - 2.164.3 Workspace cleanup plugin - 0.37 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194924.1540578037000.24520.1560176340596%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan commented on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished Hi Josh McDonald – I can confirm that completed stages are still showing as parallel, in Blue Ocean 1.17. I think that some parallel stages that had a single stage were previously not showing correctly sometimes, and that seems better. But a stage that has parallel stages that each have sequential stages in them are still showing as transparent when complete, though as before, it paints correctly as soon as the pipeline finishes. For example: --a--b--c --d--e--f If d completes, it shows as transparent (incorrect). e does show as active (which is correct). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194330.153804945.24515.1560175560206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57938) How to replace back slash with forward slash in string parameter while giving input as windows path eg. C:\Jenkins\Project\ABC
Title: Message Title Alex Earl moved an issue Jenkins / JENKINS-57938 How to replace back slash with forward slash in string parameter while giving input as windows path eg. C:\Jenkins\Project\ABC Change By: Alex Earl Project: Infrastructure Jenkins Key: INFRA JENKINS - 1806 57938 Workflow: classic default workflow JNJira + In-Review Component/s: subversion-plugin Component/s: jenkins.io Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title Jesse Glick resolved as Not A Defect Just correcting the Resolution: Fixed is used for cases where a specific issue was identified and a code change was made to address it. Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24494.1560173221929%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title Jesse Glick updated JENKINS-44659 Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: Jesse Glick Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24487.1560173221803%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title Jesse Glick updated JENKINS-44659 Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: Jesse Glick Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24480.1560173160589%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57911) Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation
Title: Message Title Baptiste Mathus commented on JENKINS-57911 Re: Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation Did you follow the process and create a PR on https://github.com/jenkins-infra/repository-permissions-updater/ ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199877.1559904418000.24477.1560173040335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat resolved as Fixed Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: elhay efrat Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24470.1560171300514%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat edited a comment on JENKINS-44659 Re: Missing workspace - workspace deleted during concurrent build [~jglick] we canb can close it the RCA it's deleting the root folder and re-create it i don't see any use case adding it in the code , so what needed to be done , just change the workspace folder to something else and it will work perfectly you need to go to slaves ( node ) > workspace folder , change it , re-run it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24463.1560171240741%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat edited a comment on JENKINS-44659 Re: Missing workspace - workspace deleted during concurrent build [~jglick] we canb close it the RCA it's deleting the root folder and re-create it i don't see any use case adding it in the code , so what needed to be done , just change the WORKSAPCE workspace folder to somthing something else and it will work perfectlly perfectly you need to go to slaves ( node ) > workspace folder , change it , re-run it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24456.1560171240640%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat commented on JENKINS-44659 Re: Missing workspace - workspace deleted during concurrent build Jesse Glick we canb close it the RCA it's deleting the root folder and re-create it i don't see any use case adding it in the code , so what needed to be done , just change the WORKSAPCE folder to somthing else and it will work perfectlly you need to go to slaves ( node ) > workspace folder , change it , re-run it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.24454.1560171240610%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge edited a comment on JENKINS-57903 Re: New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Reopening issue due to missing link to PR Status set to _In Progress_ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.24446.1560170280582%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge started work on JENKINS-57903 Change By: Jon Brohauge Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.2.1560170280551%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge reopened an issue Reopening issue due to missing link to PR Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Jon Brohauge Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.24441.1560170280517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-57937 Write a criteria list for steps in release flow Issue Type: Task Assignee: Jon Brohauge Components: promoted-builds-plugin Created: 2019-06-10 12:29 Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline Priority: Minor Reporter: Jon Brohauge Write up a list of criteria that is needed for a ticket to have a given status. Add Comment
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge edited a comment on JENKINS-57877 Re: PromotionBadge compatibility with pipelines Status should not be resolved prior to merge on the relevant PRStatus set to be _in progress,_ since __ there is no PR, or other solution presented to resolve this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.24436.1560169320238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge edited a comment on JENKINS-57877 Re: PromotionBadge compatibility with pipelines Status should not be resolved prior to merge on the relevant PR Status set to be _in progress,_ since __ there is no PR, or other solution presented to resolve this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.24434.1560169320196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge started work on JENKINS-57877 Change By: Jon Brohauge Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.24430.1560169260212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge reopened an issue Status should not be resolved prior to merge on the relevant PR Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Jon Brohauge Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.24427.1560169200344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Git plugin password bug
Title: Message Title Fabriele Fatigati updated an issue Jenkins / JENKINS-57936 Git plugin password bug Change By: Fabriele Fatigati Environment: Jenkins 2.164.3 git plugin 3.10.0git-client 2.7.7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199912.1560167892000.24425.1560168120073%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Git plugin password bug
Title: Message Title Fabriele Fatigati updated an issue Jenkins / JENKINS-57936 Git plugin password bug Change By: Fabriele Fatigati Environment: Jenkins 2.164.3 git plugin 3.10.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199912.1560167892000.24424.1560168060150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Git plugin password bug
Title: Message Title Fabriele Fatigati created an issue Jenkins / JENKINS-57936 Git plugin password bug Issue Type: Bug Assignee: Fabriele Fatigati Components: git-plugin Created: 2019-06-10 11:58 Environment: Jenkins 2.164.3 Priority: Minor Reporter: Fabriele Fatigati Dear Jenkins users, I'm use Jenkins 2.164.3 and trying to clone a repository with Git Plugin I get the error " authentication failed", because for some reason git plugin add "%24" in front of my password read from password parameter. I read from ticket JENKINS-20533 It was an old bug of 5 years ago of very old git plugin, but now should be solved! Could you help me? Thanks. Add Comment
[JIRA] (JENKINS-40684) Can't add a shell build step with docker
Title: Message Title wang libao updated an issue Jenkins / JENKINS-40684 Can't add a shell build step with docker Change By: wang libao Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177387.1482843095000.24422.1560167400203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40684) Can't add a shell build step with docker
Title: Message Title wang libao commented on JENKINS-40684 Re: Can't add a shell build step with docker I'v run into the same problem，here is the log $ docker run --rm --entrypoint /bin/true alpine:3.6 $ docker run --tty --rm --entrypoint /sbin/ip alpine:3.6 route $ docker run --tty --detach --workdir /home/q/workspace/docker_test_job --volume /home/q:/home/q:rw --volume /tmp:/tmp:rw --net bridge --add-host dockerhost:172.17.0.1 --env BUILD_DISPLAY_NAME=#18 --env BUILD_ID=18 --env BUILD_NUMBER=18 --env BUILD_TAG=jenkins-docker_test_job-18 --env BUILD_URL= http://localhost:8080/job/docker_test_job/18/ --env CLASSPATH= --env EXECUTOR_NUMBER=0 --env "HUDSON_HOME=C:\Program Files (x86)\Jenkins" --env HUDSON_SERVER_COOKIE=8431b78f294fa38a --env HUDSON_URL= http://localhost:8080/ --env "JENKINS_HOME=C:\Program Files (x86)\Jenkins" --env JENKINS_SERVER_COOKIE=8431b78f294fa38a --env JENKINS_URL= http://localhost:8080/ --env JOB_BASE_NAME=docker_test_job --env JOB_DISPLAY_URL= http://localhost:8080/job/docker_test_job/display/redirect --env JOB_NAME=docker_test_job --env JOB_URL= http://localhost:8080/job/docker_test_job/ --env NODE_LABELS=docker_test --env NODE_NAME=docker_test --env RUN_CHANGES_DISPLAY_URL= http://localhost:8080/job/docker_test_job/18/display/redirect?page=changes --env RUN_DISPLAY_URL= http://localhost:8080/job/docker_test_job/18/display/redirect --env WORKSPACE=/home/q/workspace/docker_test_job a7dc1a88f751 /bin/cat Docker container 526c98683c7a64d4f5998f6f9d5eac90450e46cccea51d557ae4b5268437dec6 started to host the build $ docker exec --tty 526c98683c7a64d4f5998f6f9d5eac90450e46cccea51d557ae4b5268437dec6 env [docker_test_job] $ docker exec --tty --user 1000:1000 526c98683c7a64d4f5998f6f9d5eac90450e46cccea51d557ae4b5268437dec6 env BUILD_DISPLAY_NAME=#18 BUILD_ID=18 BUILD_NUMBER=18 BUILD_TAG=jenkins-docker_test_job-18 BUILD_URL= http://localhost:8080/job/docker_test_job/18/ CLASSPATH= EXECUTOR_NUMBER=0 HOME=/root HOSTNAME=526c98683c7a "HUDSON_HOME=C:\Program Files (x86)\Jenkins" HUDSON_SERVER_COOKIE=8431b78f294fa38a HUDSON_URL= http://localhost:8080/ "JENKINS_HOME=C:\Program Files (x86)\Jenkins" JENKINS_SERVER_COOKIE=8431b78f294fa38a JENKINS_URL= http://localhost:8080/ JOB_BASE_NAME=docker_test_job JOB_DISPLAY_URL= http://localhost:8080/job/docker_test_job/display/redirect JOB_NAME=docker_test_job JOB_URL= http://localhost:8080/job/docker_test_job/ LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_ALL=en_US.UTF-8 NODE_LABELS=docker_test NODE_NAME=docker_test PATH=$PATH:/snap/bin RUN_CHANGES_DISPLAY_URL= http://localhost:8080/job/docker_test_job/18/display/redirect?page=changes RUN_DISPLAY_URL= http://localhost:8080/job/docker_test_job/18/display/redirect TERM=xterm WORKSPACE=/home/q/workspace/docker_test_job /bin/bash /tmp/jenkins1469389118824566527.sh /bin/bash: /tmp/jenkins1469389118824566527.sh: No such file or directory Add Comment
[JIRA] (JENKINS-57935) PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies
Title: Message Title Oleg Nenashev started work on JENKINS-57935 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199909.156016161.24416.1560166680218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57935) PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies
Title: Message Title Oleg Nenashev commented on JENKINS-57935 Re: PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies https://github.com/jenkinsci/plugin-compat-tester/pull/156 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199909.156016161.24418.1560166680261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57935) PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies
Title: Message Title Oleg Nenashev updated JENKINS-57935 Jenkins / JENKINS-57935 PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199909.156016161.24417.1560166680249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57649) Lockable resource plugin should not lock a resources when it is offline
Title: Message Title
Jim Klimov edited a comment on JENKINS-57649
Re: Lockable resource plugin should not lock a resources when it is offline
While there is a good purpose in this request, I believe it is destined to be an offtopic/WontFix here. The plugin manages the generic concept of resources, does not even care if they are physically represented or not (you can use it to e.g. throttle a maximum amount of jobs holding a limited amount of tokens at a time).That said, you *can* use the Groovy script option of implementing *your* use-case dependent logic and eveelintually eventually return a `true` or `false` about whether a proposed resource is eligible for your job. The plugin calls such script in a loop for each resource ( your script should test that it matches the label _expression_ you asked for? want then ) and makes a list of items with a "true" verdict, to offer one (or first?) of those to be locked by a job.I am not sure if it levels the load on physical resources (giving first vs random eligible).As part of this logic you can do anything; for some of our tests in the house, we have indeed a script that probes SSH availability of a remote VM we'd be setting up with our product as part of such logic, so broken VMs are not offered to jobs. A trimmed-down example would be:{code}public static boolean serverListening(String host, int port){Socket s = null;try{s = new Socket(host, port);return true;}catch (Exception e){return false;}finally{if(s != null)try {s.close();}catch(Exception e){}}}//println "Inspecting the resource to lock for requested CONTROLLER='" + CONTROLLER + "' (looking at resourceName='" + resourceName + "' resourceDescription='" + resourceDescription + "' resourceLabels='" + resourceLabels + "')"// + "' in build number " + build.getNumber() + if ( serverListening(resourceName, 22) ) {println "ACCEPTED '" + resourceName + "'"return true;}println "Resource '" + resourceName + "' is not suitable for this job"return false; // Tested resource is not appropriate for this build{code}With this, we do however miss another ability: to see quickly which resources were last diagnosed dead. Arguably, this is out of LockableResources' scope as well however (rather belongs in zabbix or similar monitoring tool, or maybe a custom job to inspect the list of resources and "lock" broken ones by a specific holder, and unlock fixed ones... maybe along the lines of this https://stackoverflow.com/a/52744986/4715872 fine example).But it would be helpful to have such a status anyway and have it all displayed in the same list of Available/Reserved/Locked/+Broken+ Jenkins resources :)
Add Comment
[JIRA] (JENKINS-57649) Lockable resource plugin should not lock a resources when it is offline
Title: Message Title
Jim Klimov commented on JENKINS-57649
Re: Lockable resource plugin should not lock a resources when it is offline
While there is a good purpose in this request, I believe it is destined to be an offtopic/WontFix here. The plugin manages the generic concept of resources, does not even care if they are physically represented or not (you can use it to e.g. throttle a maximum amount of jobs holding a limited amount of tokens at a time). That said, you can use the Groovy script option of implementing your use-case dependent logic and eveelintually return a `true` or `false` about whether a proposed resource is eligible for your job. The plugin calls such script in a loop for each resource (that matches the label _expression_ you asked for?) and makes a list of items with a "true" verdict, to offer one (or first?) of those to be locked by a job. I am not sure if it levels the load on physical resources (giving first vs random eligible). As part of this logic you can do anything; for some of our tests in the house, we have indeed a script that probes SSH availability of a remote VM we'd be setting up with our product as part of such logic, so broken VMs are not offered to jobs. A trimmed-down example would be:
public static boolean serverListening(String host, int port)
{
Socket s = null;
try
{
s = new Socket(host, port);
return true;
}
catch (Exception e)
{
return false;
}
finally
{
if(s != null)
try {s.close();}
catch(Exception e){}
}
}
//println "Inspecting the resource to lock for requested CONTROLLER='" + CONTROLLER + "' (looking at resourceName='" + resourceName + "' resourceDescription='" + resourceDescription + "' resourceLabels='" + resourceLabels + "')"
// + "' in build number " + build.getNumber() +
if ( serverListening(resourceName, 22) ) {
println "ACCEPTED '" + resourceName + "'"
return true;
}
println "Resource '" + resourceName + "' is not suitable for this job"
return false; // Tested resource is not appropriate for this build
With this, we do however miss another ability: to see quickly which resources were last diagnosed dead. Arguably, this is out of LockableResources' scope as well however (rather belongs in zabbix or similar monitoring tool, or maybe a custom job to inspect the list of resources and "lock" broken ones by a specific holder, and unlock fixed ones... maybe along the lines of this https://stackoverflow.com/a/52744986/4715872 fine example). But it would be helpful to have such a status anyway and have it all displayed in the same list of Available/Reserved/Locked/Broken Jenkins resources
[JIRA] (JENKINS-57911) Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation
Title: Message Title LambdaTest Automation commented on JENKINS-57911 Re: Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation Baptiste Mathus Can you please help with this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199877.1559904418000.24409.1560163800046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57930) Pipeline script from SCM does not expand build parameters/env variables for declarative pipeline with yamlFile specified
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-57930 Pipeline script from SCM does not expand build parameters/env variables for declarative pipeline with yamlFile specified Change By: Carlos Sanchez Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199904.1560151841000.24408.1560163740351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57935) PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57935 PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies Change By: Oleg Nenashev Labels: jcasc-devtools-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199909.156016161.24392.1560161940056%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57935) PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57935 PCT does not properly resolve plugin Group IDs for WAR bundles when they come from optional dependencies Issue Type: Bug Assignee: Oleg Nenashev Components: plugin-compat-tester Created: 2019-06-10 10:13 Priority: Major Reporter: Oleg Nenashev PCT does not resolve JCasC properly for plugins like Artifact Manager S3, because there is no Group ID resolution for plugins not included into CAP. The default "org.jenkins-ci.plugins" is used, and it is not a case for JCasC. Failed to execute goal on project artifact-manager-s3: Could not resolve dependencies for project io.jenkins.plugins:artifact-manager-s3:hpi:2.4.2: Could not find artifact org.jenkins-ci.plugins:configuration-as-code:jar:1.20 in ... -> [Help 1] Until JCasC is included into CAP, PCT tests will be failing if they include JCasC compatibility tests Acceptance criteria: PCT is updated to consult with update center when resolving group IDs for plugins There is an integration tests which verifies it
[JIRA] (JENKINS-57934) Cannot set URL variable in pipeline: you tried to assign a value to the class 'java.net.URL'
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-57934
Cannot set URL variable in pipeline: you tried to assign a value to the class 'java.net.URL'
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-06-10 09:34
Environment:
Jenkins ver. 2.164.3 BlueOcean 1.16.0 Pipeline 2.6
Labels:
pipeline jenkins user-experience
Priority:
Minor
Reporter:
Ovidiu-Florin Bogdan
With the following Jenkinsfile I get an error complaining that you tried to assign a value to the class 'java.net.URL'
pipeline {
environment {
URL = "" class="code-quote" style="color: #009100">"http://foomybar.com"
}
agent any
stages {
stage ("do the thing") {
steps {
sh "echo ${env.URL}"
}
}
}
}
I cannot set the URL environment variable through the environment block.
[JIRA] (JENKINS-57933) Landing page for build with parameters requires refresh in order to display build flow graph
Title: Message Title Jon Sten created an issue Jenkins / JENKINS-57933 Landing page for build with parameters requires refresh in order to display build flow graph Issue Type: Bug Assignee: Gustaf Lundh Components: yet-another-build-visualizer-plugin Created: 2019-06-10 09:33 Priority: Minor Reporter: Jon Sten When triggering a new build using "Build with Parameters" page, the user is sent to the job main page. At that point the freshly started build haven't had time to trigger a downstream build, which means that no Build flow view is displayed. Nor is it displayed once the build has triggered downstreams, i.e. there is no auto-refresh. This previously worked, but was "broken" in a recent change. Possible solution is to look at lastCompletedBuild to see if it has downstream/upstream builds, or if there is no lastCompletedBuild, check lastBuild. Add Comment
[JIRA] (JENKINS-56652) Wrong servers or network glitches in settings.xml leads to False negative entries in HPI caches for pom.xml inputs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56652 Wrong servers or network glitches in settings.xml leads to False negative entries in HPI caches for pom.xml inputs Change By: Oleg Nenashev Summary: Wrong servers or network glitches in settings.xml leads to False negative entries in HPI caches for pom.xml inputs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198283.155312499.24223.156015959%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57547) CWP 1.6 throws error if pom.xml is used for plugins and casc for configuration
Title: Message Title Oleg Nenashev commented on JENKINS-57547 Re: CWP 1.6 throws error if pom.xml is used for plugins and casc for configuration Apparently it was caused by connectivity issues Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199455.1558292127000.24222.1560158940122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57932) Unstash pipeline step hangs intermittently
Title: Message Title
Enrico Mills created an issue
Jenkins / JENKINS-57932
Unstash pipeline step hangs intermittently
Issue Type:
Bug
Assignee:
Jie Shen
Attachments:
AzureArtifactManager-Config.png, AzureArtifactManager-UnstashCrashLog.txt
Components:
azure-artifact-manager-plugin
Created:
2019-06-10 09:01
Environment:
Jenkins: 2.164.3, Azure Artifact Manager: 1.0.2, Agent OS: Debian Stretch with Open JDK 8
Priority:
Minor
Reporter:
Enrico Mills
I installed the latest Azure Artifact Manager plugin last week (June 6th). Since then my pipelines which are defined in a Jenkinsfile in the project get stuck at an unstash step about 70% of the time. Most of my pipelines are composed of multiple stages and the workspace is stashed and unstashed between stages. I have attached a screenshot of my Azure Artifact Manager plugin configuration plus the relevant logs. Note: When I first installed the plugin, I set the container name to "jenkins" and the base prefix to "${JOB_NAME}" because I did not realize the path already includes the project name, branch name and job number in the path. I don't think that has any bearing on the issue though.
[JIRA] (JENKINS-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth closed an issue as Fixed Fixed in 1.9.7: https://swarm.workshop.perforce.com/changes/25439 https://swarm.workshop.perforce.com/changes/25437 Jenkins / JENKINS-55737 "No polling baseline - Changes found" causing runaway polling Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197010.1548200108000.24209.1560155460471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
