[JIRA] (JENKINS-40180) Allow global post-build steps
Title: Message Title Jean Mertz created an issue Jenkins / JENKINS-40180 Allow global post-build steps Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Dec/02 7:45 AM Priority: Minor Reporter: Jean Mertz It would be nice if it where possible to define global postBuild actions that are triggered for all repositories part of an organisation folder. We have some global company-wide actions that we'd like to trigger after each build, but right now that doesn't seem possible. We do use global pipeline scripts, but specific postBuild actions trigger based on failures, which isn't easily doable in a global pipeline script. Add Comment
[JIRA] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Yannick FRINDEL edited a comment on JENKINS-27906 Re: Fail to read NUnit3 output xml same issue. Until it is fixed, the only solution I have consist to transform my results in a nunit2 xml result file.But with this solution I have less information in my xml file... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Yannick FRINDEL commented on JENKINS-27906 Re: Fail to read NUnit3 output xml same issue. Until it is fixed, I transform my results in a nunit2 xml result file. But with this solution I have less information in my xml file... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title Nick Sonneveld commented on JENKINS-38765 Re: Stage view renders incorrectly with stages appearing multiple times. Sam Van Oort Unfortunately I still see this behaviour. This is with the new workflow-api 2.8 (all other plugins are up to date as well) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38765 Stage view renders incorrectly with stages appearing multiple times. Change By: Nick Sonneveld Attachment: Screen Shot 2016-12-02 at 5.59.45 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title Nick Sonneveld commented on JENKINS-39092 Re: Pipeline branches SCM polling properties for multibranch has broken behaviour. Hrm just witnessed this behaviour again today. Haven't had a chance to install a fresh jenkins install to try to find a test case yet. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40088) JSON serialization should not fail if a plugins action failed to serialize
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40088 JSON serialization should not fail if a plugins action failed to serialize Change By: James Dumay If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is JENKINS-40083.If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-40088) JSON serialization should not fail if a plugins action failed to serialize
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40088 JSON serialization should not fail if a plugins action failed to serialize Change By: James Dumay Sprint: tethys frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39965) Add extension point for top of runs changes tab
Title: Message Title James Dumay updated JENKINS-39965 Jenkins / JENKINS-39965 Add extension point for top of runs changes tab Change By: James Dumay Status: In Review Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered when there is more that 100 nodes Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39464 pipeline with parallel but not stages shows up only first branch Change By: James Dumay Sprint: frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39513) Prompted to enable pull requests when they're already enabled
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39513 Prompted to enable pull requests when they're already enabled Change By: James Dumay Sprint: arctic, frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39549) Navigate back to Blue Ocean page after saving config
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39549 Navigate back to Blue Ocean page after saving config Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36062) Freestyle jobs should see an empty state on the result for why the pipeline graph is missing
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36062 Freestyle jobs should see an empty state on the result for why the pipeline graph is missing Change By: James Dumay Sprint: pacific, atlantic, 1.0-b05/b-06, indian , frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37798) No results shown when Unable to checkout SCM or network issue
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-37798 No results shown when Unable to checkout SCM or network issue Change By: James Dumay Assignee: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36766) Developer can get a link to the PR and Branch on Github
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36766 Developer can get a link to the PR and Branch on Github Change By: James Dumay Sprint: atlantic , frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37798) No results shown when Unable to checkout SCM or network issue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37798 No results shown when Unable to checkout SCM or network issue Change By: James Dumay Sprint: 1.0-beta-1, pacific, atlantic, 1.0-b05/b-06, indian, arctic, frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40131) "Re-run" button text needs to be translated
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: James Dumay Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39893) Enable findbugs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39893 Enable findbugs Change By: James Dumay Sprint: frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40131) "Re-run" button text needs to be translated
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: James Dumay Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39894 REGRESSION: SSE broken on MS Edge and IE11 Change By: James Dumay Sprint: frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40080) Pipeline summary makes multiple /classes requests
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-40080 Pipeline summary makes multiple /classes requests Change By: James Dumay Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39341) Update favourite card design
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39341 Update favourite card design Change By: James Dumay Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39341) Update favourite card design
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39341 Update favourite card design Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39763) Update pipeline run header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39763 Update pipeline run header Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37379) Some real-time favorite card statuses are not accurate
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-37379 Some real-time favorite card statuses are not accurate Change By: James Dumay Assignee: Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39762) Update application header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39762 Update application header Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39762) Update application header
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39762 Update application header Change By: James Dumay Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39763) Update pipeline run header
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39763 Update pipeline run header Change By: James Dumay Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title James Dumay commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input Michael Neale Vivek Pandey we should reuse what we are building in creation IMO Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Brody Maclean stopped work on JENKINS-37295 Change By: Brody Maclean Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Michael Neale commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input Vivek Pandey James Dumay perhaps this should be a drop down for credentials... is thi sthe case where it asks for a credential when it is asking for input? (we could start with a credential id text field if we needs to, or a dropdown like creation) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Brody Maclean updated JENKINS-37295 Jenkins / JENKINS-37295 Redesign the empty states Change By: Brody Maclean Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39292) Rationalise the button design and styles
Title: Message Title Brody Maclean updated JENKINS-39292 Jenkins / JENKINS-39292 Rationalise the button design and styles Change By: Brody Maclean Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38522) Long stage names overflow poorly on stage graph
Title: Message Title Brody Maclean stopped work on JENKINS-38522 Change By: Brody Maclean Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40089) Error while deploying ear to WAS
Title: Message Title Vidya Jothiraman commented on JENKINS-40089 Re: Error while deploying ear to WAS HI Greg We tried changing permission of ear file, still it doesnt help. Here is the output from build + chmod 777 /var/jenkins/workspace/WatsonSIHRestServices/Edu-K12-Codebase-Clone/SIH/StudentInfoHubEar/target/StudentInfoHubEAR.ear Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- StudentInfoHubEAR.ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0037E Could not open /var/jenkins/workspace/WatsonSIHRestServices/Edu-K12-Codebase-Clone/SIH/StudentInfoHubEar/target/StudentInfoHubEAR.ear at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:193) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Mike Kobit commented on JENKINS-39977 Re: Support for bitbucket-branch-source-plugin Actually, just ran into https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext.groovy which looks like the right place to put this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Frederick Staats edited a comment on JENKINS-40166 Re: Passwords not quoted correctly in Windows I agree that a temporary password file is a better fix than my first suggestion. I had only suggested the smallest possible change, not the most general change.Please note that all versions of Git for Windows ship with bash.exe out of the box in the same folder as git.exe (you can always use the path to git.exe as the path to bash.exe regardless of what %PATH% is set to).Type.exe has the problem that it is not always on the users path in Windows, but bash.exe is always next to git.exe. You can use bash's builtin file redirection and printf without having any other executable on your path:bash.exe --noprofile -c 'printf %s "$(
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Frederick Staats edited a comment on JENKINS-40166 Re: Passwords not quoted correctly in Windows I agree that a temporary password file is a better fix than my first suggestion. I had only suggested the smallest possible change, not the most general change.Please note that all versions of Git for Windows ship with bash.exe out of the box in the same folder as git.exe (you can always use the path to git.exe as the path to bash.exe regardless of what %PATH% is set to).Type.exe has the problem that it is not always on the users path in Windows, but bash.exe is always next to git.exe. You can use bash's builtin file redirection and printf without having any other executable on your path:bash.exe --noprofile -c 'printf %s "$(
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Frederick Staats edited a comment on JENKINS-40166 Re: Passwords not quoted correctly in Windows I agree that a temporary password file is a better fix than my first suggestion. I had only suggested the smallest possible change, not the most general change.Please note that all versions of Git for Windows ship with bash.exe out of the box in the same folder as git.exe (you can always use the path to git.exe as the path to bash.exe regardless of what %PATH% is set to).Type.exe has the problem that it is not always on the users path in Windows, but bash.exe is always next to git.exe. You can use bash's builtin file redirection and printf without having any other executable on your path:bash.exe --noprofile -c 'printf %s "$(
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Frederick Staats commented on JENKINS-40166 Re: Passwords not quoted correctly in Windows I agree that a temporary password file is a better fix than my first suggestion. I had only suggested the smallest possible change, not the most general change. Please note that all versions of Git for Windows ship with bash.exe out of the box in the same folder as git.exe (you can always use the path to git.exe as the path to bash.exe regardless of what %PATH% is set to). Type.exe has the problem that it is not always on the users path in Windows, but bash.exe is always next to git.exe. You can use bash's builtin file redirection and printf without having any other executable on your path: bash.exe --noprofile -c 'printf %s "$(
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Mike Kobit commented on JENKINS-39977 Re: Support for bitbucket-branch-source-plugin I'm interested in taking this on. Taking a look at the no changes XML it looks like they are not the job type but part of an OrganizationFolder: .* All false false true 0 0 H H * * * 8640 bitbuck SAME .* false -1 Any suggestions on what you think the best user experience would be here for a user defining a Bitbucket Branch Source folder? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38765) Stage view renders incorrectly with stages appearing multiple times.
Title: Message Title David van Laatum commented on JENKINS-38765 Re: Stage view renders incorrectly with stages appearing multiple times. Still seems broken for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Vivek Pandey updated JENKINS-38491 Jenkins / JENKINS-38491 Add new "waitingForInput" status to API for runs, dag and steps Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40179) Stray comma at end of HTML value passed to build step
Title: Message Title
Keith Currier created an issue
Jenkins / JENKINS-40179
Stray comma at end of HTML value passed to build step
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
2016/Dec/02 2:10 AM
Environment:
Jenkins 2.19.4 Active Choices Plug-in 1.5.2 Windows 7
Priority:
Minor
Reporter:
Keith Currier
I have a build job with multiple Active Choices Reactive Reference Parameters. If the Choice Type is set to either "Formatted HTML" or "Formatted Hidden HTML" the parameter value is supposed to be passed to each build step as an environment variable. The problem is that the value passed has an extraneous comma (",") at the end of it. For example, if I set the value of parameter "FOO" to "BAR", the value passed to my build step is "BAR,".
Add Comment
[JIRA] (JENKINS-40178) Use new QEMU2 Emulator engine
Title: Message Title Christopher Orr commented on JENKINS-40178 Re: Use new QEMU2 Emulator engine Yeah, I think that a recent emulator release fixed the last of the issues, but I haven't confirmed. Last time I checked, using the new engine, I think I had problems starting emulators that had been created and were started with the old engine — something about not being able to find the correct kernel image. I'll try and check it out, and see what issues there are, if any. If you fancy trying it out, you can change the line of code that keeps us on the old engine and try out a build of the plugin. Or I can create a build of the plugin hardcoded to the new engine if you need for testing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Vivek Pandey commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input James Dumay Michael Neale Credentials parameter visualization is different in classic where it shows dropdown box of available options, whereas this visual design shows it as username and password field. See the image below from classic, where it gives option to user to add a new credential as well, if you click Add, it takes you to Credential form input. I assume we are going to show list of available credentials? Which is pretty much a drop down choice box then. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-35899 Form to capture user input when pipeline is waiting for user input Change By: Vivek Pandey Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40131) "Re-run" button text needs to be translated
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: Tom FENNELLY Summary: "Re-run" button text needs to be translatd translated Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40140) Remote Docker host not working
Title: Message Title Zheng Li commented on JENKINS-40140 Re: Remote Docker host not working Thanks, didn't know that. Then the tricky thing is I'm running jenkins from the jenkins Docker image, does this mean there is no way I can get this plugin to work without manually get a docker client inside it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39867) Message: Unauthorized from OpenShift API after some time
Title: Message Title agustin burguete commented on JENKINS-39867 Re: Message: Unauthorized from OpenShift API after some time Thank you for your comments, I am bound to make some mistakes since I do not have that much experience. Nevertheless, it is when using NFS volume or Hosted volume (aprox. name, cannot check it right now) that I get the error. With no volume or Empty dir volume, it works fine, the plugin does start-up a pod in Openshift. I am using a Vagrant all-in-one version of Openshift Origin as kubernetes host, and therefore I just use a system-admin login for all purposes, so I would not expect permission issues. I am replicating the setup described in here https://blog.openshift.com/jenkins-slaves-in-openshift-using-an-external-jenkins-environment/ where two ways are used to have jenkins slaves, one is Swarm plugin (preallocated slave pods selfdiscover the master) the other kubernetes-plugin (the master actively launches slaves on kubernetes, that would be within openshift in this case). For swarm plugin I found that v2.2 does have regression in terms of honoring the NO_PROXY env. var, which is important on my setup, so it works fine if I stay in 2.0. For kubernetes-plugin I am finding the problem already stated, it launches slaves OK only if they have no volumes or empty dir volumes. I am wildguessing it might have to do with some bug in kubernetes-client which is used for the plugin?, Since it is a jenkins for experimenting, I am using an 'admin' account in jenkins too. The pod slaves preinstantiated (the ones that connect to master jenkins via swarm) do also have the same NFS volume defined (via openshift deployment config in this case) and they work just fine. NFS directory has an nfsnobody owner and group, that volumes is accessed ok for the preallocated pods launched via openshift, and anyway the other option via 'host volume' does not work either (same error). NFS directories, Openshift origin and master jenkins all are located in the same machine. Master jenkins cohabits with Openshift Origin installation (so master jenkins is not a pod within Openshift, the slaves are meant to be deployed in Openshift). The whole point of the setup is to have all slaves share a persistent volume to keep there maven's repository, so that when maven 'downloads half of internet' upon a build, is kept there and all those jars do not disappear and have to be downloaded again for a next build. Slaves preallocated with swarm do fine on this, the ones with kubernetes-plugin... seemingly cannot have a persistent volume for now...Sorry for the lengthy comment! Your suggestions are very welcome. Should this be a separate issue? Add Comment
[JIRA] (JENKINS-40116) Crash on login when using blueocean plugin
Title: Message Title James Dumay started work on JENKINS-40116 Change By: James Dumay Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40116) Crash on login when using blueocean plugin
Title: Message Title James Dumay updated JENKINS-40116 Jenkins / JENKINS-40116 Crash on login when using blueocean plugin Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40116) Crash on login when using blueocean plugin
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40116 Crash on login when using blueocean plugin Dino Hensen sorry about that - this is an easy fix we can apply in the next release. Change By: James Dumay Priority: Major Critical Sprint: tasman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-40178) Use new QEMU2 Emulator engine
Title: Message Title Josh Burton created an issue Jenkins / JENKINS-40178 Use new QEMU2 Emulator engine Issue Type: Improvement Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/Dec/02 12:26 AM Priority: Minor Reporter: Josh Burton Emulators using the new QEMU2 engine are must faster, and more stable. I am currently unable to use the Android Emulator Jenkins plugin as my tests fail with the classic engine. I understand the reason the plugin uses the classic engine is because certain commands like `ports` were not supported. It appears that ports is now supported. Is there anything else stopping the plugin from using the new engine? Add Comment
[JIRA] (JENKINS-40116) Crash on login when using blueocean plugin
Title: Message Title Tom FENNELLY commented on JENKINS-40116 Re: Crash on login when using blueocean plugin We need an NPE check in ResourceCacheControl for when the request path is empty. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40116) Crash on login when using blueocean plugin
Title: Message Title Tom FENNELLY assigned an issue to Tom FENNELLY Jenkins / JENKINS-40116 Crash on login when using blueocean plugin Change By: Tom FENNELLY Assignee: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40177) Use BitBucket Server project icon for jenkins folder icon
Title: Message Title Tiernan Messmer created an issue Jenkins / JENKINS-40177 Use BitBucket Server project icon for jenkins folder icon Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Dec/02 12:22 AM Priority: Minor Reporter: Tiernan Messmer Similar to how the GitHub plugin allows the repository or organisation icon to be used, it would be great if the BitBucket branch source plugin allowed the project icon to be used as the folder icon. Add Comment
[JIRA] (JENKINS-40131) "Re-run" button text needs to be translatd
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40131 "Re-run" button text needs to be translatd Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40159) Open Blue Ocean button is shown even after uninstalling the blueocean-beta plugin from jenkins
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-40159 Open Blue Ocean button is shown even after uninstalling the blueocean-beta plugin from jenkins Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40176) Username with password - Broken Git Https
Title: Message Title Christian E closed an issue as Not A Defect not a bug. Had it in wrong section. Jenkins / JENKINS-40176 Username with password - Broken Git Https Change By: Christian E Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40176) Username with password - Broken Git Https
Title: Message Title Christian E created an issue Jenkins / JENKINS-40176 Username with password - Broken Git Https Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Dec/01 11:46 PM Environment: OS X Jenkins 2.34 Priority: Blocker Reporter: Christian E I struggled for hours trying to get secret text to work for auth only to realize it's not supported. SSH doesn't work very well as with many repos, we get a connection reset by peer. Github even recommends https anyway. When setting up credentials under Username with password option, I now have 2 in my Credentials store, the projects show "None" In the dropdown. Sometimes the UI freaks out and shows a current but a page refresh then it goes away showing none. The only one I can get to work are SSH to appear in the project drop drown for "Git" Source code type. Add Comment
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-39407
Re: Use system default Maven, Maven Settings if not specified
[~jglick] we seem to have a problem with "{{AbstractBuild}}" versus "{{WorkflowRun}}".Maven default settings are handled by [{{jenkins.mvn.SettingsProvider#supplySettings(AbstractBuild build, TaskListener listener)}}|https://github.com/jenkinsci/jenkins/blob/51619cc80a56fb2681896ccdf6fafb85924a4ac8/core/src/main/java/jenkins/mvn/SettingsProvider.java#L29-L29] which is based on "{{AbstractBuild}}" when pipeline is based on "{{WorkflowRun}}".As we want to use {{jenkins.mvn.SettingsProvider#supplySettings()}} in " {{withMaven() {...\ }} }" , does it seem reasonable to refactor [{{jenkins.mvn.SettingsProvider#supplySettings(AbstractBuild build, TaskListener listener)}}|https://github.com/jenkinsci/jenkins/blob/51619cc80a56fb2681896ccdf6fafb85924a4ac8/core/src/main/java/jenkins/mvn/SettingsProvider.java#L29-L29] into {{jenkins.mvn.SettingsProvider#supplySettings(Run build, TaskListener listener)}}?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Cyrille Le Clerc commented on JENKINS-39407 Re: Use system default Maven, Maven Settings if not specified Jesse Glick we seem to have a problem with "AbstractBuild" versus "WorkflowRun". Maven default settings are handled by jenkins.mvn.SettingsProvider#supplySettings(AbstractBuild build, TaskListener listener) which is based on "AbstractBuild" when pipeline is based on "WorkflowRun". As we want to use jenkins.mvn.SettingsProvider#supplySettings() in withMaven(), does it seem reasonable to refactor jenkins.mvn.SettingsProvider#supplySettings(AbstractBuild build, TaskListener listener) into jenkins.mvn.SettingsProvider#supplySettings(Run build, TaskListener listener)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title Dan Alvizu commented on JENKINS-38670 Re: ability to enter build notes/parameters for a Manual step in the pipeline I've pushed some work I have to refactor the 'build card' behavior into a separate customizable class on a branch: https://github.com/jenkinsci/build-pipeline-plugin/tree/JENKINS-38670 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38670 Re: ability to enter build notes/parameters for a Manual step in the pipeline Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildCardExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/StandardBuildCard.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/configure-entries.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildCardExtension/buildCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/StandardBuildCard/config.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewConstructorTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewDisplayNameTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildCardExtensionTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/testsupport/PipelineWebDriverTestBase.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTriggerTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/8ef34e2453316a40c89550368c0837d7fa839cdd Log: JENKINS-38670 refactor build card to a BuildCardExtension class Move all "Build Card" display and trigger logic into a BuildCardExtension class. This allows plugins or other BuildCardExtension children to customize behavior, for example to require approval notes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40092) slave.jar copy via SCP fails in 2.33+
Title: Message Title Steve Todorov commented on JENKINS-40092 Re: slave.jar copy via SCP fails in 2.33+ Jesse Glick this release seems to have fixed the issue. I've upgraded to jenkins 2.34 and the latest SSH slaves plugin and everything works fine. Thanks for your fast fix! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40175) Masked Passwords are shown while rebuild.
Title: Message Title Ben Jamin created an issue Jenkins / JENKINS-40175 Masked Passwords are shown while rebuild. Issue Type: Bug Assignee: ragesh_nair Components: rebuild-plugin Created: 2016/Dec/01 10:51 PM Environment: Jenkins ver. 1.651.3 Priority: Critical Reporter: Ben Jamin 1. I have configured global parameters for masking passwords. Plugin: Mask Passwords Plugin 2. I have created job and enable mask password 3. I have created build with a password parameter in it. when I type the password it is masked, when i click on a build I can see : "You really think you can access this value?" when i click on rebuild I can see the password in clear in a plaintext input. Add Comment
[JIRA] (JENKINS-40174) Missing authentication during git checkout and git-lfs
Title: Message Title
Laurent Goujon created an issue
Jenkins / JENKINS-40174
Missing authentication during git checkout and git-lfs
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-client-plugin
Created:
2016/Dec/01 10:49 PM
Environment:
Jenkins 2.27 Git Plugin: 3.0.0 Git Client Plugin: 2.0.0
Priority:
Minor
Reporter:
Laurent Goujon
One of our repository is using git-lfs to store large objects. When trying to doing a checkout of the branch, Jenkins fails to clone the repository when the git-lfs filter is getting the objects.
Cloning the remote Git repository
Cloning repository ssh://g...@github.com/foo/repo.git
> git init /jenkins/workspace/foo/repo # timeout=10
Fetching upstream changes from ssh://g...@github.com/foo/repo.git
> git --version # timeout=10
using GIT_SSH to set credentials SSH Key to access github
> git fetch --tags --progress ssh://g...@github.com/foo/repo.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url ssh://g...@github.com/foo/repo.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url ssh://g...@github.com/foo/repo.git # timeout=10
Fetching upstream changes from ssh://g...@github.com/foo/repo.git
using GIT_SSH to set credentials SSH Key to access github
> git fetch --tags --progress ssh://g...@github.com/foo/repo.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Robert Watkins commented on JENKINS-39407 Re: Use system default Maven, Maven Settings if not specified That's pretty much the behaviour I would expect. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39647) Failed to write defaultParameterValue
Title: Message Title James Dumay commented on JENKINS-39647 Re: Failed to write defaultParameterValue I think we can solve misbehaving plugins once and for all with JENKINS-40088 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40173) Conflict with aws-java-sdk 1.11.37
Title: Message Title Franz Garsombke created an issue Jenkins / JENKINS-40173 Conflict with aws-java-sdk 1.11.37 Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Dec/01 10:25 PM Environment: Jenkins 2.30, S3 publisher plugin 0.10.10 Priority: Major Reporter: Franz Garsombke The S3 publisher plugin is unusable with the latest aws-java-sdk 1.11.37 plugin since it depends on aws-java-sdk (version:1.10.50). The following stacktrace is received javax.servlet.ServletException: java.lang.NoSuchMethodError: org.apache.http.impl.conn.CPool.setValidateAfterInactivity(I)V at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) To fix the issue we had to downgrade our aws-java-sdk plugin to 0.10.10 Add Comment
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. As far as I can tell, the only way to authenticate properly under Windows is to pass the username/password to an HTTPS url. See http://stackoverflow.com/a/33630506/14731 and JENKINS-28335 for more details. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
cowwoc commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Beware: ssh-agent will not currently work under windows: JENKINS-28279 ("git plugin", such as the "checkout" task will fail to authenticate) As far as I can tell, the only option under Windows is to pass the username/password to an HTTPS url: http://stackoverflow.com/a/33630506/14731
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40099) Job creation takes awhile
Title: Message Title Daniel Spilker resolved as Duplicate Jenkins / JENKINS-40099 Job creation takes awhile Change By: Daniel Spilker Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40102) job dsl does not respect pipeline withEnv
Title: Message Title Daniel Spilker resolved as Duplicate Jenkins / JENKINS-40102 job dsl does not respect pipeline withEnv Change By: Daniel Spilker Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40172) git pipeline scm poll workspace doesn't find git repository
Title: Message Title Jacob Keller created an issue Jenkins / JENKINS-40172 git pipeline scm poll workspace doesn't find git repository Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2016/Dec/01 10:04 PM Priority: Major Reporter: Jacob Keller The git plugin doesn't appear to find the proper workspace when performing SCM polling on a pipeline job. I use the checkout() step and have set SCM polling to 10 minutes. Every 10 minutes, the polling log shows something along these lines: Using strategy: Default [poll] Last Built Revision: Revision 5f6e2e39083ff256ccc9face14f6358a5c522ee4 (origin/master) No Git repository yet, an initial checkout is required This line appears in the git plugin code in a section that appears to be the case of "requiresWorkspaceForPolling = true" which is the case when using multiple branches, or when the branch contains wildcards. I haven't yet figured out why it thinks my configuration has multiple branches (it should only have one) but either way the polling via workspace should still work as expected... When we go through this path, it appears that the pipeline job doesn't get the correct workspace, as the one that we run polling inside does not have the repository checked out.
[JIRA] (JENKINS-40171) The "Apply" button's "Saved" message obstructs the top menu
Title: Message Title Ethan Trewhitt created an issue Jenkins / JENKINS-40171 The "Apply" button's "Saved" message obstructs the top menu Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Dec/01 9:59 PM Priority: Trivial Reporter: Ethan Trewhitt Clicking "Apply" on a project configuration screen creates a message popup at the top of the current viewport in the web UI. It fades in and obstructs the top menu. Since a common operation during project design is to click "Build Now" for the project, that's a very minor annoyance. It's so trivial that I hesitated to submit this ticket, but it's just one of those niceties that would be better if it were different. Add Comment
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Keith Zantow commented on JENKINS-39126 Re: Collect browser logs and publish via support-core A few notes Ivan, Cliff, and I had about this, from the UI perspective: Collect logs in memory, potentially using some amount of local storage Flush periodically in a background thread We need an easy JS utility API to offer channels and levels of logging If an error happens we might report more logs back to provide more context Things like SSE/connectivity errors, check the logs if there is a pending SSE error already and don't re-report the error Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Keith Zantow updated JENKINS-39852 Jenkins / JENKINS-39852 REGRESSION: Loading worm never finishes on dashboard Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40170) Separate execution functionality of image.inside() into distinct steps
Title: Message Title
Ethan Trewhitt updated an issue
Jenkins / JENKINS-40170
Separate execution functionality of image.inside() into distinct steps
Change By:
Ethan Trewhitt
Image.inside() performs a number of tasks that are useful in many cases. Unfortunately it also performs one task that cannot directly be performed with any other Groovy step: actually running code in the image. The execution step should be separated from the other steps performed by inside() so that users can control what happens. If this means that inside() remains the same, while a new method is created that _only_ executes code within the running container, that's fine. It's already a bit strange that "inside" is attached to the "Image" object, since the code is actually being executed inside a container instantiated from that image.May I suggest adding a some functiosn functions to the "container" object so that we can do this? I would envision this process to look something like this:{code}node {def image = docker.image('metatest')def container = image.run()container.execInside() {step("Get Username") {sh "whoami"}step("Report Success") {sh "echo Success!"}}container.stop()container.remove()}{code}Note that I have also separated the _stop_ and _rm_ steps for the container. I see no reason why they should be combined in the stop() method. Why not mirror the Docker commands with the same name?
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40170) Separate execution functionality of image.inside() into distinct steps
Title: Message Title
Ethan Trewhitt updated an issue
Jenkins / JENKINS-40170
Separate execution functionality of image.inside() into distinct steps
Change By:
Ethan Trewhitt
Image.inside() performs a number of tasks that are useful in many cases. Unfortunately it also performs one task that cannot directly be performed with any other Groovy step: actually running code in the image. The execution step should be separated from the other steps performed by inside() so that users can control what happens. If this means that inside() remains the same, while a new method is created that _only_ executes code within the running container, that's fine. It's already a bit strange that "inside" is attached to the "Image" object, since the code is actually being executed inside a container instantiated from that image.May I suggest adding a some functiosn to the "container" object so that we can do this? I would envision this process to look something like this: {code} node {def image = docker.image('metatest')def container = image.run()container.execInside() {step("Get Username") {sh "whoami"}step("Report Success") {sh "echo Success!"}}container.stop()container.remove()} {code} Note that I have also separated the _stop_ and _rm_ steps for the container. I see no reason why they should be combined in the stop() method. Why not mirror the Docker commands with the same name?
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40170) Separate execution functionality of image.inside() into distinct steps
Title: Message Title
Ethan Trewhitt updated an issue
Jenkins / JENKINS-40170
Separate execution functionality of image.inside() into distinct steps
Change By:
Ethan Trewhitt
Image.inside() performs a number of tasks that are useful in many cases. Unfortunately it also performs one task that cannot directly be performed with any other Groovy step: actually running code in the image. The execution step should be separated from the other steps performed by inside() so that users can control what happens. If this means that inside() remains the same, while a new method is created that _only_ executes code within the running container, that's fine. It's already a bit strange that "inside" is attached to the "Image" object, since the code is actually being executed inside a container instantiated from that image.May I suggest adding a some functiosn to the "container" object so that we can do this? I would envision this process to look something like this: {{ node {def image = docker.image('metatest')def container = image.run()container.execInside() { step("Get Username") { sh "whoami" }step("Report Success") { sh "echo Success!"} } container.stop()container.remove()} }} Note that I have also separated the _stop_ and _rm_ steps for the container. I see no reason why they should be combined in the stop() method. Why not mirror the Docker commands with the same name?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Mark Waite commented on JENKINS-40166 Re: Passwords not quoted correctly in Windows Git client plugin pull request PR207 has started the process of investigating the quoting problem. I think there is a better way which completely avoids the "shell escaping" problem. Refer to my master-PR207-exploring branch for an implementation which uses type (windows) and cat (unix) rather than echo. I think type and cat are better choices because the password can be written to a file without any escaping, then the cat (or type) command reports the contents of that file on a pipe to the git command. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40170) Separate execution functionality of image.inside() into distinct steps
Title: Message Title
Ethan Trewhitt created an issue
Jenkins / JENKINS-40170
Separate execution functionality of image.inside() into distinct steps
Issue Type:
New Feature
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2016/Dec/01 9:37 PM
Priority:
Minor
Reporter:
Ethan Trewhitt
Image.inside() performs a number of tasks that are useful in many cases. Unfortunately it also performs one task that cannot directly be performed with any other Groovy step: actually running code in the image. The execution step should be separated from the other steps performed by inside() so that users can control what happens. If this means that inside() remains the same, while a new method is created that only executes code within the running container, that's fine. It's already a bit strange that "inside" is attached to the "Image" object, since the code is actually being executed inside a container instantiated from that image. May I suggest adding a some functiosn to the "container" object so that we can do this? I would envision this process to look something like this: {{ node { def image = docker.image('metatest') def container = image.run() container.execInside() { sh "whoami" sh "echo Success!" } container.stop() container.remove() } }} Note that I have also separated the stop and rm steps for the container. I see no reason why they should be combined in the stop() method. Why not mirror the Docker commands with the same name?
[JIRA] (JENKINS-40169) CSS Style does not work with HTML publisher when Jenkins is installed as server in Windows 10.
Title: Message Title Edwin Jose created an issue Jenkins / JENKINS-40169 CSS Style does not work with HTML publisher when Jenkins is installed as server in Windows 10. Issue Type: Bug Assignee: mcrooney Components: htmlpublisher-plugin Created: 2016/Dec/01 9:24 PM Priority: Major Reporter: Edwin Jose I run my Automation script and well defined Report is generated in Workspace. I use HTML publisher so that I can give my project team a link where they can see the report at a glance. While doing the same with HTML publisher, i dont see the styles getting applied. Jenkins version : 2.19.1 Jenkins is ran as a server in Windows 10 machine. but when i open the same HTML file from my work space instead of HTML publisher in Jenkins, it looks and works fine. Add Comment
[JIRA] (JENKINS-40168) Make the override of ENTRYPOINT by image.inside optional
Title: Message Title Ethan Trewhitt created an issue Jenkins / JENKINS-40168 Make the override of ENTRYPOINT by image.inside optional Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2016/Dec/01 9:22 PM Priority: Major Reporter: Ethan Trewhitt The change made to address JENKINS-37987 breaks Docker images that use a specific ENTRYPOINT to start services. Any Docker image based on the common scenario of using supervisord to run a set of daemons will break with the override of ENTRYPOINT and CMD by image.inside, which overrides the command to "cat" to keep the image alive. While some users may need that behavior, many of us would prefer to control that directly. Add Comment
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title
Mark R commented on JENKINS-38211
Re: JenkinsFiles cannot run on Linux agent of Windows master
It comes from this: https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java
String s = script;
final Jenkins jenkins = Jenkins.getInstance();
if (!s.startsWith("#!") && jenkins != null) {
String defaultShell = jenkins.getInjector().getInstance(Shell.DescriptorImpl.class).getShellOrDefault(ws.getChannel());
s = "#!"+defaultShell+" -xe\n" + s;
}
shf.write(s, "UTF-8");
shf.chmod(0755);
The default shell for the node must be 'sh'. It should be configurable somewhere... I'll ask our build guys if that can be done. For some reason it doesn't like '#!sh'. In the mean time I am able to get it to work by manually setting the shell:
sh '#!/usr/bin/sh -xe\n env'
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-23914) Invalid element added to in job causing NPE on job load
Title: Message Title Sergio Fernandes commented on JENKINS-23914 Re: Invalid element added to in job causing NPE on job load I had the same issue with Jenkins 2.19.4, and I used Job Config History plugin to restore the previous trigger config. Currently I cannot use Poll SCM option because it writes the null element and prevents any change on the job config! H/10 * * * * false Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title
Mark R edited a comment on JENKINS-38211
Re: JenkinsFiles cannot run on Linux agent of Windows master
A coworker was able to grab the temporary script being run on the Linux agent. The line endings are fine (LF-only): {noformat} [agent].../durable-3ca81cbf:$ od -cxv script.sh000 # ! s h - x e \n e n v 212368732d206578650a766e014 {noformat} But he still sees the same error: {noformat} [agent].../durable-3ca81cbf:$ ./script.shbash: ./script.sh: sh: bad interpreter: No such file or directory {noformat} It looks to be a malformed shebang. Modifying the shebang to be an absolute path allowed the script to run successfully. {noformat} [agent].../durable-3ca81cbf:$ od -cxv mod.sh000 # ! / b i n / s h - x e \n e n 2123622f6e69732f2068782d0a656e65020 v 0076021 {noformat} I'm now looking into if that is configurable.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Mark R commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master A coworker was able to grab the temporary script being run on the Linux agent. The line endings are fine (LF-only): [agent].../durable-3ca81cbf: $ od -cxv script.sh 000 # ! s h - x e \n e n v 2123 6873 2d20 6578 650a 766e 014 But he still sees the same error: [agent].../durable-3ca81cbf: $ ./script.sh bash: ./script.sh: sh: bad interpreter: No such file or directory It looks to be a malformed shebang. Modifying the shebang to be an absolute path allowed the script to run successfully. [agent].../durable-3ca81cbf: $ od -cxv mod.sh 000 # ! / b i n / s h - x e \n e n 2123 622f 6e69 732f 2068 782d 0a65 6e65 020 v 0076 021 I'm now looking into if that is configurable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40167) readYaml requires a workspace even if the workspace is not needed
Title: Message Title
Mike Dougherty updated an issue
Jenkins / JENKINS-40167
readYaml requires a workspace even if the workspace is not needed
Change By:
Mike Dougherty
`readYaml` appears to require a workspace, even if only the `text` argument is used.Using this pipeline script:{code :groovy }echo readYaml(text: "---"){code}I get this result:{code}Started by user Mike Dougherty[Pipeline] readYamlRequired context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node[Pipeline] End of Pipelineorg.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:253) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor434.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.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-40167) readYaml requires a workspace even if the workspace is not needed
Title: Message Title Mike Dougherty created an issue Jenkins / JENKINS-40167 readYaml requires a workspace even if the workspace is not needed Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2016/Dec/01 8:55 PM Environment: Jenkins 2.19.1; pipeline-utility-steps 1.2.1 Priority: Minor Reporter: Mike Dougherty `readYaml` appears to require a workspace, even if only the `text` argument is used. Using this pipeline script: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml echo readYaml(text: "---") I get this result: Started by user Mike Dougherty [Pipeline] readYaml Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node [Pipeline] End of Pipeline org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:253) at
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Mark R commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master Any progress on this? This is a showstopper for us as we are unable to run linux shell scripts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40163) Baseline shift in breadcrumbs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40163 Baseline shift in breadcrumbs Change By: James Dumay Sprint: frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title Frederick Staats commented on JENKINS-40166 Re: Passwords not quoted correctly in Windows Can't figure out how to link issues, please note JENKINS-38194 is a subset of this quoting issue (only referring to the ampersand character.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40166) Passwords not quoted correctly in Windows
Title: Message Title
Frederick Staats created an issue
Jenkins / JENKINS-40166
Passwords not quoted correctly in Windows
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-client-plugin
Created:
2016/Dec/01 7:57 PM
Environment:
Windows
Priority:
Minor
Reporter:
Frederick Staats
In https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java Method createWindowsStandardAskpass() & createWindowsSshAskpass() create cmd.exe .bat batch files are created that echo the passwords to standard out. They use this method to encode the password: private String quoteWindowsCredentials(String str) { // Assumes the only meaningful character is %, this may be // insufficient.* return str.replace("%", "%%"); } This misses several characters are missed that also need to be quoted, see http://ss64.com/nt/syntax-esc.html for more specifics. Specifically the cmd.exe caret ^ escape character is needed to quote backslash, ampersand, right bracket, left bracket, caret, space and tab characters: ^\ ^& ^| ^> ^< ^^ ^ (note there is a space) and ^ (note there is a tab) This could easily be implemented by adding additional lines to the method for each of these extra characters. Currently when you use these characters in a Git password and run the job on windows you get very poor error messages saying that the fetch operation failed do to an error in ASKPASS.
[JIRA] (JENKINS-38882) Avoid browser cache busting after Jenkins restart
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-38882 Avoid browser cache busting after Jenkins restart Change By: Tom FENNELLY Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40092) slave.jar copy via SCP fails in 2.33+
Title: Message Title Jesse Glick commented on JENKINS-40092 Re: slave.jar copy via SCP fails in 2.33+ Released 1.12 with fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title Tom FENNELLY commented on JENKINS-39894 Re: REGRESSION: SSE broken on MS Edge and IE11 Jim Klimov can you also test on another machine please, just in case it' something relating to the local IE config. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
