[JIRA] (JENKINS-37749) Client-id and Secret gets overwritten by username and password hash
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-37749 Client-id and Secret gets overwritten by username and password hash Change By: Vincent Latombe Summary: Clinet Client -id and Secret gets overwritten by username and password hash 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-33286) logging-out with google-login-plugin is not work
Title: Message Title Vincent Latombe commented on JENKINS-33286 Re: logging-out with google-login-plugin is not work Please note that the plugin will never log you out from google. It is your responsibility to do so. If you are in a public place, you shouldn't use options such as 'Remember Me' and when you close the browser session when you are done. 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-33286) logging-out with google-login-plugin is not work
Title: Message Title Vincent Latombe started work on JENKINS-33286 Change By: Vincent Latombe 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-33286) logging-out with google-login-plugin is not work
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-33286 logging-out with google-login-plugin is not work Change By: Vincent Latombe Assignee: recampbell Vincent Latombe 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-37060) Need unprotected URLs for webhooks from CVS
Title: Message Title Vincent Latombe closed an issue as Won't Do It's not an issue with the google-login plugin, it is an issue with the corresponding plugins. Please file tickets against these plugins to expose their hooks under unauthenticated endpoints. For example, the git-plugin doesn't have this issue and exposes his hook as an UnprotectedRootAction (https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitStatus.java). Jenkins / JENKINS-37060 Need unprotected URLs for webhooks from CVS Change By: Vincent Latombe Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36558) Sort the dashboard alphabetically
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36558 Sort the dashboard alphabetically Change By: James Dumay Issue Type: Task Story 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title Vivek Pandey commented on JENKINS-37880 Re: Starting, stopping and replaying a run in quick succession does not work James Dumay that code looks alright, instanceof is false if the value being checked is null. I need to look in to it whats causing this failure. 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-37880) Starting, stopping and replaying a run in quick succession does not work
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-37880
Starting, stopping and replaying a run in quick succession does not work
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Sep/01 4:22 AM
Priority:
Minor
Reporter:
James Dumay
Steps to reproduce
Create a new multi-branch pipeline using https://github.com/i386/hellonode
Go to the branches screen
Trigger a new build for master
Open the run and click stop
Then click replay again
The goal here is to try starting, stopping then replaying really quickly. You will get a 500 error back from the replay action PUT http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/hellonode/branches/master/runs/23/replay/ 500 (Server Error)
Unknown macro: { "message" }
I attached a debugger when reproducing and got org.jenkinsci.plugins.workflow.cps.replay.ReplayAction#run2 returning null. Digging deeper it appears we can't get the flow owner
private @CheckForNull CpsFlowExecution getExecution() {
FlowExecutionOwner owner = ((FlowExecutionOwner.Executable)
[JIRA] (JENKINS-37879) Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file
Title: Message Title Bruno P. Kinoshita commented on JENKINS-37879 Re: Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file Thanks vijay nag! 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-37879) Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file
Title: Message Title vijay nag commented on JENKINS-37879 Re: Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file Attached the test result xml file. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37879) Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file
Title: Message Title vijay nag updated an issue Jenkins / JENKINS-37879 Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file Change By: vijay nag Attachment: TestResult.xml 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-37879) Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file
Title: Message Title Bruno P. Kinoshita commented on JENKINS-37879 Re: Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file It seems to complain about the report contents. Could you attach an example, so that I can try to reproduce it, please? 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-37879) Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file
Title: Message Title vijay nag created an issue Jenkins / JENKINS-37879 Jenkins NUnit plugin 0.18 gives an error while reading nunit result xml file Issue Type: Bug Assignee: Bruno P. Kinoshita Components: nunit-plugin Created: 2016/Sep/01 3:32 AM Environment: Windows Priority: Major Reporter: vijay nag When the Nunit plugin tries to read the test result xml file, it gives the below error. Results (nunit3) saved as TestResult.xml Recording NUnit tests results ERROR: Step ‘Publish NUnit test result report’ aborted due to exception: java.io.IOException: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:71) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:29) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:153) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: org.xml.sax.SAXParseException; systemId: file:/C:/Users/2554/.jenkins/workspace/TestProject/temporary-junit-reports/temp-junit.xml; lineNumber: 2; columnNumber: 3; Content is not allowed in prolog. at
[JIRA] (JENKINS-37796) @Grab Grape support for global post script plugin
Title: Message Title Hao CHEN resolved as Done Jenkins / JENKINS-37796 @Grab Grape support for global post script plugin Change By: Hao CHEN Status: Open Resolved Resolution: Done 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-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay edited a comment on JENKINS-37878 Re: Implement a DisplayURLProvider for Blue Ocean Most plugins have been converted over to use this API:* Email https://github.com/jenkinsci/mailer-plugin/pull/29* HipChat https://github.com/jenkinsci/hipchat-plugin/pull/82* Slack https://github.com/jenkinsci/slack-plugin/pull/245* Jabber, Skype, etc IM https://github.com/jenkinsci/instant-messaging-plugin/pull/15 ** IRC https://github.com/jenkinsci/ircbot-plugin/pull/17 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-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay commented on JENKINS-37878 Re: Implement a DisplayURLProvider for Blue Ocean Most plugins have been converted over to use this API: Email https://github.com/jenkinsci/mailer-plugin/pull/29 HipChat https://github.com/jenkinsci/hipchat-plugin/pull/82 Slack https://github.com/jenkinsci/slack-plugin/pull/245 Jabber, Skype, etc https://github.com/jenkinsci/instant-messaging-plugin/pull/15 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-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Justin Massey commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation ok good to know. thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Igor Matlin commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation The latest commit is for yet-to-be released version of CxSAST. Please revert back to a previous tag. 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-37830) API to remove an item from the queue
Title: Message Title Vivek Pandey started work on JENKINS-37830 Change By: Vivek Pandey 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-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37878 Implement a DisplayURLProvider for Blue Ocean Change By: James Dumay Sprint: 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37878 Implement a DisplayURLProvider for Blue Ocean Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/01 1:59 AM Priority: Minor Reporter: James Dumay The DisplayURLProvider is an extension point that allows alternative UIs (like Blue Ocean) to override the generation of URLs that are used in notifications. In Scope Create our own BlueDisplayURLProvider implementation Override all the methods and do the right thing to generate frontend URLs getTestUrl() should point to the test tab on the run modal (unlike classic we can't link to a specific test case, so the test tab will do for now) Add Comment
[JIRA] (JENKINS-37877) Permission and role checks for run, re-run and stop buttons
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37877 Permission and role checks for run, re-run and stop buttons Issue Type: Task Assignee: Cliff Meyers Components: blueocean-plugin Created: 2016/Sep/01 1:54 AM Priority: Minor Reporter: James Dumay In Scope Ensure that all the run, re-run and stop buttons are visible only when the current user can use those actions Add Comment
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Justin Massey commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Is there any plan to fix this? I am trying to modify the maximum upload size https://github.com/jenkinsci/checkmarx-plugin/blob/master/src/main/java/com/checkmarx/jenkins/CxConfig.java#L27. However, with the bug which breaks the ability to authenticate to Jenkins, I am unable to change this on the most up to date commit. I will revert to the commit before this was broken and modify the upload size. 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-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Vivek Pandey updated JENKINS-37837 Jenkins / JENKINS-37837 Regression: JWT token not present when logged in on blueocean.io 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-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title
Vivek Pandey commented on JENKINS-37837
Re: Regression: JWT token not present when logged in on blueocean.io
As mentioned above, the main issue was setting JWT specific Authentication object was not liked by github auth plugin, GithubRequireOrganizationMembershipACL.hasPermission(Permission) had:
if (a != null && a instanceof GithubAuthenticationToken) {
if (!a.isAuthenticated())
return false;
}else{
return false;
}
While gthub auth plugin is ok to have such uses, and there might be other plugins that might enforce using their own Authentication implementation. For this reason, this fix changed how Authentication instance is created and set on SecurityContext. We define JwtAuthenticationStoreFactory extension point and JwtAuthenticationStore abstraction to store Authentication in jwt token and also to re-create Authentication instance using jwt claims. There is default implementation that use in memory map to store authentication implementation. PR is in https://github.com/jenkinsci/blueocean-plugin/pull/457
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-37841) REGRESSION: unable to open log due to missing JWT token
Title: Message Title Ivan Meredith started work on JENKINS-37841 Change By: Ivan Meredith 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-37859) JWT failure when client and server (running on different machines) clocks not in sync
Title: Message Title Ivan Meredith updated JENKINS-37859 Jenkins / JENKINS-37859 JWT failure when client and server (running on different machines) clocks not in sync Change By: Ivan Meredith 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-37838) REGRESSION: Unable to open any pipelines in safari
Title: Message Title Ivan Meredith resolved as Fixed Jenkins / JENKINS-37838 REGRESSION: Unable to open any pipelines in safari Change By: Ivan Meredith Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37876) Notify user of JWT clock skew
Title: Message Title Ivan Meredith updated an issue Jenkins / JENKINS-37876 Notify user of JWT clock skew Change By: Ivan Meredith Summary: Notify user of JWT clock scew skew 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-37876) Notify user of JWT clock scew
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-37876 Notify user of JWT clock scew Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/01 12:16 AM Priority: Minor Reporter: Ivan Meredith Need to catch NotBeforeError and notify user. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37859) JWT failure when client and server (running on different machines) clocks not in sync
Title: Message Title Ivan Meredith started work on JENKINS-37859 Change By: Ivan Meredith 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-37236) Unable to negotiate
Title: Message Title Ben Walding commented on JENKINS-37236 Re: Unable to negotiate Some background on why this is now causing issues: http://www.openssh.com/legacy.html https://weakdh.org/ The diffie-hellman-group1-sha1 is insecure and considered "within range" of the LogJam attack. I can confirm this error is a problem on modern OSX machines (using Brew SSH) - as Brew installs OpenSSH v7+ # El Capitan + Brew $ /usr/local/bin/ssh -V OpenSSH_7.3p1, OpenSSL 1.0.2h 3 May 2016 # El Capitan $ /usr/bin/ssh -V OpenSSH_6.9p1, LibreSSL 2.1.8 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-37838) REGRESSION: Unable to open any pipelines in safari
Title: Message Title Michael Neale started work on JENKINS-37838 Change By: Michael Neale 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-37859) JWT failure when client and server (running on different machines) clocks not in sync
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-37859 JWT failure when client and server (running on different machines) clocks not in sync Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37859) JWT failure when client and server (running on different machines) clocks not in sync
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37859 JWT failure when client and server (running on different machines) clocks not in sync Change By: Michael Neale Priority: Critical Blocker 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-37873) HAL self href to queue item returned from "start build" API is not properly encoded
Title: Message Title Michael Neale commented on JENKINS-37873 Re: HAL self href to queue item returned from "start build" API is not properly encoded Vivek Pandey yes regression likely - or maybe this was never used for queue (more likely). Cliff Meyers is this blocking things for a beta? 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-37873) HAL self href to queue item returned from "start build" API is not properly encoded
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37873 HAL self href to queue item returned from "start build" API is not properly encoded Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36799) Failing to set string parameter from groovy script
Title: Message Title ikedam resolved as Incomplete No response from the reporter for a month. Reopen the ticket when you report more details. Jenkins / JENKINS-36799 Failing to set string parameter from groovy script Change By: ikedam Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-37713) Support reading Vault Token from file on disk
Title: Message Title Peter Tierno updated an issue Jenkins / JENKINS-37713 Support reading Vault Token from file on disk Change By: Peter Tierno Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Richard Lee edited a comment on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Same problem. The ` {quote} myImage.pull()docker.image(myImage.imageName()).inside() ` {quote} workaround for ` {quote} myImage.inside() ` {quote} seems to get around the bug, tho.
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-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Richard Lee edited a comment on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Same problem. The {{ ` myImage.pull()docker.image(myImage.imageName()).inside() }} ` workaround for {{ ` myImage.inside() }} ` seems to get around the bug, tho.
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-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Richard Lee edited a comment on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Same problem. The {{ myImage.pull()docker.image(myImage.imageName()).inside()}}workaround for {{ myImage.inside()}} seems to get around the bug, tho.
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-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Richard Lee commented on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Same problem. The {{ myImage.pull() docker.image(myImage.imageName()).inside() }} workaround for {{ myImage.inside() }} seems to get around the bug, tho.
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-37703) Copy entire tree containing jobs within nested CloudBees Folders
Title: Message Title ikedam commented on JENKINS-37703 Re: Copy entire tree containing jobs within nested CloudBees Folders Jobcopy doesn't copy contained jobs in a folder. I don't think you can do what you want, anyway. 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-37703) Copy entire tree containing jobs within nested CloudBees Folders
Title: Message Title ikedam assigned an issue to Andrew Gray Sounds like a permission issue. Please check the permission configuration (Manage Jenkins > Configure Global Security). Steps I tested (Windows 10 64bits, Java 1.8.0_101 Launch a new instance of Jenkins 2.19 Don't install plugins in SetupWizard Create an administrative user "admin" Install following plugins: Folders Plugin 5.12 Jobcopy Builder plugin 1.4.0 Create a folder "RHEL1.5" at the root of Jenkins. Create a folder "folder" at the root of Jenkins. Create a folder "subfolder" in "folder" (folder/subfolder) Create a freestyle project "copier" in "subfolder" (folder/subfolder/copier) Add "Copy Job" to "Build" From Job Name: /REL1.5 To Job Name: /REL2.0 Overwrite: unchecked Run "copier" The build fails with following message: Started by user admin Building in workspace C:\Users\ikedam\.jenkins\workspace\folder\subfolder\copier Copying /REL1.5 to /REL2.0 Error: Item '/REL1.5 'was not found. Build step 'Copy Job' marked build as failure Finished: FAILURE Install following plugins: Authorize Project 1.2.2 Go to Manage Jenkins > Configure Global Security Add "Per-project configurable Build Authorization" to "Access Controls for Builds" Configure "copier"
[JIRA] (JENKINS-37875) Absolute name for "Copy To" doesn't work
Title: Message Title ikedam created an issue Jenkins / JENKINS-37875 Absolute name for "Copy To" doesn't work Issue Type: Bug Assignee: ikedam Components: jobcopy-builder-plugin Created: 2016/Aug/31 10:54 PM Environment: jobcopy-builder 1.4.0 Priority: Minor Reporter: ikedam The job running jobcopy is "/folder/copier" To Job is "/dest" Result: "/folder/dest" is created. Workaround: Configure To Job to "../dest" Add Comment
[JIRA] (JENKINS-37873) HAL self href to queue item returned from "start build" API is not properly encoded
Title: Message Title Vivek Pandey commented on JENKINS-37873 Re: HAL self href to queue item returned from "start build" API is not properly encoded Cliff Meyers I remember this was fixed sometime back, is this regression? 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-37601) After build is queued the URL to the modal is incorrect
Title: Message Title James Dumay commented on JENKINS-37601 Re: After build is queued the URL to the modal is incorrect Thorsten Scherler if you can't reproduce this or think it is fixed, please close this ticket 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Code changed in jenkins User: Boguslaw Klimas Path: pom.xml src/findbugs/excludesFilter.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapperFactory.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/UnsupportedJobType.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/9b1243d06a5af91494417c8cd697d14af4669bf7 Log: Merge pull request #36 from jenkinsci/feature/JENKINS-34876 Feature/jenkins 34876 Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/f047198dda1e...9b1243d06a5a 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
[JIRA] (JENKINS-37666) Proceeding step is sometimes erroneously expanded
Title: Message Title Thorsten Scherler started work on JENKINS-37666 Change By: Thorsten Scherler 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-35847) Developer should see a condensed version of the change summary
Title: Message Title Thorsten Scherler updated JENKINS-35847 Jenkins / JENKINS-35847 Developer should see a condensed version of the change summary Change By: Thorsten Scherler 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-35847) Developer should see a condensed version of the change summary
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35847 Re: Developer should see a condensed version of the change summary Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/d8528c200f68632e75b77a016541a0975c29df8b Log: JENKINS-35847 Refactor gitCommit to return a promise. Add tests for notSet, condensed and notCondensed for a.authors 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Boguslaw Klimas updated JENKINS-34876 Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Boguslaw Klimas 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/b9c7ef390108df624f14c88a45b0be5156ebfe86 Log: JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractProjectJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages.properties src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/Messages_pl.properties http://jenkins-ci.org/commit/git-parameter-plugin/5fc8a95ef5d23d704ca4e60ff668671be924ee20 Log: JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM 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-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Ben Hawkins commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after pre-release build steps of release-plugin
Title: Message Title Christian Lipphardt commented on JENKINS-37871 Re: Credentials-binding plugin is executed after pre-release build steps of release-plugin Created https://github.com/jenkinsci/credentials-binding-plugin/pull/21 as 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-37871) Credentials-binding plugin is executed after pre-release build steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after pre-release build steps of release-plugin Change By: Christian Lipphardt Summary: Credentials-binding plugin is executed after prebuild pre-release build steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduce* Inject a secret through the credentials-binding plugin* Enable 'configure a release' build wrapper* Configure the release-plugin with a pre-release shell step, which echoes the injected secret to build log* Create a normal shell build step which echoes the injected secret to build logSee [^trigger-release-build.txt] for an output of the above steps.You see that the injected secret is not available in the pre-release step of the release-plugin buildwrapper, but it is in the normal build step.h5. Expected behaviorAs a user, I can inject the credentials and use them with the prebuild pre-release steps of the release-plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduce * Inject a secret through the credentials-binding plugin * Enable 'configure a release' build wrapper * Configure the release-plugin with a pre-release shell step, which echoes the injected secret to build log* Create a normal shell build step which echoes the injected secret to build logSee [^trigger-release-build.txt] for an output of the above steps.You see that the injected secret is not available in the pre-release step of the release-plugin buildwrapper, but it is in the normal build step. h5. Expected behaviorAs a user, I can inject the credentials and use them with the prebuild steps of the release - plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Attachment: trigger-release-build.txt 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-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduceh5. Expected behaviour behavior As a user, I can inject the credentials and use them with the prebuild steps of the release plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37874) Jenkins does not print warnings if it does not reach COMPLETED initialization state on startup or reloading
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-37874 Jenkins does not print warnings if it does not reach COMPLETED initialization state on startup or reloading Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Aug/31 9:49 PM Priority: Major Reporter: Oleg Nenashev It's a follow-up to JENKINS-37759. Diagnostics should be improved Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37874) Jenkins does not print warnings if it does not reach COMPLETED initialization state on startup or reloading
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37874 Jenkins does not print warnings if it does not reach COMPLETED initialization state on startup or reloading Change By: Oleg Nenashev It's a follow-up to JENKINS-37759. Diagnostics should be improved . I consider it is a bug due to the significant impact. We may need backporting to 2.19.x Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37425) Run behaviour does not work as designed
Title: Message Title Cliff Meyers started work on JENKINS-37425 Change By: Cliff Meyers 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-37873) HAL self href to queue item returned from "start build" API is not properly encoded
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-37873
HAL self href to queue item returned from "start build" API is not properly encoded
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Aug/31 9:45 PM
Priority:
Blocker
Reporter:
Cliff Meyers
The HAL href to a multi-branch queue item is not properly encoding the branch name portion of the URL. Given the following request:
URL: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/jdl1/branches/experiment%252Fbuild-locally-docker/runs/
Method: PUT
Headers:
Accept:*/*
Accept-Encoding:gzip, deflate, sdch
Accept-Language:en-US,en;q=0.8
authorization:Bearer *snipped*
Cache-Control:no-cache
Connection:keep-alive
Content-Length:0
content-type:application/json
Host:localhost:8080
Origin:http://localhost:8080
Pragma:no-cache
Referer:http://localhost:8080/jenkins/blue/organizations/jenkins/jdl1/branches
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
This is the response:
{
"_class": "io.jenkins.blueocean.service.embedded.rest.QueueItemImpl",
"_links": {
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/jdl1/pipelines/experiment%2Fbuild-locally-docker/queue/44/"
}
},
"expectedBuildNumber": 48,
"id": "44",
"organization": "jenkins",
"pipeline":
[JIRA] (JENKINS-37733) Add support for manual sorting of pipeline components in DPP
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-37733 Add support for manual sorting of pipeline components in DPP Change By: Tommy Tynjä Status: Open Resolved Assignee: Patrik Boström Suresh Kumar 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-37734) Repeatable delete button is not aligned properly in component configuration and regex configuration page
Title: Message Title Tommy Tynjä commented on JENKINS-37734 Re: Repeatable delete button is not aligned properly in component configuration and regex configuration page Merged: 3d738caca6a85089758d6d0d67147f1f0c829f51 Will be part of next release. 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-37734) Repeatable delete button is not aligned properly in component configuration and regex configuration page
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-37734 Repeatable delete button is not aligned properly in component configuration and regex configuration page Change By: Tommy Tynjä Status: Open Resolved Assignee: Patrik Boström Suresh Kumar 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-37733) Add support for manual sorting of pipeline components in DPP
Title: Message Title Tommy Tynjä commented on JENKINS-37733 Re: Add support for manual sorting of pipeline components in DPP Merged: 3d738caca6a85089758d6d0d67147f1f0c829f51 Will be part of next release. 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-36330) Make It possible to limit number of jobs in a view
Title: Message Title Tommy Tynjä commented on JENKINS-36330 Re: Make It possible to limit number of jobs in a view Merged: https://github.com/Diabol/delivery-pipeline-plugin/commit/2f01d75ba12f8581c9bbdf8037387ed87894c390 Will be part of next release. 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-36330) Make It possible to limit number of jobs in a view
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-36330 Make It possible to limit number of jobs in a view Change By: Tommy Tynjä Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37872) WorkflowRun should have getCulprits()
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37872 WorkflowRun should have getCulprits() Issue Type: Improvement Assignee: Andrew Bayer Components: workflow-job-plugin Created: 2016/Aug/31 9:18 PM Priority: Minor Reporter: Andrew Bayer It'd be handy for WorkflowRun to have getCulprits() like AbstractBuild. It'd be almost the exact same logic - admittedly, it'd potentially apply across a lot more repos than your normal Freestyle build, but I don't see that as a problem. This would enable a lot of functionality in email-ext, the mail step, etc... Add Comment
[JIRA] (JENKINS-37871) Credentials binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Summary: Credentials binding plugin is executed after Release Wrapper prebuild steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Summary: Credentials - binding plugin is executed after prebuild steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials binding plugin is executed after Release Wrapper
Title: Message Title Christian Lipphardt created an issue Jenkins / JENKINS-37871 Credentials binding plugin is executed after Release Wrapper Issue Type: Bug Assignee: Jesse Glick Components: credentials-binding-plugin Created: 2016/Aug/31 9:04 PM Environment: Jenkins 1.609.3 release-plugin:2.5.4 credentials-binding-plugin:1.9 Priority: Minor Reporter: Christian Lipphardt Problem Injecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it. Expected behaviour As a user, I can inject the credentials and use them with the prebuild steps of the release plugin. Add Comment
[JIRA] (JENKINS-37870) Pipeline "mail" step should have optional defaults for subject/body like traditional mailer
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37870 Pipeline "mail" step should have optional defaults for subject/body like traditional mailer Issue Type: New Feature Assignee: Andrew Bayer Components: workflow-basic-steps-plugin Created: 2016/Aug/31 9:03 PM Priority: Minor Reporter: Andrew Bayer We've already got default logic for subject/body in the mailer plugin - these same defaults should be available as options for the "mail" step. Add Comment This message was
[JIRA] (JENKINS-37869) Pipeline "mail" step should have flags for common notification recipients
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37869 Pipeline "mail" step should have flags for common notification recipients Issue Type: New Feature Assignee: Andrew Bayer Components: workflow-basic-steps-plugin Created: 2016/Aug/31 9:00 PM Priority: Minor Reporter: Andrew Bayer i.e., culprits, developers, etc. emailext requires a node context (so that it can do stuff with attachments etc) so I'd prefer to add some functionality to mail rather than have to use emailext everywhere... Add Comment
[JIRA] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title Ryan Wallner reopened an issue Jenkins / JENKINS-32914 Unable to locate docker daemon !!! Change By: Ryan Wallner Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title Ryan Wallner commented on JENKINS-32914 Re: Unable to locate docker daemon !!! seeing this as well, but my jenkins logs into the slave as centos and there is no jenkins user. Adding centos to the docker group didnt have any affect. 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-32914) Unable to locate docker daemon !!!
Title: Message Title Ryan Wallner edited a comment on JENKINS-32914 Re: Unable to locate docker daemon !!! seeing this as well, but my jenkins logs into the slave as centos and there is no jenkins user. Adding centos to the docker group didnt have any affect. Jenkins 2.7.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37868) P4 plugin fails to unshelve exclusive lock branch / add file revisions
Title: Message Title stuart rowe created an issue Jenkins / JENKINS-37868 P4 plugin fails to unshelve exclusive lock branch / add file revisions Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Aug/31 8:18 PM Priority: Minor Reporter: stuart rowe In the case of branch or add file revisions, the target file doesn't yet exist on the local workspace. It must be created as a new file and potentially it's parent directory must also be created. Add Comment This message was
[JIRA] (JENKINS-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Vivek Pandey commented on JENKINS-37837 Re: Regression: JWT token not present when logged in on blueocean.io Update: 403 error gone. It needed encoding granted authorizations in the token and putting them together back as JWT specific Authentication object. This was suggested by Kohsuke Kawaguchi in code review few days back for different reason, that is performance and was marked as TODO. However Jenkins.getACL().hasPermission(...) fails because github plugin looking for it's own authentication object and when it detects the given authentication is not known it returns null. So this is still an issue. Problem is plugging in JWT specific ACL, but this is on Jenkins singleton. I am going to check with Kohsuke Kawaguchi on what possibly can be done here. 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-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Harsha B created an issue Jenkins / JENKINS-37867 Adding “Perform Maven Release” option from Jenkinsfile Issue Type: Bug Assignee: Jesse Glick Components: pipeline-build-step-plugin Created: 2016/Aug/31 7:50 PM Priority: Critical Reporter: Harsha B Is there a way to make the Perform Maven Release option visible under the job created using Jenkinsfile? I have a job that is created manually and it has this option set by selecting the Maven release build option in Configure job->Build environment settings. I am trying to convert this manual job to pipeline job using Jenkinsfile. Add Comment
[JIRA] (JENKINS-37677) Handle jobs in Multibranch projects where git branches have special characters
Title: Message Title Matthew DeTullio resolved as Duplicate Jenkins / JENKINS-37677 Handle jobs in Multibranch projects where git branches have special characters Change By: Matthew DeTullio 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-37360) Selecting "edit description" for View All shows the System Message HTML text and tags.
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-37360 Selecting "edit description" for View All shows the System Message HTML text and tags. Change By: Daniel Beck Labels: configuration jenkins lts-candidate user-experience 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-36748) Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-36748 Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException Change By: Daniel Beck Labels: lts-candidate 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-29956) Wipe out repository & force clone ignore's Windows directory junctions
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29956 Wipe out repository & force clone ignore's Windows directory junctions Change By: Daniel Beck Labels: FileSystem jenkins lts-candidate windows 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-33374) Setup wizard not properly offering the restart button
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33374 Setup wizard not properly offering the restart button Change By: Daniel Beck Labels: lts-candidate 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-37757) NPE on XStream serialization
Title: Message Title Antonio Muñiz commented on JENKINS-37757 Re: NPE on XStream serialization Yes: java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at com.thoughtworks.xstream.converters.reflection.ExternalizableConverter.canConvert(ExternalizableConverter.java:73) at com.thoughtworks.xstream.core.DefaultConverterLookup.registerConverter(DefaultConverterLookup.java:74) at com.thoughtworks.xstream.XStream$2.registerConverter(XStream.java:502) ... This is after a XStream constructor call, in one of the registerConverter call in the construction chain. 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-37866) The plugin spams Github API
Title: Message Title emanuelez updated an issue Jenkins / JENKINS-37866 The plugin spams Github API Change By: emanuelez The plugin makes a vast amount of API calls to Github that results in reaching the hourly quota of the user several times a day. Here's a breakdown of the calls performed in an hour :/repositories/:repository_id/contents/?*2,557 54.648% /repositories/:repository_id/collaborators 1,038 22.184% /repositories/:repository_id/pulls/:id 177 3.783% /repositories/:repository_id163 3.484% /repositories/:repository_id/git/refs/* 157 3.355% /repositories/:repository_id/statuses/:sha 111 2.372% /repositories/:repository_id/branches 104 2.223% 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-37866) The plugin spams Github API
Title: Message Title emanuelez created an issue Jenkins / JENKINS-37866 The plugin spams Github API Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Aug/31 6:39 PM Priority: Major Reporter: emanuelez The plugin makes a vast amount of API calls to Github that results in reaching the hourly quota of the user several times a day. Here's a breakdown of the calls performed: /repositories/:repository_id/contents/?* 2,557 54.648% /repositories/:repository_id/collaborators 1,038 22.184% /repositories/:repository_id/pulls/:id 177 3.783% /repositories/:repository_id 163 3.484% /repositories/:repository_id/git/refs/* 157 3.355% /repositories/:repository_id/statuses/:sha 111 2.372% /repositories/:repository_id/branches 104 2.223% Add Comment
[JIRA] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick commented on JENKINS-37769 Re: Too long stop docker container(default docker stop timeout=10s) If stop is hitting the default 10s timeout, something deeper is wrong. I doubt that simply passing --time 0 is correcting that. 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-37865) MailerPluginTest can timeout in some environments
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-37865 MailerPluginTest can timeout in some environments Issue Type: Bug Assignee: Scott Hebert Components: acceptance-test-harness Created: 2016/Aug/31 5:55 PM Priority: Minor Reporter: Scott Hebert The timeout for MailerPluginTest#send_test_mail is only 10 secs. This may not be enough in some environments. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-28466 Re: Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked Yes, the workaround by [~javiplx] works and its great. I also tend to disagree with [~danielbeck] that setting BUILD_URL to http://localhost:8080 is useless! It is causing issues and fails my jobs that are trying to use a null BUILD_URL. If http:// loclahost localhost :8080 is what appear in the global configuration it should be reflected in a corresponding env variable. However, I do admit that mine is a special case. A quick setup of a Jenkins environment for demo purposes. In my case the less configuration the better. This would not be my production environment where a real URL would appear for Jenkisn_URL. By the way, I think that my use case is very similar to that of Javier althought for totally differnt end goals. Best regards to all for the useful discussion and workaround suggestion! 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-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title Ioannis Moutsatsos commented on JENKINS-28466 Re: Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked Yes, the workaround by Javier Palacios works and its great. I also tend to disagree with Daniel Beck that setting BUILD_URL to http://localhost:8080 is useless! It is causing issues and fails my jobs that are trying to use a null BUILD_URL. If http://loclahost:8080 is what appear in the global configuration it should be reflected in a corresponding env variable. However, I do admit that mine is a special case. A quick setup of a Jenkins environment for demo purposes. In my case the less configuration the better. This would not be my production environment where a real URL would appear for Jenkisn_URL. Best regards to all for the useful discussion and workaround suggestion! 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-37864) Provide some mechanism for looking up whether credentials exist in Pipeline
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-37864
Provide some mechanism for looking up whether credentials exist in Pipeline
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
credentials-binding-plugin
Created:
2016/Aug/31 5:24 PM
Priority:
Minor
Reporter:
R. Tyler Croy
In my use-case, I need to use the same Jenkinsfile on multiple Jenkins instances. The only differentiation between the two are the credentials which are available for use. (Basically, one instance is authorized for deployments, thus the credentials, the other is not). My ideal would be a credentials global variable, or something like that, which could have utility methods like this. E.g.
node {
if (credentials.lookup('some-credentials-id')) {
withCredentials('some-credentials-id') {
sh './deploy.sh'
}
}
}
Related to JENKINS-37863
Add Comment
[JIRA] (JENKINS-37658) Github-branch-source plugin should support git plugin extensions
Title: Message Title Jesse Glick commented on JENKINS-37658 Re: Github-branch-source plugin should support git plugin extensions At the same time, should support selection of a browser and a tool. 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-37761) case in spelling of jobname doesn't matter on downloadign using wget
Title: Message Title
Daniel Beck commented on JENKINS-37761
Re: case in spelling of jobname doesn't matter on downloadign using wget
After all Jenkins decided to restrict to this one, so it should do this consistently.
The behavior is identical to what Windows file systems do, and internally consistent. It's case-insensitive ("does not care about letter case"), but case-preserving. Lookup of FOO, foo, and Foo succeeding and returning the same item is the corollary to not being able to create Foo and foo independently.
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-37863) sshagent step doesn't error if the credentials named do not exist
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-37863
sshagent step doesn't error if the credentials named do not exist
Issue Type:
Bug
Assignee:
Unassigned
Components:
ssh-agent-plugin
Created:
2016/Aug/31 5:17 PM
Priority:
Minor
Reporter:
R. Tyler Croy
In my Pipeline script, I name credentials for the sshagent step, but when those credentials do not exist, no error happens.
node {
sshagent(credentials: ['some-nonexistent-id']) {
sh 'script-which-needs-ssh-credentials.sh'
}
}
I would have expected a typed exception (e.g. CredentialsUnavailableException) to be thrown, instead the closure happily continues and invokes the script which required the credentials
Add Comment
