[JIRA] (JENKINS-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale Summary: Editor: Branches created off of non-master get created before committing cause false "duplicate name" error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale Component/s: blueocean-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale It looks like github is treating the default branch (nominally master) specially - and this is causing the "save as branch" to only work properly off the master branch. Summary:When editing a Declarative Pipeline Jenkinsfile on the master branch, and adding it to a new branch from the editor, everything works great. But if you edit the Jenkinsfile in the branch created in the editor, and try to create a new branch from there, the branch gets created before the changes to the Jenkinsfile are saved.Steps to recreate:1. Make a change to your Jenkinsfile using the editor, and save it to a new branch. Here's a screenshot of this step already completed, where the branch I created is called "CreateANewBranchForNoReason" !image-2017-03-21-20-58-59-321.png|thumbnail! 2. Provide a description of the change, and a new branch name.3. Click "Save & run." Notice that you get an error back, saying the branch already exists: !image-2017-03-21-21-01-13-875.png|thumbnail! 4. Flip over to GitHub itself, and look at your repository. The branch has been created: !image-2017-03-21-21-02-16-445.png|thumbnail! 5. The only way to dismiss the popup is to click Cancel.6. Also note that the "Updated" information shown in GitHub is way wrong, by 5 hours. It's reporting 5 hours ago, when I actually ran through these steps about 10 minutes ago: !image-2017-03-21-21-07-03-135.png|thumbnail! Add Comment
[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Fritz Elfert commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) Not really. Exclusion of the existing classes (in order to avoid duplicate class files) is much easier this way. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale assigned an issue to Keith Zantow Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale Assignee: Vivek Pandey Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale commented on JENKINS-43014 Re: Editor: Branches created off of non-master cause false "duplicate name" error Right yes I can see this, it is exclusively when not off master. I think there is some misunderstanding/misuse of the github api causing this confusion. Definitely a problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42601) reduce or eliminate core-js footprint
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42601 reduce or eliminate core-js footprint Change By: Michael Neale Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) Injection of js libs, dependencies and extension point improvements.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38876 Injection of js libs, dependencies and extension point improvements. Change By: Michael Neale Sprint: atlantic, indian, arctic, tasman , Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) Injection of js libs, dependencies and extension point improvements.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38876 Injection of js libs, dependencies and extension point improvements. Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Change By: Michael Neale Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42601) reduce or eliminate core-js footprint
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42601 reduce or eliminate core-js footprint Change By: Michael Neale Sprint: Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) Injection of js libs, dependencies and extension point improvements.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38876 Injection of js libs, dependencies and extension point improvements. Change By: Michael Neale Sprint: atlantic, indian, arctic, tasman , Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41960) Developer can change the stage level configuration
Title: Message Title Michael Neale assigned an issue to Cliff Meyers Jenkins / JENKINS-41960 Developer can change the stage level configuration Change By: Michael Neale Assignee: Keith Zantow Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41960) Developer can change the stage level configuration
Title: Message Title Michael Neale commented on JENKINS-41960 Re: Developer can change the stage level configuration Keith Zantow if we aren't aiming for this for 1.0, I think this could be an early editor thing for Cliff Meyers to take a look at at some point (would help get familiar with internals) - if it makes sense with you. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) Injection of js libs, dependencies and extension point improvements.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38876 Injection of js libs, dependencies and extension point improvements. Change By: Michael Neale Sprint: atlantic, indian, arctic, tasman , Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42173) Blue Ocean SDK design document - extensibility improvements
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42173 Blue Ocean SDK design document - extensibility improvements Change By: Michael Neale Summary: Blue Ocean SDK design document - extensibility improvements Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42560) unable to install ATH on macos
Title: Message Title Michael Neale resolved as Fixed Tom fixed it! Jenkins / JENKINS-42560 unable to install ATH on macos Change By: Michael Neale Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42602) Improve publishing and sharing of pure JS modules/libraries
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42602 Improve publishing and sharing of pure JS modules/libraries Change By: Michael Neale Sprint: Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42173) Blue Ocean SDK design document - extensibility improvements
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42173 Blue Ocean SDK design document - extensibility improvements Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) extension point improvements using decorators
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38876 extension point improvements using decorators Change By: Michael Neale Summary: Injection of js libs, dependencies and extension point improvements . using decorators Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38876) extension point improvements using decorators
Title: Message Title Michael Neale commented on JENKINS-38876 Re: extension point improvements using decorators WIP PR was here: https://github.com/jenkinsci/blueocean-plugin/pull/632 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42602) Improve publishing and sharing of pure JS modules/libraries
Title: Message Title Michael Neale commented on JENKINS-42602 Re: Improve publishing and sharing of pure JS modules/libraries Might be related to this WIP PR: https://github.com/jenkinsci/blueocean-plugin/pull/632 (or that may just be the decorator side of things). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale edited a comment on JENKINS-43014 Re: Editor: Branches created off of non-master cause false "duplicate name" error Right yes I can see this, it is exclusively when not off master. I think there is some misunderstanding/misuse of the github api causing this confusion. Definitely a problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale edited a comment on JENKINS-43014 Re: Editor: Branches created off of non-master cause false "duplicate name" error Right yes I can see this, it is exclusively when not off master. I think there is some misunderstanding/misuse of the github api causing this confusion. Definitely a problem. I also tried this with a newer branch with some other improvements, still there. Should be solvable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43020) Unable to stop multi-branch pipeline build
Title: Message Title
Omer van Kloeten created an issue
Jenkins / JENKINS-43020
Unable to stop multi-branch pipeline build
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-multibranch-plugin
Created:
2017/Mar/22 7:39 AM
Priority:
Critical
Reporter:
Omer van Kloeten
When trying to stop a multibranch pipeline build, I get the following error: POST is required for org.jenkinsci.plugins.workflow.job.WorkflowRun.doStop This error is followed by a button marked "Try POSTing" which goes to an error page (403, missing crumb). The workaround is going to the Script Console and running: Jenkins.instance .getItemByFullName("") .getBranch("") .getBuildByNumber() .finish(hudson.model.Result.ABORTED, new java.io.IOException("Aborting build")); But this is incredibly hacky and leaves the workflow view for the build in a state of "in progress" even though the build is no longer running.
Add Comment
[JIRA] (JENKINS-43020) Unable to stop multi-branch pipeline build
Title: Message Title Omer van Kloeten updated an issue Jenkins / JENKINS-43020 Unable to stop multi-branch pipeline build Change By: Omer van Kloeten Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43020) Unable to stop multi-branch pipeline build
Title: Message Title Omer van Kloeten updated an issue Jenkins / JENKINS-43020 Unable to stop multi-branch pipeline build Change By: Omer van Kloeten Environment: Jenkins ver. 2.32.3Pipeline: Multibranch plugin ver. 2.14 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43020) Unable to stop multi-branch pipeline build
Title: Message Title
Omer van Kloeten updated an issue
Jenkins / JENKINS-43020
Unable to stop multi-branch pipeline build
Change By:
Omer van Kloeten
When trying to stop a multibranch pipeline build, I get the following error:{{POST is required for org.jenkinsci.plugins.workflow.job.WorkflowRun.doStop}}This error is followed by a button marked "Try POSTing" which goes to an error page (403, missing crumb).The workaround is going to the Script Console and running:{{Jenkins.instance}}{{ .getItemByFullName("")}}{{ .getBranch("")}}{{ .getBuildByNumber()}}{{ .finish(hudson.model.Result.ABORTED, new java.io.IOException("Aborting build"));}}But this is incredibly hacky and leaves the workflow view for the build in a state of "in progress" even though the build is no longer running. Also, on the next restart of the Jenkins server, the build will resume running.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-42959 Failed known_hosts verification for SSH agent Change By: Vladimir Eremeev Attachment: J42959.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title Vladimir Eremeev commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Peter Vohmann: Thank you, I've obtained one more key with ssh-keyscan, having ssh-rsa in it, and the slave now launches fine. Michael Clarke: I think, more information in the help message will be useful. I mean the following: - this is a help on the slave configuration page. It says nothing about supported key encodings. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale It looks like github is treating the default branch (nominally master) specially - and this is causing the "save as branch" to only work properly off the master branch. If you try to save from a non default branch, it will just save the content from the master branch to the new branch, and incorreclty report it as a duplicate. Summary: When editing a Declarative Pipeline Jenkinsfile on the master branch, and adding it to a new branch from the editor, everything works great. But if you edit the Jenkinsfile in the branch created in the editor, and try to create a new branch from there, the branch gets created before the changes to the Jenkinsfile are saved.Steps to recreate: 1. Make a change to your Jenkinsfile using the editor, and save it to a new branch. Here's a screenshot of this step already completed, where the branch I created is called "CreateANewBranchForNoReason" !image-2017-03-21-20-58-59-321.png|thumbnail! 2. Provide a description of the change, and a new branch name. 3. Click "Save & run." Notice that you get an error back, saying the branch already exists: !image-2017-03-21-21-01-13-875.png|thumbnail! 4. Flip over to GitHub itself, and look at your repository. The branch has been created: !image-2017-03-21-21-02-16-445.png|thumbnail! 5. The only way to dismiss the popup is to click Cancel. 6. Also note that the "Updated" information shown in GitHub is way wrong, by 5 hours. It's reporting 5 hours ago, when I actually ran through these steps about 10 minutes ago: !image-2017-03-21-21-07-03-135.png|thumbnail! Add Comment
[JIRA] (JENKINS-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale commented on JENKINS-43014 Re: Editor: Branches created off of non-master cause false "duplicate name" error THis astually just saves content from master - which is wrong. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: {quote}{{ Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b }} {{ [Pipeline] End of Pipeline }} {{ groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding }} {{ at groovy.lang.Binding.getVariable(Binding.java:63) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) }} {{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) }} {{ at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) }} {{ at WorkflowScript.run(WorkflowScript:1) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) }} {{ at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) }} {{ at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) }} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) }} {{ at java.lang.reflect.Method.invoke(Method.java:498) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) }} {{ at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) }} {{ at com.cloudbees.groovy.cps.Next.step(Next.java:74) }} {{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) }} {{ at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) }} {{ at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) }} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) }} {{ at java.lang.Thread.run(Thread.java:745) }} {{ Fini
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title Omer van Kloeten commented on JENKINS-42882 Re: GitSCMFile::content() doesn't handle symlinks +1 to this issue, just hit it myself. For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b [Pipeline] End of Pipeline groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: {quote}{{ Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b }} {{ [Pipeline] End of Pipeline }} {{ groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding }} {{ at groovy.lang.Binding.getVariable(Binding.java:63) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) }} {{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) }} {{ at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) }} {{ at WorkflowScript.run(WorkflowScript:1) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) }} {{ at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) }} {{ at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) }} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) }} {{ at java.lang.reflect.Method.invoke(Method.java:498) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) }} {{ at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) }} {{ at com.cloudbees.groovy.cps.Next.step(Next.java:74) }} {{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) }} {{ at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) }} {{ at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) }} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) }} {{ at java.lang.Thread.run(Thread.java:745) }} {{
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: {{ Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b }} {{ [Pipeline] End of Pipeline }} {{ groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding }} {{ at groovy.lang.Binding.getVariable(Binding.java:63) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) }} {{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) }} {{ at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) }} {{ at WorkflowScript.run(WorkflowScript:1) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) }} {{ at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) }} {{ at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) }} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) }} {{ at java.lang.reflect.Method.invoke(Method.java:498) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) }} {{ at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) }} {{ at com.cloudbees.groovy.cps.Next.step(Next.java:74) }} {{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) }} {{ at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) }} {{ at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) }} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) }} {{ at java.lang.Thread.run(Thread.java:745) }} {{ Finished
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. {quote} For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing:Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b[Pipeline] End of Pipelinegroovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE {quote}
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. {quote} For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: {quote} Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b [Pipeline] End of Pipeline groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE {quote}
[JIRA] (JENKINS-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title
Omer van Kloeten edited a comment on JENKINS-42882
Re: GitSCMFile::content() doesn't handle symlinks
+1 to this issue, just hit it myself. For reference, when Jenkinsfile is symlinked to ci/build.groovy, this is what I'm seeing: {{ Obtained Jenkinsfile from f5035722844a5de1222dfaba340171ca060f3c6b }} {{ [Pipeline] End of Pipeline }} {{ groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding }} {{ at groovy.lang.Binding.getVariable(Binding.java:63) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) }} {{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) }} {{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) }} {{ at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) }} {{ at WorkflowScript.run(WorkflowScript:1) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) }} {{ at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) }} {{ at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) }} {{ at sun.reflect.GeneratedMethodAccessor332.invoke(Unknown Source) }} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) }} {{ at java.lang.reflect.Method.invoke(Method.java:498) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) }} {{ at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) }} {{ at com.cloudbees.groovy.cps.Next.step(Next.java:74) }} {{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) }} {{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) }} {{ at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) }} {{ at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) }} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) }} {{ at java.lang.Thread.run(Thread.java:745) }} {{ Finished:
[JIRA] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title Sorin Sbarnea commented on JENKINS-25804 Re: Whitelisted signature presets for Java standard APIs and Jenkins core APIs I also have a problem related to this, It seems that I need to add "hudson.plugins.git.GitSCM getBranches" because my jobs fail with this error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches The big problem is that is currently impossible to approve these because this is never reaching the scriptApproval page, which also does not allow us to introduce free-form text. How to solve this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41328) Openstack Heat Plugin does not "Delete if already Exists"
Title: Message Title Methodes Appliquees Arkea started work on JENKINS-41328 Change By: Methodes Appliquees Arkea Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41328) Openstack Heat Plugin does not "Delete if already Exists"
Title: Message Title Methodes Appliquees Arkea updated an issue Jenkins / JENKINS-41328 Openstack Heat Plugin does not "Delete if already Exists" Hi, We changed the library and the classpath about OpenStack4j to solve the issue. Normally, the master is correct, we will publish a new revision in April 2017. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-22660) More flexible UI for approved signatures
Title: Message Title Sorin Sbarnea commented on JENKINS-22660 Re: More flexible UI for approved signatures Jesse Glick Do we need to restart Jenkins when we update scriptApproval.xml? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41329) "Update if Exists" option
Title: Message Title Methodes Appliquees Arkea commented on JENKINS-41329 Re: "Update if Exists" option Hi, The approach to employ Heat limits the uses-case. In fact, Heat permits to manage the insfrastructure as code but not to realize a configuration of an existing insfrastruture because Heat doesn't permits to query an existing infrastructure. So we offer just the possibility to create and delete the infrastructure. However, it's possible to write an script HOT that takes an id in entry from an existing resource and to apply new configuration on it without delete an existing infrastructure. Best regards. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41329) "Update if Exists" option
Title: Message Title Methodes Appliquees Arkea closed an issue as Not A Defect Hi, The approach to employ Heat limits the uses-case. In fact, Heat permits to manage the insfrastructure as code but not to realize a configuration of an existing insfrastruture because Heat doesn't permits to query an existing infrastructure. So we offer just the possibility to create and delete the infrastructure. However, it's possible to write an script HOT that takes an id in entry from an existing resource and to apply new configuration on it without delete an existing infrastructure. Best regards. Jenkins / JENKINS-41329 "Update if Exists" option Change By: Methodes Appliquees Arkea Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43021) NotSerializableException while iterating over map,using values as buildID to download from number of builds
Title: Message Title
Paul Walter created an issue
Jenkins / JENKINS-43021
NotSerializableException while iterating over map,using values as buildID to download from number of builds
Issue Type:
Bug
Assignee:
Unassigned
Components:
copyartifact-plugin
Created:
2017/Mar/22 8:29 AM
Priority:
Trivial
Reporter:
Paul Walter
In our pipeline we run number of child jobs (number can differ,buildID is not consecutive,other jobs can run child jobs as well). in pipeline script we hold the BuildID number as value of map,keys are name of parallel group execution (not relevant.), map names is branches_numbers, it holds ['branch_1']='100',['branch_2']='104' etc. While iterating over such map we got NotSerializableException when using map values as Build ID. Bellow are examples:
stage('CopyArtifact')
{
def buildNum = ''
def test = []
def branches_numbers=[:]
branches_numbers['first_group']='100'
branches_numbers['second_group']='101'
for (n in branches_numbers)
{
buildNum=n.value.toString()
print buildNum
// THIS WILL FAIL
step([$class: 'CopyArtifact', filter: '*.log', fingerprintArtifacts: true, flatten: true, projectName: , selector: [$class: 'SpecificBuildSelector', buildNumber: buildNum], target: '.'])
test.add(buildNum)
}
for (n in branches_numbers.values)
{
buildNum=n.toString()
print buildNum
// THIS WILL PASS
step([$class: 'CopyArtifact', filter: '*.log', fingerprintArtifacts: true, flatten: true, projectName: , selector: [$class: 'SpecificBuildSelector', buildNumber: buildNum], target: '.'])
}
for (int i=0;i<2;i++)
{
print test[i]
// THIS WILL PASS
step([$class: 'CopyArtifact', filter: '*.log', fingerprintArtifacts: true, flatten: true, proj
[JIRA] (JENKINS-40235) Initial run of parameterized pipeline always fails the first time
Title: Message Title Tobias Honacker commented on JENKINS-40235 Re: Initial run of parameterized pipeline always fails the first time Arpan Khandelwal Same here, using version 2.29 of workflow-cps we can't access params.variables anymore Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42971) Pipeline script from SCM does not expand build parameters/env variables.
Title: Message Title
Bertrand Latinville updated an issue
Jenkins / JENKINS-42971
Pipeline script from SCM does not expand build parameters/env variables.
Change By:
Bertrand Latinville
Summary:
Pipeline script from SCM does not expand build parameters/env Variables variables .
Pipeline from SCM does not expand parameters or environment variables Steps to reproduce: * Create a new Pipeline with a String Parameter "PIPELINE_BRANCH" * In the pipeline definition ; Select "Pipeline Script from SCM" * Enter the Repository repository URL * In branch to build, enter the parameter : $\{PIPELINE_BRANCH} * Enter your script path * Run the job with a valid branch An error in thrown : hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/$\{PIPELINE_BRANCH}:refs/remotes/origin/$\{PIPELINE_BRANCH} --prune" returned status code 128: stdout: $\{PIPELINE_BRANCH} is not replaced by its value.Same issue with an environment variable.Expanding parameters/variable is working fine for a Freestyle freestyle or matrix job.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Christian Beushausen commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I see the same issue now on one of our Jenkins 2.32.3 installations, slave was connected fine but I had to reconnect it for reasons and since then I get this same error message. Following Peter Vohmann's advice I added the RSA key to my known_hosts file, but was not able to solve the issue. Error still persists. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42350) Remove requirement for ListAllMyBuckets permission
Title: Message Title Dave Hunt commented on JENKINS-42350 Re: Remove requirement for ListAllMyBuckets permission Thanks Alexander A, I'll let our ops team know. Perhaps this issue could be resolved with a simple tweak to the error message? Something like "Configuration has been saved, but connection to S3 could not be verified. Publishing to S3 may operate as intended, however for this verification to work you will need to grant the ListAllMyBuckets permission." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos created an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Issue Type: Bug Assignee: Stephen Connolly Attachments: image1.png, image2.png, image3.png Components: credentials-plugin Created: 2017/Mar/22 8:57 AM Environment: Jenkins v1.625.3 Labels: credentials jenkins git Plugin Priority: Blocker Reporter: juan francisco sanchez ramos I am using the Credential plugin for Jenkins, and I think I have detected a bug. I am going to explain the steps I have followed .(sorry for my English ) First, I create the domain and exclude the path ** Image 1 Second, I created the credentials for my user inside this domain** Image 2 Then, I configure the job, pasting the url repo.** Image 3 And the credentials show me jsanchra and None values. I guess the Credentials o
[JIRA] (JENKINS-43023) Provide URL of triggered job
Title: Message Title Matthias Bilger created an issue Jenkins / JENKINS-43023 Provide URL of triggered job Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2017/Mar/22 9:17 AM Priority: Minor Reporter: Matthias Bilger Background: We use Jenkins as a Build Server and report the result back into Gerrit. We use one Job which then triggers other jobs on a set of conditions. The result should be reported back to gerrit so the user do not have to click a hundred times to find the error. Problem at hand: I want to be able to provide a link to the triggered job that failed. I'd currently only provide the build number and the scrambeled name (replaced with ). I'm using the 'Unsuccessful Message File'_ feature from Gerrit Trigger Plugin. Add Comment
[JIRA] (JENKINS-42652) Artifactory Release Staging failing due to missing SNAPSHOT
Title: Message Title Eyal Ben Moshe commented on JENKINS-42652 Re: Artifactory Release Staging failing due to missing SNAPSHOT The issue is caused by a conflict between the maven-release-plugin and the Artifactory Release Staging feature in Jenkins. The two cannot work together, because both of them attempt to change the snapshot version into a release version. You'll need to choose which of the two you'd like to use. If you choose the Artifactory Release Staging feature (which we use as part of our CI/CD pipeline for many years), you'll have to remove the maven-release-plugin from the pom file and configure the "install" goal in your job configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43024) Improve pagination usability
Title: Message Title Justinas Urbanavicius created an issue Jenkins / JENKINS-43024 Improve pagination usability Issue Type: Improvement Assignee: Unassigned Components: build-pipeline-plugin Created: 2017/Mar/22 9:34 AM Labels: user-experience ux pagination Priority: Minor Reporter: Justinas Urbanavicius Currently pipeline pagination is always displayed at the top only. Would be really great if you could also have it at the bottom. So we would have pagination at the top and as well at the bottom. For lengthy pipelines that have pagination enabled, you mostly scroll to bottom to scan through the builds and if you don't find the build you are looking for, you need to scroll back to the top to use the pagination. That is very uncomfortable from the user perspective - annoying really. Add Comment
[JIRA] (JENKINS-43014) Editor: Branches created off of non-master cause false "duplicate name" error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Editor: Branches created off of non-master cause false "duplicate name" error Change By: Michael Neale It looks like github is treating the default branch (nominally master) specially - and this is causing the "save as branch" to only work properly off the master branch. If you try to save from a non default branch, it will just save the content from the master branch to the new branch, and incorreclty report it as a duplicate when trying to save the changed content . Summary Write up : When editing a Declarative Pipeline Jenkinsfile on the master branch, and adding it to a new branch from the editor, everything works great. But if you edit the Jenkinsfile in the branch created in the editor, and try to create a new branch from there, the branch gets created before the changes to the Jenkinsfile are saved.Steps to recreate: 1. Make a change to your Jenkinsfile using the editor, and save it to a new branch. Here's a screenshot of this step already completed, where the branch I created is called "CreateANewBranchForNoReason" !image-2017-03-21-20-58-59-321.png|thumbnail! 2. Provide a description of the change, and a new branch name. 3. Click "Save & run." Notice that you get an error back, saying the branch already exists: !image-2017-03-21-21-01-13-875.png|thumbnail! 4. Flip over to GitHub itself, and look at your repository. The branch has been created: !image-2017-03-21-21-02-16-445.png|thumbnail! 5. The only way to dismiss the popup is to click Cancel. 6. Also note that the "Updated" information shown in GitHub is way wrong, by 5 hours. It's reporting 5 hours ago, when I actually ran through these steps about 10 minutes ago: !image-2017-03-21-21-07-03-135.png|thumbnail! Add Comment
[JIRA] (JENKINS-43024) Improve pagination usability
Title: Message Title Justinas Urbanavicius updated an issue Jenkins / JENKINS-43024 Improve pagination usability Change By: Justinas Urbanavicius Component/s: delivery-pipeline-plugin Component/s: build-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Branches saved off of non-master cause false "duplicate name" error, don't save content
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43014 Branches saved off of non-master cause false "duplicate name" error, don't save content Change By: Michael Neale Summary: Editor: Branches created saved off of non-master cause false "duplicate name" error , don't save content Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42621) Using Numerical Comparison for conditional build step via DSL
Title: Message Title Valerie Fernandes closed an issue as Fixed Thanks Jenkins / JENKINS-42621 Using Numerical Comparison for conditional build step via DSL Change By: Valerie Fernandes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41879) Heat Orchestration Template (Hot) Player in Jenkins is empty due to a problem
Title: Message Title Methodes Appliquees Arkea closed an issue as Cannot Reproduce Hi, Normally if the repository contents the heat template with the yaml extension, there's no problem. At the origin, the plugin was developped on linux platform. So I tried under a window 7 and I used a configuration with spaces and paranthesis on the differents path. The plugin works correctly when I push the test button or when I create a new job with a call to the plugin. Best regards. Jenkins / JENKINS-41879 Heat Orchestration Template (Hot) Player in Jenkins is empty due to a problem Change By: Methodes Appliquees Arkea Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41118) Allow custom workspaces in declarative pipeline
Title: Message Title
Robert RJE commented on JENKINS-41118
Re: Allow custom workspaces in declarative pipeline
This worked for me since version 1.1:
pipeline {
agent {
label {
label ""
customWorkspace "C:/work/${BRANCH_NAME}"
}
}
stages {
stage("foo") {
steps {
echo "Workspace dir is ${pwd()}"
}
}
}
}
Thanks to Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-26858) java.net.URISyntaxException when special chars are used in filename
Title: Message Title Oliver Gondža reopened an issue It turns out that the special char is actually the number. The thing is that URI is constructed without scheme part, which appears legal according to javadoc, but then beginning of the scheme-specific part needs to comply to scheme name constrains for reasons I do not really understand. Jenkins / JENKINS-26858 java.net.URISyntaxException when special chars are used in filename Change By: Oliver Gondža Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Elmar Weber commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails Hello, is there any update on this or an idea where to check? If there is anything we can do to help debug this or how to start looking to fix this would be great, we currently considering writing a script that cleans up these nodes, we may as well invest the effort in fixing it in the plugin =) a quick pointer of where to start looking would be great. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/266413c635d1ff2c6e551a54869937fc58f6d4ae Log: JENKINS-40834 Pick up https://github.com/jenkinsci/git-client-plugin/pull/236 Compare: https://github.com/jenkinsci/git-plugin/compare/7164cf26db82...266413c635d1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitRemoteHeadRefAction.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/f97f8605c5dc4001b9ba7e2d46a8f5dda2674c4b Log: JENKINS-40834 Should implement for 2.6.x branch but... Seems like the JGit Impl is not actually making the remote's HEAD available. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-26858) java.net.URISyntaxException when special chars are used in filename
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26858 java.net.URISyntaxException when special chars are used in filename Change By: SCM/JIRA link daemon Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-26858) java.net.URISyntaxException when special chars are used in filename
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26858 Re: java.net.URISyntaxException when special chars are used in filename Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/compress_artifacts/ZipStorage.java src/test/java/org/jenkinsci/plugins/compress_artifacts/CompressArtifactsTest.java src/test/java/org/jenkinsci/plugins/compress_artifacts/ZipStorageTest.java http://jenkins-ci.org/commit/compress-artifacts-plugin/c0c641d037d4ec4b0a564f6beba2bb943df59b4a Log: [FIXED JENKINS-26858] Always use scheme when constructing URI for archived file Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-26858) java.net.URISyntaxException when special chars are used in filename
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26858 Re: java.net.URISyntaxException when special chars are used in filename Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/compress_artifacts/ZipStorage.java src/test/java/org/jenkinsci/plugins/compress_artifacts/CompressArtifactsTest.java src/test/java/org/jenkinsci/plugins/compress_artifacts/ZipStorageTest.java http://jenkins-ci.org/commit/compress-artifacts-plugin/ef69f52cfec9edc69443ee11c1435c15febe0329 Log: Merge pull request #6 from olivergondza/JENKINS-26858-take2 [FIXED JENKINS-26858] Always use scheme when constructing URI for archived file Compare: https://github.com/jenkinsci/compress-artifacts-plugin/compare/49f4422a24c5...ef69f52cfec9 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43025) Using Override Credentials for parameterized remote trigger plugin via DSL
Title: Message Title Valerie Fernandes created an issue Jenkins / JENKINS-43025 Using Override Credentials for parameterized remote trigger plugin via DSL Issue Type: Improvement Assignee: Daniel Spilker Attachments: image-2017-03-22-16-06-11-008.png Components: job-dsl-plugin Created: 2017/Mar/22 10:40 AM Priority: Major Reporter: Valerie Fernandes Hi, I did not find a method to use for overriding credentials using DSL(I am using parameterized remote trigger plugin). I also checked Automatically Generated DSL but did not find it. Could you please help by adding support for it? PS : i want to avoid the configure block Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Martin Sander commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException This also occurs for me when NOT running on kubernetes. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43026) Trigger a job from jenkinsfile with build instruction without autorization
Title: Message Title olivier olivier created an issue Jenkins / JENKINS-43026 Trigger a job from jenkinsfile with build instruction without autorization Issue Type: Bug Assignee: Unassigned Components: matrix-auth-plugin Created: 2017/Mar/22 11:07 AM Environment: jenkins 2.31.1, master and slave in openshift , redhat is Priority: Critical Reporter: olivier olivier I can call a job from another with ''build'' instruction in a jenkinsfile, even if the current user are not allow to run that job ( ProjectMatrixAuthorizationStrategy ).It's ok from user interface, but we need the same user restriction when calling a job from jenkinsFile Add Comment
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/git-plugin/d2c51dc7ccb7f4f77b589ac6c83ac4077ba89037 Log: JENKINS-40834 Pick up latest -SNAPSHOT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly commented on JENKINS-43022 Re: Not correct exclude path to domains So you have not supplied a wildcard on the path, which means that you are excluding only the EXACT path /git/STEPS/ try changing your exclude path to /git/STEPS/** Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly resolved as Not A Defect Marking as not a defect as I suspect it is a configuration error on your side. Please re-open if my suggestion does not resolve the issue for you. Please close if my suggestion did fix Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: Stephen Connolly Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receivi
[JIRA] (JENKINS-43027) Force build execution on failure of previous build steps
Title: Message Title Naresh Gunda created an issue Jenkins / JENKINS-43027 Force build execution on failure of previous build steps Issue Type: Bug Assignee: wolfs Components: gradle-plugin Created: 2017/Mar/22 11:30 AM Environment: Android Priority: Critical Reporter: Naresh Gunda In my jenkins job i have three build steps. 1st Execute shell, 2nd gradle script to run testcases, 3rd executeshell. When i run this job, if any testcase is failed then the 2nd build step is marked as failed and jenkins is skipping the 3rd build step execution. Is there any workaround to forcefully execute the 3d build step even if the previous builds steps fails. Please help. Add Comment
[JIRA] (JENKINS-43027) Force build execution on failure of previous build steps
Title: Message Title Naresh Gunda updated an issue Jenkins / JENKINS-43027 Force build execution on failure of previous build steps Change By: Naresh Gunda In my jenkins job i have three build steps. 1st one Execute shell, 2nd gradle script to run testcases, 3rd executeshell. When i run this job, if any testcase is failed then the 2nd build step is marked as failed and jenkins is skipping the 3rd build step execution and marking the build as failure . Is there any workaround to forcefully execute the 3d build step even if the previous builds steps fails. Please help. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43027) Force continue build execution on failure of previous build steps
Title: Message Title Naresh Gunda updated an issue Jenkins / JENKINS-43027 Force continue build execution on failure of previous build steps Change By: Naresh Gunda Summary: Force continue build execution on failure of previous build steps Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos reopened an issue Hi stephen Change exclude to /git/STEPS/** in the same problem : Unable to render embedded object: File (image-2017-03-22-12-33-00-891.png) not found. and show credentials : Unable to render embedded object: File (image-2017-03-22-12-33-49-707.png) not found. Thanks Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: juan francisco sanchez ramos Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you
[JIRA] (JENKINS-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos updated an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: juan francisco sanchez ramos Attachment: image5.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos updated an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: juan francisco sanchez ramos Attachment: image6.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title juan francisco sanchez ramos edited a comment on JENKINS-43022 Re: Not correct exclude path to domains Hi stephenChange exclude to */git/STEPS/*** in the same problem : ! * image -2017-03-22-12-33-00-891.png! 5 and show credentials : ! * image -2017-03-22-12-33-49-707.png! 6 Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43027) Force continue build execution on failure of previous build steps
Title: Message Title Naresh Gunda updated an issue Jenkins / JENKINS-43027 Force continue build execution on failure of previous build steps Change By: Naresh Gunda In my jenkins job i have three build steps. 1st one Execute shell, 2nd gradle script to run testcases, 3rd executeshell execute shell . When i run this job, if any testcase is failed then the 2nd build step is marked as failed and , jenkins is skipping the 3rd build step execution and marking the build as failure. Is there any workaround to forcefully execute the 3d build step even if the previous builds steps fails. Please help. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43027) Force continue build execution on failure of previous build steps
Title: Message Title wolfs commented on JENKINS-43027 Re: Force continue build execution on failure of previous build steps You basically have two options: Set ignoreFailures=true on the test tasks. See for example here. You can run your shell script as a Post build step For me, the first option seems to be the correct choice. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42882) GitSCMFile::content() doesn't handle symlinks
Title: Message Title Bernhard Miklautz commented on JENKINS-42882 Re: GitSCMFile::content() doesn't handle symlinks Omer van Kloeten I have exactly the same trace except it can't find the property build as the link starts with build. If this behavior isn't intentional and it worked before with older versions it's definitely a regression because it might cause projects to fail (and the problem isn't obvious from the error messages and hard to track). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: Stephen Connolly Component/s: git-client-plugin Component/s: credentials-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly assigned an issue to Mark Waite Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: Stephen Connolly Assignee: Stephen Connolly Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly commented on JENKINS-43022 Re: Not correct exclude path to domains This is a bug in the git-client plugin. https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/GitURIRequirementsBuilder.java#L189 Does not generate PathRequirement information at all Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43022) Not correct exclude path to domains
Title: Message Title Stephen Connolly commented on JENKINS-43022 Re: Not correct exclude path to domains NOTE: The credentials plugin's helper for generating requirements does supply the path requirement: https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/domains/URIRequirementBuilder.java#L101 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42982) Editor is inop with Microsoft Edge
Title: Message Title Karl Shultz commented on JENKINS-42982 Re: Editor is inop with Microsoft Edge Hey Keith Zantow - I'm using Microsoft Edge 38.14393.0.0. According to Wikipedia, this is the current stable release. I was testing on my laptop. I'm probably going to be at home with a sick toddler for at least part of the day today, but can try to get into the office later, if you're coming in and want to see it. Or we could screenshare, either way. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-16648) changes-since-last-success plugin doesn't work
Title: Message Title Per Östman reopened an issue See comment. Jenkins / JENKINS-16648 changes-since-last-success plugin doesn't work Change By: Per Östman Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-16648) changes-since-last-success plugin doesn't work
Title: Message Title Per Östman edited a comment on JENKINS-16648 Re: changes-since-last-success plugin doesn't work I too cannot find any options to configure this plugin. Using Jenkins 2 - is it verified to work in Jenkins 2? I get the same error as the reporter of this bug - a 404 Not Found, and no buiild action seem to be available. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42284) 'chcp' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title Roel van Nuland commented on JENKINS-42284 Re: 'chcp' is not recognized as an internal or external command, operable program or batch file. Hi, Some more info: even after copying chcp.com to chcp.exe, the v1.27 plugin still produces the same error. I'm not running the Jenkins slave service as the default user (Local system) but as a dedicated User which is part of the Users group. (I did not yet fiddle with the rights of that user, just a standard new local Windows user). Might that have something to do with it? Regards, Roel. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title Christian Beushausen edited a comment on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I see the same issue now on one of our Jenkins 2.32.3 installations, slave was connected fine but I had to reconnect it for reasons and since then I get this same error message.Following [~pvohmann]'s advice I added the RSA key to my known_hosts file, but was not able to solve the issue. Error still persists. Update: Nevermind. I did not read carefully and only executed this on the slave and not on the master ... after properly updating the known_hosts file on the Jenkins master connection can be established again. Sorry for any confusion. Would also propose to update the documentation to make it easier understandable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43014) Branches saved off of non-master cause false "duplicate name" error, don't save content
Title: Message Title Keith Zantow started work on JENKINS-43014 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43028) Request to add support for Azure Managed Disks
Title: Message Title nathan crouse created an issue Jenkins / JENKINS-43028 Request to add support for Azure Managed Disks Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2017/Mar/22 1:06 PM Environment: Jenkins 2.32.3 Azure VM Agents 0.4.3 Priority: Minor Reporter: nathan crouse Request to add support for Azure Managed Disks (vs using standard storage accounts). Azure Managed Disks appears to be the Microsoft recommended storage method for VM disks in the future. Add Comment
[JIRA] (JENKINS-30572) Parallel step snippet generator error
Title: Message Title Daniel Beck commented on JENKINS-30572 Re: Parallel step snippet generator error Also affects https://jenkins.io/doc/pipeline/steps/workflow-cps/#parallel-execute-in-parallel Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42135) Pipeline Creation last steps
Title: Message Title Keith Zantow updated JENKINS-42135 Jenkins / JENKINS-42135 Pipeline Creation last steps Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42784) Unable to create new pipeline for empty repo in brand new github org
Title: Message Title Keith Zantow updated JENKINS-42784 Jenkins / JENKINS-42784 Unable to create new pipeline for empty repo in brand new github org Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43029) Inaccurate help text for FileBinding
Title: Message Title Jordan Coll created an issue Jenkins / JENKINS-43029 Inaccurate help text for FileBinding Issue Type: New Feature Assignee: Unassigned Components: credentials-binding-plugin Created: 2017/Mar/22 1:36 PM Priority: Trivial Reporter: Jordan Coll The help text states that: (The file is deleted when the build completes.) but this doesn't seem to be true; the file is deleted when exiting the withCredentials block Add Comment
[JIRA] (JENKINS-43003) label parameter does not enforse execution on the labels
Title: Message Title akostadinov resolved as Duplicate Seems like we're hitting JENKINS-36568 Jenkins / JENKINS-43003 label parameter does not enforse execution on the labels Change By: akostadinov Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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
