[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl commented on JENKINS-58177 Re: Leading - in workspace directory names mangled in multibranch pipeline Jesse Glick maybe you could have a look at it or share your opinion, as you have worked on JENKINS-2111. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.7828.1561442280168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Jesse Glick Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.7826.1561442160183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title
Roman Pickl updated an issue
Jenkins / JENKINS-58177
Leading - in workspace directory names mangled in multibranch pipeline
Change By:
Roman Pickl
Apparently, some of our workspaces for specific branch names are mangled in a way that the directories start with a "-" (or multiple!). This would require some special handling in scripts and we would like to avoid that. There also have been some discussions about this special case in the now obsolete implementation in JENKINS-38706:https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=272733=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272733https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=324422=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-324422https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=345815=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-345815https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=348257=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-348257I had a look and it seems to happen here:[https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L193] It can be tested with this small java program: {code:java}import org.apache.commons.lang3.StringUtils;public class Test {public static void main(String args[]) {int MAX_LENGTH=32;String fullName= "JIRA-1054_rename_1234_to_abcdef_try2";String mnemonic = mnemonicOf(fullName);String path = StringUtils.right(mnemonic, MAX_LENGTH); System.out.println(path);}private static String mnemonicOf(String name) {// Do not need the complexity of NameMangler here, since we uniquify as needed.return name.replaceAll("(%[0-9A-F]{2}|[^a-zA-Z0-9-_.])+", "_");}}{code} For the moment i have increased MAX_LENGTH on our jenkins, but I would really love to see this fixed in Jenkins.
Add Comment
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title
Roman Pickl created an issue
Jenkins / JENKINS-58177
Leading - in workspace directory names mangled in multibranch pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
branch-api-plugin
Created:
2019-06-25 05:54
Environment:
jenkins-war:2.176.1 branch-api-plugin: 2.5.2
Priority:
Minor
Reporter:
Roman Pickl
Apparently, some of our workspaces for specific branch names are mangled in a way that the directories start with a "-" (or multiple!). This would require some special handling in scripts and we would like to avoid that. There also have been some discussions about this special case in the now obsolete implementation in JENKINS-38706: https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=272733=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272733 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=324422=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-324422 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=345815=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-345815 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=348257=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-348257 I had a look and it seems to happen here: https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L193 It can be tested with this small java program:
import org.apache.commons.lang3.StringUtils;
public class Test {
public static void main(String
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title hhkkss commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin Thanks for the feedback. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200156.1561013839000.7822.1561441680112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58176) Create Phase 1 Blog Post
Title: Message Title Natasha Stopa started work on JENKINS-58176 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200227.1561440641000.7820.1561440780074%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58175) Build Status Success even after disconnection of ALM
Title: Message Title Daniel Gront commented on JENKINS-58175 Re: Build Status Success even after disconnection of ALM Anda Sorina Laakso, you could use the following to abort the job "throw new AbortException()" or set the build to FAILURE if failed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200226.1561440325000.7819.1561440720149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58176) Create Phase 1 Blog Post
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58176 Create Phase 1 Blog Post Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-25 05:30 Labels: gsoc-2019 plugin-manager documentation Priority: Major Reporter: Natasha Stopa Part of Phase 1 evaluations inclue a blog post published to Jenkins.io and announced on the GSoC mailing list. Information here: https://jenkins.io/projects/gsoc/students/ Add Comment
[JIRA] (JENKINS-58175) Build Status Success even after disconnection of ALM
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-58175 Build Status Success even after disconnection of ALM Change By: Daniel Gront Labels: UFT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200226.1561440325000.7812.1561440600498%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58175) Build Status Success even after disconnection of ALM
Title: Message Title Daniel Gront assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-58175 Build Status Success even after disconnection of ALM Change By: Daniel Gront Assignee: Daniel Gront Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200226.1561440325000.7815.1561440600599%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58175) Build Status Success even after disconnection of ALM
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-58175 Build Status Success even after disconnection of ALM Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-06-25 05:25 Environment: Jennkins: CloudBees Jenkins Enterprise 2.150.3.2 rolling Plugin: Execute Micro Focus functional tests from Micro Focus ALM (5.6 and 5.8 & Beta version) Priority: Major Reporter: Govind Sureka Integrated UFT automation test cases from ALM with Jenkins. Individual test script taking more than 4 hours run are experience Jenkins and ALM disconnection resulting in this error: Note: Though the execution has not completed but the status of the job is being shown as 'Success' which is misleading. Last Section of Logs: 24/06/2019 08:27:14 Running: [1]06_ACC_ActionAppropriation 24/06/2019 08:27:14 Running test: [1]06_ACC_ActionAppropriation, Test id: 973, Test instance id: 950 Test: [1]06_ACC_ActionAppropriation, Id: 950, Execution status: Running Test: [1]06_ACC_ActionAppropriation, Id: 950, Execution status: Unknown, Message: Testing tool was terminated during test run Test: [1]06_ACC_ActionAppropriation, Id: 950, Execution status: Error, Message: Testing tool was terminated during test run Unhandled Exception: System.NullReferenceException: Your Quality Center session has been disconnected. Contact your system administrator for more information at Mercury.TD.Client.Ota.QC9.ITSTest.get_LastRun() at HpToolsLauncher.AlmTestSetsRunner.GetTestRunId(ITSTest currentTest) at HpToolsLauncher.AlmTestSetsRunner.WriteTestRunSummary(ITSTest prevTest) at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost) at HpToolsLauncher.AlmTestSetsRunner.Run() at
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58157 "delete build" button is to long Change By: Minghui Ma after upgrade to 2.176.1, "delete build" button is to long. see my attachment picture at bleow. h1. JENKINS-55848 https://github.com/jenkinsci/jenkins/pull/3871 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.7808.1561438560066%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-58157 "delete build" button is to long Change By: Minghui Ma after upgrade to 2.176.1, "delete build" button is to long. see my attachment picture at bleow. h1. JENKINS-55848 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.7807.1561438500065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58174) Azure Storage plugin new changes creates temp files and should remove it after upload
Title: Message Title Hung Vo created an issue Jenkins / JENKINS-58174 Azure Storage plugin new changes creates temp files and should remove it after upload Issue Type: Improvement Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2019-06-25 04:25 Priority: Minor Reporter: Hung Vo Hi, I've noticed build node disk filled up very fast as this plugin create file in %temp% but not remove them after finished upload to blob. I uploaded 10GB ++ to Azure storage twice a week. It's nice change if the plugin clean up these temporary files after upload. Add Comment
[JIRA] (JENKINS-27512) Support icons for folders
Title: Message Title Daniel Spilker commented on JENKINS-27512 Re: Support icons for folders Roman Donchenko the multi-branch-project-plugin is deprecated. Are there any other non-deprecated icon types? I do not want to add a feature that is supported by a deprecated plugin only. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161314.1426786361000.7803.1561435920158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53424) script-security plugin breaks parameterized pipeline builds
Title: Message Title sun shuanjijn assigned an issue to sun shuanjijn Jenkins / JENKINS-53424 script-security plugin breaks parameterized pipeline builds Change By: sun shuanjijn Assignee: Andrew Bayer sun shuanjijn Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193613.1536130405000.7794.1561432200256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190313.1525203384000.7751.1561431360546%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM
Title: Message Title Roy Lu commented on JENKINS-55276 Re: HP ALM Plugin - when job is branched only branch appear in HP ALM Could you please provide the console output of this job? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7749.1561428720192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58173) Multi-configuration projects are not restartable
Title: Message Title Pavel Roskin created an issue Jenkins / JENKINS-58173 Multi-configuration projects are not restartable Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2019-06-25 00:40 Environment: Jenkins 2.176.1, Matrix project plugin 1.14 Labels: restart matrix-project Priority: Minor Reporter: Pavel Roskin When I request Jenkins safe restart while a matrix project is building, all configurations of that project are built before Jenkins restarts. That is, the matrix project behaves like a free-style project, i.e. the whole matrix runs without interruption. That seems an artificial limitation to me. The top level build is pure Java, it should be able to save its state and continue after the restart. When the restart is requested, the top level build should stop running new configuration builds, wait until the running configuration builds complete and restart. That would greatly help with Jenkins updates on systems with large matrix projects.
[JIRA] (JENKINS-57813) Bump jenkins-core requirement to 2.138
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Fixed in 3.8.0 Jenkins / JENKINS-57813 Bump jenkins-core requirement to 2.138 Change By: Cyrille Le Clerc Status: In Progress 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.199765.1559507753000.7745.1561417200218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Liam Newman commented on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
Timo Sand Yeah, JobDSL always has the configure block option. I agree it is ugly but in the short term it give you a work around (you could wrap that in method call and put it in a library to make it look cleaner). This sounds like something that would be better to fix/enhance in the JobDSL plugin. Maybe it could detect this from context? In the DSL, {sshCheckoutTrait} is a descendant of {github} , the package for which is {org.jenkinsci.plugins.github_branch_source} . If there a trait in the same package, it would seem reasonable to choose it instead of failing. Then all the branch source plugins would be fixed in one shot. Of course, I don't know enough about the JobDSL plugin to know if that would be difficult.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194446.1538670788000.7743.1561415940211%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson assigned an issue to Jeff Thompson Jenkins / JENKINS-53322 Remove patched dom4j from Stapler Change By: Jeff Thompson Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.7740.1561413660261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-58172 Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source Change By: Mark Waite Summary: Deleting a & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.7737.1561413420163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits PR-194 has merged and I think the fix will be in v2.5.4 of the plugin. Will check as soon as I can find the builds and see if it's updated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.7732.1561413120647%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt assigned an issue to John Gaunt Jenkins / JENKINS-47867 Make "Committers To Ignore" configurable via traits Change By: John Gaunt Assignee: John Gaunt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.7727.1561412880225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even if not all of them are suitable for the context.For example having installed: - [https://plugins.jenkins.io/github-branch-source] , - [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] and - [https://plugins.jenkins.io/mercurial] installed: *SCMSource* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.mercurialSCMSource]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even if not all of them are suitable for the context.For example having [https://plugins.jenkins.io/github-branch-source] and , [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] and [https://plugins.jenkins.io/mercurial] installed:*SCMSource* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]- [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.mercurialSCMSource]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even if not all of them are suitable for the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:*SCMSource* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.mercurialSCMSource] *ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even if not all of them are suitable for the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:* SCMSources SCMSource * - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even if not all of them are suitable for the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:*SCMSources* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess SCMTraits) are shown in multiple places, even not all of them are suitable for the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:*SCMSources* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess {{SCMTrait}}s) are shown in multiple places, even not all of them are suitable the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:*SCMSources* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe edited a comment on JENKINS-45860
Re: Support traits for ScmNavigators
[~daspilker] do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like {{getTraitsDescriptorLists}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.5/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMNavigator.java#L634-L666] and [here|https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.5.3/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java#L1404-L1434].Currently all available traits (I guess {{SCMTrait}}s SCMTraits ) are shown in multiple places, even not all of them are suitable the context.For example having [https://plugins.jenkins.io/github-branch-source] and [https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] installed:*SCMSources* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.bitbucket]*ScmNavigatorsContext* - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket|http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.bitbucket] - [http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-45860) Support traits for ScmNavigators
Title: Message Title
René Scheibe commented on JENKINS-45860
Re: Support traits for ScmNavigators
Daniel Spilker do you think it's also feasible to filter the traits shown in the Job DSL API viewer? Maybe using something like getTraitsDescriptorLists here and here. Currently all available traits (I guess {{SCMTrait}}s) are shown in multiple places, even not all of them are suitable the context. For example having https://plugins.jenkins.io/github-branch-source and https://plugins.jenkins.io/cloudbees-bitbucket-branch-source installed: SCMSources
http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.github
http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/jenkins.scm.api.SCMSource$$List.Bitbucket
ScmNavigatorsContext
http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.Bitbucket
http://localhost:8080/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.workflow.ScmNavigatorsContext.github
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184072.150127966.7611.1561412100584%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57126) Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH
Title: Message Title Ray Kivisto commented on JENKINS-57126 Re: Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH I've implemented cygwin detection, and re-tested the feature. It's working for me locally and I've submitted a PR: https://github.com/jenkinsci/ssh-slaves-plugin/pull/134 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198876.1555767267000.7608.1561411140276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58172) Deleting a remaking a tag makes Jenkins stop building the tag forever
Title: Message Title Mark Waite commented on JENKINS-58172 Re: Deleting a remaking a tag makes Jenkins stop building the tag forever Changed the assigned project from the git plugin to the github branch source plugin since the github branch source plugin is in the stack trace rather than the git plugin. The git plugin does not use the GitHub API's. It uses calls to either command line git or to JGit, without invoking any hosting provider specific APIs. You may also want to refer to the comments in JENKINS-55284. They describe why it is considered bad practice in git to create a new tag at a new location which uses the same tag name as an existing tag. Once a tag name has been used and cloned outside the original repository, it is usually best to consider that tag "consumed" and to never create or modify it again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.7605.1561410120146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58172) Deleting a remaking a tag makes Jenkins stop building the tag forever
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58172 Deleting a remaking a tag makes Jenkins stop building the tag forever Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.7601.1561409880303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58172) Deleting a remaking a tag makes Jenkins stop building the tag forever
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-58172 Deleting a remaking a tag makes Jenkins stop building the tag forever Change By: Mark Waite Component/s: github-branch-source-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.7599.1561409880277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58172) Deleting a remaking a tag makes Jenkins stop building the tag forever
Title: Message Title
Ethan Diamond updated an issue
Jenkins / JENKINS-58172
Deleting a remaking a tag makes Jenkins stop building the tag forever
Change By:
Ethan Diamond
*Issue:* When I click Jenkins reports a tag that exists as "Not Found" and failing the build with this message: 12:52:41 Branch indexing19:52:41 [2019-06-24T19:52:41.964Z] Connecting to [ https://api.github.com |https://api.github.com/] using dev-rafabuildadmin/** (github dev-rafabuildadmin user (required to publish build/deploy status))12:52:42 java.io.FileNotFoundException: [ https://api.github.com/repos/rafastealth/ios-patient-client/git/refs/tags/0.0.4 ] 12:52:42 at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)12:52:42 at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)12:52:42 at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)12:52:42 at org.kohsuke.github.Requester.parse(Requester.java:625)12:52:42 at org.kohsuke.github.Requester.parse(Requester.java:607)12:52:42 at org.kohsuke.github.Requester._to(Requester.java:285)12:52:42 Caused: org.kohsuke.github.GHFileNotFoundException: \{"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"}12:52:42 at org.kohsuke.github.Requester.handleApiError(Requester.java:699)12:52:42 at org.kohsuke.github.Requester._to(Requester.java:306)12:52:42 at org.kohsuke.github.Requester.to(Requester.java:247)12:52:42 at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891)12:52:42 at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1521)12:52:42 at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)12:52:42 at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)12:52:42 at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)12:52:42 at hudson.model.ResourceController.execute(ResourceController.java:97)12:52:42 at hudson.model.Executor.run(Executor.java:429)12:52:42 Finished: FAILURE See "github_tag.png" for proof the tag does indeed exist. I've tried re-indexing, but the issue never resolves. *Repro Steps:* - Set up tags to build with your repo (see tag_setup.png)- Create a tag (say, 0.0.4) in your git repo and push it up to origin. This will cause it to auto build.- In git, delete the tag and push that deletion up to Github.- In git, tag a new commit with the same tag name (0.0.4) as above and push it up to Github.- In Jenkins, in the job made by the tag, click "Build Now" - Note that Jenkins can't find the tag
[JIRA] (JENKINS-58172) Deleting a remaking a tag makes Jenkins stop building the tag forever
Title: Message Title Ethan Diamond created an issue Jenkins / JENKINS-58172 Deleting a remaking a tag makes Jenkins stop building the tag forever Issue Type: Bug Assignee: Mark Waite Attachments: github_tag.png, tag_setup.png Components: git-plugin Created: 2019-06-24 20:27 Environment: System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit buildInfoConfig.propertiesFile /home/jenkins/workspace/rafastealth_client-tests_PR-906@tmp/artifactory/buildInfo5201462940584537637.properties com.sun.org.apache.xml.internal.dtm.DTMManager com.sun.org.apache.xml.internal.dtm.ref.DTMManagerDefault com.zaxxer.hikari.pool_number 1 executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-0.43.amzn1.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-0.43.amzn1.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-0.43.amzn1.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_201-b09 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_201 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.201-b09 javax.xml.parsers.DocumentBuilderFactory com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl JENKINS_HOME /var/lib/jenkins jetty.git.hash 27208684755d94a92186989f695db2d7b21ebc51 jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna8894856556497448699.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title Jon Campbell closed an issue as Fixed Didn't see duplicate #57232 Jenkins / JENKINS-58171 Configuration as Code - Audit Trail Configuration Change By: Jon Campbell 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.200222.1561407126000.7592.1561407240445%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title Jon Campbell created an issue Jenkins / JENKINS-58171 Configuration as Code - Audit Trail Configuration Issue Type: New Feature Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-06-24 20:12 Priority: Minor Reporter: Jon Campbell As a Jenkins administrator, I would like to be able to configure audit-trail plugin with configuration-as-code plugin. Thank you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title
Matt Sicker updated an issue
Jenkins / JENKINS-58170
Allow credential parameters to shadow credential ids in lookup
Change By:
Matt Sicker
As a pipeline author, suppose I have a pipeline that performs a deployment action that requires credentials from Jenkins. A naive approach might be to add my credentials to the global Jenkins credential store (call it {{deployKey}} as its id); then I can reference it in my pipeline later like so: {code:java}node { // ... stage('Deploy') {withCredentials([usernameColonPassword(credentialsId: 'deployKey', variable: 'DEPLOY_CREDENTIALS')]) { sh 'curl -u "${DEPLOY_CREDENTIALS}" ...'} }}{code}But then I want to make my pipeline more secure. One option I might have is to have a dedicated Jenkins instance for running deployments. This is a _large_ maintenance burden (e.g., trusted.ci.j.io versus ci.j.io), so digging deeper into Jenkins' existing features, I find user-scoped credentials. I can simply use credentials attached to my user account instead of Jenkins itself, though in order for my pipeline to recognize and use these credentials, I find that I must make them parameterized to the build itself so that I can select my credentials upon starting a build (there's an alternative option using the Authorize Project plugin, but this plugin is not widely used). A neat side-effect of this functionality is that other users can also deploy using the same pipeline but with their own user-scoped credentials. This can also allow me the flexibility of using a default global credential and allowing users to override that specifically for a pipeline run.Thus, I modify my pipeline to add a build parameter for the deploy credentials as well as using a modified syntax in {{withCredentials}} to indicate that the {{credentialId}} parameter being provided is in fact a build parameter name and not the actual credential id. Combined, we get the following updated pipeline:{code:java}properties([parameters([credentials(credentialType: 'com.cloudbees.plugins.credentials.common.StandardUsernamePasswordCredentials', name: 'deployKey', required: true)])])node { // ... stage('Deploy') {withCredentials([usernameColonPassword(credentialsId: '${deployKey}', variable: 'DEPLOY_CREDENTIALS')]) { sh 'curl -u "${DEPLOY_CREDENTIALS}" ...'} }}{code}Notice how we need to use a special syntax: {{credentialsId: '${deployKey}'}}. This syntax is misleading because it can be easily confused with the similar but not equivalent GString syntax: {{credentialsId: "${deployKey}"}}. In fact, this latter syntax would never work for a user-scoped credential because user-scoped credentials are currently only looked up if the credential id is provided using that the former template syntax.What I am proposing we change here is to make credential parameters referenced by name take precedent over a globally-scoped credential with an id of the same name as the parameter name itself. Thus, we could update the above pipeline using this feature to be a little
[JIRA] (JENKINS-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title
Lance Johnson commented on JENKINS-52150
Re: High CPU sys time consumption after upgrade to 2.107.3
We are seeing the same behavior with v2.180
# time strace -c -f -p 25129
% time seconds usecs/call callserrors syscall
-- --- --- - -
64.24 325.7725072399135794 17935 futex
21.78 110.426436 800192 13861 restart_syscall
9.17 46.523219 35898 1296 epoll_wait
3.97 20.126873 972 2070529 recvfrom
0.522.624930 2763195 accept
0.130.642494 22 29615 getrusage
0.050.272781 24 11607 write
[pid 25189] futex(0x7fa0814d3a54, FUTEX_WAIT_BITSET_PRIVATE, 1, {372183, 895437760}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 25189] futex(0x7fa0814d3a28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 25189] futex(0x7fa0814d3a54, FUTEX_WAIT_BITSET_PRIVATE, 1, {372183, 945599747}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 25189] futex(0x7fa0814d3a28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 25189] futex(0x7fa0814d3a54, FUTEX_WAIT_BITSET_PRIVATE, 1, {372183, 995774240}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 25189] futex(0x7fa0814d3a28, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 25189] futex(0x7fa0814d3a54, FUTEX_WAIT_BITSET_PRIVATE, 1, {372184, 45936909}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 25189] futex(0x7fa0814d3a28, FUTEX_WAKE_PRIVATE, 1) = 0
# java -jar /usr/lib/jenkins/jenkins.war --version
2.180
Add Comment
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title Matt Sicker started work on JENKINS-58170 Change By: Matt Sicker 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.200221.1561401761000.7575.1561401960188%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title Matt Sicker updated JENKINS-58170 Jenkins / JENKINS-58170 Allow credential parameters to shadow credential ids in lookup Change By: Matt Sicker 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.200221.1561401761000.7576.1561401960243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title
Matt Sicker created an issue
Jenkins / JENKINS-58170
Allow credential parameters to shadow credential ids in lookup
Issue Type:
New Feature
Assignee:
Matt Sicker
Components:
credentials-plugin
Created:
2019-06-24 18:42
Priority:
Minor
Reporter:
Matt Sicker
As a pipeline author, suppose I have a pipeline that performs a deployment action that requires credentials from Jenkins. A naive approach might be to add my credentials to the global Jenkins credential store (call it deployKey as its id); then I can reference it in my pipeline later like so:
node {
// ...
stage('Deploy') {
withCredentials([usernameColonPassword(credentialsId: 'deployKey', variable: 'DEPLOY_CREDENTIALS')]) {
sh 'curl -u "${DEPLOY_CREDENTIALS}" ...'
}
}
}
But then I want to make my pipeline more secure. One option I might have is to have a dedicated Jenkins instance for running deployments. This is a large maintenance burden (e.g., trusted.ci.j.io versus ci.j.io), so digging deeper into Jenkins' existing features, I find user-scoped credentials. I can simply use credentials attached to my user account instead of Jenkins itself, though in order for my pipeline to recognize and use these credentials, I find that I must make them parameterized to the build itself so that I can select my credentials upon starting a build (there's an alternative option using the Authorize Project plugin, but this plugin is not widely used). A neat side-effect of this functionality is that other users can also deploy using the same pipeline but with their own user-scoped credentials. This can also allow me the flexibility of using a default global credential and allowing users to
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I normally use job-dsl-plugin to manage all my jobs i.e. I won't have the pain of managing multiple jobs. Do check it out. Alternatively, jira-trigger-plugin could support triggers DSL, but unfortunately I don't think I have the capacity to implement that at the moment. Feel free to contribute, the repository is community driven. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200156.1561013839000.7572.1561397460127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56898) Add support for configuration-as-code
Title: Message Title Steve Springett commented on JENKINS-56898 Re: Add support for configuration-as-code In v5.0 of the plugin (once released), there isn't a lot of configuration involved. The Jenkins plugin (the builder anyway) as you know it, doesn't exist anymore. It's a global tool which is installed. There are no global configuration options and only a few per-job configuration options. In v5, a job will have a textarea form field in which a user can specify any of the CLI arguments detailed here https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html Once v5 is released, come back to this thread and see what configuration-as-code would look like for a globally installed tool - which supports everything from Dependency-Check v1.0.0 to present. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198569.155445398.7569.1561395540173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title
Joel Brown edited a comment on JENKINS-58119
Re: Cant run P4Groovy sync on multiple executors
Workaround should be to start all nodes running concurrent builds to not use "@": start jvm with {{"-Dhudson.slaves.WorkspaceList=_"}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200164.1561045657000.7567.1561395120087%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title Joel Brown commented on JENKINS-58119 Re: Cant run P4Groovy sync on multiple executors Workaround should be to start all nodes running concurrent builds to not use "@": "-Dhudson.slaves.WorkspaceList=_" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200164.1561045657000.7565.1561395000117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-58169 JMX: Use hierarchical names Change By: Vincent Latombe Attachment: after.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200220.1561394126000.7563.1561394880139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-58169 JMX: Use hierarchical names Change By: Vincent Latombe Attachment: before.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200220.1561394126000.7561.1561394820332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57126) Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH
Title: Message Title Ray Kivisto edited a comment on JENKINS-57126 Re: Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH I tested my WIP at [https://github.com/jenkinsci/ssh-slaves-plugin/compare/master...rkivisto:alternative-windows-drives]using Cygwin by following the instructions at: [https://go.cloudbees.com/docs/cloudbees-core/cloud-admin-guide/agents/#_microsoft_windows]I found that my WIP still needs to take into account when the build agent is using Cygwin OpenSSH, because right now it is passing the "/d" argument to "cd" from Cygwin, and it fails with the message: "bash: line 0: cd: too many arguments" I see that there is the environment variable "OSTYPE=cygwin" that is available , so I could check if we are using cygwin , but it is not available until after the remoting connection is already established . The problem is, the shell command "cmd" is determined before the remoting connection is established, and is passed to "session.execCommand(cmd);" https://github.com/rkivisto/ssh-slaves-plugin/blob/ca2821bddac099bb6c9e87a721476d92caa5187e/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L613 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198876.1555767267000.7559.1561394400130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe updated JENKINS-58169 Jenkins / JENKINS-58169 JMX: Use hierarchical names Change By: Vincent Latombe 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.200220.1561394126000.7556.1561394220193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58169 JMX: Use hierarchical names Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200220.1561394126000.7554.1561394160457%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe started work on JENKINS-58169 Change By: Vincent Latombe 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.200220.1561394126000.7552.1561394160380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58169) JMX: Use hierarchical names
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-58169 JMX: Use hierarchical names Issue Type: Improvement Assignee: Unassigned Components: metrics-plugin Created: 2019-06-24 16:35 Priority: Minor Reporter: Vincent Latombe Metrics are currently exported by using the metric name as the JMX name. However JMX has a hierarchical model which uses a list of key-values separated by commas in order to build the structure. The metrics themselves use the dot as a separator and can be easily mapped to JMX in a hierarchical way which is more user-friendly for JMX consumers. Add Comment
[JIRA] (JENKINS-57126) Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH
Title: Message Title Ray Kivisto commented on JENKINS-57126 Re: Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH I tested my WIP at https://github.com/jenkinsci/ssh-slaves-plugin/compare/master...rkivisto:alternative-windows-drives using Cygwin by following the instructions at: https://go.cloudbees.com/docs/cloudbees-core/cloud-admin-guide/agents/#_microsoft_windows I found that my WIP still needs to take into account when the build agent is using Cygwin OpenSSH, because right now it is passing the "/d" argument to "cd" from Cygwin, and it fails with the message: "bash: line 0: cd: too many arguments" I see that there is the environment variable "OSTYPE=cygwin" that is available so I could check if we are using cygwin, but it is not available until after the remoting connection is already established. The problem is, the shell command "cmd" is determined before the remoting connection is established, and is passed to "session.execCommand(cmd);" https://github.com/rkivisto/ssh-slaves-plugin/blob/ca2821bddac099bb6c9e87a721476d92caa5187e/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L613 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198876.1555767267000.7548.1561393980133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov commented on JENKINS-58143 Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized I added the option + restarted pod. Monitoring how it behaves. Carlos Sanchez thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.7541.1561393560285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe assigned an issue to Unassigned Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Pietro Pepe Assignee: Pietro Pepe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7530.1561392840168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe assigned an issue to Pietro Pepe Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Pietro Pepe Assignee: Pietro Pepe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7527.1561392720364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Also in our infrastructure we get the same issue using BlueOcean 1.17.0 (on Jenkins 2.176.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7525.1561392720314%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Jesse Glick commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN kubernetes plugin 1.14.9 Please do not use JIRA to discuss issues present in obsolete software versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196500.1546530449000.7488.1561392420741%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-58166
Re: build step does not execute a job if the call is not different
in the example , it only launching launches 2 jobs one per parallel block, it does not correct I've launched 16 jobs{code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19{code}{code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy) (hide)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20{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
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-58166
Re: build step does not execute a job if the call is not different
Ok, in the example it only launching 2 jobs one per parallel block, it does not correct I've launched 16 jobs , but this would be another bug {code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19{code}{code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy) (hide)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20{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.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-58166
Re: build step does not execute a job if the call is not different
Ok, in the example it only launching 2 jobs one per parallel block, it does not correct I've launched 16 jobs{code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19Starting building: test-dummy #19{code}{code}Scheduling project: test-dummy[Pipeline] build (Building test-dummy) (hide)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummy[Pipeline] build (Building test-dummy)Scheduling project: test-dummyStarting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20Starting building: test-dummy #20{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
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly Eric noted in the ticket that the Warning is there in 1.7.2. Upon reviewing my 1.9.7 console, I can confirm I also see that. That was just the first thing I saw that looked off, so I didn't post the rest of the console. You can see below that the behavior in mine is slightly different. Instead of using the latest changelist, mine uses change -1 for some reason. My assumption is these are the same issue, but I could not say for sure. In any case, the fact remains that 1.9.7 works and 1.10.0 doesn't. My 1.10.0 output is a little different: P4: no revisions under //jenkins-notaclientyettest/...@DCIlabel using change: -1... p4 repos -C - p4 repos -C P4: builds: -1 ... p4 client -o jenkins-notaclientyettest - p4 client -o jenkins-notaclientyettest ... p4 info + ... p4 info + ... p4 client -o jenkins-notaclientyettest + P4 Task: establishing connection. ... server: 10.5.10.123:1 ... node: dwhitfield-CentOS7-p4d-withgui Building on Node: master... p4 client -o jenkins-notaclientyettest + ... p4 info + ... p4 info + ... p4 client -o jenkins-notaclientyettest + P4 Task: establishing connection. ... server: 10.5.10.123:1 ... node: dwhitfield-CentOS7-p4d-withgui P4 Task: syncing files at change: -1... p4 sync -q /var/lib/jenkins/workspace/testing labels/...@-1 + P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): Invalid changelist/client/label/date '@-1'. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Tilman Blumenbach updated an issue Jenkins / JENKINS-55203 Jenkins EC2 plugin prints private key contents in Jenkins log Change By: Tilman Blumenbach Released As: Amazon EC2 plug-in v1.44 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196273.1544798485000.7480.1561389780414%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57895) Enable/Disable Job via REST redirects after succeeding causing 403
Title: Message Title James VanderZouwen commented on JENKINS-57895 Re: Enable/Disable Job via REST redirects after succeeding causing 403 ok - thanks. FYI - I was able to get past the redirect using the workaround here: https://stackoverflow.com/questions/52637039/invoke-webrequest-gets-401-on-post-but-not-on-get-with-basic-auth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199859.1559847216000.7476.1561389780367%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58164) how to use when branch keyword
Title: Message Title Karl Wirth resolved as Fixed Seems to work. Jenkins / JENKINS-58164 how to use when branch keyword Change By: Karl Wirth Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200215.156138344.7474.1561389540552%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58164) how to use when branch keyword
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-58164 how to use when branch keyword Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200215.156138344.7472.1561389540524%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58164) how to use when branch keyword
Title: Message Title
Karl Wirth commented on JENKINS-58164
Re: how to use when branch keyword
Hello Hokwang Lee, I have just tested and this seems to work with a multibranch pipeline. In the following only the branch 'main' exists:
pipeline {
agent any
stages {
stage('Checkout') {
when {
branch 'BRANCH_DOES_NOT_EXIST'
}
steps {
echo 'Don't show this...'
}
}
stage('Build') {
when {
branch 'main'
}
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
}
}
The relevant output I get in the console log is:
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
Stage "Checkout" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] echo
Building...
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] echo
Testing...
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Note that the stage 'Checkout' is successfully skipped when I run this against 'main' because it is not 'BRANCH_DOES_NOT_EXIST'.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 build step does not execute a job if the call is not different Change By: Ivan Fernandez Calvo Environment: Jenkins ver. 2.179, Jenkins ver. 2.182, and Jenkins ver. 2.150.2BO 1.16.0 and BO 1.17.0 Pipeline: 2.6Pipeline: API 2.35Pipeline: Build Step 2.9Pipeline: Declarative 1.3.9Pipeline: Groovy 2.70 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200217.1561384383000.7468.1561389420147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 build step does not execute a job if the call is not different Change By: Ivan Fernandez Calvo Environment: Jenkins ver. 2.179 and , Jenkins ver. 2.182 , and Jenkins ver. 2.150.2 BO 1.16.0 and BO 1.17.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.200217.1561384383000.7467.1561389120081%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-58166
Re: build step does not execute a job if the call is not different
if you set the wait to false it does not help also{code}node(){def parallelTasks = [:]parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-07'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}parallelTasks['pstep-08'] = {build job: 'test-dummy', quietPeriod: 15 , wait: false }parallel(parallelTasks)}{code}{code}Starting building: test-dummy #63{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.200217.1561384383000.7466.1561388100047%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-58166
Re: build step does not execute a job if the call is not different
if you set the wait to false it does not help also
node(){
def parallelTasks = [:]
parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-07'] = {build job: 'test-dummy', quietPeriod: 15, wait: false}
parallelTasks['pstep-08'] = {build job: 'test-dummy', quietPeriod: 15}
parallel(parallelTasks)
}
Starting building: test-dummy #63
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Amadeu Carvalho commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN hello Sanket, I'm having the same problem Can you solve 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.196500.1546530449000.7430.1561387740978%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-58166
build step does not execute a job if the call is not different
Change By:
Ivan Fernandez Calvo
If you launch a job with the build step on a parallel way only the first stage has the link to the downstream job, this should change recently it was working using the parallel step, and it was not working with parallel stages, now both are broken. Digging a little seems like build step does not execute a job if the call is not different, so it is not possible to run the same job N times with the build step on parallel stages, even do in concurrent builds. !image-2019-06-24-15-43-26-909.png|thumbnail! !image-2019-06-24-15-43-39-955.png|thumbnail! !image-2019-06-24-15-43-49-073.png|thumbnail! !image-2019-06-24-15-43-57-438.png|thumbnail! Main job{code}pipeline { agent { label 'master' } stages {stage('Parallel step'){ steps { script { def parallelTasks = [:] parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-07'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-08'] = {build job: 'test-dummy', quietPeriod: 15} parallel(parallelTasks) } }}stage('Parallel stages'){ parallel {stage('ps-01'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-02'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-03'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-04'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-05'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-06'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-07'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-08'){steps{build job: 'test-dummy', quietPeriod: 15}} }} }}{code}test-dummy job, it is configured to keep 100 builds{code}node(){ echo "hello"}{code}
[JIRA] (JENKINS-58166) build step does not execute a job if the call is not different
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 build step does not execute a job if the call is not different Change By: Ivan Fernandez Calvo Summary: downstream jobs lose the build step does not execute a job link if the call is not different Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200217.1561384383000.7422.1561387260057%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57895) Enable/Disable Job via REST redirects after succeeding causing 403
Title: Message Title Daniel Beck commented on JENKINS-57895 Re: Enable/Disable Job via REST redirects after succeeding causing 403 The client needs to be instructed to send auth headers with every request. You're already jumping through hoops because Powershell apparently cannot send regular auth without a 401 challenge. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199859.1559847216000.7416.1561386960342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58168) java.io.InterruptedIOException: executor rejected
Title: Message Title
Amadeu Carvalho created an issue
Jenkins / JENKINS-58168
java.io.InterruptedIOException: executor rejected
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-06-24 14:33
Priority:
Minor
Reporter:
Amadeu Carvalho
jenkins 2.170 kubernetes 1.14.9 We have the same problem, running version 1.14.9 of the plugin. This error occurs sometimes
[Pipeline] { (Delete old jobs)
[Pipeline] sh
java.io.InterruptedIOException: executor rejected
at okhttp3.RealCall$AsyncCall.executeOn(RealCall.java:185)
at okhttp3.Dispatcher.promoteAndExecute(Dispatcher.java:186)
at okhttp3.Dispatcher.enqueue(Dispatcher.java:137)
at okhttp3.RealCall.enqueue(RealCall.java:126)
at okhttp3.internal.ws.RealWebSocket.connect(RealWebSocket.java:193)
at okhttp3.OkHttpClient.newWebSocket(OkHttpClient.java:435)
at io.fabric8.kubernetes.client.dsl.internal.PodOperationsImpl.exec(PodOperationsImpl.java:274)
at io.fabric8.kubernetes.client.dsl.internal.PodOperationsImpl.exec(PodOperationsImpl.java:58)
at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:333)
at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:246)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
...
...
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by:
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 downstream jobs lose the job link Change By: Ivan Fernandez Calvo Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200217.1561384383000.7410.1561386660171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58166 Re: downstream jobs lose the job link but if you launch concurrent build of the main job, it would launch the same jobs on every build I guess because the parameter is the same build #9 Starting building: test-dummy #48 Starting building: test-dummy #46 Starting building: test-dummy #47 Starting building: test-dummy #45 Starting building: test-dummy #52 Starting building: test-dummy #51 Starting building: test-dummy #49 Starting building: test-dummy #50 build #10 Starting building: test-dummy #48 Starting building: test-dummy #46 Starting building: test-dummy #47 Starting building: test-dummy #45 Starting building: test-dummy #52 Starting building: test-dummy #51 Starting building: test-dummy #49 Starting building: test-dummy #50 build #11 Starting building: test-dummy #48 Starting building: test-dummy #46 Starting building: test-dummy #47 Starting building: test-dummy #45 Starting building: test-dummy #52 Starting building: test-dummy #51 Starting building: test-dummy #49 Starting building: test-dummy #50 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57895) Enable/Disable Job via REST redirects after succeeding causing 403
Title: Message Title James VanderZouwen commented on JENKINS-57895 Re: Enable/Disable Job via REST redirects after succeeding causing 403 can you elaborate? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199859.1559847216000.7404.1561386480252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58167) Add option to not store affected files
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-58167
Add option to not store affected files
Change By:
Ulli Hafner
Summary:
Add option to not store affected files -with-issues folders excessively large
Issue Type:
Bug Improvement
We are using the warnings-ng plugin to analyze some of our projects with the following code{code:java}recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')] {code}This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin.An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-58166
Re: downstream jobs lose the job link
In order to launch the correct number of jobs with the build step, I have to add a parameter to the job and put a random value to make it works
pipeline {
agent { label 'master' }
stages {
stage('Parallel step'){
steps {
script {
def parallelTasks = [:]
parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '1')]}
parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '2')]}
parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '3')]}
parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '4')]}
parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '5')]}
parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '6')]}
parallelTasks['pstep-07'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '7')]}
parallelTasks['pstep-08'] = {build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '8')]}
parallel(parallelTasks)
}
}
}
stage('Parallel stages'){
parallel {
stage('ps-01'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '10')]
}
}
stage('ps-02'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '11')]
}
}
stage('ps-03'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '12')]
}
}
stage('ps-04'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '13')]
}
}
stage('ps-05'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '14')]
}
}
stage('ps-06'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '15')]
}
}
stage('ps-07'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '16')]
}
}
stage('ps-08'){
steps{
build job: 'test-dummy', quietPeriod: 15, parameters: [string(name: 'random', value: '17')]
}
}
}
}
}
}
pipeline{
agent { label 'master' }
parameters {
string defaultValue: '', description: '', name: 'random', trim: false
}
stages {
stage('Parallel step'){
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title
Amadeu Carvalho commented on JENKINS-55392
Re: java.util.concurrent.RejectedExecutionException AGAIN
any update on the problem? We still see similar issues: kubernetes plugin 1.14.9, jenkins 2.170
[Pipeline] { (Delete old jobs)
[Pipeline] sh
java.io.InterruptedIOException: executor rejected
at okhttp3.RealCall$AsyncCall.executeOn(RealCall.java:185)
at okhttp3.Dispatcher.promoteAndExecute(Dispatcher.java:186)...
Caused by: java.util.concurrent.RejectedExecutionException: Task okhttp3.RealCall$AsyncCall@192d2ae5 rejected from java.util.concurrent.ThreadPoolExecutor@698d8fe9[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 228] ...
hudson.remoting.ProxyException: io.fabric8.kubernetes.client.KubernetesClientException: No response
at io.fabric8.kubernetes.client.dsl.internal.ExecWebSocketListener.onFailure(ExecWebSocketListener.java:230)
at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:571)
at okhttp3.internal.ws.RealWebSocket$2.onFailure(RealWebSocket.java:221)
at okhttp3.RealCall$AsyncCall.executeOn(RealCall.java:188)
at okhttp3.Dispatcher.promoteAndExecute(Dispatcher.java:186)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196500.1546530449000.7366.1561386301720%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58166 Re: downstream jobs lose the job link Ok, in the example it only launching 2 jobs one per parallel block, it does not correct I've launched 16 jobs, but this would be another bug Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Starting building: test-dummy #19 Scheduling project: test-dummy [Pipeline] build (Building test-dummy) (hide) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy [Pipeline] build (Building test-dummy) Scheduling project: test-dummy Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Starting building: test-dummy #20 Add Comment
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 downstream jobs lose the job link Change By: Ivan Fernandez Calvo Environment: Jenkins ver. 2.179 and Jenkins ver. 2.182 BO 1.16.0 and BO 1.17.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.200217.1561384383000.7357.156138546%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-58166 downstream jobs lose the job link Change By: Ivan Fernandez Calvo Environment: Jenkins ver. 2.179 and Jenkins ver. 2.182 BO 1.16.0 and BO 1.17.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.200217.1561384383000.7356.1561385400249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title Bogdan Grosu edited a comment on JENKINS-58141 Re: Jenkins Startup issues with jobConfigHistory I am running the same version as you tried. Is it possible to be some misconfiguration in the XML files?Within my team, we are baking the Jenkins configurations via XML files and then we build the docker image and deploy it. Nothing is done manually, every config that we do is configured inside the XML file.Let me know what kind of configuration files do you need so I can share with you? I might miss something and broke the XML files. Although this issue started since Jenkins was upgraded to the latest version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200186.156111651.7352.1561385040403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title Bogdan Grosu commented on JENKINS-58141 Re: Jenkins Startup issues with jobConfigHistory I am running the same version as you tried. Is it possible to be some misconfiguration in the XML files? Within my team, we are baking the Jenkins configurations via XML files and then we build the docker image and deploy it. Nothing is done manually, every config that we do is configured inside the XML file. Let me know what kind of configuration files do you need so I can share with you? I might miss something and broke the XML files. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200186.156111651.7350.1561385040341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58167) files-with-issues folders excessively large
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-58167 files-with-issues folders excessively large Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-06-24 13:59 Environment: Jenkins 2.164.3 warnings-ng 5.1.0 Priority: Minor Reporter: Philipp Moeller We are using the warnings-ng plugin to analyze some of our projects with the following code recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')] This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin. An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-58166
downstream jobs lose the job link
Change By:
Ivan Fernandez Calvo
If you launch a job with the build step on a parallel way only the first stage has the link to the downstream job, this should change recently it was working using the parallel step, and it was not working with parallel stages, now both are broken. !image-2019-06-24-15-43-26-909.png|thumbnail! !image-2019-06-24-15-43-39-955.png|thumbnail! !image-2019-06-24-15-43-49-073.png|thumbnail! !image-2019-06-24-15-43-57-438.png|thumbnail! Main job{code}pipeline { agent { label 'master' } stages {stage('Parallel step'){ steps { script { def parallelTasks = [:] parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-07'] = {build job: 'test-dummy', quietPeriod: 15} parallelTasks['pstep-08'] = {build job: 'test-dummy', quietPeriod: 15} parallel(parallelTasks) } }}stage('Parallel stages'){ parallel {stage('ps-01'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-02'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-03'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-04'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-05'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-06'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-07'){steps{build job: 'test-dummy', quietPeriod: 15}}stage('ps-08'){steps{build job: 'test-dummy', quietPeriod: 15}} }} }}{code}test-dummy job , it is configured to keep 100 builds {code}node(){ echo "hello"}{code}
[JIRA] (JENKINS-58166) downstream jobs lose the job link
Title: Message Title
Ivan Fernandez Calvo created an issue
Jenkins / JENKINS-58166
downstream jobs lose the job link
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2019-06-24-15-43-26-909.png, image-2019-06-24-15-43-39-955.png, image-2019-06-24-15-43-49-073.png, image-2019-06-24-15-43-57-438.png
Components:
blueocean-plugin
Created:
2019-06-24 13:53
Environment:
Jenkins ver. 2.179 BO 1.16.0 and BO 1.17.0
Priority:
Major
Reporter:
Ivan Fernandez Calvo
If you launch a job with the build step on a parallel way only the first stage has the link to the downstream job, this should change recently it was working using the parallel step, and it was not working with parallel stages, now both are broken. Main job
pipeline {
agent { label 'master' }
stages {
stage('Parallel step'){
steps {
script {
def parallelTasks = [:]
parallelTasks['pstep-01'] = {build job: 'test-dummy', quietPeriod: 15}
parallelTasks['pstep-02'] = {build job: 'test-dummy', quietPeriod: 15}
parallelTasks['pstep-03'] = {build job: 'test-dummy', quietPeriod: 15}
parallelTasks['pstep-04'] = {build job: 'test-dummy', quietPeriod: 15}
parallelTasks['pstep-05'] = {build job: 'test-dummy', quietPeriod: 15}
parallelTasks['pstep-06'] = {build job: 'test-dummy', quietPeriod: 15}
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-58165 support-core doesn't take into account %t on GC logs Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-06-24 13:51 Priority: Minor Reporter: Ramon Leon When you specify %t in the log file for garbage collection: Xloggc:$path/gc%t.log: specifies where the verbose GC data is written to. The %t in the gc log file path will cause the JVM to generate a new file with each JVM restart with a timestamp. From: https://go.cloudbees.com/docs/solutions/jvm-troubleshooting/ The support-core plugin cannot find the log file used for that, so it doesn't include the file in the bundle. It throws the warning: Jun 24, 2019 3:42:25 PM com.cloudbees.jenkins.support.impl.GCLogs addContents WARNING: [Support Bundle] GC Logging apparently configured, but file '/JENKINS HOME PATH/gc-%t.log' not found The reason is that the code looks for the exact file name, but it should be a pattern: https://github.com/jenkinsci/support-core-plugin/blob/5fb61461e578fa82190c8a1f1dd5efd95235702f/src/main/java/com/cloudbees/jenkins/support/impl/GCLogs.java#L80
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58119 Cant run P4Groovy sync on multiple executors Change By: Karl Wirth Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200164.1561045657000.7334.1561383900072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58119 Cant run P4Groovy sync on multiple executors Change By: Karl Wirth Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200164.1561045657000.7333.1561383841634%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58164) how to use when branch keyword
Title: Message Title
Hokwang Lee updated an issue
Jenkins / JENKINS-58164
how to use when branch keyword
Change By:
Hokwang Lee
Hi, Is there a p4 way for below ? Please refer to [https://jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/]There's _expression_ like {code:java} ``` stage('a') { when { branch 'dev' } steps { } } {code} ``` How can I use for this in p4?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200215.156138344.7332.1561383540060%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
