[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP The UnprotectedRootAction is verifying that the Host header is set to the second domain, right? Yes, only responds with 404s on not-the-second-domain (while a filter responds with 404 on everything not accessing the action on the second domain). That works and didn't seem notable. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178741.1486645144000.7053.1569649620269%40Atlassian.JIRA.
[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage
Title: Message Title runze xia updated JENKINS-47591 Jenkins / JENKINS-47591 Allow each Kubernetes slave pod to use unique Persistent Volume / Storage Change By: runze xia Status: In Review Resolved Resolution: Fixed Released As: v1.19.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186064.1508775809000.7044.1569646980788%40Atlassian.JIRA.
[JIRA] (JENKINS-59293) Test Result Column Does not Work on Folders
Title: Message Title Fred G commented on JENKINS-59293 Re: Test Result Column Does not Work on Folders Is this something that has to be fixed in the extra column plugin or has the folders plugin provide the aggregated test results? Yes, this would need to be fixed in the extra columns plugin. I have one concern: depending on the number of jobs in a folder, calculating the aggregated test results could lead to performance issues. So this should be tested extensively. Due to time constraints I won't be able to work on this in the near future, but I'd happily accept and review pull requests. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201837.1568104556000.7034.1569628980091%40Atlassian.JIRA.
[JIRA] (JENKINS-57141) Multiple Build Duration Columns resets values when returning to Edit View
Title: Message Title Fred G updated JENKINS-57141 Fixed in version 1.21. Jenkins / JENKINS-57141 Multiple Build Duration Columns resets values when returning to Edit View Change By: Fred G Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-51171) Use Regex to filter for an Buildparameter
Title: Message Title Fred G started work on JENKINS-51171 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190479.1525682766000.7027.1569627720315%40Atlassian.JIRA.
[JIRA] (JENKINS-51171) Use Regex to filter for an Buildparameter
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21. Jenkins / JENKINS-51171 Use Regex to filter for an Buildparameter Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-43605) ability to specify parameters to show and parameters to exclude for a view
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding regex filters to the configuration of the build parameter column. Jenkins / JENKINS-43605 ability to specify parameters to show and parameters to exclude for a view Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-43605) ability to specify parameters to show and parameters to exclude for a view
Title: Message Title Fred G started work on JENKINS-43605 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180930.1492189451000.7023.1569627540163%40Atlassian.JIRA.
[JIRA] (JENKINS-20953) Suggestion: "Last Build Time" column
Title: Message Title Fred G started work on JENKINS-20953 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152475.1386742549000.7013.1569627420979%40Atlassian.JIRA.
[JIRA] (JENKINS-20953) Suggestion: "Last Build Time" column
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-20953 Suggestion: "Last Build Time" column Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-29655) Last build
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-29655 Last build Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-29655) Last build
Title: Message Title Fred G started work on JENKINS-29655 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164134.1438009468000.7003.1569627300230%40Atlassian.JIRA.
[JIRA] (JENKINS-54567) Last deployed/published/finished column
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-54567 Last deployed/published/finished column Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-54567) Last deployed/published/finished column
Title: Message Title Fred G started work on JENKINS-54567 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195346.1541871979000.6999.1569627120177%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Jesse Glick updated JENKINS-56809 Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.198 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198459.1553858983000.6955.1569619320218%40Atlassian.JIRA.
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title red der updated an issue Jenkins / JENKINS-59567 Server Credentials created from Jenkins credentials don't show up in maven settings.xml I linked the wrong ticket to this. This is a different issue than the one described in the ticket I linked initially Change By: red der Summary: Server Credentials created from Jenkins credentials don't show up in maven settings.xml (regression) Looks like pretty much this same issue: https://issues.jenkins-ci.org/browse/JENKINS-29805 Also on SO: [https://stackoverflow.com/questions/58139761/pipeline-maven-plugin-not-replacing-servers-in-global-settings-xml-from-jenkin]hard coding "" in the config file works but configuring "Server Credentials" from jenkins credentials is not working. I tried with and without "Replace all" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59567) Credentials don't show up in maven settings.xml (regression)
Title: Message Title red der created an issue Jenkins / JENKINS-59567 Credentials don't show up in maven settings.xml (regression) Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin, pipeline-maven-plugin Created: 2019-09-27 21:15 Environment: config-file-provider-plugin 3.5 pipeline-maven-plugin 3.8.1 credentials-plugin 2.1.19 Priority: Blocker Reporter: red der Looks like pretty much this same issue: https://issues.jenkins-ci.org/browse/JENKINS-29805 Also on SO: https://stackoverflow.com/questions/58139761/pipeline-maven-plugin-not-replacing-servers-in-global-settings-xml-from-jenkin hard coding "" in the config file works but configuring "Server Credentials" from jenkins credentials is not working. I tried with and without "Replace all" Add Comment
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Guillaume DeMengin commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. this issue might be fixed in the GUI ... but it still exists for 2 uses cases in which variant information is not available anymore and makes some parts of the logs unusable: when logs are accessed programmatically (using currentBuild.rawBuild.log for example) when logs are accessed through the /consoleText link (to import the logs in a log gatherer for example) for those 2 uses cases this workaround might help: https://github.com/gdemengin/pipeline-logparser (implementation of https://stackoverflow.com/a/57351397/8380249) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.6935.1569618300458%40Atlassian.JIRA.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title red der edited a comment on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline this issue is back. Im on version [3.8.1,|https://jenkins3.bommie.co/teams-bombora/pluginManager/plugin/pipeline-maven/thirdPartyLicenses]hard coding server setting in the settings file works but using a username and password to replace does not work [https://stackoverflow.com/questions/58139761/pipeline-maven-plugin-not-replacing-servers-in-global-settings-xml-from-jenkin] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196414.1545726603000.6932.1569617640153%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Jesse Glick commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP Do we need a guarantee around the expiration of URLs here to limit potential problems? I would think all table entries should be time-limited. Not sure I followed every detail above, particularly the usage of Stapler.invoke, but it sounds right. The UnprotectedRootAction is verifying that the Host header is set to the second domain, right? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178741.1486645144000.6924.1569614700226%40Atlassian.JIRA.
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title Derek Ellis commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set matt matthews I downloaded the prior version of the plugin from the download site here: https://updates.jenkins-ci.org/download/plugins/ec2/ Them I uninstalled the EC2 plugin, restarted Jenkins, and then manually installed the plugin via Plugin UI (see upload plugin in the advanced tab). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202173.1569501392000.6917.1569613800258%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Steve Boardwell commented on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating Liam Newman, I would love to help, just not sure when I will be able to get around to it. I think now that it might, in fact, be a problem with the job-dsl-plugin itself (looking at my last comment). Let me have a look over the next few days and get back to you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.6914.1569608700178%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman commented on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating Steve Boardwell Seem like we should have some JobDSL tests as part of this plugin's build. Would you be willing to make some? This is likely the only way to avoid (or at least be aware of) future breaking changes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.6912.1569608280143%40Atlassian.JIRA.
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title red der edited a comment on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline this issue is back. Im on version [3.8.1,|https://jenkins3.bommie.co/teams-bombora/pluginManager/plugin/pipeline-maven/thirdPartyLicenses]hard coding server setting in the settings file works but using a username and password to replace does not work Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196414.1545726603000.6910.1569607740507%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck started work on JENKINS-41891 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178741.1486645144000.6903.1569607620241%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title
Daniel Beck commented on JENKINS-41891
Re: Serve static files from second domain as an alternative to setting CSP
Alternatively, I may be able to use this mechanism to write the actual response.
This is what I'm currently doing and it seems to work pretty well. It even means we don't need the option discussed above, as we can always perform a "live" permission check an arbitrarily long suffix of the pathInfo. (We start after the last AccessControlled). DBS register themselves as soon as generateResponse is called (which seems safer than the constructor, as it's actual "time of use" rather than an object that could still be passed around), if we're not responding to a request on the second/resource domain, with…
the full URL (except for the file path within the DBS),
the nearest ancestor AccessControlled,
the restOfPath,
and the Authentication.name
…stored in a ResourceHolder wrapper object in a per-session map keyed by the URL (again with any file path within the DBS removed). If an equivalent ResourceHolder already exists for the URL key – and we compare object identity of the AccessControlled, it's reused, else a new one is added. Then whatever we got from that is added, if necessary, to a global list from UUID to ResourceHolder (WeakReference to that, actually, so hopefully reaping the sessions will remove obsolete {{ResourceHolder}}s but so far untested) which is what allows the request routing to work. If a request arrives at the UnprotectedRootAction, we look up the ResourceHolder corresponding to the UUID, map the actually requested URL (with file path) to the corresponding restOfPath + filePath , and call Stapler#invoke(req, rsp, accessControlled, restOfPathPlusFilePath) as Authorization.name. That just writes the file into the response. The underlying assumption here is that the AccessControlled will implement a StaplerProxy style permission check, or the restOfPath contains enough permission checks – for a job workspace, we'd start routing at the job, go through its getTarget permission check, call doWs (with a more specific permission check) and let that handle the response. To make sure requests go to the UnprotectedRootAction, a DBS holds an identifier (the UUID but can be anything) after successful registration. If it comes to serving a single file, the second/resource domain is configured, and we're not on the second/resource domain, we serve an HTTP 302 redirect to the corresponding URL over there. Otherwise, we serve the file directly, with CSP headers. A few things left to figure out:
The global list grows unbounded with no cleanup. It maps UUID to WeakReference – unsure how much of a problem that is.
The per-session lists are built the same way (AFAICT) as BoundObjectTable with strong references in a session attribute, but I haven't seen this get cleaned up yet. Time to #doSimulateOutOfMemory and see what happens…
Weird
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Larry West updated an issue Jenkins / JENKINS-43820 Stage name must be a string literal Change By: Larry West Comment: [~abayer] - a "design decision" that neither satisfies the customer nor addresses some inherent constraint is indistinguishable from a design flaw.Please have someone else in your organization – who is not invested in this "design decision" – re-evaluate this.Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.6895.1569607441460%40Atlassian.JIRA.
[JIRA] (JENKINS-59566) Automatically label Scientific Linux agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59566
Automatically label Scientific Linux agents
Change By:
Mark Waite
Automatically label Scientific Linux agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of Scientific Linux.Refer to [pull request 98|https://github.com/jenkinsci/platformlabeler-plugin/pull/98] for an example of the files to modify.Refer to [generate_lsb_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_lsb_release_output.sh]. and [generate_os_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_os_release_output.sh] for instructions to create the data files used to test operating system version reporting. Refer to the Scientific Linux docker image on [hub.docker.com|https://hub.docker.com/r/scientificlinux/sl/tags].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59566) Automatically label Scientific Linux agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59566
Automatically label Scientific Linux agents
Change By:
Mark Waite
Automatically label Red Hat Enterprise Scientific Linux agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of Red Hat Enterprise Scientific Linux.Refer to [pull request 98|https://github.com/jenkinsci/platformlabeler-plugin/pull/98] for an example of the files to modify.Refer to [generate_lsb_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_lsb_release_output.sh]. and [generate_os_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_os_release_output.sh] for instructions to create the data files used to test operating system version reporting. Refer to the docker image on [hub.docker.com|https://hub.docker.com/r/scientificlinux/sl/tags].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59566) Automatically label Scientific Linux agents
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59566 Automatically label Scientific Linux agents Issue Type: Improvement Assignee: Unassigned Components: platformlabeler-plugin Created: 2019-09-27 17:19 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite Automatically label Red Hat Enterprise Linux agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of lsb_release -a in the test suite so that others can confirm the label operates as expected without installing their own copy of Red Hat Enterprise Linux. Refer to pull request 98 for an example of the files to modify. Refer to generate_lsb_release_output.sh. and generate_os_release_output.sh for instructions to create the data files used to test operating system version reporting. Add Comment
[JIRA] (JENKINS-59565) Automatically label Linux Mint agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59565
Automatically label Linux Mint agents
Change By:
Mark Waite
Automatically label [ SUSE Linux (SUSE Linux Enterprise Server - SLES) Mint |https://www. suse linuxmint .com/ products/server/ ] agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of SUSE Linux Mint .Refer to [pull request 98|https://github.com/jenkinsci/platformlabeler-plugin/pull/98] for an example of the files to modify.Refer to [generate_lsb_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_lsb_release_output.sh]. and [generate_os_release_output.sh|https://github.com/jenkinsci/platformlabeler-plugin/blob/master/src/test/resources/org/jvnet/hudson/plugins/platformlabeler/generate_os_release_output.sh] for instructions to create the data files used to test operating system version reporting. A Linux Mint image is available on [hub.docker.com|https://hub.docker.com/u/linuxmintd].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59565) Automatically label Linux Mint agents
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59565 Automatically label Linux Mint agents Issue Type: Improvement Assignee: Unassigned Components: platformlabeler-plugin Created: 2019-09-27 17:13 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite Automatically label SUSE Linux (SUSE Linux Enterprise Server - SLES) agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of lsb_release -a in the test suite so that others can confirm the label operates as expected without installing their own copy of SUSE Linux. Refer to pull request 98 for an example of the files to modify. Refer to generate_lsb_release_output.sh. and generate_os_release_output.sh for instructions to create the data files used to test operating system version reporting. Add Comment
[JIRA] (JENKINS-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title red der commented on JENKINS-55325 Re: System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline this issue is back. Im on version 3.8.1, hard coding server setting in the settings file works but using a username and password to replace does not Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196414.1545726603000.6863.1569602700358%40Atlassian.JIRA.
[JIRA] (JENKINS-56834) Build permission on agents is not working
Title: Message Title Arindom Sarkar commented on JENKINS-56834 Re: Build permission on agents is not working Does anyone figured it out? How to resolve the issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198493.1554129738000.6853.1569602280292%40Atlassian.JIRA.
[JIRA] (JENKINS-59564) Network interfaces and an instance-level subnet ID may not be specified on the same request
Title: Message Title Jakub Bochenski commented on JENKINS-59564 Re: Network interfaces and an instance-level subnet ID may not be specified on the same request I'm guessing this might be related to https://issues.jenkins-ci.org/browse/JENKINS-58578 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202199.1569599527000.6850.1569599760152%40Atlassian.JIRA.
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title matt matthews commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set What's the fix? with a new . jenkins instance I have no option on the UI to downgrade. I tried manually installing but it does not work: ``` $java -jar /tmp/jenkins-cli.jar -s http://127.0.0.1:8080/ install-plugin https://updates.jenkins-ci.org/download/plugins/ec2/1.45/ec2.hpi Sep 27, 2019 3:51:31 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProvider INFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider Installing a plugin from https://updates.jenkins-ci.org/download/plugins/ec2/1.45/ec2.hpi ERROR: Unexpected exception occurred while performing install-plugin command. java.util.zip.ZipException: error in opening zip file ``` Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202173.1569501392000.6843.1569599640243%40Atlassian.JIRA.
[JIRA] (JENKINS-59564) Network interfaces and an instance-level subnet ID may not be specified on the same request
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-59564
Network interfaces and an instance-level subnet ID may not be specified on the same request
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-09-27 15:52
Environment:
ec2 plugin 1.46
Priority:
Critical
Reporter:
Jakub Bochenski
After upgrading to 1.46 the plugin can no longer spawn instances. I get the above error from AWS. This works correctly when I downgrade to 1.45. My plugin configuration is
final cloud = new AmazonEC2Cloud(
'ec2',
false,
'',
config.ec2_region,
config.ec2_ssh_key,
config.ec2_instance_cap,
[
new SlaveTemplate(
config.ec2_ami_id,
'',
null,
config.ec2_security_groups,
'/opt/jenkins',
InstanceType.fromValue(config.ec2_instance_type),
false,
config.ec2_label,
Node.Mode.NORMAL,
"ec2 (${config.ec2_ami_id})",
'',
'/tmp',
'''#!/bin/bash -xe
mkfs.ext4 /dev/nvme1n1
mkdir -p /opt/jenkins
mount /dev/nvme1n1 /opt/jenkins
chown -R admin:admin /opt/jenkins
service docker stop
mkdir -p /opt/jenkins/docker/lib
mv /var/lib/docker
[JIRA] (JENKINS-53500) Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed"
Title: Message Title
Vincent Latombe updated an issue
Jenkins / JENKINS-53500
Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed"
Change By:
Vincent Latombe
Pipeline execution fails consistently at the script execution step on Windows with this error: {code} [Pipeline] End of Pipelinejava.io.IOException: Pipe closed at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260) at java.io.PipedInputStream.receive(PipedInputStream.java:226) at java.io.PipedOutputStream.write(PipedOutputStream.java:149) at java.io.OutputStream.write(OutputStream.java:75) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.setupEnvironmentVariable(ContainerExecDecorator.java:402) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:364) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:449) at org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:84) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:93) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:86) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:182) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor1054.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:120) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at
[JIRA] (JENKINS-59562) Bug creating EC2 instance
Title: Message Title James Green commented on JENKINS-59562 Re: Bug creating EC2 instance Downgraded the plugin, we are back working now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202197.1569590952000.6832.1569596760288%40Atlassian.JIRA.
[JIRA] (JENKINS-59562) Bug creating EC2 instance
Title: Message Title James Green commented on JENKINS-59562 Re: Bug creating EC2 instance Our Jenkins instance is no longer able to launch any agents as a result of this. All ours are EC2 in a private subnet. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202197.1569590952000.6828.1569596280167%40Atlassian.JIRA.
[JIRA] (JENKINS-59563) Jenkins jobs disappear after Windows slave restart
Title: Message Title Parvathi S created an issue Jenkins / JENKINS-59563 Jenkins jobs disappear after Windows slave restart Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2019-09-27 14:46 Environment: Jenkins Production environment. Jenkins jobs disappear (Freestyle job with PowerShell plugin and parameters ) after Windows slave restart. Tried this... Check Jenkins logs for errors (Manage Jenkins/System Log) Fix the errors in config.xml of each job. ( path: JENKINS_HOME/jobs//config.xml) Restart jenkins or choose option reload configurations from disk (Manage Jenkins/Reload Configuration from Disk). Then had to recreate the job. Would you please tell me why did the job definition disappear? Is this a bug? Priority: Minor Reporter: Parvathi S Add Comment
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl commented on JENKINS-59542 Re: There is problem while I'm trying to give CIFS share builds in Jenkins Please don't assign the issue to me, I do not work on this plugin anymore. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.6821.1569595260265%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.6819.1569595260172%40Atlassian.JIRA.
[JIRA] (JENKINS-59562) Bug creating EC2 instance
Title: Message Title Raihaan Shouhell commented on JENKINS-59562 Re: Bug creating EC2 instance Thanks for the bug report! A pr has been made against this: https://github.com/jenkinsci/ec2-plugin/pull/402 You can test the incremental from here: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ec2/1.47-rc1054.16312ec8439f/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202197.1569590952000.6817.1569595020252%40Atlassian.JIRA.
[JIRA] (JENKINS-59359) Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min)
Title: Message Title Ulli Hafner started work on JENKINS-59359 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201910.1568378623000.6814.1569594420159%40Atlassian.JIRA.
[JIRA] (JENKINS-59562) Bug creating EC2 instance
Title: Message Title Alexander KIRILOV created an issue Jenkins / JENKINS-59562 Bug creating EC2 instance Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-09-27 13:29 Priority: Blocker Reporter: Alexander KIRILOV This is a Bug report: Plugin Version: ec2-1.46 Description: Since the new update the change in the following commit breaks the EC2 creation process: https://github.com/jenkinsci/ec2-plugin/commit/816203b6eae8ea41b035198c2a9cb7d79f0684b4 Lines 1000 - 1004 ``` .AmazonEC2Exception: Network interfaces and an instance-level subnet ID may not be specified on the same request (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination ``` How Reproduce: Create a new EC2 Template with Private IP and SubnetID Add Comment
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Sandeep Yadav commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Yes Anda Sorina Laakso we did try by taking the timeout after the last suggestion. That did not resolve it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.6779.1569590820212%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer updated JENKINS-59311 Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Change By: Christoph Fetzer Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.6777.1569589920206%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer updated JENKINS-59311 Was solved somewhere between V2.176.2 and v2.190.1. Relation to any plugin or module not clear. Solution is released. Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Change By: Christoph Fetzer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-59008) Merge before build, reference is not a tree on second build
Title: Message Title Mark Waite commented on JENKINS-59008 Re: Merge before build, reference is not a tree on second build No progress and none planned. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201360.1566299152000.6774.1569588180126%40Atlassian.JIRA.
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title Jan Heylen edited a comment on JENKINS-28119 Re: Link to log of failed step Is there already any way to get the link to 'blue/rest/organizations/jenkins/pipelines//runs//nodes//log/ from within a pipeline parallel node ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162432.1430162718000.6718.1569587403158%40Atlassian.JIRA.
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title Jan Heylen commented on JENKINS-28119 Re: Link to log of failed step Is there already any way to get the link to 'blue/rest/organizations/jenkins/pipelines//runs//nodes//log/ ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162432.1430162718000.6716.1569587403124%40Atlassian.JIRA.
[JIRA] (JENKINS-59561) MAC Machine: Keychain not Found to store error
Title: Message Title Mark Waite updated JENKINS-59561 Jenkins / JENKINS-59561 MAC Machine: Keychain not Found to store error Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202194.1569584258000.6660.1569587280415%40Atlassian.JIRA.
[JIRA] (JENKINS-59561) MAC Machine: Keychain not Found to store error
Title: Message Title Mark Waite updated JENKINS-59561 This is not a bug in either the git plugin or the git client plugin. Refer to superuser.com for suggestions on the configuration issue that may be causing the problem. Refer to stackoverflow also as a possible source of hints. Jenkins / JENKINS-59561 MAC Machine: Keychain not Found to store error Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Ulli Hafner commented on JENKINS-59558 Re: Hyperlink to result in project view not working What exactly is not working, can you please add some more details? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202191.1569578601000.6656.1569587160158%40Atlassian.JIRA.
[JIRA] (JENKINS-59427) Rename SSH Slaves Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59427 Rename SSH Slaves Plugin Change By: Oleg Nenashev Released As: ssh-slaves-1.27 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202010.1568797619000.6654.1569585961309%40Atlassian.JIRA.
[JIRA] (JENKINS-43610) Split Trilead out from Core
Title: Message Title Jesse Glick updated JENKINS-43610 Jenkins / JENKINS-43610 Split Trilead out from Core Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181011.1492247358000.6641.1569585960851%40Atlassian.JIRA.
[JIRA] (JENKINS-59506) Incorrect identation in Wiki for job-dsl JCasC example
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59506 Incorrect identation in Wiki for job-dsl JCasC example Change By: Oleg Nenashev Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202128.1569322468000.6638.1569585900205%40Atlassian.JIRA.
[JIRA] (JENKINS-59551) jCasC: enable colums for sectionedView
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59551 jCasC: enable colums for sectionedView Change By: Oleg Nenashev Labels: configuration jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202182.1569510957000.6635.1569585840289%40Atlassian.JIRA.
[JIRA] (JENKINS-59561) MAC Machine: Keychain not Found to store error
Title: Message Title Pradeep Borse updated an issue Jenkins / JENKINS-59561 MAC Machine: Keychain not Found to store error Change By: Pradeep Borse I am facing error "Keychain not found to store" while git fetch on Mac machine using jenkins.Please see attached image for the same. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202194.1569584258000.6631.1569584340218%40Atlassian.JIRA.
[JIRA] (JENKINS-59561) MAC Machine: Keychain not Found to store error
Title: Message Title Pradeep Borse created an issue Jenkins / JENKINS-59561 MAC Machine: Keychain not Found to store error Issue Type: Bug Assignee: Mark Waite Attachments: Kaychain not found.JPG Components: git-client-plugin, git-plugin Created: 2019-09-27 11:37 Priority: Minor Reporter: Pradeep Borse I am facing error "Keychain not found to store" while git fetch on Mac machine using jenkins. Please attached image for the same. Add Comment
[JIRA] (JENKINS-59559) Jenkins Agent Fails to start with 1.46
Title: Message Title Ignacio Tolstoy commented on JENKINS-59559 Re: Jenkins Agent Fails to start with 1.46 this duplicates https://issues.jenkins-ci.org/browse/JENKINS-59543 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202192.1569581206000.6614.1569583200129%40Atlassian.JIRA.
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title Ignacio Tolstoy commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set Confirming 1.46 breaks scaling up nodes. 1.45 works fine Our jenkins is in version 2.197 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202173.1569501392000.6608.1569583140249%40Atlassian.JIRA.
[JIRA] (JENKINS-59560) Multibranch pipeline checkout NPE exception
Title: Message Title
Artem Gryshyn updated an issue
Jenkins / JENKINS-59560
Multibranch pipeline checkout NPE exception
Change By:
Artem Gryshyn
Multibranch pipeline jobs are failing on git checkout step after update to the latest versions of pipeline plugins. {code: java }java .lang.NullPointerException at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:836) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1101) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:133) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:91) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:78) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE {code} Multibranch pipeline job does not fail with Pipeline: SCM Step 2.7 version, next versions (2.8, 2.9) leads to fails with NPE.This is an example of Jenkinsfile: {code:java}pipeline { agent none options {timeout(time: 1, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20'))disableConcurrentBuilds()timestamps() } stages {stage('Build and publish') { agent { label 'environment/qa && java/1.8' } steps {git branch: 'test',url: 'g...@github.com:yourorganization/yourgit.git'sh 'echo test' }} }}{code}
Add Comment
[JIRA] (JENKINS-59560) Multibranch pipeline checkout NPE exception
Title: Message Title
Artem Gryshyn updated an issue
Jenkins / JENKINS-59560
Multibranch pipeline checkout NPE exception
Change By:
Artem Gryshyn
Multibranch pipeline jobs are failing on git checkout step after update to the latest versions of pipeline plugins. java.lang.NullPointerException at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:836) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1101) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:133) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:91) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:78) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Finished: FAILURE Multibranch pipeline job does not fail with Pipeline: SCM Step 2.7 version, next versions (2.8, 2.9) leads to fails with NPE.This is an example of Jenkinsfile: {code:java}pipeline { agent none options {timeout(time: 1, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20'))disableConcurrentBuilds()timestamps() } stages {stage('Build and publish') { agent { label 'environment/qa && java/1.8' } steps {git branch: 'test',url: 'g...@github.com:yourorganization/yourgit.git'sh 'echo test' }} }}{code}
Add Comment
[JIRA] (JENKINS-59560) Multibranch pipeline checkout NPE exception
Title: Message Title Artem Gryshyn created an issue Jenkins / JENKINS-59560 Multibranch pipeline checkout NPE exception Issue Type: Bug Assignee: Denis Saponenko Attachments: Screen Shot 2019-09-27 at 14.04.07.png Components: pipeline-multibranch-defaults-plugin Created: 2019-09-27 11:11 Environment: Jenkins version 2.176.3 openjdk version "1.8.0_222" Pipeline: Multibranch 2.21 Pipeline: SCM Step 2.9 Priority: Major Reporter: Artem Gryshyn Multibranch pipeline jobs are failing on git checkout step after update to the latest versions of pipeline plugins. java.lang.NullPointerException at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:836) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1101) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:133) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:91) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:78) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Alex Earl Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: trinadh teegala Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.6599.1569581820265%40Atlassian.JIRA.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to trinadh teegala Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl trinadh teegala Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202172.1569500879000.6597.1569581820242%40Atlassian.JIRA.
[JIRA] (JENKINS-59559) Jenkins Agent Fails to start with 1.46
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-59559 Jenkins Agent Fails to start with 1.46 Change By: Ebrahim Moshaya Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202192.1569581206000.6595.1569581280182%40Atlassian.JIRA.
[JIRA] (JENKINS-59559) Jenkins Agent Fails to start with 1.46
Title: Message Title Ebrahim Moshaya created an issue Jenkins / JENKINS-59559 Jenkins Agent Fails to start with 1.46 Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-09-27 10:46 Environment: 1.46, Jenkins ver. 2.197 Priority: Minor Reporter: Ebrahim Moshaya When updating this plugin from 1.45 to 1.46, I get the following error when launching a new ec2 instance: com.amazonaws.services.ec2.model.AmazonEC2Exception: Network interfaces and an instance-level subnet ID may not be specified on the same request (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 25233001-3158-4545-853a-19de118c0834) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1712) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1367) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1113) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:770) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:744) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:726) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:686) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:668) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:532) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:512) at
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library Hi Adam Smith - Change of plan. I'm able to reproduce this if I use a static label in that field: p4 changes -m1 -ssubmitted //jenkins-lib-56ca85cd-43c2-4b6f-b216-cf9fc5b75707/...@1,-1 Invalid changelist/client/label/date '@-1'. ERROR: P4: Unable to initialise CheckoutTask: com.perforce.p4java.exception.RequestException: Invalid changelist/client/label/date '@-1'. Therefore when you get in please check if you are using a label in the 'Default Version' field, if there are any spaces or you are using different case to 'now'. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6591.1569579720107%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Kevin Broselge updated an issue Jenkins / JENKINS-59558 Hyperlink to result in project view not working Change By: Kevin Broselge The hyperlinks to the warning results are not working -> see Screenshot ( left side gcc STM32F** Warnings ) !image-2019-09-27-12-02-31-940.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202191.1569578601000.6589.1569578760264%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Kevin Broselge updated an issue Jenkins / JENKINS-59558 Hyperlink to result in project view not working Change By: Kevin Broselge Environment: Jenkins ver. 2.176.2plugin version: 6.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202191.1569578601000.6587.1569578760228%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Kevin Broselge created an issue Jenkins / JENKINS-59558 Hyperlink to result in project view not working Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-09-27-12-02-31-940.png Components: warnings-ng-plugin Created: 2019-09-27 10:03 Priority: Minor Reporter: Kevin Broselge The hyperlinks to the warning results are not working -> see Screenshot Add Comment
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Adam Smith commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library Not at all, please do. I won't be available for another several hours, but will respond then. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6583.1569577920138%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library Hi Adam Smith Thank. No obvious discrepencies there. Do you mind if I email you directly? I'd like to try and set up a meeting to look at your system. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6581.1569577260115%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted updated JENKINS-59504 Jenkins / JENKINS-59504 Credentials shown in plaintext in Splunk Console Output Change By: Ted Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6576.1569577140356%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Adam Smith commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library Good morning! I'm not at my computer at the moment, but will add a comment with the rest of the requested information as possible. In the meantime... 1. I'm only using the "build now" option 2. I'm using the gui, not a pipeline from scm. I will try using a Jenkinsfile to add data points 3. I'm defining the shared library under Manage Jenkins. Screenshots forthcoming. 4. Screenshots forthcoming, but since I'm not polling I imagine this isn't it My setup looks very similar to your provided screenshot, but where your console output is p4 changes -m1 //depot/myLibrary/...@now, mine said p4 changes -m1 //depot/myLibrary/.../...@now Removing the trailing "/..." from my Library Depot Path produced output that matched yours, but still presented the error reported in the ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6571.1569577020129%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted commented on JENKINS-59504 Re: Credentials shown in plaintext in Splunk Console Output I would recommend scripted pipeline for such cases Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6565.1569576720124%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title
Ted commented on JENKINS-59504
Re: Credentials shown in plaintext in Splunk Console Output
If you click the "pipeline steps" on job build page, you will find out something like this The step env step executed first before sendSplunkConsoleLog
environment {
userAndPass = credentials('5d407101-23e0-43e7-83b6-badfdd189698')
}
And because sendSplunkConsoleLog is wrapped inside the scope, it sees the clear text instead of masked ones, just like other steps inside withCredentials such as
withCredentials([usernameColonPassword(credentialsId: '5d407101-23e0-43e7-83b6-badfdd189698', variable: 'abc')]) {
// sh step sees the clear text actually
sh "echo $abc > /tmp/abc.txt"
}
I think it is specific to declarative pipeline design: environment step has higher order. In the contract, we can control the order of execution in scripted pipeline, such as
sendSplunkConsoleLog {
node {
echo "testing console log"
withCredentials([usernameColonPassword(credentialsId: 'blah', variable: 'abc')]) {
echo abc
sh "echo $abc"
echo "hello there"
}
echo "done"
}
}
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted updated an issue Jenkins / JENKINS-59504 Credentials shown in plaintext in Splunk Console Output Change By: Ted Attachment: Screen Shot 2019-09-27 at 5.17.58 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6561.1569576180256%40Atlassian.JIRA.
[JIRA] (JENKINS-53500) Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed"
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-53500 Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed" Change By: Vincent Latombe Component/s: kubernetes-plugin Component/s: kubernetes-pipeline-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193972.1536613109000.6558.1569575700271%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title
Karl Wirth edited a comment on JENKINS-59556
Re: Global Pipeline shared library version "now" fails when using Helix Library
Hi [~asmith_pipeworks]. I haven't been able to reproduce this error with a pipeline polled job with a Jenkinsfile containing your code and your versions of Jenkins and plugin (see my setup below). Note that my shared library is defined under Manage Jenkins.Note that we have added code in [ recently|[ https://swarm.workshop.perforce.com/changes/25826] ] to minimise the number of changes return when looking for differences with source during polling so my guess is that this code is being applied when it shouldn't be.Please answer the following questions: * Does the problem occur when you click the Jenkins "Build Now" button? * Are you using a Jenkinsfile or the GUI? * Where are you defining the library? Manage Jenkins, folder level or somewhere else? Please send me screenshots. * If you go to manage Jenkins and look at 'Perforce: Query limits' what values are set? Here is my working setup:!MySharedLibrary.png!The console output was: ... p4 changes -m1 //depot/myLibrary/...@now +... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 +{code:java}Console OutputStarted by user unknown or anonymousRunning in Durability level: MAX_SURVIVABILITY[Pipeline] libraryLoading library my-shared-library@now... p4 changes -m1 //depot/myLibrary/...@now +... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 +--- cut---P4 Task: syncing files at change: 496... p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-share___ -p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-shared-library/...@496... totalFileSize 4341... totalFileCount 2duration: (2ms){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Adrien Lecharpentier edited a comment on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 [~jonesbusy] sadly, I'm not confident that there is an easy way to fix this. The source code of the libray being hidden (most of it, we can still uncompile it) makes it really difficult for me to have a clear idea. I opened a second PR with a test to show the problem: https://github.com/jenkinsci/crowd2-plugin/pull/37 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201849.156813782.6552.1569575580639%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59556 Global Pipeline shared library version "now" fails when using Helix Library Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6549.1569575580598%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-59556 Global Pipeline shared library version "now" fails when using Helix Library Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6547.1569575580562%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title
Karl Wirth edited a comment on JENKINS-59556
Re: Global Pipeline shared library version "now" fails when using Helix Library
Hi [~asmith_pipeworks]. I haven't been able to reproduce this error with a pipeline polled job with a Jenkinsfile containing your code and your versions of Jenkins and plugin (see my setup below). Note that my shared library is defined under Manage Jenkins.Note that we have added code [recently|[https://swarm.workshop.perforce.com/changes/25826]] to minimise the number of changes return when looking for differences with source during polling so my guess is that this code is being applied when it shouldn't be.Please answer the following questions: * Does the problem occur when you click the Jenkins "Build Now" button? * Are you using a Jenkinsfile or the GUI? * Where are you defining the library? Manage Jenkins, folder level or somewhere else? Please send me screenshots. * If you go to manage Jenkins and look at 'Perforce: Query limits' what values are set? Here is my working setup:!MySharedLibrary.png!The console output was: ... p4 changes -m1 //depot/myLibrary/...@now +... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 +{code:java}Console OutputStarted by user unknown or anonymousRunning in Durability level: MAX_SURVIVABILITY[Pipeline] libraryLoading library my-shared-library@now... p4 changes -m1 //depot/myLibrary/...@now +... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 +--- cut---P4 Task: syncing files at change: 496... p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-share___ -p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-shared-library/...@496... totalFileSize 4341... totalFileCount 2duration: (2ms){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library Hi Adam Smith. I haven't been able to reproduce this error with a pipeline polled job with a Jenkinsfile containing your code and your versions of Jenkins and plugin (see my setup below). Note that my shared library is defined under Manage Jenkins. Note that we have added code [recently|https://swarm.workshop.perforce.com/changes/25826] to minimise the number of changes return when looking for differences with source during polling so my guess is that this code is being applied when it shouldn't be. Please answer the following questions: Does the problem occur when you click the Jenkins "Build Now" button? Are you using a Jenkinsfile or the GUI? Where are you defining the library? Manage Jenkins, folder level or somewhere else? Please send me screenshots. If you go to manage Jenkins and look at 'Perforce: Query limits' what values are set? Here is my working setup: The console output was: ... p4 changes -m1 //depot/myLibrary/...@now +... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 + Console OutputStarted by user unknown or anonymous Running in Durability level: MAX_SURVIVABILITY [Pipeline] library Loading library my-shared-library@now ... p4 changes -m1 //depot/myLibrary/...@now + ... p4 client -o jenkins-lib-a5181aaa-9ab1-49c7-ae00-ca4a511ab508 + --- cut--- P4 Task: syncing files at change: 496 ... p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-share___ -p4 sync -f -q /var/lib/jenkins/workspace/JENKINS-59556-LoadALibrary%40libs/my-shared-library/...@496 ... totalFileSize 4341 ... totalFileCount 2 duration: (2ms) Add Comment
[JIRA] (JENKINS-53500) Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed"
Title: Message Title Vincent Latombe commented on JENKINS-53500 Re: Kubernetes Pipeline fails on Windows agents with "java.io.IOException: Pipe closed" https://github.com/jenkinsci/kubernetes-plugin/blob/7753d3579015bcbcd68a838e9eb6040c28bdc445/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L445 is unix only. Would need a patch to make it windows compatible. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193972.1536613109000.6539.1569575220248%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Adrien Lecharpentier commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 Valentin Delaye sadly, I'm not confident that there is an easy way to fix this. The source code of the libray being hidden (most of it, we can still uncompile it) makes it really difficult for me to have a clear idea. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201849.156813782.6533.1569574320476%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59556 Global Pipeline shared library version "now" fails when using Helix Library Change By: Karl Wirth Attachment: MySharedLibrary.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202188.156953784.6530.1569573180155%40Atlassian.JIRA.
[JIRA] (JENKINS-54163) Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds
Title: Message Title Amit Dar commented on JENKINS-54163 Re: Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds Alex Earl, your effort in this matter is greatly appreciated! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194792.1539944186000.6525.1569572940204%40Atlassian.JIRA.
[JIRA] (JENKINS-49412) Description length
Title: Message Title Marat Radchenko resolved as Won't Fix So don't do that. What behavior do you expect from Jenkins? Jenkins / JENKINS-49412 Description length Change By: Marat Radchenko Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-31209) Make the length of the build description display user settable
Title: Message Title Marat Radchenko resolved as Duplicate Fixed by https://github.com/jenkinsci/jenkins/pull/4209 and should be released in 2.198 next week. History widget no longer truncates build description. Jenkins / JENKINS-31209 Make the length of the build description display user settable Change By: Marat Radchenko Status: Open Resolved Resolution: Duplicate Released As: 2.198 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-19760) Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax
Title: Message Title Marat Radchenko updated JENKINS-19760 Fixed by https://github.com/jenkinsci/jenkins/pull/4209 and should be released in 2.198 next week. Jenkins / JENKINS-19760 Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax Change By: Marat Radchenko Status: Open Fixed but Unreleased Resolution: Fixed Released As: 2.198 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-19760) Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax
Title: Message Title Marat Radchenko edited a comment on JENKINS-19760 Re: Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax Fixed by https://github.com/jenkinsci/jenkins/pull/4209 and should be released in 2.198 next week. History widget no longer truncates build description. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151279.1380131448000.6509.1569571141067%40Atlassian.JIRA.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Anda Sorina Laakso commented on JENKINS-57334 Re: "Run on planned host" from Build section not working Where can I upload the fix for this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199108.1557111748000.6499.1569570660215%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing But can you remove the timeout and just for testing purposes try to run the test again? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.6496.1569570300143%40Atlassian.JIRA.
[JIRA] (JENKINS-59008) Merge before build, reference is not a tree on second build
Title: Message Title P K commented on JENKINS-59008 Re: Merge before build, reference is not a tree on second build any progress on this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201360.1566299152000.6494.1569569400311%40Atlassian.JIRA.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title
zy zhang commented on JENKINS-19022
Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Hi, you can use the below groovy script to delete git revisions for the current build. import jenkins.model.* jenkinsInstance = jenkins.model.Jenkins.get() def job = jenkinsInstance.getItemByFullName(JOB_NAME); def build = job.getBuild(BUILD_NUMBER) def prj = build.project def gitActions = build.getActions(hudson.plugins.git.util.BuildData.class) if (gitActions != null) { for (action in gitActions) { build.actions.remove(action) //build.actions.add(action) build.save() } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150469.1375284228000.6420.1569567241384%40Atlassian.JIRA.
