[JIRA] (JENKINS-59541) Multijob plugin: Prints "java.lang.NullPointerException" when trying to start a disabled job
Title: Message Title Dirk Heinrichs commented on JENKINS-59541 Re: Multijob plugin: Prints "java.lang.NullPointerException" when trying to start a disabled job Any news here? It's still confusing people. 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.202170.1569497187000.4975.1576051140267%40Atlassian.JIRA.
[JIRA] (JENKINS-59656) executors widget makes it easy to interrupt the wrong build
Title: Message Title Thomas de Grenier de Latour updated JENKINS-59656 Fixed via PR #4264, should be released in 2.209. Jenkins / JENKINS-59656 executors widget makes it easy to interrupt the wrong build Change By: Thomas de Grenier de Latour 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 jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-55311) Blue Ocean: Pipeline editor always assumes "main" branch is named master
Title: Message Title Dirk Heinrichs commented on JENKINS-55311 Re: Blue Ocean: Pipeline editor always assumes "main" branch is named master This is heading towards its first anniversary. Any news? 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.196398.1545482632000.4973.1576051080465%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Hemnaath Govartan commented on JENKINS-60334 Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing Hi Ted Xiao, Thanks for guiding me on this, now I am able to install the plugin and communicate with Splunk instance from Jenkins by clicking the Test Connection. But now I am facing another issue, as per the documentation I have configured the Jenkins plugin for meta data, but unable to see any data via Splunk App for Jenkins. I had followed the below steps. Steps: Installed Java 1.8 version in 64 bit Windows Platform. Installed Jenkins-2.190.3 in 64 bit windows Platform. Splunk Enterprise 7.3 (Single instance deployment method). Installed Splunk App for Jenkins 2.0. Created HEC token in splunk. Configured Splunk plugin for Jenkins. Test Connection --> Splunk connection Verified. Validating the connection checking the Splunk console and able to see the below events information when we perform "Test Connection" 12/9/19 10:04:25.036 PM ping from jenkins plugin raw event ping host = x source = http:jenkins sourcetype = text:jenkins Configured custom metadata --> Data Source --> Build Event Config Item --> Index Value --> Customer_index Could you please throw some lights on this or let me know from where I can trouble shoot 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
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Nico Prediger commented on JENKINS-60393 Re: cloudbees-folder circular dependency My Jenkins instances can also start, yet when I try to create a new folder, I get an IllegalStateExcaption, which I_think_ may be caused by this error? ```java.lang.IllegalStateException at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.get(AbstractFolderConfiguration.java:26) at com.cloudbees.hudson.plugins.folder.AbstractFolder.init(AbstractFolder.java:293) at com.cloudbees.hudson.plugins.folder.Folder.init(Folder.java:115) at com.cloudbees.hudson.plugins.folder.Folder.(Folder.java:104) at com.cloudbees.hudson.plugins.folder.Folder$DescriptorImpl.newInstance(Folder.java:374) at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:316) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:205) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3940) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:312) at hudson.model.AllView.doCreateItem(AllView.java:99) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) [...] ``` Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Reinhold Füreder commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Thanks again Devin Nusbaum! And following your advice => JENKINS-60434 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.169794.1460663849000.4879.1576045681428%40Atlassian.JIRA.
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-60434 "Prepare for shutdown" should continue executing already running pipelines to completion Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-12-11 06:26 Priority: Major Reporter: Reinhold Füreder Based on Devin Nusbaum's comment from JENKINS-34256: A fix for this issue was just released in Pipeline: Groovy Plugin version 2.78. I think there is/was some confusion as to the expected behavior (myself included!), so let me try to clarify: When Jenkins prepares for shutdown, all running Pipelines are paused, and this is the intended behavior. The unintended behavior was that if you canceled shutdown, Pipelines remained paused. This has been fixed in 2.78; Pipelines will now resume execution if shutdown is canceled. Before 2.78, you had to manually pause and unpause each Pipeline to get it to resume execution, or restart Jenkins. Additionally, preparing Jenkins for shutdown and canceling shutdown now each cause a message to be printed to Pipeline build logs indicating that the Pipeline is being paused or resumed due to shutdown so that it is easier to understand what is happening. Based on comments here and elsewhere, I think some users would prefer a variant of "Prepare for shutdown" in which Pipelines continue executing to completion, the same as other types of jobs like Freestyle. If that is something you want, please open a new ticket, describing your use case and the desired behavior. [...] If there is some other aspect of this issue that you would like to see addressed, or a different behavior you would prefer, please open a new ticket describing your
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Reinhold Füreder commented on JENKINS-60393 Re: cloudbees-folder circular dependency Naive question: My Jenkins server was starting up fine => is downgrading strictly necessary so that "Folder" job etc is working? 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.203447.1575664332000.4875.1576043880428%40Atlassian.JIRA.
[JIRA] (JENKINS-59261) Remote console output treated as JSON array
Title: Message Title Dennis Keitzel commented on JENKINS-59261 Re: Remote console output treated as JSON array Helena Butow: Thank you, this sounds indeed very promising! 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.201729.1567755822000.4869.1576043880340%40Atlassian.JIRA.
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder commented on JENKINS-60411 Re: Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. Duplicate of JENKINS-60393, I guess 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.203468.1575917826000.4865.1576043760178%40Atlassian.JIRA.
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder commented on JENKINS-60411 Re: Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. After updating some plugins (cloudbees-folder:6.10.0, branch-api:2.5.5, workflow-api:2.38) and restarting afterwards => naively guessing "cloudbees-folder:6.10.0" (from v6.9) is the culprit: ... 2019-12-11 05:43:27.054+ [id=36]INFOjenkins.InitReactorRunner$1#onAttained: Started all plugins 2019-12-11 05:43:27.505+ [id=33]INFOh.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping 2019-12-11 05:43:27.520+ [id=33]INFOh.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping 2019-12-11 05:43:27.521+ [id=33]WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:194) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.(AbstractFolderConfiguration.java:36) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration$$FastClassByGuice$$2295d22e.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at
[JIRA] (JENKINS-60411) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface.
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-60411 Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. Change By: Reinhold Füreder Component/s: cloudbees-folder-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.203468.1575917826000.4859.1576043640294%40Atlassian.JIRA.
[JIRA] (JENKINS-60433) Version 1.80.0 throws JEP-200 error
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-60433 Version 1.80.0 throws JEP-200 error Issue Type: Bug Assignee: evernat Components: monitoring-plugin Created: 2019-12-11 05:41 Environment: Monitoring plugin 1.80.0 Jenkins 2.190.2 Priority: Major Reporter: Owen Mehegan Upon startup with Monitoring plugin version 1.80.0, Jenkins logs this error: WARNING jenkins.security.ClassFilterImpl#notifyRejected: net.bull.javamelody.internal.model.HsErrPid in file:/var/cache/jenkins/plugins/monitoring/WEB-INF/lib/javamelody-core-1.80.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ Apparently the latest release of the plugin has run afoul of the JEP-200 whitelist requirements. Add Comment
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal updated an issue Jenkins / JENKINS-60418 issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Change By: vikas goyal Priority: Minor Blocker 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.203480.1575978042000.4854.1576042501033%40Atlassian.JIRA.
[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue
Title: Message Title Roy Lu commented on JENKINS-60395 Re: ALM jenkins plugin: ALM results upload issue Could you please send me the console output of the 1st and 2nd job by email? 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.203449.1575673998000.4797.1576030440192%40Atlassian.JIRA.
[JIRA] (JENKINS-60432) Bitbucket ignore Jenkinsfile checkout for merge conflicted PRs
Title: Message Title Caleb Mayeux commented on JENKINS-60432 Re: Bitbucket ignore Jenkinsfile checkout for merge conflicted PRs In our case we have a large repo being used for gitops style work that's constantly bombarded with PR's from automated systems, many of which end up in conflicts and sit for some time. These unfortunate design choices end up causing scores of gigabyte sized clones on the master, which are threatening to fill up the Jenkins master's home directory. Resolving this issue would eliminate all that wasted space and also fail faster for merge conflicts. 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.203504.1576026617000.4795.1576026780048%40Atlassian.JIRA.
[JIRA] (JENKINS-60432) Bitbucket ignore Jenkinsfile checkout for merge conflicted PRs
Title: Message Title Caleb Mayeux created an issue Jenkins / JENKINS-60432 Bitbucket ignore Jenkinsfile checkout for merge conflicted PRs Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-12-11 01:10 Environment: Jenkins 2.176.4 bitbucket-branch-source-plugin 2.5.0 Priority: Minor Reporter: Caleb Mayeux The bitbucket-branch-source-plugin creates a full clone on the master of repos when trying to build PRs that are in a conflicted state, taking up potentially lots of space depending on the number of outstanding merge conflicts and the size of the repo. The bitbucket-branch-source-plugin attempts to do a lightweight checkout of the Jenkinsfile on the master, and failing that falls back to a full clone. The logic being used in the case of PRs is to do a GET to the Bitbucket rest api to retrieve the Jenkinsfile. However, in the case of a PR that is in a merge conflict state, that api endpoint does not exist (which makes sense because there is no merged codebase) resulting in a heavyweight clone on the master. The end result is the Jenkinsfile is still not obtained via the heavyweight clone because the merge of the code can't happen locally on the Jenkins agent, so the heavyweight fallback in this case is spending time and resources doing a clone, and if you have a large repo it consumes a lot of space on the master for indefinite periods of time if nobody cleans up the or fixes the merge conflicted PRs. I believe a good solution would be for PRs to first do a rest call to the Bitbucket api to check that the PR is not in a merge conflict state before attempting to checkout the Jenkinsfile.
[JIRA] (JENKINS-60431) Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored
Title: Message Title ovi craciun created an issue Jenkins / JENKINS-60431 Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored Issue Type: Bug Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 2019-12-11 00:33 Environment: Jenkins ver. 2.190.3 installed on Windows 2016 Priority: Critical Reporter: ovi craciun The option "Cancel outdated jobs?" although selected in "Bitbucket Pull Requests Builder" settings section is not honored. The build in progress is not cancelled by a new commit for the same PR, even worse, a new build is never triggered, so the PR gets approved although the latest commit was not built Add Comment
[JIRA] (JENKINS-53321) Test functioning across restarts
Title: Message Title Alex Earl commented on JENKINS-53321 Re: Test functioning across restarts Jesse Glick I'm pretty new to the RestartableJenkinsRule tests, does this test actually test what you are looking for? https://github.com/slide/webhook-step-plugin/blob/JENKINS-53321/src/test/java/org/jenkinsci/plugins/webhookstep/WaitForWebhookRestartTest.java 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.193402.1535548072000.4770.1576020660183%40Atlassian.JIRA.
[JIRA] (JENKINS-57472) Parameterized Trigger: incorrectly sets node label to master if node disconnects
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-57472 Parameterized Trigger: incorrectly sets node label to master if node disconnects Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Parameterized Trigger 2.36 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.199332.1557867776000.4767.1576020180485%40Atlassian.JIRA.
[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job
Title: Message Title Oleg Nenashev updated JENKINS-57442 Jenkins / JENKINS-57442 Parameterized Trigger Plugin should print link to running job Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Parameterized Trigger 2.36 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.199255.1557794112000.4765.1576020180444%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Rob Petti updated an issue Jenkins / JENKINS-60430 stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Change By: Rob Petti Component/s: p4-plugin Component/s: perforce-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.203502.1576019104000.4758.1576019220340%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Rob Petti commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) perforce-plugin is deprecated, and it looks like you are using p4-plugin anyway. Please double check the plugin name before filing tickets in the future. 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.203502.1576019104000.4763.1576019280115%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-60430 stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Change By: Rob Petti Assignee: Rob Petti 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.203502.1576019104000.4761.1576019220385%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Eric Daigneault created an issue Jenkins / JENKINS-60430 stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Issue Type: Bug Assignee: Rob Petti Attachments: image-2019-12-10-17-53-47-541.png Components: perforce-plugin Created: 2019-12-10 23:05 Priority: Major Reporter: Eric Daigneault We had setup our sync to use AutoCleanImpl As the sync method for our project but noticed that when we stopped a job that was in the process of reconcile the job in Jenkins would stop normally but the agent would carry on with the reconcile. Here is a stack trace obtained by monitoring an agent that was effectively idle on which we had just cancelled a job during a reconcile : pool-1-thread-146 for JNLP4-connect connection to jenkis-server-url/10.144.6.28:20555 id=17503 java.io.WinNTFileSystem.list(Native Method) java.io.File.list(File.java:1134) java.io.File.listFiles(File.java:1219) com.perforce.p4java.impl.mapbased.rpc.func.client.ClientSystemFileMatchCommands.traverseDirs(ClientSystemFileMatchCommands.java:726) com.perforce.p4java.impl.mapbased.rpc.func.client.ClientSystemFileMatchCommands.traverseDirs(ClientSystemFileMatchCommands.java:790) com.perforce.p4java.impl.mapbased.rpc.func.client.ClientSystemFileMatchCommands.traverseDirs(ClientSystemFileMatchCommands.java:790) com.perforce.p4java.impl.mapbased.rpc.func.client.ClientSystemFileMatchCommands.traverseDirs(ClientSystemFileMatchCommands.java:790) com.perforce.p4java.impl.mapbased.rpc.func.client.ClientSystemFileMatchCommands.traverseDirs(ClientSystemFileMatchCommands.java:790)
[JIRA] (JENKINS-60429) Replace @ symbol in workspace suffix path for parallel builds
Title: Message Title Nicolas Hess created an issue Jenkins / JENKINS-60429 Replace @ symbol in workspace suffix path for parallel builds Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-12-10 22:50 Environment: Confirmed with Jenkins 2.204 with default docker image. Agents on CentOS7 and Ubuntu-16.04/18.04 Priority: Minor Reporter: Nicolas Hess Hi all, When Jenkins runs the same job in parallel, it creates a new folder and add the suffix @2, @3 and so on. This is great and allows us to runs multiple things with different parameter without interrupting or waiting for the previous build (either in multi-branch pipeline or freestyle job). However a few compilers or build tools don't appreciate when the path contains the '@' character (like yocto, fern for selinux or more recently proguard). Thereby, some Jenkinsfile have to use a few more line to replace @ symbol from current workspace and then execute everything inside in a second stage. As it happened for different tools and must be constraining for other people, I'd like to see if Jenkins can update the suffix from @ symbol to something else? Personally I replace @ to __ (double underscores) and it's been working well so far. Thank you!
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Dean Smith commented on JENKINS-60409 Re: Cloud Configuration Length Cap We have also been experiencing the same error when replaying builds since 2.205. It seems to only be for jobs with a large Jenkinsfile (84,100 characters/ ~1800 lines) but not jobs with smaller Jenkinsfiles, although even the large ones are below 200,000 characters. 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.203466.1575915955000.4745.1576016880150%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release New release is published, please re-check. 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.203491.1575988624000.4742.1576016820147%40Atlassian.JIRA.
[JIRA] (JENKINS-60428) Builds occasionally stuck in envfile loop
Title: Message Title jeanny macasio created an issue Jenkins / JENKINS-60428 Builds occasionally stuck in envfile loop Issue Type: Bug Assignee: Unassigned Components: envfile-plugin Created: 2019-12-10 22:24 Environment: Jenkins version 2.150.1, UP board computer Priority: Major Reporter: jeanny macasio After running command: catkin_make -DCMAKE_BUILD_TYPE=Release run_tests Jenkins processes and only prints the following output infinitely. Several times, the build has ran for over 24 hours printing the same output. [envfile] Reading environment variables from file. [envfile] Path to file: /var/lib/jenkins/EnvironmentVariables.properties [envfile]committer_email=git...@gh.mm.st For example, this is what an infinite output looks like:
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz started work on JENKINS-60421 Change By: Pierre Beitz 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.203493.1575991654000.4739.1576016400416%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz commented on JENKINS-60421 Re: NPE when saving Jenkins configuration if audit console logger is added in JCASC Alexander Smirnov I reproduced the issue and started working on a fix. Issue is bigger than you though as currently the plugin won't perform correctly if configured with JCASC only (no remaining audit-trail xml on disk, and that even if the UI in the global config looks ok). I have a working fix, but I want to double check all the use cases and writing non regression tests... I hope to commit something within the week. 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.203493.1575991654000.4737.1576016400141%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-60421 NPE when saving Jenkins configuration if audit console logger is added in JCASC Change By: Pierre Beitz Priority: Minor Blocker 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.203493.1575991654000.4735.1576016280335%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Devin Nusbaum edited a comment on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines A fix for this issue was just released in Pipeline: Groovy Plugin version 2.78. I think there is/was some confusion as to the expected behavior (myself included!), so let me try to clarify: When Jenkins prepares for shutdown, all running Pipelines are paused, and this is the intended behavior. The unintended behavior was that if you canceled shutdown, Pipelines remained paused. This has been fixed in 2.78; Pipelines will now resume execution if shutdown is canceled. Before 2.78, you had to manually pause and unpause each Pipeline to get it to resume execution, or restart Jenkins. Additionally, preparing Jenkins for shutdown and canceling shutdown now each cause a message to be printed to Pipeline build logs indicating that the Pipeline is being paused or resumed due to shutdown so that it is easier to understand what is happening. Based on comments here and elsewhere, I think some users would prefer a variant of "Prepare for shutdown" in which Pipelines continue executing to completion, the same as other types of jobs like Freestyle. If that is something you want, please open a new ticket, describing your use case and the desired behavior.For anyone curious as to why Pipelines are paused when Jenkins prepares for shutdown, instead of continuing to execute and only saving at the last possible second when Jenkins is stopped, the reasoning is to avoid race conditions saving Pipeline metadata that could prevent Pipelines from resuming correctly.If there is some other aspect of this issue that you would like to see addressed, or a different behavior you would prefer, please open a new ticket describing your particular use case.Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Devin Nusbaum updated JENKINS-34256 Jenkins / JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.78 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.169794.1460663849000.4597.1576014544889%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Devin Nusbaum commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines A fix for this issue was just released in Pipeline: Groovy Plugin version 2.78. I think there is/was some confusion as to the expected behavior (myself included!), so let me try to clarify: When Jenkins prepares for shutdown, all running Pipelines are paused, and this is the intended behavior. The unintended behavior was that if you canceled shutdown, Pipelines remained paused. This has been fixed in 2.78; Pipelines will now resume execution if shutdown is canceled. Before 2.78, you had to manually pause and unpause each Pipeline to get it to resume execution, or restart Jenkins. Based on comments here and elsewhere, I think some users would prefer a variant of "Prepare for shutdown" in which Pipelines continue executing to completion, the same as other types of jobs like Freestyle. If that is something you want, please open a new ticket, describing your use case and the desired behavior. For anyone curious as to why Pipelines are paused when Jenkins prepares for shutdown, instead of continuing to execute and only saving at the last possible second when Jenkins is stopped, the reasoning is to avoid race conditions saving Pipeline metadata that could prevent Pipelines from resuming correctly. If there is some other aspect of this issue that you would like to see addressed, or a different behavior you would prefer, please open a new ticket describing your particular use case. 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
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Added you both to PR. 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.203491.1575988624000.4525.1576013940149%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Ok, I tested locally and haven't seen any issues creating BB/GH orgs. I will release soon, could you please re-test? 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.203491.1575988624000.4522.1576013280182%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Michel Zanini commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release I agree. Option 2 should be ok. 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.203491.1575988624000.4515.1576012020146%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Thanks for your feedback Victor, let's wait for Michel and then I will do changes and release. 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.203491.1575988624000.4507.1576010880142%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Matt Sicker commented on JENKINS-59107 Re: User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) I've isolated this problem to the code in UserSeedSecurityListener.authenticated() which will overwrite the current session's user seed with the authorized user's seed instead. This seed is not restored after the build completes (or ever), so essentially, you end up with the authorize user's session which doesn't 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.201530.1566934526000.4511.1576011000252%40Atlassian.JIRA.
[JIRA] (JENKINS-60427) Fix deadlock introduced by JENKINS-57232
Title: Message Title Pierre Beitz resolved as Fixed Jenkins / JENKINS-60427 Fix deadlock introduced by JENKINS-57232 Change By: Pierre Beitz 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 https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203499.1576010318000.4501.1576010700177%40Atlassian.JIRA.
[JIRA] (JENKINS-60427) Fix deadlock introduced by JENKINS-57232
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-60427 Fix deadlock introduced by JENKINS-57232 Change By: Pierre Beitz Labels: 3.1-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 https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203499.1576010318000.4502.1576010700258%40Atlassian.JIRA.
[JIRA] (JENKINS-60427) Fix deadlock introduced by JENKINS-57232
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-60427 Fix deadlock introduced by JENKINS-57232 Issue Type: Task Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-12-10 20:38 Priority: Blocker Reporter: Pierre Beitz JENKINS-57232 introduced a potential deadlock as it is initialized the AuditTrailFilter on PLUGINS_PREPARED instead of EXTENSION_PREPARED. "CustomOrganizationFolderDescriptor.addSpecificDescriptors":"CustomOrganizationFolderDescriptor.addSpecificDescriptors": at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xd5d1d408> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at com.google.inject.internal.CycleDetectingLock$CycleDetectingLockFactory$ReentrantCycleDetectingLock.lockOrDetectPotentialLocksCycle(CycleDetectingLock.java:160) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:136) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at
[JIRA] (JENKINS-60427) Fix deadlock introduced by JENKINS-57232
Title: Message Title Pierre Beitz started work on JENKINS-60427 Change By: Pierre Beitz 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.203499.1576010318000.4500.1576010340277%40Atlassian.JIRA.
[JIRA] (JENKINS-57079) pass token as registerWebhook Step argument
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-57079 pass token as registerWebhook Step argument Change By: Alex Earl Assignee: Chris Pitman 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.198822.1555499262000.4498.1576010040974%40Atlassian.JIRA.
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-59808 Jenkins PR(pull request) build fails for 1st time Change By: Alex Earl Component/s: webhook-step-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.202539.1571256507000.4495.1576010040655%40Atlassian.JIRA.
[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title
Nick Jones commented on JENKINS-54278
Re: Pipeline builds fail when cleanWs() in post stage
Aha – in my case the answer was that an error was being thrown by the build before it got into the pipeline stages, specifically by a credentials('SOME_ID') command being used in a root-level environment block, for a credential ID that didn't exist. This failed the build immediately, but because cleanWS() was in an always block, it tried to execute it, and the agent node hadn't actually been (fully?) allocated yet, hence this error. The error obscured the true root cause, and arguably cleanWs() could have been more tolerant of these conditions rather than throwing, but at least I have an explanation 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.194924.1540578037000.4482.1576008960496%40Atlassian.JIRA.
[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Nick Jones commented on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage Same issue here, under Jenkins 2.190.3 LTS and Workspace Cleanup 0.37, on a Windows Server agent. These are the first builds of a multibranch pipeline on this particular Jenkins instance, filtered to build only a specific PR, and that same PR (thus with the same Jenkinsfile) has been building successfully on a separate Jenkins instance running all the same versions of plugins, etc. A workspace is actually being allocated on the expected node, but cleanWS() still throws this no matter how many times I restart the job. 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.194924.1540578037000.4469.1576008240500%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title
René Scheibe edited a comment on JENKINS-60393
Re: cloudbees-folder circular dependency
Note for plugin developers: The stacktrace can simply be reproduced by running "{{mvn hpi:run}}" on the source code using the "cloudbees-folder-6.10.0" tag. I quick check shows that this issue was introduced in https://github.com/jenkinsci/cloudbees-folder-plugin/commit/25872b140d135f46d7169571e4a5300e51114bac.
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.203447.1575664332000.4440.1576004760410%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Victor Martinez commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release For some reason when I created that PR I though the annotation https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/5/files#diff-23463add934ca349639c9de7d8e2R66 was intended to help with this. Good to know for the future. Sorry about that, I'd say option 2) could be more beneficial. 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.203491.1575988624000.4435.1576004700268%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title
René Scheibe edited a comment on JENKINS-60393
Re: cloudbees-folder circular dependency
Note for plugin developers: The stacktrace can simply be reproduced by running "{{mvn hpi:run}}" on the source code using the "cloudbees-folder-6.10.0" tag. I quick check shows that this issue was introduced in [ https://github.com/jenkinsci/cloudbees-folder-plugin/commit/25872b140d135f46d7169571e4a5300e51114bac ] .
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.203447.1575664332000.4442.1576004760438%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title René Scheibe commented on JENKINS-60393 Re: cloudbees-folder circular dependency Note for plugin developers: The stacktrace can simply be reproduced by running "mvn hpi:run" on the source code using the "cloudbees-folder-6.10.0" tag. 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.203447.1575664332000.4402.1576004160707%40Atlassian.JIRA.
[JIRA] (JENKINS-60405) Owner 'xyz' is neither a user/group/subgroup
Title: Message Title Bert Oost commented on JENKINS-60405 Re: Owner 'xyz' is neither a user/group/subgroup I have tried downgrading the plugin to 1.2 and even downgraded Jenkins itself, but nothing was working. Probably something has changed in the Gitlab API why this isn't working anymore. Please help. This is causing all my Gitlab projects not building anymore (even not showing up in Jenkins) 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.203460.1575905424000.4411.1576004160893%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Erez Arbell commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Not working. I ran: def lib = library( identifier : '@3216471',retriever: modernSCM(globalLib(charset: 'none', credential: env.P4_CREDENTIAL, id: '9bb4320c-c31c-46ce-8c5f-68872f519067', path: args.p4Mapping))) and got error: (p4):cmd:... p4 sync -q /home/jenkins/.jenkins/workspace/test-p4%40libs/...#none p4 sync -q /home/jenkins/.jenkins/workspace/test-p4%40libs/...#none (p4):stop:9 ... rm -rf /home/jenkins/.jenkins/workspace/test-p4@libs P4 Task: syncing files at change: -1 (p4):cmd:... p4 sync -f -q /home/jenkins/.jenkins/workspace/test-p4%40libs/...@-1 p4 sync -f -q /home/jenkins/.jenkins/workspace/test-p4%40libs/...@-1 Invalid changelist/client/label/date '@-1'. (p4):stop:10 P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): Invalid changelist/client/label/date '@-1'. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-60393
cloudbees-folder circular dependency
Change By:
René Scheibe
Seeing the following in my Jenkins log as a stacktrace :{code}2019-12-06 19:26:29.676+ [id=29] WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:193) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.(AbstractFolderConfiguration.java:36) at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration$$FastClassByGuice$$2295d22e.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68) at
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-60393
cloudbees-folder circular dependency
Change By:
René Scheibe
Seeing the following in my jenkins Jenkins log as a stacktrace : { { code} 2019-12-06 19:26:29.676+ [id=29] WARNING h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration, annotation=[none]]; skipping this component }} {{ com.google.inject.ProvisionException: Unable to provision, see the following errors: }}{{ 1) Tried proxying com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration to support a circular dependency, but it is not an interface. }}{{ 1 error }} {{ at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) }} {{ at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) }} {{ at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) }} {{ at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) }} {{ at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) }} {{ at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) }} {{ at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) }} {{ at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) }} {{ at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) }} {{ at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) }} {{ at hudson.ExtensionList.load(ExtensionList.java:381) }} {{ at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) }} {{ at hudson.ExtensionList.getComponents(ExtensionList.java:183) }} {{ at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:193) }} {{ at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) }} {{ at hudson.ExtensionList.iterator(ExtensionList.java:172) }} {{ at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.(AbstractFolderConfiguration.java:36) }} {{ at com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration$$FastClassByGuice$$2295d22e.newInstance() }} {{ at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) }} {{ at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) }} {{ at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) }} {{ at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) }} {{ at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89) }} {{ at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115) }} {{ at hudson.ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567)
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: René Scheibe Assignee: Francisco Fernández René Scheibe 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.203447.1575664332000.4366.1576003800430%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title René Scheibe assigned an issue to Unassigned Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: René Scheibe Assignee: René Scheibe 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.203447.1575664332000.4371.1576003800524%40Atlassian.JIRA.
[JIRA] (JENKINS-59261) Remote console output treated as JSON array
Title: Message Title Helena Butow commented on JENKINS-59261 Re: Remote console output treated as JSON array Dennis Keitzel: I think this will be resolved via https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/61 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.201729.1567755822000.4358.1576001280204%40Atlassian.JIRA.
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title Allan Lewis commented on JENKINS-41929 Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found Thanks, Michael Brunner - I've considered doing something similar, except maybe making it SCM-triggered since my pipeline is designed to only be manually triggered. 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.178785.1486740246000.4234.1575999842285%40Atlassian.JIRA.
[JIRA] (JENKINS-23496) Notify user that put slave temporarily offline that it has become idle
Title: Message Title Oliver Gondža commented on JENKINS-23496 Re: Notify user that put slave temporarily offline that it has become idle Kevin Cruise, please file a bug in this component, this is a RFE to introduce that feature. Be sure to specify relevant details. 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.155811.1403205036000.4231.1575999780369%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Erez Arbell commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Thank you. I will try it. How can I get the latest changelist? What is the "id"? 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.190940.1527360591000.4223.1575999540552%40Atlassian.JIRA.
[JIRA] (JENKINS-56000) Pipeline fails if more than 250 parameters specified
Title: Message Title Jan Sprinz commented on JENKINS-56000 Re: Pipeline fails if more than 250 parameters specified This can quickly be caused by matrices. 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.197417.1549481049000.4220.1575999480305%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski edited a comment on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Good morning,Thanks a lot for reporting.I have couple of options:1. Roll back the changes by Victor Martinez [~v2v] and let him create a separate plugin for GitHub Branch Source2. I have a local snapshot which has classes and method names renamed, tried to create GitHub/BitBucket organization and it was successfulWhich way will be preferable for you [~michelzanini]? 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.203491.1575988624000.4218.1575999180772%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Alex Dubrouski commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Good morning, Thanks a lot for reporting. I have couple of options: 1. Roll back the changes by Victor Martinez and let him create a separate plugin for GitHub Branch Source 2. I have a local snapshot which has classes and method names renamed, tried to create GitHub/BitBucket organization and it was successful Which way will be preferable for you Michel Zanini? 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.203491.1575988624000.4216.1575999060208%40Atlassian.JIRA.
[JIRA] (JENKINS-41929) Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Title: Message Title
Michael Brunner commented on JENKINS-41929
Re: Offer "Build with Parameters" on first build when declarative Jenkinsfile found
Here my workaround: I've added pipeline options
skipDefaultCheckout true
and in the first stage the following script
script {
// On first build by user just load the parameters as they are not available of first run on new branches
if (env.BUILD_NUMBER.equals("1") && currentBuild.getBuildCauses('hudson.model.Cause$UserIdCause') != null) {
currentBuild.displayName = 'Parameter loading'
addBuildDescription('Please restart pipeline')
currentBuild.result = 'ABORTED'
error('Stopping initial manually triggered build as we only want to get the parameters')
}
}
So first time pressing the button does not lead to a build but a parameter loading. Perhaps I can find a solution, where it is triggered automatically on branch creation by scm. Any ideas?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-14392) Optional Extensions should be reloaded when dependencies are dynamically loaded
Title: Message Title Jesse Glick commented on JENKINS-14392 Re: Optional Extensions should be reloaded when dependencies are dynamically loaded Or JENKINS-50336? See JENKINS-19508 for general advice. 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.145028.1342028201000.4075.1575998640187%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Patrik Boström edited a comment on JENKINS-60110 Re: Update AWS Java SDK The plugin uses AWS SDK Plugin [https://plugins.jenkins.io/aws-java-sdk] so as long as there is a version of that plugin that bundles AWS Java SDK 1.11.623, or higher the plugin should use that. As long as that version of AWS SDK plugin is installed on your Jenkins the plugin should use that version.The latest version includes 1.11.687 in AWS SDK plugin Please test with latest version of AWS SDK plugin and report back. 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.202956.1573228427000.4072.1575997800138%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Patrik Boström edited a comment on JENKINS-60110 Re: Update AWS Java SDK The plugin uses AWS SDK Plugin [https://plugins.jenkins.io/aws-java-sdk] so as long as there is a version of that plugin that bundles AWS Java SDK 1.11.623, or higher the plugin should use that. As long as that version of AWS SDK plugin is installed on your Jenkins the plugin should use that version. The latest version includes 1.11.687 in AWS SDK 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.202956.1573228427000.4069.1575997740172%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Patrik Boström edited a comment on JENKINS-60110 Re: Update AWS Java SDK The plugin uses AWS SDK Plugin [https://plugins.jenkins.io/aws-java-sdk] so as long as there is a version of that plugin that bundles AWS Java SDK 1.11.623, or higher the plugin should use that.As long as that version of AWS SDK plugin is installed on our your Jenkins the plugin should use that version. 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.202956.1573228427000.4066.1575997500350%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Patrik Boström edited a comment on JENKINS-60110 Re: Update AWS Java SDK The plugin uses AWS SDK Plugin [https://plugins.jenkins.io/aws-java-sdk] so as long as there is a version of that plugin that bundles AWS Java SDK 1.11.623, or higher the plugin should use that. As long as that version of AWS SDK plugin is installed on our Jenkins the plugin should use that version. 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.202956.1573228427000.4064.1575997500282%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Patrik Boström commented on JENKINS-60110 Re: Update AWS Java SDK The plugin uses AWS SDK Plugin https://plugins.jenkins.io/aws-java-sdk so as long as there is a version of that plugin that bundles AWS Java SDK 1.11.623, or higher the plugin should use that. 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.202956.1573228427000.4061.1575997440168%40Atlassian.JIRA.
[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title
Christian Opitz updated an issue
Jenkins / JENKINS-60426
All stages show up as UNSTABLE when one stage is unstable
Change By:
Christian Opitz
In the classical GUI all stages are shown as unstable when only one stage is (in BlueOcean it is displayed correct)My expectation: Only the unstable stage is displayed as unstable, others are not (while the complete build still is marked as unstable) !2019-12-10_17h49_44.png! {code:java}#!groovypipeline { agent anystages {stage('successful') {steps {echo ('hello')}}stage('unstable') {steps {unstable(message: "Failed: ${STAGE_NAME} => return UNSTABLE status")}}}}{code} Potentially related to JENKINS-39203
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
[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title
Christian Opitz created an issue
Jenkins / JENKINS-60426
All stages show up as UNSTABLE when one stage is unstable
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
2019-12-10_17h49_44.png
Components:
pipeline-stage-view-plugin
Created:
2019-12-10 16:52
Environment:
Jenkins 2.176.3, Pipeline Stage View Plugin 2.12
Priority:
Minor
Reporter:
Christian Opitz
In the classical GUI all stages are shown as unstable when only one stage is (in BlueOcean it is displayed correct) My expectation: Only the unstable stage is displayed as unstable, others are not (while the complete build still is marked as unstable)
#!groovy
pipeline {
agent any
stages {
stage('successful') {
steps {
echo ('hello')
}
}
stage('unstable') {
steps {
unstable(message: "Failed: ${STAGE_NAME} => return UNSTABLE status")
}
}
}
}
[JIRA] (JENKINS-60425) Fortify plugin in pipeline executes on master (k8s)
Title: Message Title Steven Deal created an issue Jenkins / JENKINS-60425 Fortify plugin in pipeline executes on master (k8s) Issue Type: Bug Assignee: Anna Karyakina Components: fortify-plugin Created: 2019-12-10 16:49 Priority: Minor Reporter: Steven Deal When using the fortify plugin in a pipeline, it observes the node block to run on Windows agent; however, if the pipeline runs on a k8s pod with the same node block to use the Windows agent, it is ignored and it appears to try to find the Fortify scripts on the master. Add Comment
[JIRA] (JENKINS-60424) logstash-plugin does not work with ElasticSearch 7
Title: Message Title Richard Schaefer created an issue Jenkins / JENKINS-60424 logstash-plugin does not work with ElasticSearch 7 Issue Type: Bug Assignee: Jakub Bochenski Components: logstash-plugin Created: 2019-12-10 16:41 Environment: Jenkins 2.190.2.2, logstash-plugin 2.3.1 Labels: logstash elasticsearch Priority: Major Reporter: Richard Schaefer Ref Jenkins-50562 we configured our Jenkins instance with ES 6 to send logs to the logstash/jenkins index. We're being told we have to migrate to ES 7 but index types were deprecated in ES 7 so logstash/jenkins doesn't work anymore. I tried specifying just a jenkins index but now get the HTTP 405 Invalid Method error. Add Comment
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding edited a comment on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. I imagine any other plugin that uses AWS SDK, including the SSM plugin one, would have the same constraint when used with Cloudbees Core.The SDK downgrade also broke support for fine-grained IAM policies in my plugin . And , and I’ve already received a bug report from a user affected by this.So Cloudbees Core needs its AWS SDK dependency upgraded ASAP, to enable both of our plugins to upgrade in turn. 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.202956.1573228427000.4046.1575995520185%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding edited a comment on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. I imagine the SSM plugin would have the constraint when used with Cloudbees Core. The SDK downgrade also broke support for fine-grained IAM policies in that my plugin. And I’ve already received a bug report from a user affected by this , so this .So Cloudbees Core needs fixing soon its AWS SDK dependency upgraded ASAP, to enable both of our plugins to upgrade in turn . 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.202956.1573228427000.4043.1575995340153%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I have to thank the developers for this. Your definition was mostly correct. For ModernSCM the 'identifier' should be '@' followed by the changelist number. For example: def lib = library( identifier : '@23312',retriever: modernSCM(globalLib(charset: 'none', credential: 'JenkinsMaster', id: '9bb4320c-c31c-46ce-8c5f-68872f519067', path: '//depot/lib_autoload/libs/...'))) Note that it also doesnt allow you to specify the workspace path so I specified the depot path just above 'src' which seems to work for me. 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.190940.1527360591000.4022.1575994620305%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Jorge Cordoba updated JENKINS-60394 Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Jorge Cordoba Status: In Review Resolved 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" 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.203448.1575669122000.4020.1575994500960%40Atlassian.JIRA.
[JIRA] (JENKINS-60394) Can't load http://localhost:8080
Title: Message Title Jorge Cordoba updated JENKINS-60394 Jenkins / JENKINS-60394 Can't load http://localhost:8080 Change By: Jorge Cordoba Status: In Progress Review 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.203448.1575669122000.4018.1575994500753%40Atlassian.JIRA.
[JIRA] (JENKINS-60110) Update AWS Java SDK
Title: Message Title Chris Kilding commented on JENKINS-60110 Re: Update AWS Java SDK I recently got a request to downgrade the AWS SDK dependency on the Secrets Manager Credentials Provider plugin, to make it compatible with Cloudbees Core 2.176.4.3. The SDK downgrade also broke support for fine-grained IAM policies in that plugin. I’ve already received a bug report from a user affected by this, so this needs fixing soon. 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.202956.1573228427000.4016.1575993960357%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title Aleksander Kasprzyk created an issue Jenkins / JENKINS-60423 Powershell fails when the script starts with 'CmdletBinding' attribut Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2019-12-10 15:58 Labels: powershell Priority: Major Reporter: Aleksander Kasprzyk Hi, Since upgrade to the latest version of PowerShell Plugin (1.4) a lot of my scripts does not work any more. Especially when inline or script files starts with the 'CmdletBinding' attribut. [workspace] $ powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File C:\Users\ATHICS~1\AppData\Local\Temp\jenkins8862236051379677851.ps1 Au caractŠre C:\Users\AthicService\AppData\Local\Temp\jenkins8862236051379677851.ps1:3 : 1 + [CmdletBinding()] ~+ ~~ Attribut inattendu ®ÿCmdletBindingÿ¯. Au caractŠre C:\Users\AthicService\AppData\Local\Temp\jenkins8862236051379677851.ps1:4 : 1 + param([switch]$Elevated ~+ ~~ Jeton inattendu ®ÿparamÿ¯ dans l'_expression_ ou l'instruction. + CategoryInfo : ParserError: ( [], ParentContainsErrorRecordException + FullyQualifiedErrorId : UnexpectedAttribute Build step 'PowerShell' marked build as failure As I have a lot of PS scripts like that, I have to downgrade to 1.3 version.
[JIRA] (JENKINS-60422) keep all build history when using jiraSendBuildInfo
Title: Message Title walid boussafa updated an issue Jenkins / JENKINS-60422 keep all build history when using jiraSendBuildInfo Change By: walid boussafa right now, jiraSendBuildInfo only keep the status of the last build.it would be very practical to provide an option to keep all full build history. 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.203494.157599220.4012.1575992280400%40Atlassian.JIRA.
[JIRA] (JENKINS-60422) keep all build history when using jiraSendBuildInfo
Title: Message Title walid boussafa updated an issue Jenkins / JENKINS-60422 keep all build history when using jiraSendBuildInfo Change By: walid boussafa Summary: keep all build history when using jiraSendBuildInfo 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.203494.157599220.4010.1575992221351%40Atlassian.JIRA.
[JIRA] (JENKINS-60422) keep all build history
Title: Message Title walid boussafa created an issue Jenkins / JENKINS-60422 keep all build history Issue Type: Improvement Assignee: Rafal Myslek Components: atlassian-jira-software-cloud-plugin Created: 2019-12-10 15:36 Priority: Major Reporter: walid boussafa right now, jiraSendBuildInfo only keep the status of the last build. it would be very practical to provide an option to keep all build history. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Alexander Smirnov created an issue Jenkins / JENKINS-60421 NPE when saving Jenkins configuration if audit console logger is added in JCASC Issue Type: Bug Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-12-10 15:27 Priority: Minor Reporter: Alexander Smirnov Audit Trail plugin 3.0 is installed in Jenkins 2.190.3. Audit console logger is added in JCASC block: audit-trail: logBuildCause: true loggers: - console: dateFormat: "-MM-dd HH:mm:ss:SSS" logPrefix: "audit" output: STD_OUT pattern: ".*/(?:configSubmit|doDelete|postBuildResult|enable|disable|cancelQueue|stop|toggleLogKeep|doWipeOutWorkspace|createItem|createView|toggleOffline|cancelQuietDown|quietDown|restart|exit|safeExit)" The following exception is thrown when clicking on save or apply button: java.lang.NullPointerException at hudson.plugins.audit_trail.ConsoleAuditLogger.log(ConsoleAuditLogger.java:49) at hudson.plugins.audit_trail.AuditTrailFilter.onRequest(AuditTrailFilter.java:129) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:105) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at
[JIRA] (JENKINS-23496) Notify user that put slave temporarily offline that it has become idle
Title: Message Title Kevin Cruise edited a comment on JENKINS-23496 Re: Notify user that put slave temporarily offline that it has become idle [~olivergondza] This is occurring again no longer working in version 1.16, should this ticket be re-opened or a new one created? 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.155811.1403205036000.4000.1575991020450%40Atlassian.JIRA.
[JIRA] (JENKINS-23496) Notify user that put slave temporarily offline that it has become idle
Title: Message Title Kevin Cruise commented on JENKINS-23496 Re: Notify user that put slave temporarily offline that it has become idle Oliver Gondža This is occurring again in version 1.16, should this ticket be re-opened or a new one created? 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.155811.1403205036000.3996.1575990900312%40Atlassian.JIRA.
[JIRA] (JENKINS-60404) Warning exception after upgrading to Folders 6.10
Title: Message Title Francisco Fernández closed an issue as Duplicate Jenkins / JENKINS-60404 Warning exception after upgrading to Folders 6.10 Change By: Francisco Fernández Status: Open Closed Resolution: Duplicate 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.203459.1575899541000.3992.1575990541010%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Bogomil Vasilev commented on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Yes, the builds continue working as usual. The Node plugin is also working, despite the conversion warning. I just don't know how to fix it in order to suppress the message from showing up. 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.203189.1574194043000.3994.1575990541164%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-59227 Global Pipeline Libraries configuration lost Change By: Devin Nusbaum Component/s: permissive-script-security-plugin Component/s: core Component/s: pipeline 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.201684.1567609146000.3981.1575990180608%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Devin Nusbaum commented on JENKINS-59227 Re: Global Pipeline Libraries configuration lost Based on the comments here, in JENKINS-57171, and JENKINS-59145 (which looks like the same issue but when configuring a Pipeline job from SCM instead of a shared library SCM), the issue seems to be specific to Permissive Script Security 0.5 (I think this is the only change in that release), so I am changing the component. There may be some issue in the interaction between Permission Script Security and Script Security, but I'm not sure. If anyone has any relevant error messages or stack traces in your Jenkins logs, or any error messages in your browser console, that would be helpful. 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.201684.1567609146000.3973.1575990060237%40Atlassian.JIRA.
[JIRA] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build
Title: Message Title Jesse Glick resolved as Won't Fix After JENKINS-39134 we are not using Guice in this way so this is probably obsolete. Jenkins / JENKINS-38354 Failure to resume a wrapper step leads to hanging build Change By: Jesse Glick Status: Open Resolved Assignee: Kohsuke Kawaguchi Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-60404) Warning exception after upgrading to Folders 6.10
Title: Message Title Michel Zanini commented on JENKINS-60404 Re: Warning exception after upgrading to Folders 6.10 This is a duplicate of JENKINS-60393 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.203459.1575899541000.3969.1575988860341%40Atlassian.JIRA.
[JIRA] (JENKINS-20992) possible endless loop getting index for interface hudson.Extension from classLoader hudson.PluginManager$UberClassLoader
Title: Message Title Jesse Glick resolved as Cannot Reproduce Do not recall seeing this recently. Jenkins / JENKINS-20992 possible endless loop getting index for interface hudson.Extension from classLoader hudson.PluginManager$UberClassLoader Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce 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-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Michel Zanini created an issue Jenkins / JENKINS-60420 Skip notifications plugin fails after 1.0.4 release Issue Type: Bug Assignee: Alex Dubrouski Components: skip-notifications-trait-plugin Created: 2019-12-10 14:37 Environment: Install Gihub and Bitbucket on the same Jenkins instance Priority: Minor Reporter: Michel Zanini If you have Github and Bitbucket installed as plugins and you use Skip Notifications Trait you will get this error after `1.0.4` release: ERROR: Found multiple extensions which provide method skipNotificationsTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.notifications.SkipNotificationsTrait, org.jenkinsci.plugins.github.notifications.SkipNotificationsTrait]]
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title
Michel Zanini updated an issue
Jenkins / JENKINS-60420
Skip notifications plugin fails after 1.0.4 release
Change By:
Michel Zanini
If you have Github and Bitbucket installed as plugins and you use Skip Notifications Trait you will get this error after `1.0.4` release: {code:java}ERROR: Found multiple extensions which provide method skipNotificationsTrait with arguments []: [[com.cloudbees.jenkins.plugins.bitbucket.notifications.SkipNotificationsTrait, org.jenkinsci.plugins.github.notifications.SkipNotificationsTrait]]{code} This problem was introduced by this PR:[https://github.com/jenkinsci/skip-notifications-trait-plugin/pull/5]
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-60409) Cloud Configuration Length Cap
Title: Message Title Mahmoud Ksemtini updated an issue Jenkins / JENKINS-60409 Cloud Configuration Length Cap Change By: Mahmoud Ksemtini Attachment: Screenshot 2019-12-10 at 15.27.37.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.203466.1575915955000.3955.1575988140880%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Mahmoud Ksemtini commented on JENKINS-60409 Re: Cloud Configuration Length Cap I get the same error when trying to replay a job from the UI. 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.203466.1575915955000.3958.1575988141370%40Atlassian.JIRA.
