[JIRA] (JENKINS-37795) Allow use of credentials from Global name/password pairs
Title: Message Title Albert Shamsiyan created an issue Jenkins / JENKINS-37795 Allow use of credentials from Global name/password pairs Issue Type: New Feature Assignee: redsolo Components: tfs-plugin Created: 2016/Aug/30 5:57 AM Priority: Major Reporter: Albert Shamsiyan Global name/password pairs are masked in both Jenkins Portal and logs. It will be very convenient if TFS plugin will be updated to allow the use of those instead of having to specify them on each job? The that use of the Credentials is good in cases no need to execute TF command again during the Job, otherwise, one is needed to manage credentials in two places ... Add Comment
[JIRA] (JENKINS-14713) Cancel permission is granted for users having build permission
Title: Message Title Nico Falk commented on JENKINS-14713 Re: Cancel permission is granted for users having build permission Hi, I have many builds using ClearCase Plugin. If the job gets canceled during SCM access, my ClearCase View is irreparably damaged. Thus, in this particular case it would be quite handy to remove the "Cancel" permission independent of the "Build" permission! Thanks a lot. 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-37794) JGit filter tags with "/" in their name
Title: Message Title Jeremie Bresson created an issue Jenkins / JENKINS-37794 JGit filter tags with "/" in their name Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Aug/30 5:24 AM Priority: Major Reporter: Jeremie Bresson As discussed in JENKINS-37635, there is a difference between the JGit and the native git implementation: Take this demo repository as example: https://github.com/klimas7/Learn It contains 3 tags: v1.0.0, release/v.1.0.0 and release-tags/v.1.0.0 Depending on the git client used (JGit or native git) the results are not the same. JGit only find v1.0.0. Add Comment
[JIRA] (JENKINS-37635) Git Tags with "/" in their name are not displayed
Title: Message Title Jeremie Bresson commented on JENKINS-37635 Re: Git Tags with "/" in their name are not displayed Thank you, I have opened JENKINS-37794 to continue to track this issue. 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-34416) workflow-cps-global-lib: global variables are not global singletons
Title: Message Title
Martin Vehovsky edited a comment on JENKINS-34416
Re: workflow-cps-global-lib: global variables are not global singletons
Now that is peculiar, because [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin#defining-global-variables] doesn't say a word about the fact that global variables shouldn't be available in the [{{shared code}}|https://github.com/jenkinsci/workflow-cps-global-lib-plugin#writing-shared-code]. So I say the they are definitely not wrong. In {{Zot}} i simply want to access global variable {{acme}}. And I am able to access it. It's just not the same instance of the {{acme}} as it was in the {{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-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Michael Neale commented on JENKINS-37312 Re: BlueOcean "Failed to write numberOfFailingBranches" exception Unfortunately this didn't make the latest alpha, but there should be another one along soon that has it in. 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-34416) workflow-cps-global-lib: global variables are not global singletons
Title: Message Title
Martin Vehovsky edited a comment on JENKINS-34416
Re: workflow-cps-global-lib: global variables are not global singletons
Now that is peculiar, because [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin#defining-global-variables] doesn't say a word about the fact that global variables shouldn't be available in the [{{shared code}}|https://github.com/jenkinsci/workflow-cps-global-lib-plugin#writing-shared-code]. So I way say the are definitely not wrong. In {{Zot}} i simply want to access global variable {{acme}}. And I am able to access it. It's just not the same instance of the {{acme}} as it was in the {{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-34416) workflow-cps-global-lib: global variables are not global singletons
Title: Message Title Martin Vehovsky commented on JENKINS-34416 Re: workflow-cps-global-lib: global variables are not global singletons Now that is peculiar, because documentation doesn't say a word about the fact that global variables shouldn't be available in the shared code. So I way the are definitely not wrong. In Zot i simply want to access global variable acme. And I am able to access it. It's just not the same instance of the acme as it was in the 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-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Vivek Pandey updated JENKINS-37312 Fix merged. Jenkins / JENKINS-37312 BlueOcean "Failed to write numberOfFailingBranches" exception Change By: Vivek Pandey Status: In Review 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-37782) Pipeline Config: Unable to refer to environment var in input string
Title: Message Title Michael Neale commented on JENKINS-37782 Re: Pipeline Config: Unable to refer to environment var in input string Ah, I get you. OK that works. Is still slightly confusing but can drop the priority of this. The ' vs " is a little hard to teach. 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-16872) Make the Mask Passwords Plugin work with Jenkins Promoted Builds plugin console
Title: Message Title Rick Liu commented on JENKINS-16872 Re: Make the Mask Passwords Plugin work with Jenkins Promoted Builds plugin console Any 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-37793) Developer can see meaningful page titles
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37793 Developer can see meaningful page titles Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Aug/30 1:29 AM Priority: Minor Reporter: James Dumay In Scope Dashboard Jenkins – Dashboard Pipeline Jenkins – $pipelineName Run Jenkins – $pipelineName $runId Add Comment
[JIRA] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Title: Message Title Denys Digtiar commented on JENKINS-27927 Re: Some interface idioms do not work in Groovy CPS Jesse Glick My bad. Didn't think about it. Tried as keyword, it is still causing an error. 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-33166) Problem with settings validation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33166 Re: Problem with settings validation Code changed in jenkins User: Emilio Escobar Path: src/main/java/hudson/plugins/jira/JiraSite.java http://jenkins-ci.org/commit/jira-plugin/b7d807c7d610eb848d027659de5112fed85ce8e1 Log: JENKINS-33166 check for nonnull url inside constructor 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-33166) Problem with settings validation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33166 Re: Problem with settings validation Code changed in jenkins User: Radosław Antoniuk Path: src/main/java/hudson/plugins/jira/JiraSite.java http://jenkins-ci.org/commit/jira-plugin/4e6793fa8a70f746dea03827dc2fdf19dbbd69d3 Log: Merge pull request #100 from escoem/JENKINS-33166 JENKINS-33166 check for nonnull url inside constructor Compare: https://github.com/jenkinsci/jira-plugin/compare/a79b0fd5b002...4e6793fa8a70 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-35712) Failed step doesn't show as FlowNode
Title: Message Title Michael Neale edited a comment on JENKINS-35712 Re: Failed step doesn't show as FlowNode [~vivek] for this to work, however, the whole job would need to return no steps, and then it will default to showing just the full log... right [~jamesdumay] ? Or do we rely on the user to pop open the log when they see that things failed but not where? what should this look like? To be clear, this is a sytactic error - will show that bit error message I think right now if you try it (which is ok). With pipeline-config the error message will be clearer, but there will be no flow nodes in either case. This is ok IF this defaults to showing just the log (ie error message). Where this is bad is if the build starts, but then fails on that parallel branch ... then it isn't clear what to show. What is expected behavior, if we can't get a flownode? 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-35712) Failed step doesn't show as FlowNode
Title: Message Title Michael Neale edited a comment on JENKINS-35712 Re: Failed step doesn't show as FlowNode [~vivek] for this to work, however, the whole job would need to return no steps, and then it will default to showing just the full log... right [~jamesdumay] ? Or do we rely on the user to pop open the log when they see that things failed but not where? what should this look like?To be clear, this is a sytactic error - will show that bit error message I think right now if you try it (which is ok). With pipeline-config the error message will be clearer, but there will be no flow nodes in either case. This is ok IF this defaults to showing just the log (ie error message). 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-35712) Failed step doesn't show as FlowNode
Title: Message Title Michael Neale commented on JENKINS-35712 Re: Failed step doesn't show as FlowNode Vivek Pandey for this to work, however, the whole job would need to return no steps, and then it will default to showing just the full log... right James Dumay ? Or do we rely on the user to pop open the log when they see that things failed but not where? what should this look like? 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-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Coltrey Mather commented on JENKINS-36047 Re: Read users do not have permission to view Snippet Generator and Step Reference Jesse Glickv hudson.model.Item.ExtendedRead is what I gave in config.xml, not Item.VIEW_CONFIGURATION. Not sure if it's just a terminology thing, but the source was definitely checking for hudson.model.Item.ExtendedRead 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-35712) Failed step doesn't show as FlowNode
Title: Message Title Vivek Pandey commented on JENKINS-35712 Re: Failed step doesn't show as FlowNode Jesse Glick I see. Referring to Kohsuke Kawaguchi's comment, something that can be implemented? Not sure what kind of changes its going to result in to though. Michael Neale Since we show logs only for steps, we can use full log to show such errors as workaround. We flag failing node (branch or stage) status in the json DAG using parallel's endNode. If there is UI to show node level log, such error can be returned as log? 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-33632) docker.inside broken
Title: Message Title Christopher Eck commented on JENKINS-33632 Re: docker.inside broken Jesse, the problem seems to be that the plugin isn't issuing --volumes-from in this case. It's still attempting to use -v. 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-37743) Update style of progress bar to match mockup
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37743 Update style of progress bar to match mockup Change By: James Dumay Attachment: Result - load...@1x.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-37602) Branches tab does not showed queued runs
Title: Message Title Keith Zantow commented on JENKINS-37602 Re: Branches tab does not showed queued runs Maybe Ivan Meredith could shed some light, if I set queue size to 0, and run a branch, I immediately get a queued and then a job_started event. Was there some handling of this to keep the pipeline in queued status? 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-36584) pipeline branched build failes with workspace not a directory issue
Title: Message Title Jacob Keller commented on JENKINS-36584 Re: pipeline branched build failes with workspace not a directory issue I'll try to get a copy of the steps I'm running tomorrow. 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-37602) Branches tab does not showed queued runs
Title: Message Title Keith Zantow commented on JENKINS-37602 Re: Branches tab does not showed queued runs Note: make sure to clean node. I've seen some issue when rolling through updates where the SSE events just stop working until you clean and rebuild node stuff. 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-37602) Branches tab does not showed queued runs
Title: Message Title Keith Zantow commented on JENKINS-37602 Re: Branches tab does not showed queued runs Michael Neale Well, in multibranch jobs, the branches start when they're queued (due to a job_started event), but they definitely seem to be showing activity for me, am I missing a project type or use case? 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-37792) Pipeline Config: Notifications per stage
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37792 Pipeline Config: Notifications per stage Issue Type: Story Assignee: Andrew Bayer Components: pipeline-config-plugin Created: 2016/Aug/29 11:48 PM Environment: Pipeline Config 0.1 Priority: Minor Reporter: Andrew Bayer It'd be handy to be able to have notifications specified for individual stages as well as for the whole build. Add Comment
[JIRA] (JENKINS-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37312 BlueOcean "Failed to write numberOfFailingBranches" exception Change By: Michael Neale Sprint: 1.0-beta-1 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-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title James Dumay commented on JENKINS-37791 Re: When running a pipeline from a favourite we should not move the card Cliff Meyers something to think about but low priority for the moment. 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-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37791 When running a pipeline from a favourite we should not move the card Issue Type: Task Assignee: Unassigned Attachments: Aug-30-2016 09-10-38.gif Components: blueocean-plugin Created: 2016/Aug/29 11:16 PM Priority: Trivial Reporter: James Dumay If you run a pipeline from a favourite card it will move to the top automatically. Could we change the behaviour so that if the user clicks a run/rerun/etc action from the card that it doesn't move until the next time it naturally sorts? Add Comment
[JIRA] (JENKINS-36267) WorkflowRun.getEnvironment() do not include current node() environment
Title: Message Title Jesse Glick resolved as Not A Defect The environment applies to the whole build. It makes no sense to return node-specific environment here. There might be multiple node blocks running in parallel! Jenkins / JENKINS-36267 WorkflowRun.getEnvironment() do not include current node() environment Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-36265) parallel jobs don't show error traceback for some failures
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36265 parallel jobs don't show error traceback for some failures Change By: Jesse Glick 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-36235) Add optional 'timeout' parameter to 'input' step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36235 Add optional 'timeout' parameter to 'input' step Change By: Jesse Glick Component/s: pipeline-input-step-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-36225) load step causes changes to parameters to be discarded
Title: Message Title Jesse Glick commented on JENKINS-36225 Re: load step causes changes to parameters to be discarded Steps to reproduce from scratch? Probably something to do with use of global variables. Prefer lexical variables (def keyword). 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-36224) Environment variables not visible / linked for pipeline jobs
Title: Message Title Jesse Glick resolved as Not A Defect EnvInject is not, and will not be, compatible with Pipeline. Not sure about the other plugin. Jenkins / JENKINS-36224 Environment variables not visible / linked for pipeline jobs Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-36225) load step causes changes to parameters to be discarded
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36225 load step causes changes to parameters to be discarded Change By: Jesse Glick 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-36216) Documentation for nested objects is unclear
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36216 Documentation for nested objects is unclear Change By: Jesse Glick 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-36213) build-step - obtain environment variables from a non-pipeline job
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-36213 build-step - obtain environment variables from a non-pipeline job Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Jesse Glick commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Not to be confused with JENKINS-35988: multibranch indexing does not use SCM.compareRemoteRevisionWith at all. 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: workflow-scm-step-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-36195) Pipeline polling ignores special polling rules
Title: Message Title Jesse Glick commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules I'm not sure how it would honor the polling settings inside the Jenkinsfile in the repository. This is automatic, based on the checkout done in the last build. Not sure offhand, should work, since Pipeline supports workspace-based polling, but perhaps there is some bug, Git-specific or not, and missing test coverage. Generally speaking, polling exclusions are discouraged for Git since the plugin does not currently support them without reverting to workspace-based polling, which is always bad. AbstractGitSCMSource does define a caching system which could be used to fix that, but non-multibranch parts of the Git plugin do not currently take advantage of it. 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-36836) Git path polling ignores do not work in Pipeline jobs
Title: Message Title Jesse Glick resolved as Duplicate Sounds like a duplicate. Jenkins / JENKINS-36836 Git path polling ignores do not work in Pipeline jobs Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36098) General purpose fire-and-forget command "wrapper" for Pipeline
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-36098 General purpose fire-and-forget command "wrapper" for Pipeline Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Jesse Glick resolved as Not A Defect Indeed to use Snippet Generator you need to have Item.VIEW_CONFIGURATION permission. Jenkins / JENKINS-36047 Read users do not have permission to view Snippet Generator and Step Reference Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-36047) Read users do not have permission to view Snippet Generator and Step Reference
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36047 Read users do not have permission to view Snippet Generator and Step Reference Change By: Jesse Glick Component/s: workflow-multibranch-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-36038) Replay causes javax.servlet.ServletException: java.lang.UnsupportedOperationException
Title: Message Title Jesse Glick commented on JENKINS-36038 Re: Replay causes javax.servlet.ServletException: java.lang.UnsupportedOperationException I think what you were really looking for was JENKINS-26431. Also the first few lines would be better expressed as currentBuild.rawBuild. 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-37753) REGRESSION: Steps showing up as incomplete when they are in fact complete
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37753 REGRESSION: Steps showing up as incomplete when they are in fact complete Change By: Michael Neale Summary: REGRESSION: Steps showing up as incomplete when they are in fact complete 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-36038) Replay causes javax.servlet.ServletException: java.lang.UnsupportedOperationException
Title: Message Title Jesse Glick resolved as Duplicate Do not use as. Jenkins / JENKINS-36038 Replay causes javax.servlet.ServletException: java.lang.UnsupportedOperationException Change By: Jesse Glick Status: Open Resolved 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-36013) Automatically abort ExecutorPickle rehydration from an ephemeral node
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node Change By: Jesse Glick Component/s: workflow-durable-task-step-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-36007) Way to mask arbitrary Secret (was: Password is clear on log with input parameter)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36007 Way to mask arbitrary Secret (was: Password is clear on log with input parameter) Change By: Jesse Glick Labels: pipeline plugin security 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-36007) Way to mask arbitrary Secret (was: Password is clear on log with input parameter)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36007 Way to mask arbitrary Secret (was: Password is clear on log with input parameter) Change By: Jesse Glick Component/s: credentials-binding-plugin Component/s: mask-passwords-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-35691) Log user input on pipeline input step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35691 Log user input on pipeline input step Change By: Jesse Glick Component/s: pipeline-input-step-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-35712) Failed step doesn't show as FlowNode
Title: Message Title Jesse Glick resolved as Not A Defect A FlowNode is only created when there is a successful attempt to at least start a Step. In this case you should just see a failure attached to the end block of the parallel branch. Jenkins / JENKINS-35712 Failed step doesn't show as FlowNode Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-35698) Initial run of parameterized pipeline build should return properties default value
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35698 Initial run of parameterized pipeline build should return properties default value Change By: Jesse Glick Component/s: workflow-multibranch-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-35698) Initial run of parameterized pipeline build should return properties default value
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35698 Initial run of parameterized pipeline build should return properties default value Change By: Jesse Glick Labels: multibranch 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-35692) New syntax/snippet builder does not show environment variables
Title: Message Title Jesse Glick resolved as Cannot Reproduce Pipeline Syntax » Global Variables Reference » env Jenkins / JENKINS-35692 New syntax/snippet builder does not show environment variables Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce 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-35691) Log user input on pipeline input step
Title: Message Title Jesse Glick resolved as Won't Do There are all sorts of steps whose return value you might, or might not, care to see for debugging purposes. Would be undesirable in general to be too chatty in the logs. Jenkins / JENKINS-35691 Log user input on pipeline input step Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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
[JIRA] (JENKINS-35685) Auto-generate help for RunWrapperBinder/RunWrapper
Title: Message Title Jesse Glick commented on JENKINS-35685 Re: Auto-generate help for RunWrapperBinder/RunWrapper Maybe. I have no proposal in mind. 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-35691) Log user input on pipeline input step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35691 Log user input on pipeline input step Change By: Jesse Glick Labels: pipeline 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-35685) Auto-generate help for RunWrapperBinder/RunWrapper
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35685 Auto-generate help for RunWrapperBinder/RunWrapper Change By: Jesse Glick 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-35663) Aborting pipeline build does not work
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35663 Aborting pipeline build does not work Change By: Jesse Glick 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-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Change By: Jesse Glick Labels: testing 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-35647) Unable to abort parallel pipeline when failfast is used
Title: Message Title Jesse Glick resolved as Duplicate Sounds the same as JENKINS-35663. Jenkins / JENKINS-35647 Unable to abort parallel pipeline when failfast is used Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-37772) Support Core: Initializer(after = InitMilestone.COMPLETED) kills Jenkins initialization FSM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37772 Re: Support Core: Initializer(after = InitMilestone.COMPLETED) kills Jenkins initialization FSM Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/support/SupportPlugin.java http://jenkins-ci.org/commit/support-core-plugin/571a06f6fd4fe744349177e603ae2d7056f680c1 Log: JENKINS-37772 - Get rid of Initializer(after = InitMilestone.COMPLETED) (#73) 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-35663) Aborting pipeline build does not work
Title: Message Title Jesse Glick commented on JENKINS-35663 Re: Aborting pipeline build does not work Would need a minimal, self-contained reproducible test case. 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-35647) Unable to abort parallel pipeline when failfast is used
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35647 Unable to abort parallel pipeline when failfast is used Change By: Jesse Glick Component/s: workflow-cps-plugin Component/s: workflow-multibranch-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-35482) Multibranch pipeline does not have workspace view
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-35482 Multibranch pipeline does not have workspace view Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36358) ws step does not lock the workspace
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36358 ws step does not lock the workspace Change By: Jesse Glick Component/s: workflow-durable-task-step-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-35634) It would be nice to be able to query which node(s) a particular pipeline build built on via the REST API
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-35634 It would be nice to be able to query which node(s) a particular pipeline build built on via the REST API Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36687) Refactor RunPipeline to use HAL hrefs in internal logic
Title: Message Title Cliff Meyers updated JENKINS-36687 Jenkins / JENKINS-36687 Refactor RunPipeline to use HAL hrefs in internal logic Change By: Cliff Meyers 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-35796) Developer can stop the run of an executing pipeline
Title: Message Title Cliff Meyers updated JENKINS-35796 Jenkins / JENKINS-35796 Developer can stop the run of an executing pipeline Change By: Cliff Meyers 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-36974) Developer can stop a run from the activity tab
Title: Message Title Cliff Meyers updated JENKINS-36974 Jenkins / JENKINS-36974 Developer can stop a run from the activity tab Change By: Cliff Meyers 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-36687) Refactor RunPipeline to use HAL hrefs in internal logic
Title: Message Title Cliff Meyers commented on JENKINS-36687 Re: Refactor RunPipeline to use HAL hrefs in internal logic https://github.com/jenkinsci/blueocean-plugin/pull/446 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-36974) Developer can stop a run from the activity tab
Title: Message Title Cliff Meyers commented on JENKINS-36974 Re: Developer can stop a run from the activity tab PR: https://github.com/jenkinsci/blueocean-plugin/pull/446 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-35796) Developer can stop the run of an executing pipeline
Title: Message Title Cliff Meyers commented on JENKINS-35796 Re: Developer can stop the run of an executing pipeline PR: https://github.com/jenkinsci/blueocean-plugin/pull/446 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-37425) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-37425 Re: Run behaviour does not work as designed Michael Neale I believe Ivan Meredith updated the run modal to accept either a runId or a itemId - so whichever id can be used? 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-35609) GitStep is missing its descriptor with example build
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-35609 GitStep is missing its descriptor with example build Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36809) Ability to control the Orphaned Item Strategy from Jenkinsfile
Title: Message Title Jesse Glick resolved as Won't Do Jenkins / JENKINS-36809 Ability to control the Orphaned Item Strategy from Jenkinsfile Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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-35537) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title
Jesse Glick resolved as Incomplete
jenkinsci$ find {workflow,pipeline}-*-plugin/src/main/java -type f -exec fgrep -q doFillCredentialsIdItems {} \; -print
jenkinsci$
Jenkins / JENKINS-35537
Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Change By:
Jesse Glick
Status:
Open Resolved
Resolution:
Incomplete
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37782) Pipeline Config: Unable to refer to environment var in input string
Title: Message Title Michael Neale commented on JENKINS-37782 Re: Pipeline Config: Unable to refer to environment var in input string but you can use those vars in shell scripts that are no in a withEnv block? 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-37425) Run behaviour does not work as designed
Title: Message Title Michael Neale commented on JENKINS-37425 Re: Run behaviour does not work as designed IF that is the case, then yes. Although https://github.com/jenkinsci/blueocean-plugin/pull/441 is still pending, I am not sure of relationship. It doesn't seem to use that same expected run number value? cc 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-37711) Percent encoding cause fail in Visual Studio
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37711 Percent encoding cause fail in Visual Studio Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36109) Pre and post indexing hooks.
Title: Message Title Jesse Glick resolved as Won't Fix You could write such code in a plugin. Jenkins / JENKINS-36109 Pre and post indexing hooks. Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix 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-37425) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-37425 Re: Run behaviour does not work as designed Michael Neale Cliff Meyers Isn't this the same as clicking on the queued run in the activity list? 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-2111) removing a job does not remove the workspace
Title: Message Title Nicholas Bencriscutto commented on JENKINS-2111 Re: removing a job does not remove the workspace We are also experiencing this. It seems to cause issues at the most inconvenient time. (Of course when would it ever be convenient). Please give this more priority. 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-35686) Make multibranch pipeline jobs share workspace
Title: Message Title
Jesse Glick resolved as Won't Do
Use the {[ws}} step if you prefer to specify a location.
Jenkins / JENKINS-35686
Make multibranch pipeline jobs share workspace
Change By:
Jesse Glick
Status:
Open Resolved
Resolution:
Won't Do
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-35686) Make multibranch pipeline jobs share workspace
Title: Message Title
Jesse Glick edited a comment on JENKINS-35686
Re: Make multibranch pipeline jobs share workspace
Use the { [ { ws}} step if you prefer to specify a location.
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-37586) WORKSPACE environment variable not available in Jenkins pipeline
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37586 WORKSPACE environment variable not available in Jenkins pipeline Change By: Jesse Glick Status: Open Resolved 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36584) pipeline branched build failes with workspace not a directory issue
Title: Message Title Jesse Glick resolved as Incomplete Maybe some issue with ArtifactArchiverStepExecution. Steps to reproduce from scratch? Jenkins / JENKINS-36584 pipeline branched build failes with workspace not a directory issue Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-36584) pipeline branched build failes with workspace not a directory issue
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36584 pipeline branched build failes with workspace not a directory issue Change By: Jesse Glick Component/s: workflow-basic-steps-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-35521) pipeline to call RunListener.onInitialize
Title: Message Title Jesse Glick resolved as Incomplete I have no idea what is expected here. The method seems to have been newly added. The Javadoc is unclear. How does “entering execution” differ from “will now start running on an executor” of onStarted? WorkflowRun does not really use Run.State. It is probably meaningless for non-AbstractBuild implementations. Anyway from what I can piece together from JENKINS-34923, it is talking about the issue of build logs picking up encoding settings from agents. But WorkflowRun does not do that—it could not. Currently it just hardcodes UTF-8. Cf. JENKINS-31096. In other words, whatever one-shot-executor is trying to do, this is not going to help. You need to develop the complete feature as a unit before proposing APIs that we can never delete. Jenkins / JENKINS-35521 pipeline to call RunListener.onInitialize Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34615) Global error handler for pipeline
Title: Message Title Michael Neale closed an issue as Fixed Jenkins / JENKINS-34615 Global error handler for pipeline Change By: Michael Neale Status: Open Closed 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-34615) Global error handler for pipeline
Title: Message Title Michael Neale commented on JENKINS-34615 Re: Global error handler for pipeline I think we can close this as this is already handled in pipeline config plugin now via postBuild actions. 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-37790) abort on pipeline with parallel not succeeding / providing feedback on nodes
Title: Message Title Leah Klearman updated an issue Jenkins / JENKINS-37790 abort on pipeline with parallel not succeeding / providing feedback on nodes Change By: Leah Klearman Jenkinsfile is creating ~24 sub-jobs and running 5 of them at a time in parallel.Each sub-job is running up to 5 VMs that need to be cleaned up on abort to make room for the next jobs.The only time I have seen abort work on the first click is when all of the jobs are in the queue and none of them are running. Every other time, the console output has given me "Click here to forcibly terminate running steps" and later "Click here to forcibly kill entire build", and if i don't click those links, the job will stick around for days. In this instance, i've created two support bundles, at the times indicated.When I went to manually clean up the VMs, i found that 2 out of 5 of the workspaces had been successfully cleaned up before I got there, but all 5 workspaces look the same from the POV of the console output...they all look like they failed to abort.=Aborted by LeahKlearman...Sending interrupt signal to process..Sending interrupt signal to processSending interrupt signal to processSending interrupt signal to processSending interrupt signal to process[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node[Pipeline] // node [looks like all the queued sub-jobs have been successfully canceled here] Click here to forcibly terminate running steps[clicked "forcibly terminate running steps" now and created bundle support_2016-08-29_20.44.15]Terminating shTerminating shTerminating shTerminating shTerminating sh[output from one of the jobs]Click here to forcibly kill entire build[clicked "forcibly kill entire build" now and created support_2016-08-29_20.45.14]Hard kill!=
[JIRA] (JENKINS-37425) Run behaviour does not work as designed
Title: Message Title Michael Neale edited a comment on JENKINS-37425 Re: Run behaviour does not work as designed Not sure this is truly reliable in the case of freestyle where things really sit in the queued item for a while - we only have an expected run id, not the actual one, so OPEN isn't really advisable . is it? 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-37425) Run behaviour does not work as designed
Title: Message Title Michael Neale commented on JENKINS-37425 Re: Run behaviour does not work as designed Not sure this is truly reliable in the case of freestyle where things really sit in the queued item for a while - we only have an expected run id, not the actual one, so OPEN isn't really advisable. 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-35521) pipeline to call RunListener.onInitialize
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35521 pipeline to call RunListener.onInitialize Change By: Jesse Glick Component/s: workflow-job-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-35521) pipeline to call RunListener.onInitialize
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35521 pipeline to call RunListener.onInitialize Change By: Jesse Glick Summary: pipeline to call RunListener. onInitialized onInitialize 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-35519) no visible list of environment variables in pipeline editor
Title: Message Title Jesse Glick resolved as Cannot Reproduce Pipeline Syntax » Global Variables Reference Jenkins / JENKINS-35519 no visible list of environment variables in pipeline editor Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce 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-35506) Add a symbol to the build step in the hpi Maven archetype
Title: Message Title Jesse Glick commented on JENKINS-35506 Re: Add a symbol to the build step in the hpi Maven archetype As noted in the PR, this should rather take advantage of JENKINS-29922 and add a @Symbol. More broadly I would prefer to see an archetype for an empty plugin, as well as example archetype for plugins doing sundry things, one of which would be adding a Builder. 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.
