[JIRA] (JENKINS-37627) Allow writing response to file in pipeline
Title: Message Title Janario Oliveira started work on JENKINS-37627 Change By: Janario Oliveira Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title David van Laatum commented on JENKINS-37717 Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline So are you saying you'r using recursive expansion or are you saying withEnv breaks CHANGES_SINCE_LAST_SUCCESS? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Mark Waite commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Thanks Jesse Glick, I've removed the remoteTargetDir setting from my pipeline test jobs. It will take a while before I have time to take any more active measures to hide that option from a pipeline user. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Caleb Chenoweth edited a comment on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation [~elordahl] - we are running chechmarx v8.1.0 I believe.(our team is not in charge of the server that runs the scans.The web login spash splash page shows that version number.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Caleb Chenoweth commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Eric Lordahl - we are running chechmarx v8.1.0 I believe. (our team is not in charge of the server that runs the scans. The web login spash page shows that version number.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title Janario Oliveira commented on JENKINS-40043 Re: Allow custom values for Content-Type Header in Pipelines I plan to deprecate 'acceptType', 'contentType' in favor to use headers. It's bad to have 2 configuration that do the same, and one of it very limited. Also it could generate duplicated headers from both. But I plan to do it keeping compatibility. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-27906 Fail to read NUnit3 output xml Change By: Alex Earl Assignee: Bruno P. Kinoshita Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41803) httpRequest step called outside node causes exception
Title: Message Title Janario Oliveira resolved as Not A Defect This is expected by Jenkins not the plugin. As it shows on its logs > Required context class hudson.FilePath is missing > Perhaps you forgot to surround the code with a step that provides this, such as: node It would also happen if I tried to access workspace inside the job execution Jenkins / JENKINS-41803 httpRequest step called outside node causes exception Change By: Janario Oliveira Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-42610) NPE during pipeline execution in test-stability-plugin
Title: Message Title Raphael LANG edited a comment on JENKINS-42610 Re: NPE during pipeline execution in test-stability-plugin [~seanf] , [~kutzi] : applying the same change as -- - JENKINS-36504-- - fixed the issue for me; a pull request is available at [https://github.com/jenkinsci/test-stability-plugin/pull/4] for review, but I did not do test it outside of my pipeline jobs with the configuration described above. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42610) NPE during pipeline execution in test-stability-plugin
Title: Message Title Raphael LANG commented on JENKINS-42610 Re: NPE during pipeline execution in test-stability-plugin Sean Flanigan , kutzi : applying the same change as -JENKINS-36504- fixed the issue for me; a pull request is available at https://github.com/jenkinsci/test-stability-plugin/pull/4 for review, but I did not do test outside of my pipeline jobs with the configuration described above. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43065) Task Scanner Plugin - Ignore case broken
Title: Message Title Ulli Hafner commented on JENKINS-43065 Re: Task Scanner Plugin - Ignore case broken Can you please add some screenshots or details? Do you mean that the warning is not shown or that the tag is not shown in lowercase? I just started the acceptance test https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/TaskScannerPluginTest.java#L65 without any problems. Maybe I need some more verifications? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43068) Result Page of findbugs plugin has wrong links
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-43068 Result Page of findbugs plugin has wrong links Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43100) bapSshPublisher closure requires sshCredentials in Jenkins DSL.
Title: Message Title
Eric Wallengren created an issue
Jenkins / JENKINS-43100
bapSshPublisher closure requires sshCredentials in Jenkins DSL.
Issue Type:
Bug
Assignee:
bap
Components:
publish-over-ssh-plugin
Created:
2017/Mar/24 10:50 PM
Environment:
ubuntu 16.04 jenkins 2.32.3 publish-over-ssh 1.17
Priority:
Minor
Reporter:
Eric Wallengren
When using the closure bapSshPublisher in Jenkins DSL, sshCredentials is required even though it appears to be optional when creating a job through the Jenkins UI: configName(String value) - required Select an SSH configuration from the list configured in the global configuration of this Jenkins. sshCredentials {} - required Set the credentials to use with this connection.If you want to use different credentials from those configured for this server, or if the credentials have not been specified for this server, then enable this option and set them here. The resulting job allows de-selection of credentials, but DSL requires it. sshCredentials should optional when using bapSshPublisher in the Jenkins DSL, especially when there's a global configuration that is referenced through configName.
[JIRA] (JENKINS-36916) Delivery Pipeline not showing trigger button to start manual downstream project
Title: Message Title Ryan Cox commented on JENKINS-36916 Re: Delivery Pipeline not showing trigger button to start manual downstream project Any update on this issue? I am seeing similar behavior on some but not all workflow executions. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43099) Marathon Plug-in Problem
Title: Message Title Chad Schmidt created an issue Jenkins / JENKINS-43099 Marathon Plug-in Problem Issue Type: Bug Assignee: Colin Attachments: marathon.json Components: marathon-plugin Created: 2017/Mar/24 9:14 PM Environment: Jenkins version 2.32.2, Marathon Deployment plug-in version 1.4.0 Priority: Major Reporter: Chad Schmidt The following error is encountered when I attempt to run the Marathon plugin against the attached marathon.json. Please note that I have scrubbed the URL of my corporate dockerhub URL for privacy purposes. I have also verified with Mesosphere staff that the attached marathon.json is in a valid format and should have worked with the plugin. com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 377 path $.env. at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:221) at com.google.gson.Gson.fromJson(Gson.java:861) at com.google.gson.Gson.fromJson(Gson.java:826) at com.google.gson.Gson.fromJson(Gson.java:775) at com.google.gson.Gson.fromJson(Gson.java:747) at com.mesosphere.velocity.marathon.impl.MarathonBuilderImpl.build(MarathonBuilderImpl.java:172) at com.mesosphere.velocity.marathon.MarathonRecorder.perform(MarathonRecorder.java:124) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title
Jesse Glick edited a comment on JENKINS-43052
Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Since there is a generic way to select the base directory in Pipeline—{{dir}}—any historical SCM plugin options created for the benefit of freestyle projects and are obsolete and should be considered deprecated in the context of Pipeline.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43098) The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups
Title: Message Title Julio García Muñoz commented on JENKINS-43098 Re: The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups Pull request submitted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40557) Remove "pipeline script" references from workflow-cps-plugin
Title: Message Title Patrick Wolf assigned an issue to CloudBees Inc. Jenkins / JENKINS-40557 Remove "pipeline script" references from workflow-cps-plugin Change By: Patrick Wolf Assignee: Patrick Wolf CloudBees Inc. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title akostadinov commented on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node Jesse Glick, have a job with label parameter build manually => the default value of parameter is respected build from a pipeline (without specifying this parameter) => job is built on a random node (i.e. the default value of the label parameter is not respected) And in the latter case, when you go to the executed build parameters, you see the label parameter with the default values. They just didn't take effect. But probably this is a separate issue so I will file one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43098) The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups
Title: Message Title Julio García Muñoz updated an issue Jenkins / JENKINS-43098 The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups Change By: Julio García Muñoz Summary: The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43098) The check for "commitToStream" and "viewDefects" permissions
Title: Message Title Julio García Muñoz created an issue Jenkins / JENKINS-43098 The check for "commitToStream" and "viewDefects" permissions Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 2017/Mar/24 8:07 PM Environment: Plugin version: 1.9.0 Priority: Major Reporter: Julio García Muñoz Version 1.9.0 introduced a check for the user permissions "commitToStream" and "viewDefects". That check is only done on the user direct roles, it doesn't take into account inherited roles from groups assigned to the user. There is no way to disable the check and it can block previously working jobs. Add Comment
[JIRA] (JENKINS-40558) Remove "pipeline script" references from pipeline mutlibranch plugin
Title: Message Title R. Tyler Croy commented on JENKINS-40558 Re: Remove "pipeline script" references from pipeline mutlibranch plugin This looks like this should be closed correct? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40557) Remove "pipeline script" references from workflow-cps-plugin
Title: Message Title R. Tyler Croy commented on JENKINS-40557 Re: Remove "pipeline script" references from workflow-cps-plugin This still is an issue of confusion for users, plans on fixing this UI any time soon? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40557) Remove "pipeline script" references from workflow-cps-plugin
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-40557 Remove "pipeline script" references from workflow-cps-plugin Change By: R. Tyler Croy Attachment: pipeline-script-booo.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33595) Disable SSHD by default
Title: Message Title Jesse Glick updated JENKINS-33595 Jenkins / JENKINS-33595 Disable SSHD by default Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33595) Disable SSHD by default
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-33595 Disable SSHD by default Change By: Jesse Glick Assignee: Keith Zantow Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33595) Disable SSHD by default
Title: Message Title Jesse Glick started work on JENKINS-33595 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43097) Request to support premium level storage account
Title: Message Title nathan crouse created an issue Jenkins / JENKINS-43097 Request to support premium level storage account Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2017/Mar/24 8:01 PM Environment: Jenkins 2.23.3 Windows Server 2012 R2 Azure VM Agents 0.4.3 Priority: Minor Reporter: nathan crouse Request to support premium storage account. This would allow much higher scaling of number of vm's and increased performance of the agents stood up on the storage account. Currently when trying to use premium storage account logs indicate that 'Block Blobs are not supported'. I believe this is because the customscriptextension is a block blob and is trying to save to premium storage and is unsupported. Perhaps there could be a separate storage account field for the script extension location and this storage account would be required to be standard storage in order to support block blobs. Add Comment
[JIRA] (JENKINS-33595) Disable SSHD by default
Title: Message Title Jesse Glick commented on JENKINS-33595 Re: Disable SSHD by default move its configuration to /configureSecurity Done already in PR 9. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title John McGehee commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Maybe some more–or all–of these options should be removed when the project type is Pipeline. Jesse Glick, perhaps you meant, "...are obsolete and should be considered..." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33433) jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Title: Message Title Joe Martinez commented on JENKINS-33433 Re: jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch We are using 2.0.8 as well. We also had to revert: Git Plugin, we are using 3.0.1 Githug API Plugin, we are using 1.84 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43093) Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set
Title: Message Title Tatiana Didik resolved as Fixed Jenkins / JENKINS-43093 Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set Change By: Tatiana Didik Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43093) Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set
Title: Message Title Tatiana Didik commented on JENKINS-43093 Re: Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set fixed in https://github.com/jenkinsci/sonar-gerrit-plugin/commit/c40f3fd568d66b330fab2a29b8bdab0fe0cd7aee Version 1.0.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars
Title: Message Title Jesse Glick commented on JENKINS-29144 Re: SimpleBuildStep to receive EnvVars Currently if you want to access environment variables, you cannot; you must implement Step instead. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Jesse Glick commented on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin Not currently. Read my last comment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars
Title: Message Title David Brooks commented on JENKINS-29144 Re: SimpleBuildStep to receive EnvVars Jesse Glick The header of our class is public class IntrepidBuilder extends Builder implements SimpleBuildStep since we want our plugin to be compatible with both Freestyle and Pipelines. How might we update this to still allow the end user to use the "pipeline syntax generator" to call our build step? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars
Title: Message Title Jesse Glick commented on JENKINS-29144 Re: SimpleBuildStep to receive EnvVars This is blocking our company from … If you implement Step directly there are no restrictions. Could the solution be as easy as … No, that is not how it would work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title Jesse Glick commented on JENKINS-25804 Re: Whitelisted signature presets for Java standard APIs and Jenkins core APIs Unrelated to this issue Sorin Sbarnea. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22660) More flexible UI for approved signatures
Title: Message Title Jesse Glick commented on JENKINS-22660 Re: More flexible UI for approved signatures In principle you could reload config, pending JENKINS-23578. I have not tested it and do not plan to support it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Jesse Glick resolved as Not A Defect akostadinov whatever your issue is—I find it hard to follow—it sounds unrelated to what was reported here. Better to use the user list. Jenkins / JENKINS-36568 workflow script node step cannot trigger build on specific node Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title Cliff Meyers updated JENKINS-42123 Jenkins / JENKINS-42123 No feedback when clicking "connect" when entering Github access key Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43096) Form submission progress / error / success states
Title: Message Title Cliff Meyers created an issue Jenkins / JENKINS-43096 Form submission progress / error / success states Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/24 6:58 PM Labels: technical-debt Priority: Minor Reporter: Cliff Meyers In JENKINS-42123, some button styles were added to show that a form submission is in-progress or succeeded. (Error state was also supported, but not actually displayed in the UI, as the existing form validation error messaging was deemed sufficient feedback). A reusable button control was created to accomplish this but it may not be ideal from an API / coupling perspective (see discussion here: https://github.com/jenkinsci/blueocean-plugin/pull/912) Once a few more concrete use cases are established, we should try to make supporting these kinds of behaviors as easy as possible so that we have consistent UX and components that are easily transferrable to other teams. Add Comment
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Jesse Glick commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Since there is a generic way to select the base directory in Pipeline—dir—any historical SCM plugin options created for the benefit of freestyle projects and obsolete and should be considered deprecated in the context of Pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-43052 Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Change By: Jesse Glick Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20161) 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
Title: Message Title
Jesse Glick commented on JENKINS-20161
Re: 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
No this is simply a bug in RunParameterDefinition.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Jesse Glick assigned an issue to Unassigned Certainly it is a problem. Your build record storage is corrupt. I cannot speculate why. Jenkins / JENKINS-43055 "List of flow heads unset for CpsFlowExecution[null]" Warning Change By: Jesse Glick Component/s: core Component/s: pipeline Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42149) unclassified error using dynamic parameter in pipeline properties
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-42149 unclassified error using dynamic parameter in pipeline properties Change By: Jesse Glick Component/s: pipeline Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Jesse Glick commented on JENKINS-32650 Re: Make PerformancePublisher a SimpleBuildStep The Double issue is the well-known JENKINS-31967. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title Jesse Glick commented on JENKINS-37144 Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Mike Neary checkout scm Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29144) SimpleBuildStep to receive EnvVars
Title: Message Title David Brooks commented on JENKINS-29144 Re: SimpleBuildStep to receive EnvVars Has there been any progress on this issue? This is blocking our company from updating our jobs to from Freestyle to Pipelines. Could the solution be as easy as doing what the old AbstractBuild getEnvironment() did which was holding onto an array that contained the RunListener's environments and NodeProperty's environments? And then in Run getEnvironment() we could add the environments from the array we gathered via buildEnvironmentFor(this,env,listener); ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title Jesse Glick commented on JENKINS-40109 Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector A fix of JENKINS-26137 would make the bug here more apparent. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title Jesse Glick commented on JENKINS-40109 Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector Is there a way a syntax/compile error could be reported by file and line instead? That is normally what happens, of course. Somehow that breaks down under certain conditions, for unknown reasons. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37139) 'Build periodically with parameters' option not available for Pipeline jobs
Title: Message Title Kenneth Baltrinic commented on JENKINS-37139 Re: 'Build periodically with parameters' option not available for Pipeline jobs +1 we need this soonest. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43095) Option to have Parameterized Trigger plugin report a build as failed when triggered job fails to trigger.
Title: Message Title Andrew Starkey created an issue Jenkins / JENKINS-43095 Option to have Parameterized Trigger plugin report a build as failed when triggered job fails to trigger. Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2017/Mar/24 6:21 PM Priority: Minor Reporter: Andrew Starkey Builds will be reported as successful when the Parameterized Trigger plugin encounters an error. EG: 16:11:38 ERROR: Failed to build parameters to trigger project: 16:11:38 java.lang.IllegalArgumentException: Illegal choice for parameter BRANCH_PATH: Trunk 16:11:38 at hudson.model.ChoiceParameterDefinition.checkValue(ChoiceParameterDefinition.java:79) 16:11:38 at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:91) 16:11:38 at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:19) 16:11:38 at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.convertToDefinedType(ProjectSpecificParameterValuesActionTransform.java:82) 16:11:38 at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.transformParametersAction(ProjectSpecificParameterValuesActionTransform.java:33) 16:11:38 at hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.getProjectSpecificBuildActions(ProjectSpecificParametersActionFactory.java:33) 16:11:38 at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getBuildActions(BuildTriggerConfig.java:351) 16:11:38 at hudson.plugins.parameterizedtrigger.ParameterizedDependency.shouldTriggerBuild(ParameterizedDependency.java:60) 16:11:38 at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) 16:11:38 at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:684) 16:11:38
[JIRA] (JENKINS-42949) MultiBranch Pipeline periodically stops functioning
Title: Message Title josh harshman closed an issue as Cannot Reproduce resolved on it's own. cannot reproduce Jenkins / JENKINS-42949 MultiBranch Pipeline periodically stops functioning Change By: josh harshman Status: Open Closed Assignee: josh harshman Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-42772) New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1
Title: Message Title Andrew Bayer commented on JENKINS-42772 Re: New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1 And a PR - https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/145 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42772) New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1
Title: Message Title Andrew Bayer updated JENKINS-42772 Jenkins / JENKINS-42772 New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1 Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42772) New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1
Title: Message Title Andrew Bayer started work on JENKINS-42772 Change By: Andrew Bayer Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43035) expression does not see imported classes
Title: Message Title Jesse Glick commented on JENKINS-43035 Re: _expression_ does not see imported classes Maybe you should just get rid of scripted expressions. People who need to do fancy things like that can just use scripted Pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36570 Re: Implement pipeline compatibility Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/db5cf31926d7e009cf30ed14a8e7325d384067e9 Log: Merge pull request #428 from oleg-nenashev/PrioritySorter JENKINS-36570 - Add PrioritySorter to the Pipeline Compatibility list Compare: https://github.com/jenkinsci/pipeline-plugin/compare/74522f80f474...db5cf31926d7 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36570 Re: Implement pipeline compatibility Code changed in jenkins User: Oleg Nenashev Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/615a0b9b0c3ade0157da4cd8118398b608a1e679 Log: JENKINS-36570 - Add PrioritySorter to the Pipeline Compatibility list Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null)
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null) Change By: Christopher Head Environment: openjdk 1.8.0_121Jenkins 2. 48 51 Copy Artifact 1.38.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null)
Title: Message Title Christopher Head commented on JENKINS-41773 Re: Copy Artifact sometimes crashes on startup (Jenkins#getDescriptorByType looks sometimes return null) By the way, when it doesn’t crash, this is what I see: - hudson.plugins.copyartifact.BuildSelectorParameter$DescriptorImpl@52bd274a - [hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@23b7cdab, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@4471979e, hudson.plugins.copyartifact.TriggeredBuildSelector$DescriptorImpl@6290d06b, hudson.plugins.copyartifact.DownstreamBuildSelector$DescriptorImpl@23ae25a8, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@3ee96ee3, hudson.plugins.copyartifact.PermalinkBuildSelector$DescriptorImpl@766cd3c7, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@121b56e9, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@40caa267, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@35a152eb] - [hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@23b7cdab, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@4471979e, hudson.plugins.copyartifact.TriggeredBuildSelector$DescriptorImpl@6290d06b, hudson.plugins.copyartifact.DownstreamBuildSelector$DescriptorImpl@23ae25a8, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@3ee96ee3, hudson.plugins.copyartifact.PermalinkBuildSelector$DescriptorImpl@766cd3c7, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@121b56e9, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@40caa267, hudson.plugins.copyartifact.SimpleBuildSelectorDescriptor@35a152eb] - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Fahd Arshad commented on JENKINS-43092 Re: Jenkins stages executions hangs when creating stages dynamically Thanks Sam Van Oort I understand your point. I ll see if i can work without @NonCPS functions. Thanks for the prompt response though appreciated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell assigned an issue to Alvaro Lobato Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Change By: Chris Russell Assignee: Chris Russell Alvaro Lobato Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell assigned an issue to Chris Russell Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Change By: Chris Russell Assignee: Alvaro Lobato Chris Russell Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42772) New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1
Title: Message Title Andrew Bayer reopened an issue Re-opening - I think I'm going to set it to not fail when it sees no parameters passed to a single-argument @DataBoundConstructor. Jenkins / JENKINS-42772 New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1 Change By: Andrew Bayer Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-30782) Failed to read environment variable table error
Title: Message Title Oleg Nenashev commented on JENKINS-30782 Re: Failed to read environment variable table error I am currently working on the fix. I wish I could just take the implementation from processhacker2 "https://github.com/processhacker2/processhacker2/blob/69d9dcd2c79d52ce987cc8f0150f639426eb67f9/phlib/native.c#L867-L990", but it cannot be done since the code there is GNU GPL. Will consider alternatives Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell created an issue Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/24 5:03 PM Priority: Minor Reporter: Chris Russell The standard Maven Project in Jenkins provides the ability to fingerprint consumed artifacts. If the consumed artifact was created by a Jenkins build (and fingerprinted), Jenkins will link you back to the point of origin. Use cases: When an upstream project causes an exception, you can easily find the build of the dependency to get information which will help narrow in on the root cause like the upstream changelog. When releasing (or preparing to release) the downstream build, you can see exactly what upstream builds are implicitly being released with it. Add Comment
[JIRA] (JENKINS-41336) Cron based jobs are triggered at random times and also at the time Stash is unavailable
Title: Message Title Larry Brigman commented on JENKINS-41336 Re: Cron based jobs are triggered at random times and also at the time Stash is unavailable I'm seeing jobs queue when I get this error: Mar 23, 2017 4:43:00 PM stashpullrequestbuilder.stashpullrequestbuilder.StashRepository getTargetPullRequests INFO: Fetch PullRequests (ansible-checks). java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Read timed out at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:202) at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getRequest(StashApiClient.java:254) at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getPullRequests(StashApiClient.java:86) Using Jenkins 2.44 on Ubuntu 14.04 LTS OpenJDK 64bit Java 1.7.0_79 Stash Pull Request Builder 1.7 Against Stash/Bitbucket v4.4.1 The timeout is due to an issue on the bitbucket end but it shouldn't be causing a build to be queued. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title dan turner commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build bump, just spent 1/2 a day looking for this! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-43078 Admin users could be defined as organization*team too Change By: Sam Gleske Environment: Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-43078 Admin users could be defined as organization*team too Change By: Sam Gleske Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful. edit: migrated description from environment by [~sag47] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske commented on JENKINS-43078 Re: Admin users could be defined as organization*team too I think the GitHub Committer Authorization Strategy needs a complete overhaul. The way I'd like to see it done is akin to the matrix based authorization strategy but allowing users to define what Jenkins permissions a user gets based on their access to a repository. I don't really have off-hours time to commit at the moment to perform such an overhaul. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43066) With pipeline, tools does not setup properly the environment
Title: Message Title Sébastien Bro commented on JENKINS-43066 Re: With pipeline, tools does not setup properly the environment I'm facing the same issue with the standard Jenkins jobs. NodeJS is not added to the path while checking "Provide Node & npm bin/ folder to PATH" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23251) BUILD_USER_ID is not set when the build is fired using the API
Title: Message Title Marcin Zajączkowski commented on JENKINS-23251 Re: BUILD_USER_ID is not set when the build is fired using the API Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 . However, a build cause doesn't know about triggering user when a token is used and only "remoteTrigger" dummy username is set. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort closed an issue as Not A Defect Jenkins / JENKINS-43092 Jenkins stages executions hangs when creating stages dynamically Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort commented on JENKINS-43092 Re: Jenkins stages executions hangs when creating stages dynamically Fahd Arshad It is not supported to run pipeline steps inside NonCPS blocks – this is in the pipeline docs, but the explanation here (best practices, bullet point 3c) is probably the most concise explanation. If you attempt to run steps inside a NonCPS block it is not guaranteed or even expected to work correctly, and hangs like this are merely one possibility. Remove the all the enclosing @NonCPS functions when dynamically defining stages and it should work (you can call out to NonCPS functions within that). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-43092 Jenkins stages executions hangs when creating stages dynamically Change By: Sam Van Oort Component/s: pipeline-stage-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25199) Build user variables not supported for Auto triggered jobs
Title: Message Title Marcin Zajączkowski commented on JENKINS-25199 Re: Build user variables not supported for Auto triggered jobs Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43090) Set BUILD_USER_ID for anonymous user
Title: Message Title Marcin Zajączkowski commented on JENKINS-43090 Re: Set BUILD_USER_ID for anonymous user Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43093) Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set
Title: Message Title Tatiana Didik created an issue Jenkins / JENKINS-43093 Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set Issue Type: Improvement Assignee: Tatiana Didik Components: sonar-gerrit-plugin Created: 2017/Mar/24 3:42 PM Priority: Minor Reporter: Tatiana Didik If Gerrit change number and patchset numer are not set build will be failed with NPE exception. (Example: if build is not triggered by Gerrit but started manually by button "Build now") Replace it with corresponding messages java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:542) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.plugins.sonargerrit.SonarToGerritPublisher.perform(SonarToGerritPublisher.java:237) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)
[JIRA] (JENKINS-29253) Please set BUILD_USER to 'timer' for scheduled jobs
Title: Message Title Marcin Zajączkowski commented on JENKINS-29253 Re: Please set BUILD_USER to 'timer' for scheduled jobs Fix provided in https://github.com/jenkinsci/build-user-vars-plugin/pull/13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29253) Please set BUILD_USER to 'timer' for scheduled jobs
Title: Message Title Marcin Zajączkowski assigned an issue to Marcin Zajączkowski Jenkins / JENKINS-29253 Please set BUILD_USER to 'timer' for scheduled jobs Change By: Marcin Zajączkowski Assignee: Marcin Zajączkowski Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title Martin Sander commented on JENKINS-36765 Re: Pipeline: Send notification "Back to normal" state Jan Viktorin: The attached code snippet is for the Pipeline Plugin, see e.g. https://jenkins.io/solutions/pipeline/. Your snippet seems to be using the "declarative pipeline" from the Pipeline Model Definition Plugin, which is not the same. The latter is supposed to be easier to use, but less powerful. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title Martin Sander edited a comment on JENKINS-36765 Re: Pipeline: Send notification "Back to normal" state [~jviki]:The attached code snippet is for the [Pipeline Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin], see e.g. https://jenkins.io/solutions/pipeline/.Your snippet seems to be using the "declarative pipeline" from the [Pipeline Model Definition Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin], which is not the same. The latter is supposed to be easier to use, but less powerful. Maybe you are looking for https://jenkins.io/blog/2017/02/15/declarative-notifications/. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title
Fahd Arshad created an issue
Jenkins / JENKINS-43092
Jenkins stages executions hangs when creating stages dynamically
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline, pipeline-stage-view-plugin
Created:
2017/Mar/24 3:02 PM
Environment:
2.32.3
Labels:
pipeline pipeline-stage-view shell shell-command steps
Priority:
Minor
Reporter:
Fahd Arshad
i have created a groovy closure inside a jenkinsfile like:
job {
stage1 = sh "something"
stage2 = sh "something2"
}
Using Jenkins global libraries i read the closure and create different stages by dynamically counting the number of times 'stage' word was used For each stage i use the "sh" command to run a script. The problem i am facing is, once a stage is created and the shell script runs inside the stage, even after the shell script exits jenkins does not move on to creating the next stage instead it hangs on the same stage. job.groovy
#!groovy def call(body) {
def args = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = args
body()
// Loading jenkins jenkinsLibrary
def lib =
[JIRA] (JENKINS-39207) "RSS for all" shows only a few builds
Title: Message Title Peter Goins edited a comment on JENKINS-39207 Re: "RSS for all" shows only a few builds I have the same problem. I first noticed something Removing my comment - my issue was wrong because the weather icon with missing metrics settings for one of our folders was Sunny (some builds have recently broken) and hovering over it didn't provide any summary on the ~15 projects within the a folder. When I looked at the "RSS for all", it only showed 21 builds across 9 of the projects.I renamed one of the earlier projects shortly after creating it, but there was already some build history. Perhaps that project rename corrupted something? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37203) "Override Authentication Token?" do not work
Title: Message Title Peter Tierno commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Alexandru Calistru I dont have a deadline. time for this has been limited. pr's are welcome. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37203) "Override Authentication Token?" do not work
Title: Message Title Peter Tierno commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Vaclav Adamec yes, i do. time has been an issue though. pr's are welcome. ideally i would like to create a legitimate pipeline step for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43091 Re: Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/a591b57c1a82f70128a685f724672b6411e4000a Log: JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43091 Re: Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/5e653988a136a0f2d73105390a78ec617f89dc9d Log: Merge pull request #72 from fbelzunc/JENKINS-43091 [FIXED JENKINS-43091] Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Compare: https://github.com/jenkinsci/active-directory-plugin/compare/847ace3121c2...5e653988a136 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/active-directory-plugin/pull/72 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2017/Mar/24 2:42 PM Priority: Minor Reporter: Félix Belzunce Arcos After restart, we are seeing: INFO: Started termination Mar 24, 2017 12:47:07 PM jenkins.model.Jenkins$21 onTaskFailed SEVERE: Failed ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors com.google.inject.ConfigurationException: Guice configuration errors: 1) Could not find a suitable constructor in hudson.plugins.active_directory.ActiveDirectorySecurityRealm. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private. at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.class(ActiveDirectorySecurityRealm.java:108) while locating hudson.plugins.active_directory.ActiveDirectorySecurityRealm 1 error at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1042) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) at jenkins.ProxyInjector.getInstance(ProxyInjector.java:98) at hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:124) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at jenkins.model.Jenkins$20.execute(Jenkins.java:3240) at
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos started work on JENKINS-43091 Change By: Félix Belzunce Arcos Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43090) Set BUILD_USER_ID for anonymous user
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-43090 Set BUILD_USER_ID for anonymous user Issue Type: Improvement Assignee: Marcin Zajączkowski Components: build-user-vars-plugin Created: 2017/Mar/24 2:41 PM Environment: 1.5 Priority: Minor Reporter: Marcin Zajączkowski For anonymous user BUILD_USER is set, but BUILD_USER_ID is not. It's problematic in places which use BUILD_USER_ID. ID should be set to "anonymous" which is a reserved username in Jenkins. Add Comment
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42831 Re: Enable StartTls is always TRUE in the UI Code changed in jenkins User: Emilio Escobar Path: src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/configAdvanced.jelly http://jenkins-ci.org/commit/active-directory-plugin/acfe14518fdb38a3eea2a00f0a05de60bc31ea18 Log: [FIXED JENKINS-42831] should be default instead of checked Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35185) Trigger github multi-branch build via SQS
Title: Message Title
Idikoro Eradiri commented on JENKINS-35185
Re: Trigger github multi-branch build via SQS
the flow looks like this: github -> SNS -> SQS -> jenkins and this is the Jenkinsfile I used in my repo for the multibranch pipeline
pipeline {
agent any
triggers {
githubPush()
}
stages {
stage(do something') {
steps {
echo 'hello'
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42969) Computer.addAction will throw UnsupportedOperationException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42969 Re: Computer.addAction will throw UnsupportedOperationException Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/model/labels/LabelAtom.java test/src/test/java/hudson/model/ComputerTest.java http://jenkins-ci.org/commit/jenkins/838357700d3173380170ecb28f131a554da0af63 Log: [FIXED JENKINS-42969] UnsupportedOperationException from Computer.addAction. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
