[JIRA] (JENKINS-58024) Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses
Title: Message Title Raihaan Shouhell started work on JENKINS-58024 Change By: Raihaan Shouhell 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.200044.156053795.9003.1561528500422%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58024) Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses
Title: Message Title Raihaan Shouhell assigned an issue to Raihaan Shouhell Jenkins / JENKINS-58024 Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses Change By: Raihaan Shouhell Assignee: FABRIZIO MANFREDI Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200044.156053795.9001.1561528500396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58024) Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses
Title: Message Title Raihaan Shouhell updated JENKINS-58024 Jenkins / JENKINS-58024 Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses Change By: Raihaan Shouhell 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.200044.156053795.9005.1561528500471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Raihaan Shouhell commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version tapvir virk can you try the build from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ec2/1.45-rc980.7e1580e3f8d5/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8997.1561526520115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58202) File-pattern of report-files no longer configurable
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-58202 File-pattern of report-files no longer configurable Issue Type: Bug Assignee: Nikolas Falco Attachments: screen-xunit.jpg Components: xunit-plugin Created: 2019-06-26 04:51 Environment: Jenkins ver. 2.176.1, Windows server 2019 x64 xUnit-plugin 2.3.5 Priority: Critical Reporter: GMC Software Development B Corporate In "older" freestyle-jobs the file-pattern is still used, but with the current xUnit-release 2.3.5 this parameter is no longer shown nor can be changed. Within the raw XML-config-file of these older jobs the XML-item beginns with and have still have an pattern-entry. See attached sreenshot (screen-xunit.jpg) showing the current presentation of this post-build action ... Best regards from Salzburg, Markus
[JIRA] (JENKINS-58180) How to retrieve JIRA task status using jira-steps-plugin
Title: Message Title hhkkss updated an issue Jenkins / JENKINS-58180 How to retrieve JIRA task status using jira-steps-plugin Change By: hhkkss Issue Type: Task 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.200231.1561451131000.8991.1561522260263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Raihaan Shouhell started work on JENKINS-58193 Change By: Raihaan Shouhell 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.200248.1561491352000.8988.1561520400231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Raihaan Shouhell assigned an issue to Raihaan Shouhell Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: Raihaan Shouhell Assignee: Matt Sicker Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8986.1561519740252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Raihaan Shouhell commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Hey Tapvir can you show us your agent configuration? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8983.1561517700157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58182 azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200233.1561454364000.8978.1561513560317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58182) azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs
Title: Message Title Jie Shen commented on JENKINS-58182 Re: azure-commons blocks starting Jenkins when dc.services.visualstudio.com hangs I will look into 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.200233.1561454364000.8980.1561513560347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58201) com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com
Title: Message Title vanchinathan lokanathan created an issue Jenkins / JENKINS-58201 com.amazonaws.SdkClientException: Unable to execute HTTP request: sts.amazonaws.com Issue Type: Bug Assignee: Vincent Latombe Attachments: aws-error-jenkins-2019-06-26_08h36_23.png Components: aws-java-sdk-plugin Created: 2019-06-26 00:44 Environment: using Jenkins ver. 2.176.1 plugin and its version: please refer to the attachment Priority: Major Reporter: vanchinathan lokanathan We are build a spring boot application configured as a maven project in Jenkins. The job is able to build our the artifacts successful but in the end of the build the error happens. Please refer to the exception below. I am not sure about this error. Please help to resolve. Exception: [INFO] repository-server .. SUCCESS [ 12.009 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 05:38 min [INFO] Finished at: 2019-06-25T18:31:41+08:00 [INFO] Final Memory: 332M/1048M [INFO] Waiting for Jenkins to finish collecting data [JENKINS] Archiving cleanInstallBsinno/plugin-sdk/plugin-generator/generator-templates-java/pom.xml to
[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"
Title: Message Title Henry Chen updated an issue Jenkins / JENKINS-58200 Console logs are masking my data as "FILTERED" Change By: Henry Chen Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200256.1561506249000.8973.1561506300332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"
Title: Message Title
Henry Chen created an issue
Jenkins / JENKINS-58200
Console logs are masking my data as "FILTERED"
Issue Type:
Bug
Assignee:
Tzach Solomon
Components:
console-log-text-replacer-plugin
Created:
2019-06-25 23:44
Environment:
Jenkins ver. 2.131
Priority:
Minor
Reporter:
Henry Chen
I have a job that pulls log files from AWS and scrubs it. This issue has started sometime within the last week or two where my Jenkins console is masking my data. Has anyone encountered this? Jenkins console shows: {:timestamp=>156123100590, :message=>"[FILTERED]", :ingestion_time=>1562203601119} My local (laptop) shows : {:timestamp=>156123100590, :message=>"[ACTUAL DATA PULLED FROM AWS]", :ingestion_time=>1562203601119}
Add Comment
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title
Henry Chen edited a comment on JENKINS-57990
Re: Avoid filtering contents without sensible data and do per-content anonymization
I've recently (last week) been seeing my console data being masked as "FILTERED". Is this related to the bug/issue? Jenkins console displays: {:timestamp=>15616234449694, :message=>"[FILTERED]", :ingestion_time=>15616234449694} Local displays ( should see ) :{:timestamp=>15616234449694, :message=>"[ACTUAL DATA]", :ingestion_time=>15616234449694}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199975.1560350087000.8969.1561505820139%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title
Henry Chen commented on JENKINS-57990
Re: Avoid filtering contents without sensible data and do per-content anonymization
I've recently (last week) been seeing my console data being masked as "FILTERED". Is this related to the bug/issue? {:timestamp=>15616234449694, :message=>"[FILTERED]", :ingestion_time=>15616234449694} should see: {:timestamp=>15616234449694, :message=>"[ACTUAL DATA]", :ingestion_time=>15616234449694}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199975.1560350087000.8967.1561505760112%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58199) Alpha Release of Plugin Installation Manager Tool
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58199 Alpha Release of Plugin Installation Manager Tool Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-25 23:26 Labels: gsoc-2019 plugin-manager release Priority: Minor Reporter: Natasha Stopa Release the alpha version of the plugin installation manager library and cli. Add Comment
[JIRA] (JENKINS-58198) JIRA plugin passes configuration test but does nothing
Title: Message Title Aaron Sua commented on JENKINS-58198 Re: JIRA plugin passes configuration test but does nothing I tried downgrading the Apache HttpComponents Client 4.x API to 4.5.5-2.1 but the issue persists Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200254.1561502874000.8964.156150339%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58198) JIRA plugin passes configuration test but does nothing
Title: Message Title Aaron Sua created an issue Jenkins / JENKINS-58198 JIRA plugin passes configuration test but does nothing Issue Type: Bug Assignee: Unassigned Attachments: stacktrace.txt Components: jira-plugin Created: 2019-06-25 22:47 Environment: Jenkins ver. 2.164.3 Jira Plugin ver. 3.0.7 Apache HttpComponents Client 4.x API 4.5.5-3.0 Labels: plugin Priority: Critical Reporter: Aaron Sua In the jenkins UI testing the authentication yields a success. When using sample curl commands against the Jira API successful data is returned. However Jobs complete without creating new versions or moving tickets and the Parameter to pickup Jira Versions gets a stack trace. As a result all of the Jira automations have had to be removed from the builds and Jira steps are having to be done manually
[JIRA] (JENKINS-58197) Enable the Release Drafter for the repository
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58197 Enable the Release Drafter for the repository Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-25 22:34 Priority: Minor Reporter: Oleg Nenashev Since there is a plan to have a number of Alpha/Beta releases for the tool, it makes sense to do some automation for changelog generation to save some time. Jenkins project supports Release Drafter, and I suggest enabling it. See https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc and the linked examples Add Comment
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Jonathan B edited a comment on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We're also experiencing this after an upgrade to BlueOcean 1.17.0 and Jenkins 2.176.1. I filed https://issues.jenkins-ci.org/browse/JENKINS-58145 about it. I tried downgrading BlueOcean back to 1.16.0 but that didn't actually help. I also tried downgrading all the pipeline-model* plugins from 1.39 back to 1.38 (which was the version we were on when this was working properly), but that also did not help. From my hasty testing, my best guess right now is that the issue was introduced by one of workflow-step-api:2.20 (2.19 was fine), workflow-durable-task-step:2.31 (2.30 was fine), or workflow-cps:2.70 (2.69 was fine). Those are tricky to downgrade because there is some complicated web of dependencies that require us to be on the latest of all of them. Since you mention that downgrading BlueOcean to 1.16 fixed it for you, I will have to try that 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.200110.1560887329000.8956.1561501440175%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 Jonathan B commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" We're also experiencing this after an upgrade to BlueOcean 1.17.0 and Jenkins 2.176.1. I filed https://issues.jenkins-ci.org/browse/JENKINS-58145 about it. I tried downgrading BlueOcean back to 1.16.0 but that didn't actually help. I also tried downgrading all the pipeline-model* plugins from 1.39 back to 1.38 (which was the version we were on when this was working properly), but that also did not help. From my hasty testing, my best guess right now is that the issue was introduced by one of workflow-step-api:2.20 (2.19 was fine), workflow-durable-task-step:2.31 (2.30 was fine), or workflow-cps:2.70 (2.69 was fine). Those are tricky to downgrade because there is some complicated web of dependencies that require us to be on the latest of all of them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an 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.8950.1561501320729%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58196) UTF8 BOM override issue in 1.10.0
Title: Message Title Peter Hopkins created an issue Jenkins / JENKINS-58196 UTF8 BOM override issue in 1.10.0 Issue Type: Bug Assignee: Unassigned Attachments: packages.config, packages.config.borked Components: p4-plugin Created: 2019-06-25 22:17 Environment: p4-plugin 1.10.0 jenkins 2.176.1 docker lts image ubuntu Server version: P4D/LINUX26X86_64/2017.1/1622573 (2018/02/20) Priority: Blocker Reporter: Peter Hopkins In upgrading from 1.9.6 to 1.10.1 it seems that the utf8bom filesys options is no longer honoured. Might be related to the p4java upgrade? We use this normally on a windows slave to correct old utf8bom issues. -Dcom.perforce.p4java.filesys.utf8bom=0 Attached is a packages.config file synced correctly, and packages.config.borked which is the same file synced with an extra bom character Add
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson commented on JENKINS-53322 Re: Remove patched dom4j from Stapler I've been working on this one for a while, compiling different libraries and plugins and running tests and checks. The specific tasks or conclusions I've found are a little different from those originally reported, but the overview remains the same. The forked dom4j version we use is ancient and really isn't necessary. We can get rid of it with a relatively few, independent tweaks. That will get us on a better footing. I'll start pushing a few PRs to various components to prepare them. Once we actually make the switch there are a few other places we can clean up. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an 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.8946.1561500360184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Mark Waite commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Jim D this issue won't be fixed in 4.0.0. The incompatibilities from the BuildDetails change were too great for the community. The accidental release of git plugin 4.0.0-rc to the production update centers showed incompatibilities that I had missed in my testing and that others had missed in their testing. BuildData will be the same bloated memory user in 4.0.0 that it is in 3.x. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150469.1375284228000.8940.1561499402387%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors
Title: Message Title Stanislav Zapolsky commented on JENKINS-57595 Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors We are having exactly the same issue as Kevin Nelson described. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199519.1558510674000.8864.1561497720312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title
Will Curry updated an issue
Jenkins / JENKINS-47496
No automatic builds for tags
Change By:
Will Curry
After upgrading to the Git Plugin 3.6.0 I activated the "Discover Tags" option in a Multibranch Pipeline Job. The tag is also discovered as expected, but no build is triggered. {code:java}Checking tags... Checking tag PNR-12345 ‘Jenkinsfile’ found Met criteria Changes detected: PNR-12345 (null → d56c6578f5f04403f4bd64bf2647f3dd0f36e826) No automatic builds for PNR-12345 Processed 1 tags{code}I expected that a new build is triggered, when a new tag is found. How to achieve this?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.8852.1561497660399%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58195) promoted builds plugin incompatible with Artifactory plugin
Title: Message Title Chris Warren created an issue Jenkins / JENKINS-58195 promoted builds plugin incompatible with Artifactory plugin Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2019-06-25 21:02 Priority: Minor Reporter: Chris Warren When using the Artifactory plugin, the promoted-builds plugin, version 3.3, is not compatible. Having it installed results in being unable to configure artifactory plugin settings in job configurations. Specifically the target repository drop down field will not populate, even after a successful api call to retrieve the available repositories. Also, the upload URL field is duplicated on the screen. Downgrading promoted-builds plugin to version 3.2 resolved this problem. This happened with multiple recent artifactory plugin versions. Same behavior each time. Add Comment
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jim D commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Mark Waite, I'm glad I found the comments in this issue, thank you! When the final 4.0.0 is released with the changes for this issue, will it make sure to handle both BuildDetails and BuildData for previous build runs? We updated to 4.0.0-rc some time back, and I just came across this thread recently trying to resolve a BuildData issue, and rolled back to 3.9.3. At this point, Git plugin is working and creating BuildData for each build run, but all those old builds done with 4.0.0-rc don't have any kind of "Git Build Data" in the Jenkins UI anymore, and no BuildData or BuildDetails when retrieved programmatically from WorkflowRun.getAllActions. I think it must be that 3.9.3 isn't able to read the new BuildDetails object info. Will 4.0.0 be able to read both, from both 3.9.X builds and 4.0.0 builds? Thanks 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.150469.1375284228000.8782.1561495441189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48087) URLTrigger Plugin causes stack trace on pipeline job
Title: Message Title Dominic Lam commented on JENKINS-48087 Re: URLTrigger Plugin causes stack trace on pipeline job We have the identical issue as well. And our Jenkins is very recent 2.164.2 is URL trigger plugin 0.45. It seems this has been opened for a very long time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186651.1510930655000.8766.1561494000444%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version This is the exception getting logged in the jenkins logs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8763.1561492740114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58194) Unsatisfied dependencies gitlab-hook
Title: Message Title Kaila Trawitzki created an issue Jenkins / JENKINS-58194 Unsatisfied dependencies gitlab-hook Issue Type: Bug Assignee: Javier Palacios Components: gitlab-hook-plugin, ruby-runtime-plugin Created: 2019-06-25 19:54 Environment: OS: Windows 10 Web browser: Chrome Jenkins version: 2.1.8.2 Labels: plugin Priority: Minor Reporter: Kaila Trawitzki Hi, I am new to Jenkins and DevOps, and I am trying to install the ruby-runtime plugin as I have received this warning message: Correct Dependency errors: Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to restore the functionality provided by these plugins. Gitlab Hook Plugin version 1.4.2 ruby-runtime version 0.12 is missing. To fix, install version 0.12 or later. however, I have downloaded the ruby-runtime plugin three times, as well as restarted Jenkins. Why is it not showing up in my installed plugins?
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title Nathan Vahrenberg edited a comment on JENKINS-57434 Re: Unable to add or edit roles [~oleg_nenashev] is there any other info I can provide that might help? This has been difficult for us to work around unfortunately. Edit: speaking of workarounds, editing the config.xml to add a new entry in the does work after cycling Jenkins. It's not ideal, but we can at least add new permission groups this way Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199247.1557753306000.8754.1561492440239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: Matt Sicker Comment: Do you have more of a stack trace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8752.1561492380119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk updated an issue Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: tapvir virk EC2 instances are getting terminated right away on initializing in 1.44 versionBelow is the error message Jun 25, 2019 3:49:22 PM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0dedca71f82852276Jun 25, 2019 3:49:22 PM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Jun 25, 2019 3:49:22 PM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Jun 25, 2019 3:49:22 PM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-slave (SHA-1 fingerprint e7:f4)Jun 25, 2019 3:49:22 PM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userJun 25, 2019 3:49:23 PM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.188.11.241 on port 22, with timeout 1.Jun 25, 2019 3:49:33 PM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Jun 25, 2019 3:49:33 PM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Jun 25, 2019 3:49:38 PM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Jun 25, 2019 3:50:46 PM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existJun 25, 2019 3:50:46 PM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionopenjdk full version "1 . 8.0_201-b09"Jun 25, 2019 3:50:46 PM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpJun 25, 2019 3:50:46 PM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpJun 25, 2019 3:50:46 PM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead SSH2 Connection): java -jar /tmp/remoting.jar -workDir ERROR: unexpected stream terminationjava. io.EOFException: unexpected stream termination at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:431) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:262) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) It's working fine in 1.43 version
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Matt Sicker commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Do you have more of a stack trace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8750.1561492320433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Alexander Komarov edited a comment on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start I had the same issue when I upgraded only some (not all) plugins while runing Jenkins 2.174. My plugins were all 3-5 months old. # I then installed the *kubernetes* plugin, which * pulled in some dependencies * (some pipeline, etc). The log shows that the upgrade failed (see attached), but Jenkins UI happily restarted on completion.# Jenkins would not start (error in this ticket)# I restored plugins, Jenkins started# I then upgraded all plugins, Jenkins started fine. [^upgrade-log.txt] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198873.1555704698000.8746.1561492260158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-57123 Script Security Plugins latests version caused Jenkins 2.173 failed to start Change By: Alexander Komarov Attachment: upgrade-log.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198873.1555704698000.8740.1561492200277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Alexander Komarov commented on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start I had the same issue when I upgraded only some (not all) plugins while runing Jenkins 2.174. My plugins were all 3-5 months old. I then installed the kubernetes plugin, which pulled in some dependencies (some pipeline, etc). The log shows that the upgrade failed (see attached), but Jenkins UI happily restarted on completion. Jenkins would not start (error in this ticket) I restored plugins, Jenkins started I then upgraded all plugins, Jenkins started fine. upgrade-log.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198873.1555704698000.8743.1561492200341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk updated an issue Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: tapvir virk EC2 instances are getting terminated right away on initializing in 1.44 version Below is the error messagejava.io.EOFException: unexpected stream termination Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.8735.1561491480312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk updated an issue Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Change By: tapvir virk EC2 instances are getting terminated right away on initializing in 1.44 versionBelow is the error messagejava.io.EOFException: unexpected stream termination It's working fine in 1.43 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.200248.1561491352000.8737.1561491480341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk created an issue Jenkins / JENKINS-58193 EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Issue Type: Bug Assignee: Matt Sicker Components: ec2-plugin Created: 2019-06-25 19:35 Priority: Blocker Reporter: tapvir virk EC2 instances are getting terminated right away on initializing in 1.44 version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title Nathan Vahrenberg commented on JENKINS-57434 Re: Unable to add or edit roles Oleg Nenashev is there any other info I can provide that might help? This has been difficult for us to work around unfortunately. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199247.1557753306000.8726.1561491240257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58084) Vetoable version of GraphListener
Title: Message Title Andrew Bayer started work on JENKINS-58084 Change By: Andrew Bayer 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.200109.1560881323000.8724.1561489620317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58084) Vetoable version of GraphListener
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-58084 Vetoable version of GraphListener Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200109.1560881323000.8722.1561489620293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila closed an issue as Cannot Reproduce Jenkins / JENKINS-57767 Remote call failed Change By: John Zila Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199714.1559241868000.8720.1561488120755%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila commented on JENKINS-57767 Re: Remote call failed This seems to not be happening any more. I'm going to close the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199714.1559241868000.8718.1561488060483%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) showRawYaml doesn't work inside podTemplate
Title: Message Title Oliver Nocon commented on JENKINS-57717 Re: showRawYaml doesn't work inside podTemplate addressed via https://github.com/jenkinsci/kubernetes-plugin/pull/519 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199660.1559055292000.8716.1561486680121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Change By:
Jon Kelley
Job error:*No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types* I have defined a job pipeline DSL from SCM according to documentation:{code:java}node('master'){withEnv(['JENKINS_CREDENTIAL_ID_GITHUB=540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f','GIT_BRANCH=development','GIT_REPO=g...@github.com:x/x.git','GROOVY_SCRIPT_DIR=jenkinsfiles','GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy']){stage('Clean Workspace') {cleanWs()}stage('Clone sources') {git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"}stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {def repos = "a,b,c,d"dir("${env.GROOVY_SCRIPT_DIR}") {sh "echo CWD is `pwd`"// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#use-job-dsl-in-pipeline-scriptsstep([$class: 'ExecuteDslScripts',targets: "${env.GROOVY_SCRIPT_FILENAME}",removedJobAction: 'IGNORE',removedViewAction: 'IGNORE',removedViewAction: 'IGNORE',lookupStrategy: 'SEED_JOB',additionalParameters: [REPO_LIST: "${repos}"] // repos PARAM was created manually])}}}} {code} This executes my groovy script, which fails when building with the error: ERROR: (dslCreatePushPipeline.groovy, line 9) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types: (java.lang.String) values: [swarm] Here is "dslCreatePipeline.groovy" for reference. If there is proper way to set worker labels, let me know. This works fine when pasting the script into ""Process job DSL"" box inline so I am assuming there's a bug here.{code:java}def repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")println "Generating PR push jobs for the following repos:: $repoList"repoList.each { def cookbook = it pipelineJob("${cookbook}-PR-push") {label('swarm') // this is throwing an error // why does this work without SCM?description("Chef push pipeline job")properties { githubProjectUrl("https://github.com/git_org/${cookbook}/")}scm { git {remote { github("git_org/${cookbook}", 'ssh') refspec('+refs/pull/*:refs/remotes/origin/pr/*') credentials('d6f6e9f1-43cb-4ea1-83da-e5581d3f9472')}branch('${ghprbActualCommit}')extensions { relativeTargetDirectory("${cookbook}")}configure { gitScm -> gitScm / 'extensions' << 'hudson.plugins.git.extensions.impl.UserExclusion' {
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Change By:
Jon Kelley
I have defined a job pipeline DSL from SCM according to documentation:{code:java}node('master'){withEnv(['JENKINS_CREDENTIAL_ID_GITHUB=540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f','GIT_BRANCH=development','GIT_REPO=g...@github.com:x/x.git','GROOVY_SCRIPT_DIR=jenkinsfiles','GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy']){stage('Clean Workspace') {cleanWs()}stage('Clone sources') {git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"}stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {def repos = "a,b,c,d"dir("${env.GROOVY_SCRIPT_DIR}") {sh "echo CWD is `pwd`"// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves #use-job-dsl-in-pipeline-scripts step([$class: 'ExecuteDslScripts',targets: "${env.GROOVY_SCRIPT_FILENAME}",removedJobAction: 'IGNORE',removedViewAction: 'IGNORE',removedViewAction: 'IGNORE',lookupStrategy: 'SEED_JOB',additionalParameters: [REPO_LIST: "${repos}"] // repos PARAM was created manually])}}}} {code} This executes my groovy script, which fails when building with the error: ERROR: (dslCreatePushPipeline.groovy, line 9) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types: (java.lang.String) values: [swarm] Here is "dslCreatePipeline.groovy" for reference. If there is proper way to set worker labels, let me know. This works fine when pasting the script into ""Process job DSL"" box inline so I am assuming there's a bug here.{code:java}def repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")println "Generating PR push jobs for the following repos:: $repoList"repoList.each { def cookbook = it pipelineJob("${cookbook}-PR-push") {label('swarm') // this is throwing an error // why does this work without SCM?description("Chef push pipeline job")properties { githubProjectUrl("https://github.com/git_org/${cookbook}/")}scm { git {remote { github("git_org/${cookbook}", 'ssh') refspec('+refs/pull/*:refs/remotes/origin/pr/*') credentials('d6f6e9f1-43cb-4ea1-83da-e5581d3f9472')}branch('${ghprbActualCommit}')extensions { relativeTargetDirectory("${cookbook}")}configure { gitScm -> gitScm / 'extensions' << 'hudson.plugins.git.extensions.impl.UserExclusion' {excludedUsers('doxbot') }} }}triggers { githubPullRequest {
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Change By:
Jon Kelley
I have defined a job pipeline DSL from SCM according to documentation:{code:java}node('master'){withEnv(['JENKINS_CREDENTIAL_ID_GITHUB=540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f','GIT_BRANCH=development ' ,'GIT_REPO=g...@github.com:x/x.git','GROOVY_SCRIPT_DIR=jenkinsfiles','GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy']){stage('Clean Workspace') {cleanWs()}stage('Clone sources') {git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"}stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {def repos = "a,b,c,d"dir("${env.GROOVY_SCRIPT_DIR}") {sh "echo CWD is `pwd`"// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Movesstep([$class: 'ExecuteDslScripts',targets: "${env.GROOVY_SCRIPT_FILENAME}",removedJobAction: 'IGNORE',removedViewAction: 'IGNORE',removedViewAction: 'IGNORE',lookupStrategy: 'SEED_JOB',additionalParameters: [REPO_LIST: "${repos}"]])}}}} {code} This executes my groovy script, which fails when building with the error:ERROR: (dslCreatePushPipeline.groovy, line 9) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types: (java.lang.String) values: [swarm] Here is "dslCreatePipeline.groovy" for reference. If there is proper way to set worker labels, let me know. This works fine when pasting the script into ""Process job DSL"" box inline so I am assuming there's a bug here.{code:java}def repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")println "Generating PR push jobs for the following repos:: $repoList"repoList.each { def cookbook = it pipelineJob("${cookbook}-PR-push") {label('swarm') // this is throwing an error // why does this work without SCM?description("Chef push pipeline job")properties { githubProjectUrl("https://github.com/git_org/${cookbook}/")}scm { git {remote { github("git_org/${cookbook}", 'ssh') refspec('+refs/pull/*:refs/remotes/origin/pr/*') credentials('d6f6e9f1-43cb-4ea1-83da-e5581d3f9472')}branch('${ghprbActualCommit}')extensions { relativeTargetDirectory("${cookbook}")}configure { gitScm -> gitScm / 'extensions' << 'hudson.plugins.git.extensions.impl.UserExclusion' {excludedUsers('doxbot') }} }}triggers { githubPullRequest {admin('')orgWhitelist(['git_org'])
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Change By:
Jon Kelley
I have defined a job pipeline DSL from SCM according to documentation:{code:java}node('master'){withEnv(['JENKINS_CREDENTIAL_ID_GITHUB=540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f','GIT_BRANCH=development','GIT_REPO=g...@github.com:x/x.git','GROOVY_SCRIPT_DIR=jenkinsfiles','GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy']){stage('Clean Workspace') {cleanWs()}stage('Clone sources') {git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"}stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {def repos = "a,b,c,d"dir("${env.GROOVY_SCRIPT_DIR}") {sh "echo CWD is `pwd`"// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Movesstep([$class: 'ExecuteDslScripts',targets: "${env.GROOVY_SCRIPT_FILENAME}",removedJobAction: 'IGNORE',removedViewAction: 'IGNORE',removedViewAction: 'IGNORE',lookupStrategy: 'SEED_JOB',additionalParameters: [REPO_LIST: "${repos}"] // repos PARAM was created manually ])}}}} {code} This executes my groovy script, which fails when building with the error: ERROR: (dslCreatePushPipeline.groovy, line 9) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types: (java.lang.String) values: [swarm] Here is "dslCreatePipeline.groovy" for reference. If there is proper way to set worker labels, let me know. This works fine when pasting the script into ""Process job DSL"" box inline so I am assuming there's a bug here.{code:java}def repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")println "Generating PR push jobs for the following repos:: $repoList"repoList.each { def cookbook = it pipelineJob("${cookbook}-PR-push") {label('swarm') // this is throwing an error // why does this work without SCM?description("Chef push pipeline job")properties { githubProjectUrl("https://github.com/git_org/${cookbook}/")}scm { git {remote { github("git_org/${cookbook}", 'ssh') refspec('+refs/pull/*:refs/remotes/origin/pr/*') credentials('d6f6e9f1-43cb-4ea1-83da-e5581d3f9472')}branch('${ghprbActualCommit}')extensions { relativeTargetDirectory("${cookbook}")}configure { gitScm -> gitScm / 'extensions' << 'hudson.plugins.git.extensions.impl.UserExclusion' {excludedUsers('doxbot') }} }}triggers { githubPullRequest {admin('')
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley created an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-06-25 17:16
Environment:
Job-dsl-plugin: 1.74 Jenkins: 2.176.1
Priority:
Minor
Reporter:
Jon Kelley
I have defined a job pipeline DSL from SCM according to documentation:
node('master')
{
withEnv([
'JENKINS_CREDENTIAL_ID_GITHUB=540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f',
'GIT_BRANCH=development,
'GIT_REPO=g...@github.com:x/x.git',
'GROOVY_SCRIPT_DIR=jenkinsfiles',
'GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy'
]){
stage('Clean Workspace') {
cleanWs()
}
stage('Clone sources') {
git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"
}
stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {
def repos = "a,b,c,d"
dir("${env.GROOVY_SCRIPT_DIR}") {
sh "echo CWD is `pwd`"
// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves
step([
$class: 'ExecuteDslScripts',
targets: "${env.GROOVY_SCRIPT_FILENAME}",
removedJobAction: 'IGNORE',
removedViewAction: 'IGNORE',
removedViewAction: 'IGNORE',
lookupStrategy: 'SEED_JOB',
additionalParameters: [REPO_LIST:
[JIRA] (JENKINS-57865) Enhance plugin installation manager by fixing installation script docker issues
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-57865 Enhance plugin installation manager by fixing installation script docker issues Change By: Natasha Stopa Sprint: GSoC 2019. Coding Phase 1 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199827.1559753516000.8698.1561482721637%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57865) Enhance plugin installation manager by fixing installation script docker issues
Title: Message Title Natasha Stopa commented on JENKINS-57865 Re: Enhance plugin installation manager by fixing installation script docker issues Changed sprint to coding phase 2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199827.1559753516000.8697.1561482721290%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58123) Recursively Resolve Dependencies for Downloaded Plugins
Title: Message Title Natasha Stopa updated JENKINS-58123 Jenkins / JENKINS-58123 Recursively Resolve Dependencies for Downloaded Plugins Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200168.1561050492000.8689.1561482660523%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58075) Create demo for end of Phase 1 coding period
Title: Message Title Natasha Stopa updated JENKINS-58075 Jenkins / JENKINS-58075 Create demo for end of Phase 1 coding period Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200099.1560871996000.8695.1561482660799%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57800) Convert Docker Plugin Bash Script to Java
Title: Message Title Natasha Stopa updated JENKINS-57800 Jenkins / JENKINS-57800 Convert Docker Plugin Bash Script to Java Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199751.1559326912000.8693.1561482660751%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57869) Add CI to repository
Title: Message Title Natasha Stopa updated JENKINS-57869 Jenkins / JENKINS-57869 Add CI to repository Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199832.1559780313000.8688.1561482600096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58191) Get information about security and available updates from CLI w/o installing plugins
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58191 Get information about security and available updates from CLI w/o installing plugins Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-25 17:07 Labels: gsoc-2019 plugin-manager cli Priority: Minor Reporter: Natasha Stopa The current CLI tool for plugin management will defaults in the plugin .txt file listing the plugins to download and plugin directory to install plugins if none are entered and will automatically download plugins if no CLI options regarding plugin downloads are chosen. This leads to unexpected behavior if the user choses to see the security warnings, since they might expect to only see this information and not download plugins at the same time. Add Comment
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Jake Hilborn edited a comment on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline I believe I tested this on Jenkins 2.164.2. However, it doesn't work well enough to be usable. Console logs are duplicated and shown in multiple stages when using this sequential inside parallel hack. It makes the approach useless. For example, in the image I posted above, I would see "one-child2" console messages inside the "one-child2" stage and the "two-child2" stage which makes debugging very confusing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193173.1534855202000.8620.1561480143284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Jake Hilborn commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline I believe I tested this on 2.164.2. However, it doesn't work well enough to be usable. Console logs are duplicated and shown in multiple stages when using this sequential inside parallel hack. It makes the approach useless. For example, in the image I posted above, I would see "one-child2" console messages inside the "one-child2" stage and the "two-child2" stage which makes debugging very confusing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193173.1534855202000.8618.1561480143262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev commented on JENKINS-57604 Re: Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC https://github.com/jenkinsci/configuration-as-code-plugin/pull/932 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199530.1558528518000.8553.1561479962159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev commented on JENKINS-57604 Re: Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC After some discovery, it looks like the issue is on the JCasC plugin side. We need to update HeteroDescribableConfigurator to properly match cases when a field type does not represent a root extension class for which we can fetch descriptors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199530.1558528518000.8552.1561479961590%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev updated JENKINS-57604 Jenkins / JENKINS-57604 Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199530.1558528518000.8554.1561479962510%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57604 Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC Change By: Oleg Nenashev Component/s: configuration-as-code-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.199530.1558528518000.8551.1561479240060%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58190) timeout on parallel sequential stage killed processes in the wrong stage!
Title: Message Title boris ivan created an issue Jenkins / JENKINS-58190 timeout on parallel sequential stage killed processes in the wrong stage! Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-06-25 15:57 Priority: Blocker Reporter: boris ivan I have a pipeline with parallel sequential stages. In one of the sequential stages (that has multiple 'stages'), there was a stage that had a timeout of 20 minutes. That stage took too long, but instead of it being aborted – a different stage had a process killed – a maven build running in a different parallel sequential stream abruptly aborted. Something in parallel stages isn't being tracked properly in the pipeline, I think. once my pipeline gets to the "testing" phase, there are a few parallel stages (some of which have multiple stages), like this: a--b--c -d-e- ---g--- ---h--- ---i In my case, b had a timeout of 20 minutes. But it ran for 24 with nothing stopping it – the stage is a shell script step running a suite of npm/node.js tests. At the 24 minute mark when it finished normally (but should have been aborted at 20 minutes!!), stage e abruptly had it's maven surefire unit tests abort mid-suite. It's at exactly the same time that stage b finished (which should have aborted earlier) It's as if the code set to kill the processes due to the timeout was delayed ignored by stage "b", and then stage "e" ended up being the victim.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-57604 Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199530.1558528518000.8548.1561477560105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57604) Git Plugin: assemblaWeb browser configuration can be exported but not configured by JCasC
Title: Message Title Oleg Nenashev started work on JENKINS-57604 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199530.1558528518000.8549.1561477560153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Gaurav Chhabra commented on JENKINS-45455 Re: Restarting stages Thanks for the response Blake Devcich. Hardware dependency can definitely be one reason but will tying a job to a slave also ensure that subsequent builds will use the same workspace which was used by last failed build? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183623.1499805325000.8547.1561476363531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58189) Submitting user input causes unhandledPromiseRejection in Blue Ocean
Title: Message Title Andrei Muresianu created an issue Jenkins / JENKINS-58189 Submitting user input causes unhandledPromiseRejection in Blue Ocean Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-06-25 15:10 Priority: Minor Reporter: Andrei Muresianu I have a Declarative pipeline that runs a couple of http requests and based on the responses, it prompts the user for some input, using the input resource. The form does not always open without refreshing the page, but the more pressing issue that I would like to track is that when the input is submitted, the build does not progress onto the next stage like it should. On some occasions it does after 20 seconds, on others after 3 minutes, sometimes it stays at the same step with the form open until I refresh the page. In the Safari Dev Tools I can see that there is an Unhandled Promise Rejection that is raised after I submit the input - which, like I mentioned above, seems to sometimes get recovered from. I am using Jenkins Version 2.180 and Blue Ocean version 1.17.0 Add Comment
[JIRA] (JENKINS-57126) Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH
Title: Message Title Ray Kivisto started work on JENKINS-57126 Change By: Ray Kivisto 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.198876.1555767267000.8435.1561474560221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title Andrei Muresianu commented on JENKINS-47584 Re: Result screen not refreshing with error "Cannot read property 'self' of undefined" I am able to reproduce this in a declarative pipeline that has a user input step. After pressing on the button to proceed, sometimes the pipeline continues to the next stage without refreshing the page, other times the UI just hangs there until I refresh it although things are happening and visible in the standard console logs. Jenkins version: 2.180 Tried with a few different versions of Blue Ocean to no avail: 1.17.0. 1.11.0, 1.8.0, 1.7.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186054.1508756187000.8425.1561473960373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58188) Remoting-Kafka-K8s-Coding-Phase-2
Title: Message Title Andrey Falko updated an issue Jenkins / JENKINS-58188 Remoting-Kafka-K8s-Coding-Phase-2 Change By: Andrey Falko Summary: Remoting-Kafka-K8s- Config Coding -Phase-2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200242.1561472627000.8423.1561473120120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58081) Upgrade Kafka version
Title: Message Title Andrey Falko updated an issue Jenkins / JENKINS-58081 Upgrade Kafka version Change By: Andrey Falko Sprint: GSoC 2019. Coding Phase 1 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200106.1560879624000.8419.1561473000221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58188) Remoting-Kafka-K8s-Config-Phase-2
Title: Message Title Andrey Falko updated an issue Jenkins / JENKINS-58188 Remoting-Kafka-K8s-Config-Phase-2 Change By: Andrey Falko Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200242.1561472627000.8412.1561472700776%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47430) SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock
Title: Message Title Liam Newman started work on JENKINS-47430 Change By: Liam Newman 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.185876.1507914808000.8410.1561472700716%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47430) SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock
Title: Message Title Liam Newman updated JENKINS-47430 Jenkins / JENKINS-47430 SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock Change By: Liam Newman Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185876.1507914808000.8414.1561472700819%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58188) Remoting-Kafka-K8s-Config-Phase-2
Title: Message Title Andrey Falko created an issue Jenkins / JENKINS-58188 Remoting-Kafka-K8s-Config-Phase-2 Issue Type: Epic Assignee: Long Vu Components: remoting, remoting-kafka-plugin Created: 2019-06-25 14:23 Priority: Minor Reporter: Andrey Falko Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200242.1561472627000.8406.1561472640160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58082) Prepare demo presentation for Coding Phase 1
Title: Message Title Andrey Falko updated JENKINS-58082 Jenkins / JENKINS-58082 Prepare demo presentation for Coding Phase 1 Change By: Andrey Falko 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.200107.1560879641000.8404.1561472520196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57842) Ec2-fleet Autoscaling Description
Title: Message Title sivanarayana baisani updated JENKINS-57842 Jenkins / JENKINS-57842 Ec2-fleet Autoscaling Description Change By: sivanarayana baisani Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199800.1559657538000.8400.1561471981629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57842) Ec2-fleet Autoscaling Description
Title: Message Title sivanarayana baisani updated JENKINS-57842 Jenkins / JENKINS-57842 Ec2-fleet Autoscaling Description Change By: sivanarayana baisani Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199800.1559657538000.8402.1561471981838%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58187) Jenkins unable to launch batch file
Title: Message Title Sheick Busgeet created an issue Jenkins / JENKINS-58187 Jenkins unable to launch batch file Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: chromedriver.exe, debug.log, Demo.py, SimpleScript.bat Components: batch-task-plugin, jenkinsfile-runner, jenkinslint-plugin Created: 2019-06-25 13:56 Environment: Windows 10 Priority: Major Reporter: Sheick Busgeet Hi Team, I am new to Jenkins and would like to execute some batch scripts. Steps performed: 1) Create a python script with imported selenium libraries 2) Download and install Jenkins 3) Download chromedriver 4) Create a new item in Jenkins (Freestyle project with build action: execute windows batch command). Command: call "C:\Users\sheick.m.busgeet\Desktop\JenkinsPythonSelenium\SimpleScript.bat" When i launch the batch file outside Jenkins, everything works but when i launch through Jenkins, it does not work and a debug file is generated (see attached). Kindly help, Regards, Sheick
[JIRA] (JENKINS-20353) EC2 plugin forgets about some instances it launched when Jenkins restarts
Title: Message Title Jakub Bochenski reopened an issue I have this happening after almost every restart, see JENKINS-57795 Jenkins / JENKINS-20353 EC2 plugin forgets about some instances it launched when Jenkins restarts Change By: Jakub Bochenski Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151873.1383169757000.8391.1561470420944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart FABRIZIO MANFREDI it would be nice to at least get some pointers on how to debug this further or work around 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.199745.1559315049000.8387.1561470180140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Andrei Muresianu commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing This is affecting us too and it is more visible after upgrading form jenkins 2.112 to 2.180, BO version: 1.13.1 The 'Triggered Builds' section does not get populated until the build finishes. It gets even worse sometimes when the entire pipeline stays grey until it finishes completely - things look like they are working and progressing through fine in the standard console though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194240.1537766287000.8377.156147655%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Andrei Muresianu updated an issue Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Andrei Muresianu Attachment: image-2019-06-25-14-39-06-908.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.194240.1537766287000.8379.156147725%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57929) BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Title: Message Title
Devin Nusbaum commented on JENKINS-57929
Re: BlueOcean steps do not appear green when they were successful when using parallel stages while still running
the "testing" stage calls to a script{} block and inside of there is some groovy scripting that uses the "parallel" command in order to fire a bunch of jobs in parallel
Ah ok, yeah running stages/parallel blocks inside of script blocks in a Declarative Pipeline generally breaks the visualization, so I'm surprised that it ends up working once the build is complete. Fixing this is probably nontrivial, and might require some substantial changes to the graph generation code in Blue Ocean.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199903.1560145735000.8368.1561469340234%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Blake Devcich commented on JENKINS-45455 Re: Restarting stages Gaurav Chhabra: Yes, in this particular case, we have it tied to a slave for hardware dependency reasons. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183623.1499805325000.8258.1561468802888%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title
Andrew Widdersheim edited a comment on JENKINS-44679
Re: need to support script inside options
I have a similar need here but a bit more complex than the original reporter. I see that this issue is closed but hopefully we can re-examine the use case. I can also make a new issue.In my case I'd much rather omit {{buildDiscarder()}}. Also the original solution doesn't really work with things like {{disableConcurrentBuilds()}}. For example, it is not possible AFAIK to do something like: {code:java} pipeline \ {options {disableConcurrentBuilds(env.FOO ? true : false)}} {code} Either way I'd much prefer to do something like this:{code:java}pipeline { options {script {if (env.FOO) { buildDiscarder logRotator(daysToKeepStr: '30')disableConcurrentBuilds()} }} }{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.182543.1496663658000.8255.1561468200797%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title
Andrew Widdersheim commented on JENKINS-44679
Re: need to support script inside options
I have a similar need here but a bit more complex than the original reporter. I see that this issue is closed but hopefully we can re-examine the use case. I can also make a new issue. In my case I'd much rather omit buildDiscarder(). Also the original solution doesn't really work with things like disableConcurrentBuilds(). For example, it is not possible AFAIK to do something like: pipeline { options { disableConcurrentBuilds(env.FOO ? true : false) } } Either way I'd much prefer to do something like this:
pipeline {
options {
script {
if (env.FOO) {
buildDiscarder logRotator(daysToKeepStr: '30')
disableConcurrentBuilds()
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182543.1496663658000.8252.1561467960286%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58186) Jenkins Matser Slave builds(Linux to Linux) are getting stuck after few successful builds
Title: Message Title Bujjireddy Regalla created an issue Jenkins / JENKINS-58186 Jenkins Matser Slave builds(Linux to Linux) are getting stuck after few successful builds Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-06-25 13:05 Environment: I have Linux to Linux Master Slave configuration Priority: Major Reporter: Bujjireddy Regalla I am able to execute few builds successfully but after that builds are getting stuck hanged on TSFLAG. Add Comment
[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track
Title: Message Title Artem Fedorov commented on JENKINS-49022 Re: Performance plugin. Allow choosing percentiles to track Hi Goldy Liang Do you asking about feature that was already implemented ~ year ago? https://github.com/jenkinsci/performance-plugin/pull/158 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187841.1516285574000.8248.1561465200264%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Gaurav Chhabra edited a comment on JENKINS-45455 Re: Restarting stages [~bdevcich]: I have also voted for the ticket [ JENKINS-53167 |https://issues . jenkins-ci.org/browse/JENKINS-53167]. For the workaround that you have in place, have you tied the job to a particular slave and use the same workspace each time the job runs? I am asking this because if a job ran the build and test phases successfully and then failed during packaging phase, how will you restart job and ensure _ensure_ that it picks up the _already built binary_ for packaging phase. I am also looking for running a particular phase each time (or may be having the option to run it whenever i want) irrespective of whichever phase i restart my job from. I have included my use case in your ticket [ JENKINS-53167 |https://issues.jenkins-ci.org/browse/JENKINS-53167] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183623.1499805325000.8136.1561464422384%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Gaurav Chhabra commented on JENKINS-45455 Re: Restarting stages Blake Devcich: I have also voted for the ticket JENKINS-53167. For the workaround that you have in place, have you tied the job to a particular slave and use the same workspace each time the job runs? I am asking this because if a job ran the build and test phases successfully and then failed during packaging phase, how will you restart job and ensure that it picks up the already built binary for packaging phase. I am also looking for running a particular phase each time (or may be having the option to run it whenever i want) irrespective of whichever phase i restart my job from. I have included my use case in your ticket JENKINS-53167 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183623.1499805325000.8025.1561464362143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53167) Add ability to always run particular stages when restarting
Title: Message Title Gaurav Chhabra commented on JENKINS-53167 Re: Add ability to always run particular stages when restarting I am also looking for this functionality for my use case. If my scm checkout and build phases run fine but test case execution fails, then in such case, i would like to run the checkout (which will now have fix for test case issue) and test case again but skip the build phase. Actually, the ability to run a particular phase as an optional feature will be the most ideal situation for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193178.1534861787000.8018.1561464300272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57822) JCasC definition doesn't work
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-57822 JCasC definition doesn't work Change By: Pavel Janoušek Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199776.1559570699000.8015.1561463160167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58184) Jacoco delta threshold failures if coverage *increases* over threshold
Title: Message Title Raino Kolk commented on JENKINS-58184 Re: Jacoco delta threshold failures if coverage *increases* over threshold Why not check before abs that coverage delta is negative? It should be ok to ignore positive delta from that check. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200238.1561460352000.8013.1561462080119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58178) Git Plugin fails to mergeBeforeBuild with "ambiguous argument"
Title: Message Title Mark Waite updated JENKINS-58178 Jenkins / JENKINS-58178 Git Plugin fails to mergeBeforeBuild with "ambiguous argument" Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200229.1561448635000.8011.1561461900388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58178) Git Plugin fails to mergeBeforeBuild with "ambiguous argument"
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58178 Git Plugin fails to mergeBeforeBuild with "ambiguous argument" 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.200229.1561448635000.8009.1561461900362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
