[JIRA] (JENKINS-39955) Re-running a failed build via re-run button from results screen breaks karaoke mode
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-39955
Re-running a failed build via re-run button from results screen breaks karaoke mode
Change By:
Michael Neale
When you run a build from a failed results screen, it won't follow along. If you run from the branches/activity, and then click into it, it will follow along. See it here: https://media.giphy.com/media/l0MYQC89znwd5zvXy/giphy.gifIn the console log there is a bunch of stuff like this: {noformat}http://localhost:8080/jenkinsundefined/undefined/log/ Failed to load resource: the server responded with a status of 404 (Not Found)jenkins-js-extension.js:29008 error Error: Not Found(…)(anonymous function) @ jenkins-js-extension.js:29008blueocean.js:1578 GET http://localhost:8080/jenkinsundefined/undefined/log/ 404 (Not Found)dedupeFetch @ blueocean.js:1578request @ blueocean.js:1640dedupe @ blueocean.js:4264dedupe @ blueocean.js:4287rawFetch @ blueocean.js:1652fetch @ blueocean.js:1727fetchLogsInjectStart @ jenkins-js-extension.js:28397(anonymous function) @ jenkins-js-extension.js:28980(anonymous function) @ blueocean.js:88168(anonymous function) @ blueocean.js:88247componentWillMount @ jenkins-js-extension.js:23443performInitialMount @ blueocean.js:74372mountComponent @ blueocean.js:74279mountComponent @ blueocean.js:81292updateChildren @ blueocean.js:72557_reconcilerUpdateChildren @ blueocean.js:80145_updateChildren @ blueocean.js:80244updateChildren @ blueocean.js:80231_updateDOMChildren @ blueocean.js:75989updateComponent @ blueocean.js:75807receiveComponent @ blueocean.js:75765receiveComponent @ blueocean.js:81371_updateRenderedComponent @ blueocean.js:74773_performComponentUpdate @ blueocean.js:74743updateComponent @ blueocean.js:74664receiveComponent @ blueocean.js:74566receiveComponent @ blueocean.js:81371_updateRenderedComponent @ blueocean.js:74773_performComponentUpdate @ blueocean.js:74743updateComponent @ blueocean.js:74664receiveComponent @ blueocean.js:74566receiveComponent @ blueocean.js:81371updateChildren @ blueocean.js:72545_reconcilerUpdateChildren @ blueocean.js:80145_updateChildren @ blueocean.js:80244updateChildren @ blueocean.js:80231_updateDOMChildren @ blueocean.js:75989updateComponent @ blueocean.js:75807receiveComponent @ blueocean.js:75765receiveComponent @ blueocean.js:81371_updateRenderedComponent @ blueocean.js:74773_performComponentUpdate @ blueocean.js:74743updateComponent @ blueocean.js:74664receiveComponent @ blueocean.js:74566receiveComponent @ blueocean.js:81371updateChildren @ blueocean.js:72545_reconcilerUpdateChildren @ blueocean.js:80145_updateChildren @ blueocean.js:80244updateChildren @ blueocean.js:80231_updateDOMChildren @ blueocean.js:75989updateComponent @ blueocean.js:75807receiveComponent @ blueocean.js:75765receiveComponent @ blueocean.js:81371updateChildren @ blueocean.js:72545_reconcilerUpdateChildren @ blueocean.js:80145_updateChildren @ blueocean.js:80244updateChildren @ blueocean.js:80231_updateDOMChildren @ blueocean.js:75989updateComponent @ blueocean.js:75807r
[JIRA] (JENKINS-39962) The layout of the remote jobs (in te remote job view) is not correct.
Title: Message Title Mario Goorden created an issue Jenkins / JENKINS-39962 The layout of the remote jobs (in te remote job view) is not correct. Issue Type: Bug Assignee: Jeff Horan Components: remote-jobs-view-plugin Created: 2016/Nov/23 7:54 AM Environment: Jenkins 2.33 windows Server 2008 R2 remote-jobs-view-plugin version 0.3 Priority: Minor Reporter: Mario Goorden The layout of the remote jobs (in te remote job view) is not correct. An empty paragraph (about 3/4 of the page) is shown before the jobs are shown. This empty paragraph dissappears after jenkins has been restarted. If you edit the view after a restart the empty paragraph is shown again. The column layout of the plugin is not consistent and disaapears after a restart of jenkins. Add Comment
[JIRA] (JENKINS-39961) pipeline-rest-api link points to Pipeline Stage View Plugin
Title: Message Title Roman Pickl created an issue Jenkins / JENKINS-39961 pipeline-rest-api link points to Pipeline Stage View Plugin Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Nov/23 7:01 AM Priority: Minor Reporter: Roman Pickl The link to the pipeline-rest-api plugin points to https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin (where the pipeline-rest-api link in the dependencies points to the same page) Add Comment This message was se
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title Christoph Obexer commented on JENKINS-39943 Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean Jesse Glick Why would the script security plugin not know which method is to be called considering the error points at the correct class, the correct method name and somewhat correct parameters(should be a boolean not the wrapper class)? Passing the true as the return value of Boolean.valueOf (which needed to be approved and did show up in /scriptApproval ) did not change the message tough. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title
Christoph Obexer edited a comment on JENKINS-39943
Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
To reproduce from scratch do:1.) Configure Artifactory server with ID "local-dummy-server" (does not need to exist)2.) Configure a Gradle installation with name "Gradle_2_14_1" with that same version (URL: https://services.gradle.org/distributions/gradle-2.14.1-all.zip) (well likely not needed either) 3.) Create a pipeline job with below script{noformat}node ('master') {def server = Artifactory.server('local-dummy-server')def rtGradle = Artifactory.newGradleBuild()rtGradle.usesPlugin = true // or rtGradle.setUsesPlugin(true)rtGradle.tool = "Gradle_2_14_1"def buildInfo = rtGradle.run buildFile: 'build.gradle', tasks: 'clean artifactoryPublish'}{noformat}4.) run => exception
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title
Christoph Obexer edited a comment on JENKINS-39943
Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
To reproduce from scratch do:1.) Configure Artifactory server with ID "local-dummy-server" (does not need to exist)2.) Configure a Gradle installation with name "Gradle_2_14_1" with that same version (URL: https://services.gradle.org/distributions/gradle-2.14.1-all.zip)3.) Create a pipeline job with below script ``` {noformat} node ('master') {def server = Artifactory.server('local-dummy-server')def rtGradle = Artifactory.newGradleBuild()rtGradle.usesPlugin = true // or rtGradle.setUsesPlugin(true)rtGradle.tool = "Gradle_2_14_1"def buildInfo = rtGradle.run buildFile: 'build.gradle', tasks: 'clean artifactoryPublish'} ``` {noformat} 4.) run => exception
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title
Christoph Obexer edited a comment on JENKINS-39943
Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
To reproduce from scratch do:1.) Configure Artifactory server with ID "local-dummy-server" (does not need to exist)2.) Configure a Gradle installation with name "Gradle_2_14_1" with that same version (URL: https://services.gradle.org/distributions/gradle-2.14.1-all.zip)3.) Create a pipeline job with below script {{ ``` node ('master') {def server = Artifactory.server('local-dummy-server')def rtGradle = Artifactory.newGradleBuild()rtGradle.usesPlugin = true // or rtGradle.setUsesPlugin(true)rtGradle.tool = "Gradle_2_14_1"def buildInfo = rtGradle.run buildFile: 'build.gradle', tasks: 'clean artifactoryPublish'} }} ``` 4.) run => exception
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title
Christoph Obexer commented on JENKINS-39943
Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
To reproduce from scratch do: 1.) Configure Artifactory server with ID "local-dummy-server" (does not need to exist) 2.) Configure a Gradle installation with name "Gradle_2_14_1" with that same version (URL: https://services.gradle.org/distributions/gradle-2.14.1-all.zip) 3.) Create a pipeline job with below script {{node ('master') { def server = Artifactory.server('local-dummy-server') def rtGradle = Artifactory.newGradleBuild() rtGradle.usesPlugin = true // or rtGradle.setUsesPlugin(true) rtGradle.tool = "Gradle_2_14_1" def buildInfo = rtGradle.run buildFile: 'build.gradle', tasks: 'clean artifactoryPublish' } }} 4.) run => exception
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title
Christoph Obexer edited a comment on JENKINS-39943
Re: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
To reproduce from scratch do:1.) Configure Artifactory server with ID "local-dummy-server" (does not need to exist)2.) Configure a Gradle installation with name "Gradle_2_14_1" with that same version (URL: https://services.gradle.org/distributions/gradle-2.14.1-all.zip)3.) Create a pipeline job with below script{{ node ('master') {def server = Artifactory.server('local-dummy-server')def rtGradle = Artifactory.newGradleBuild()rtGradle.usesPlugin = true // or rtGradle.setUsesPlugin(true)rtGradle.tool = "Gradle_2_14_1"def buildInfo = rtGradle.run buildFile: 'build.gradle', tasks: 'clean artifactoryPublish'} }}4.) run => exception
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Roman Pickl commented on JENKINS-39887 Re: redmine plugin crashes blue ocean show more link thx for the input (makes sense!). I used the pipeline snippet generator. can this setting be included in there as well? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title Christoph Obexer assigned an issue to Eyal Ben Moshe Jenkins / JENKINS-39943 unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean Change By: Christoph Obexer Assignee: Eyal Ben Moshe Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title
j ada updated an issue
Jenkins / JENKINS-39960
EC2 Plugin: Invalid groupID parameter when provisioning
Change By:
j ada
Hello,Attempting to test the EC2 plugin, have configured the Cloud Settings and AWS Access Credentials etc. However, when i goto create a new node and click on the 'Provision via' button, i get the following error: (quote) {code} com.amazonaws.services.ec2.model.AmazonEC2Exception: Value () for parameter groupId is invalid. The value cannot be empty (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; (quote) {code} Haven't been able to suss out exactly which param is missing here. Any ideas?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/opto
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title j ada updated an issue Jenkins / JENKINS-39960 EC2 Plugin: Invalid groupID parameter when provisioning Change By: j ada Hello,Attempting to test the EC2 plugin, have configured the Cloud Settings and AWS Access Credentials etc. However, when i goto create a new node and click on the 'Provision via' button, i get the following error: ``` (quote) com.amazonaws.services.ec2.model.AmazonEC2Exception: Value () for parameter groupId is invalid. The value cannot be empty (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; ``` (quote) Haven't been able to suss out exactly which param is missing here. Any ideas? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title j ada created an issue Jenkins / JENKINS-39960 EC2 Plugin: Invalid groupID parameter when provisioning Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Nov/23 5:46 AM Priority: Minor Reporter: j ada Hello, Attempting to test the EC2 plugin, have configured the Cloud Settings and AWS Access Credentials etc. However, when i goto create a new node and click on the 'Provision via' button, i get the following error: ```com.amazonaws.services.ec2.model.AmazonEC2Exception: Value () for parameter groupId is invalid. The value cannot be empty (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; ``` Haven't been able to suss out exactly which param is missing here. Any ideas? Add Comment
[JIRA] (JENKINS-39959) Document and unit test mobx services
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-39959 Document and unit test mobx services Issue Type: Task Assignee: Ivan Meredith Components: blueocean-plugin Created: 2016/Nov/23 5:42 AM Priority: Minor Reporter: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Iss
[JIRA] (JENKINS-39958) Convert RunDetails test tab to use mobx
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-39958 Convert RunDetails test tab to use mobx Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/23 5:41 AM Priority: Minor Reporter: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Iss
[JIRA] (JENKINS-39957) Convert karoke/rundetailspipeline to mobx
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-39957 Convert karoke/rundetailspipeline to mobx Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/23 5:41 AM Priority: Minor Reporter: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins I
[JIRA] (JENKINS-39956) Convert personalization to mobx
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-39956 Convert personalization to mobx Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/23 5:40 AM Priority: Minor Reporter: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" gro
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Matthew Douglass commented on JENKINS-39946 Re: Support for publishing to SNS Ended up very straightforward, sent you a PR with basic functionality at https://github.com/jenkinsci/pipeline-aws-plugin/pull/1. Send any suggestions/changes my way. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39955) Re-running a failed build via re-run button from results screen breaks karaoke mode
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39955 Re-running a failed build via re-run button from results screen breaks karaoke mode Change By: Michael Neale Sprint: Bundles management UI Sprint Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39955) Re-running a failed build via re-run button from results screen breaks karaoke mode
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Ivan Meredith just giving this to you so you can co-ordinate looking at it with Thor Jenkins / JENKINS-39955 Re-running a failed build via re-run button from results screen breaks karaoke mode Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39955) Re-running a failed build via re-run button from results screen breaks karaoke mode
Title: Message Title Michael Neale commented on JENKINS-39955 Re: Re-running a failed build via re-run button from results screen breaks karaoke mode This is more obviously an issue when https://github.com/jenkinsci/blueocean-plugin/pull/585 is merged BTW. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39955) Re-running a failed build via re-run button from results screen breaks karaoke mode
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-39955 Re-running a failed build via re-run button from results screen breaks karaoke mode Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/23 4:06 AM Priority: Major Reporter: Michael Neale When you run a build from a failed results screen, it won't follow along. If you run from the branches/activity, and then click into it, it will follow along. See it here: https://media.giphy.com/media/l0MYQC89znwd5zvXy/giphy.gif In the console log there is a bunch of stuff like this: http://localhost:8080/jenkinsundefined/undefined/log/ Failed to load resource: the server responded with a status of 404 (Not Found) jenkins-js-extension.js:29008 error Error: Not Found(…)(anonymous function) @ jenkins-js-extension.js:29008 blueocean.js:1578 GET http://localhost:8080/jenkinsundefined/undefined/log/ 404 (Not Found)dedupeFetch @ blueocean.js:1578request @ blueocean.js:1640dedupe @ blueocean.js:4264dedupe @ blueocean.js:4287rawFetch @ blueocean.js:1652fetch @ blueocean.js:1727fetchLogsInjectStart @ jenkins-js-extension.js:28397(anonymous function) @ jenkins-js-extension.js:28980(anonymous function) @ blueocean.js:88168(anonymous function) @ blueocean.js:88247componentWillMount @ jenkins-js-extension.js:23443performInitialMount @ blueocean.js:74372mountComponent @ blueocean.js:74279mountComponent @ blueocean.js:81292updateChildren @ blueocean.js:72557_reconcilerUpdateChildren @ blueocean.js:80145_updateChildren @ blueocean.js:80244updateChildren @ blueocean.js:80231_updateDOMChildren @ blueocean.js:75989updateComponent @ blueocean.js:75807receiveComponent @ blueocean.js:75765receiveComponent @ blueocean.js:81371_updateRenderedComponent @ blueocean.js:74773_performComponentUpdate @ blueocean.js:74743update
[JIRA] (JENKINS-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Michael Neale commented on JENKINS-39854 Re: REGRESSION: activity/branch run status is not updated after closing karaoke mode Ivan Meredith so it looks like this isn't solved by the mobx change - are you going to look at it or need some help? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Michael Neale updated JENKINS-39854 Jenkins / JENKINS-39854 REGRESSION: activity/branch run status is not updated after closing karaoke mode Change By: Michael Neale Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39953) Under some conditions clicking on activity forces a reload
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-39953 Under some conditions clicking on activity forces a reload Change By: James Dumay Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39954) Cloud foundry plugin failed to deploy NodeJs app
Title: Message Title Kiran Mullapudi created an issue Jenkins / JENKINS-39954 Cloud foundry plugin failed to deploy NodeJs app Issue Type: Bug Assignee: William Gautier Attachments: CF Plugin error.txt Components: cloudfoundry-plugin Created: 2016/Nov/23 3:42 AM Environment: WIndows Serverr 2012 R2 Labels: jenkins plugin cloudfoundry Priority: Major Reporter: Kiran Mullapudi Hi Team, I am trying to push a nodeJs application to PCF using Cloud foundry plugin for Jenkins. Looks like the plugin is always trying to install npm through i already installed before pushing. When i try to push the same artifacts using "cf push" from command line, things are working good. The issue exists only when i push from Cloud foundry plugin for Jenkins. Please find the attached error log for more details. Thanks in advance, Kiran.
[JIRA] (JENKINS-39953) Under some conditions clicking on activity forces a reload
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39953 Under some conditions clicking on activity forces a reload Change By: James Dumay Sprint: frank tasman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39953) Under some conditions clicking on activity forces a reload
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39953 Under some conditions clicking on activity forces a reload Change By: James Dumay Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39953) Under some conditions clicking on activity forces a reload
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39953 Under some conditions clicking on activity forces a reload Issue Type: Task Assignee: Unassigned Attachments: Nov-23-2016 14-14-25.gif Components: blueocean-plugin Created: 2016/Nov/23 3:16 AM Priority: Minor Reporter: James Dumay Steps to reproduce Open the Activity tab Click on Branches Open the latest result for a branch Close the result Click on Activity The page reloads We should never reload the page in this circumstance. Add Comment
[JIRA] (JENKINS-39291) Form elements
Title: Message Title Brody Maclean updated JENKINS-39291 Jenkins / JENKINS-39291 Form elements Change By: Brody Maclean Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title
Vivek Pandey edited a comment on JENKINS-39229
Re: Regression: Initial stage run does not show graph
[~jamesdumay] Nothing to do with bismuth. Its just that SSE code is not aware of block scoped stages. SSE code should use PipelineNodeUtil to determine whether given node is stage or not or to get stage name etc. Current SSE code relies on StageAction, that was for non-block scoped stage, so won't work for blocked scoped stage.To keep SSE pipeline related code and /nodes API in sync, I suggest it uses whats implemented in /nodes. For example code something like following is all it needs. I can make it more general purpose if needed. Otherwise there is always going to be duplication in some form and things can get out of sync. For example handling of synthetic stage, SSE might treat as normal stage and fire event where as such stages won't appear in the DAG returned by /nodes API. {code}NodeGraphBuilder graphBuilder graphBuilder = NodeGraphBuilder.NodeGraphBuilderFactory.getInstance(workflowRun);public List getStages(NodeGraphBuilder builder){List nodes = new ArrayList<>();for(FlowNodeWrapper node: builder.getPipelineNodes()){if(node.type == FlowNodeWrapper.NodeType.STAGE){nodes.add(node.getNode());}}return nodes;}public List getStagesAndParallels(NodeGraphBuilder builder){List nodes = new ArrayList<>();for(FlowNodeWrapper node: builder.getPipelineNodes()){if(node.type == FlowNodeWrapper.NodeType.STAGE || node.type == FlowNodeWrapper.NodeType.PARALLEL){nodes.add(node.getNode());}}return nodes;}public List getStagesAndParallels getParallels (NodeGraphBuilder builder){List nodes = new ArrayList<>();for(FlowNodeWrapper node: builder.getPipelineNodes()){if(node.type == FlowNodeWrapper.NodeType.PARALLEL){nodes.add(node.getNode());}}return nodes;}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36862) Jira plugin does not work inside promotion block
Title: Message Title Pall Yoon commented on JENKINS-36862 Re: Jira plugin does not work inside promotion block I want to report the same issue. JIRA Plugin 2.2.1 Jenkins LTS 1.651.3 Jira v7.2.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39753) Expose readonly type option for Manual workspaces
Title: Message Title Tristan Lewis commented on JENKINS-39753 Re: Expose readonly type option for Manual workspaces I have realized that the client type field is not exposed at all in the latest version of the P4Java API, so there's no way for this to be implemented currently. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39753) Expose readonly type option for Manual workspaces
Title: Message Title Tristan Lewis updated an issue Jenkins / JENKINS-39753 Expose readonly type option for Manual workspaces Change By: Tristan Lewis Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Sam Van Oort URL: https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/22 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39952) There is no "Configure Docker Registry: CloudBees Docker Build and Publish" section in Jenkins/Configure System
Title: Message Title nkcfan nkcfan created an issue Jenkins / JENKINS-39952 There is no "Configure Docker Registry: CloudBees Docker Build and Publish" section in Jenkins/Configure System Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2016/Nov/23 1:26 AM Priority: Major Reporter: nkcfan nkcfan As mentioned in https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Thanks Thorsten Scherler, I think perhaps Tom FENNELLY might be able to tackle this later this week? Vivek is out for thanksgiving - Tom FENNELLY able to take a look? Jenkins / JENKINS-39229 Regression: Initial stage run does not show graph Change By: Michael Neale Assignee: tom kessler Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title Michael Neale stopped work on JENKINS-39229 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title Michael Neale assigned an issue to tom kessler Jenkins / JENKINS-39229 Regression: Initial stage run does not show graph Change By: Michael Neale Assignee: tom kessler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39229 Regression: Initial stage run does not show graph Change By: James Dumay Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed Vivek Pandey NM - I am confused and you should ignore me (I was looking for https://issues.jenkins-ci.org/browse/JENKINS-38150) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title Vivek Pandey commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed James Dumay you mean ticket to handle skipped stages (SKIPPED_FOR_CONDITIONAL) in UI? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title
Vivek Pandey commented on JENKINS-39229
Re: Regression: Initial stage run does not show graph
James Dumay Nothing to do with bismuth. Its just that SSE code is not aware of block scoped stages. SSE code should use PipelineNodeUtil to determine whether given node is stage or not or to get stage name etc. Current SSE code relies on StageAction, that was for non-block scoped stage, so won't work for blocked scoped stage. To keep SSE pipeline related code and /nodes API in sync, I suggest it uses whats implemented in /nodes. For example code something like following is all it needs. I can make it more general purpose if needed. Otherwise there is always going to be duplication in some form and things can get out of sync. For example handling of synthetic stage, SSE might treat as normal stage and fire event where as such stages won't appear in the DAG returned by /nodes API.
NodeGraphBuilder graphBuilder graphBuilder = NodeGraphBuilder.NodeGraphBuilderFactory.getInstance(workflowRun);
public List getStages(NodeGraphBuilder builder){
List nodes = new ArrayList<>();
for(FlowNodeWrapper node: builder.getPipelineNodes()){
if(node.type == FlowNodeWrapper.NodeType.STAGE){
nodes.add(node.getNode());
}
}
return nodes;
}
public List getStagesAndParallels(NodeGraphBuilder builder){
List nodes = new ArrayList<>();
for(FlowNodeWrapper node: builder.getPipelineNodes()){
if(node.type == FlowNodeWrapper.NodeType.STAGE || node.type == FlowNodeWrapper.NodeType.PARALLEL){
nodes.add(node.getNode());
}
}
return nodes;
}
public List getStagesAndParallels(NodeGraphBuilder builder){
List nodes = new ArrayList<>();
for(FlowNodeWrapper node: builder.getPipelineNodes()){
if(node.type == FlowNodeWrapper.NodeType.PARALLEL){
nodes.add(node.getNode());
}
}
return nodes;
}
Add Comment
[JIRA] (JENKINS-37250) Rework stores for MobX
Title: Message Title James Dumay updated JENKINS-37250 Jenkins / JENKINS-37250 Rework stores for MobX Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed Vivek Pandey is there a ticket tracking that in the blue ocean component? If not, can you create one when you have a chance? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39888) REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location
Title: Message Title James Dumay commented on JENKINS-39888 Re: REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location Cliff Meyers Fantastic! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39890) REGRESSION: Activity, branch and PR tab table columns no longer right ellipsis when too long
Title: Message Title James Dumay commented on JENKINS-39890 Re: REGRESSION: Activity, branch and PR tab table columns no longer right ellipsis when too long Thanks for the update Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title James Dumay commented on JENKINS-39229 Re: Regression: Initial stage run does not show graph Thorsten Scherler thanks mate. Perhaps this is related to a few changes Vivek Pandey made when we adopted bismuth? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39951) "java -jar jenkins.war --httpPort 8080" fails with a stack trace
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-39951 "java -jar jenkins.war --httpPort 8080" fails with a stack trace Issue Type: Bug Assignee: Unassigned Components: winstone-jetty Created: 2016/Nov/23 12:06 AM Priority: Minor Reporter: Kohsuke Kawaguchi User error like this shouldn't result in a stack trace, yet this is the output you get: % java -jar jenkins.war --httpPort 8080 Running from: /home/kohsuke/ws/jenkins/jenkins/war/target/jenkins.war webroot: $user.home/.jenkins Nov 22, 2016 4:06:19 PM Main deleteWinstoneTempContents WARNING: Failed to delete the temporary Winstone file /tmp/winstone/jenkins.war Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at Main._main(Main.java:264) at Main.main(Main.java:112) Caused by: java.lang.IllegalArgumentException: Expecting httpPort=VALUE but found no value at winstone.cmdline.CmdLineParser.parse(CmdLineParser.java:61) at winstone.Launcher.getArgsFromCommandLine(Launcher.java:359) at winstone.Launcher.main(Launcher.java:332) ... 6 more
[JIRA] (JENKINS-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Michael Neale commented on JENKINS-39852 Re: REGRESSION: Loading worm never finishes on dashboard ARIGATO Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-39852 REGRESSION: Loading worm never finishes on dashboard Change By: Keith Zantow Assignee: Thorsten Scherler Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Keith Zantow commented on JENKINS-39852 Re: REGRESSION: Loading worm never finishes on dashboard Not sure, maybe the introduction of cloning children affected the lifecycle somehow. I'll take a look at it in more detail. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: Michael Neale Labels: adoption blueocean x-team Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Michael Neale commented on JENKINS-37324 Re: We would like a more meaningful description of a step cc Sam Van Oort this is the ticket I was talking about - some good ideas thrown around Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39658) Include failed step's error to it's log
Title: Message Title Michael Neale commented on JENKINS-39658 Re: Include failed step's error to it's log Had a discussion with Sam Van Oort and vivek and agreed this is doable Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39440) Groovy exceptions are not logged in Blue Ocean
Title: Message Title Michael Neale closed an issue as Duplicate We have another ticket which is tracking how to solve this generally. Jenkins / JENKINS-39440 Groovy exceptions are not logged in Blue Ocean Change By: Michael Neale Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38277) The webhook registration didn't register the push hook
Title: Message Title Guillaume Jacquet commented on JENKINS-38277 Re: The webhook registration didn't register the push hook I am also facing the same issue. I first noticed that with the multibranch plugin but I have the same behaviour with the github organization folder plugin. I have setup a Dockerfile that demonstrate this behaviour: https://github.com/gjacquet/jenkins-multibranch-test/ I made the Jenkins configuration as close as possible to what I currently use. Some of the plugins are probably not needed to demo but that's pretty much my real setup, the one I am facing this issue with. At the moment this issue is keeping me from deploying Jenkins pipelines in my organization. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28035) Space delimiter is not supported
Title: Message Title
Julio Gonzalez Gil edited a comment on JENKINS-28035
Re: Space delimiter is not supported
I know this is an old issue, but it seems it's not fixed yet.However there is a workaround if you can use [EnvInject Plugin|https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=65143760].1. Enable 'Prepare an environment for the run'2. At 'Evaluated Groovy script' add a groovy script to return a map with the required variables modified so the commas are replaced by spaces.For example in my case I have two parameters which I use at the configuration matrix , PG_VERS and DISTROS, and the script is:{quote}return [PG_VERS: PG_VERS.replaceAll(',',' '), DISTROS: DISTROS.replaceAll(',',' ')] {quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28035) Space delimiter is not supported
Title: Message Title
Julio Gonzalez Gil edited a comment on JENKINS-28035
Re: Space delimiter is not supported
I know this is an old issue, but it seems it's not fixed yet.However there is a workaround if you can use [EnvInject Plugin|https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=65143760].1. Enable 'Prepare an environment for the run'2. At 'Evaluated Groovy script' add a groovy script to return a map with the required variables modified so the commas are replaced by spaces.For example in my case I have two paramters parameters , PG_VERS and DISTROS, and the script is:{quote}return [PG_VERS: PG_VERS.replaceAll(',',' '), DISTROS: DISTROS.replaceAll(',',' ')] {quote}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28035) Space delimiter is not supported
Title: Message Title
Julio Gonzalez Gil commented on JENKINS-28035
Re: Space delimiter is not supported
I know this is an old issue, but it seems it's not fixed yet. However there is a workaround if you can use EnvInject Plugin. 1. Enable 'Prepare an environment for the run' 2. At 'Evaluated Groovy script' add a groovy script to return a map with the required variables modified so the commas are replaced by spaces. For example in my case I have two paramters, PG_VERS and DISTROS, and the script is:
return [PG_VERS: PG_VERS.replaceAll(',',' '), DISTROS: DISTROS.replaceAll(',',' ')]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39950) Incorrect URLs for job actions if job is within a Folder
Title: Message Title Sergey Zhemzhitsky created an issue Jenkins / JENKINS-39950 Incorrect URLs for job actions if job is within a Folder Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector-plugin Created: 2016/Nov/22 10:20 PM Environment: Jenkins 2.33 Ubuntu 14.04 LTS Priority: Major Reporter: Sergey Zhemzhitsky For jobs contained withing folders action urls (urls to access warnings are generated) incorrectly leading to 404 http status codes. There is a pull request that fixes this issue by changing jobs' shortUrl to absoluteUrl to work correctly for jobs contained in folders. Add Comment
[JIRA] (JENKINS-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder commented on JENKINS-39887 Re: redmine plugin crashes blue ocean show more link No problem Roman . I believe you can still hit this error, because RedmineRepositoryBrowser depends on RedmineProjectProperty. You should also define RedmineProjectProperty in your Jenkinsfile / Jenkins DSL Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Matthew Douglass commented on JENKINS-39946 Re: Support for publishing to SNS I'll be looking through it this evening and I'll let you know. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Thorsten Hoeger commented on JENKINS-39946 Re: Support for publishing to SNS Sure, sounds good. Do you need further information or would you be able to start implementing? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Matthew Douglass commented on JENKINS-39946 Re: Support for publishing to SNS We used the sns notifier plugin previously to send a notification at the start and end of the build with a custom subject and body (which we made json). Sadly, that one doesn't seem to support pipeline and may have lapsed support. For this proposed functionality, I'd actually like to be able to send custom messages at any point during the build, not just begin/end. For example, I know already I'd like to send them before/after input requests to notify that the input is waiting. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Thorsten Hoeger commented on JENKINS-39946 Re: Support for publishing to SNS Hi, can you elaborate on the features this SNS support would have? Did you check other SNS plugins for Jenkins? I would love to support more use cases in this plugin and I would gladly approve a pull request that fits in the plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39949) Pipeline script from SCM not working for TFS
Title: Message Title Kevin Pluck created an issue Jenkins / JENKINS-39949 Pipeline script from SCM not working for TFS Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Nov/22 9:14 PM Environment: Windows 10 latest jenkins all plugins up to date Team Foundation Server Plug-in Labels: tfs-plugin pipeline Priority: Blocker Reporter: Kevin Pluck When I create a new pipeline job and then select "Pipeline script from SCM" definition followed by "Team Foundation Version control (TFVC)" SCM along with appropriate url, path and credentials then save. I then return to the configuration for this project and find that the SCM selected is "git" along with empty fields related to git. There are now only two options in the SCM dd: git and Subversion I expect to find my previously entered TFS settings.
[JIRA] (JENKINS-29314) Improving teamforge-collabnet plugin.
Title: Message Title John McNally closed an issue as Fixed Change is committed. Will be in 2.0 release. Jenkins / JENKINS-29314 Improving teamforge-collabnet plugin. Change By: John McNally Status: Open Closed Assignee: JCAT John McNally Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Goog
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Jan Roehrich resolved as Fixed Resolved in 1.7-SNAPSHOT Jenkins / JENKINS-36823 Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles Change By: Jan Roehrich Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32237) Exception when trying to add Build Promotion process
Title: Message Title Michael Fowler reopened an issue I still get a warning saying adding a promotion to a multi branch project is not supported and it references this ticket. Was the fix ever merged? I don't a commit tagged with Jenkins-32237 in github. Jenkins / JENKINS-32237 Exception when trying to add Build Promotion process Change By: Michael Fowler Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this gro
[JIRA] (JENKINS-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" I've attached a snapshot build with the changes so also you could test the bugfix. Due a previous refactor (more than one year ago) of this plugin to be compliant with more recent jenkins api if you have the envinject plugin the action of "Provide Node & npm bin/ folder to PATH" will not work because JENKINS-26583 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39948) add support for nicer pipeline syntax with bitbucket alias
Title: Message Title mcrooney commented on JENKINS-39948 Re: add support for nicer pipeline syntax with bitbucket alias You can see how android-lint implemented this here: https://github.com/jenkinsci/android-lint-plugin/compare/android-lint-2.3...android-lint-2.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39948) add support for nicer pipeline syntax with bitbucket alias
Title: Message Title mcrooney updated an issue Jenkins / JENKINS-39948 add support for nicer pipeline syntax with bitbucket alias Change By: mcrooney Right now we can use "step([$class: 'StashNotifier'])" (which is awesome, thanks for the Pipeline support!), and it would be even cooler to use the syntactic sugar that various steps/plugins support and just say 'notifyStash'. As part of this, it would also make a lot of sense to also add an alias command of 'notifyBitbucket' as Stash was renamed a bit ago to Bitbucket so it is a bit will be confusing for our devs anyone who started using the service as Bitbucket . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39948) add support for nicer pipeline syntax with bitbucket alias
Title: Message Title mcrooney updated an issue Jenkins / JENKINS-39948 add support for nicer pipeline syntax with bitbucket alias Change By: mcrooney Right now we can use "step([$class: 'StashNotifier'])" (which is awesome, thanks for the Pipeline support!), and it would be even cooler to use the syntactic sugar that various steps/plugins support and just say 'notifyStash'.As part of this, it would make a lot of sense to also add an alias command of 'notifyBitbucket' as Stash was renamed a bit ago to Bitbucket so . This way, it will be less confusing for anyone who started using the service as Bitbucket. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39948) add support for nicer pipeline syntax with bitbucket alias
Title: Message Title mcrooney assigned an issue to Pavel Batanov Jenkins / JENKINS-39948 add support for nicer pipeline syntax with bitbucket alias Change By: mcrooney Assignee: Pavel Batanov Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39948) add support for nicer pipeline syntax with bitbucket alias
Title: Message Title mcrooney created an issue Jenkins / JENKINS-39948 add support for nicer pipeline syntax with bitbucket alias Issue Type: Improvement Assignee: Unassigned Components: stashnotifier-plugin Created: 2016/Nov/22 8:22 PM Priority: Minor Reporter: mcrooney Right now we can use "step([$class: 'StashNotifier'])" (which is awesome, thanks for the Pipeline support!), and it would be even cooler to use the syntactic sugar that various steps/plugins support and just say 'notifyStash'. As part of this, it would also make a lot of sense to also add an alias command of 'notifyBitbucket' as Stash was renamed a bit ago to Bitbucket so it is a bit confusing for our devs. Add Comment
[JIRA] (JENKINS-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Attachment: nodejs.hpi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37086) Support for pipeline DSL in stashnotifier-plugin
Title: Message Title mcrooney resolved as Fixed Jenkins / JENKINS-37086 Support for pipeline DSL in stashnotifier-plugin Change By: mcrooney Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39947) Job URLs do not work correctly with Folder plugin
Title: Message Title Sergey Zhemzhitsky created an issue Jenkins / JENKINS-39947 Job URLs do not work correctly with Folder plugin Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin, dashboard-view-plugin Created: 2016/Nov/22 8:12 PM Environment: Jenkins 2.33 Ubuntu 14.04 LTS Priority: Major Reporter: Sergey Zhemzhitsky In case of multibranch pipelines which use Folders plugin and Folders plugin itself, job urls are not correctly reflect real action urls, so it is preferable to use absolute urls instead of short ones. There is a PR that allows for the action urls to be generated correctly by means of using job absolute urls instead of short ones. Add Comment
[JIRA] (JENKINS-39947) Job URLs do not work correctly with Folder plugin
Title: Message Title Sergey Zhemzhitsky updated an issue Jenkins / JENKINS-39947 Job URLs do not work correctly with Folder plugin Change By: Sergey Zhemzhitsky In case of multibranch pipelines which use Folders plugin and Folders plugin itself, job urls are not correctly reflect real action urls, so it is preferable to use absolute urls instead of short ones.[There is a PR|https://github.com/jenkinsci/analysis-core-plugin/pull/37] that allows for the action urls to be generated correctly by means of using job absolute urls instead of short ones. P.S. A few days ago JENKINS-31202 has been resolved, but in case of multibranch pipelines action urls (for created by means of Dashboard plugin are not generated correctly when using job's short urls).The PR mentioned above fixes action urls using absolute job url instead of short one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To uns
[JIRA] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title Matt Taylor updated an issue Jenkins / JENKINS-20947 Failed to monitor for Free Swap Space Change By: Matt Taylor Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39943 unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean Any “unclassified” error means that script-security could not even figure out what method you are trying to call, so whether that method is in fact whitelisted is irrelevant. No idea offhand why that would be thrown in this case; usually the result of doing something overly clever with Groovy. Would need to investigate, assuming there are some steps to reproduce from scratch. Change By: Jesse Glick Summary: script approvals broken unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean Component/s: artifactory-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39946) Support for publishing to SNS
Title: Message Title Matthew Douglass created an issue Jenkins / JENKINS-39946 Support for publishing to SNS Issue Type: New Feature Assignee: Thorsten Hoeger Components: pipeline-aws-plugin Created: 2016/Nov/22 7:53 PM Priority: Minor Reporter: Matthew Douglass Would love to have support for publishing notifications to SNS. Any plans for this? Or would you consider a pull request that supported it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39355) API improvements based on real-world implementation and usage
Title: Message Title Jesse Glick updated JENKINS-39355 Jenkins / JENKINS-39355 API improvements based on real-world implementation and usage Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39355) API improvements based on real-world implementation and usage
Title: Message Title Jesse Glick started work on JENKINS-39355 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco updated JENKINS-22102 Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" The PR was merged and the fix was completed with other commit. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco started work on JENKINS-22102 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39945) Support wiki format reports
Title: Message Title Simon Bennetts created an issue Jenkins / JENKINS-39945 Support wiki format reports Issue Type: Improvement Assignee: Goran Sarenkapa Components: zap-plugin Created: 2016/Nov/22 6:33 PM Priority: Minor Reporter: Simon Bennetts The plugin already supports html json and xml reports, be goods to also support markdown/ wiki format, which is supported by the ZAP core api: http://localhost:8090/UI/core/other/mdreport/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71
[JIRA] (JENKINS-39229) Regression: Initial stage run does not show graph
Title: Message Title Thorsten Scherler commented on JENKINS-39229 Re: Regression: Initial stage run does not show graph I located the problematic part and I am surprised that Karaoke is still working. src/main/java/io/jenkins/blueocean/events/PipelineEventListener.java around line 155 It seems that currentStageName is now always null (not have been like that before) in src/main/js/components/RunDetailsPipeline.jsx we are using event.pipeline_step_stage_id to determine whether to fetchNodes or fetchSteps. However that is not set anymore. Will need to debug PipelineEventListener why the currentStageName now is always null Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Srinivasan Venkataraman commented on JENKINS-31979 Re: Enable SASL authentication checkbox missing Any update on this? 2 more have reported in the last 2 months. and I am waiting since June. I see the same results in Jenkins ver. 2.19.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Srinivasan Venkataraman updated an issue Jenkins / JENKINS-31979 Enable SASL authentication checkbox missing Change By: Srinivasan Venkataraman Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39541) Pipeline Stage View No Longer Shown After Plugin Upgrade
Title: Message Title Severian Autarch commented on JENKINS-39541 Re: Pipeline Stage View No Longer Shown After Plugin Upgrade I have the same jenkins version (2.19.2) and same stage view plugin version (2.2) and also not seeing the stages. In dev console i can see jquery2.js:998 GET [SERVER_URL]/wfapi/runs?fullStages=true&_=1479837967515 500 (Server Error) Are you suggesting upgrade to 2.19.3 or 2.30 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39944) String::replaceAll method in groovy script works not as described in man.
Title: Message Title
Vladimir Fomenko updated an issue
Jenkins / JENKINS-39944
String::replaceAll method in groovy script works not as described in man.
Change By:
Vladimir Fomenko
...def testString = "Multi line" def testStringReplaced = ( testString.replaceAll(~/(line)/, { it[0] + it[0] }) ) echo testStringReplaced...This block produce produces output: linelineI expect it to produce: Multi lineline
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39944) String::replaceAll method in groovy script works not as described in man.
Title: Message Title
Vladimir Fomenko created an issue
Jenkins / JENKINS-39944
String::replaceAll method in groovy script works not as described in man.
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Nov/22 6:02 PM
Priority:
Minor
Reporter:
Vladimir Fomenko
... def testString = "Multi line" def testStringReplaced = ( testString.replaceAll(~/(line)/, { it[0] + it[0] } ) ) echo testStringReplaced ... This block produce output: lineline I expect it to produce: Multi lineline
Add Comment
[JIRA] (JENKINS-39699) regression: arrays of objects no longer serializable
Title: Message Title Thomas Gimpel updated an issue Jenkins / JENKINS-39699 regression: arrays of objects no longer serializable Change By: Thomas Gimpel Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39943) script approvals broken
Title: Message Title Christoph Obexer created an issue Jenkins / JENKINS-39943 script approvals broken Issue Type: Bug Assignee: Unassigned Components: script-security-plugin Created: 2016/Nov/22 5:37 PM Environment: Jenkins 2.33 Script Security 1.24 Artifactory 2.8.1 Gradle 1.25 Priority: Blocker Reporter: Christoph Obexer In code that attempts to publish to artifactory using gradle I can't set the usesPlugin property like: def rtGradle = Artifactory.newGradleBuild() rtGradle.tool = "Gradle_2_14_1" rtGradle.setUsesPlugin(true) causes: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method org.jfrog.hudson.pipeline.types.GradleBuild setUsesPlugin java.lang.Boolean Which is @Whitelisted according to: https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-2.8.1/src/main/java/org/jfrog/hudson/pipeline/types/deployers/GradleDeployer.java#L46 The documented way to set this boolean is: rtGradle.usesPlugin = true but that causes: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jfrog.hudson.pipeline.types.GradleBuild usesPlugin My /scriptApproval/ shows nothing to approve.
