[JIRA] (JENKINS-40348) Support execution of arbitrary scripts
Title: Message Title peter hauschulz commented on JENKINS-40348 Re: Support execution of arbitrary scripts Reference this issue for additional documentation on why having the ability to have custom scripts execute in a customizable order. https://groups.google.com/forum/#!topic/zaproxy-jenkins/4nsxCi-fR0U Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52844) java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps
Title: Message Title tang alby updated JENKINS-52844 Thank you for your attention. I can't reproduce the problem,It's normal now. Jenkins / JENKINS-52844 java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps Change By: tang alby Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-54335 Upstream Downstream Column plugin displays wrong data Change By: Flemming Steffensen Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54593) jenkins is hanging after clean the system cache
Title: Message Title tang alby updated an issue Jenkins / JENKINS-54593 jenkins is hanging after clean the system cache Change By: tang alby I execute the shell to clean system cache when jenkins runing : echo 3 > /proc/sys/vm/drop_cachesI integrated jenkins with ldap.Then, jenkins login UI has been loaded.After a long time, it's logged in. I can click system configration,etc. But can not click enter in a job when is running. After long time,the job build is back to normal.Sometimes ,someone can log in ,it looks nornamls.But others cannot log in.The user interface is always showing calculations. It show Looking forward to your reply~Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54593) jenkins is hanging after clean the system cache
Title: Message Title tang alby updated an issue Jenkins / JENKINS-54593 jenkins is hanging after clean the system cache Change By: tang alby Attachment: web_ui_show.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54593) jenkins is hanging after clean the system cache
Title: Message Title tang alby updated an issue Jenkins / JENKINS-54593 jenkins is hanging after clean the system cache Change By: tang alby I execute the shell to clean system cache when jenkins runing : echo 3 > /proc/sys/vm/drop_cachesI integrated jenkins with ldap.Then, jenkins login UI has been loaded.After a long time, it's logged in. I can click system configration,etc. But can not click enter in a job when is running. After long time,the job build is back to normal.Sometimes ,someone can log in ,it looks nornamls.But others cannot log in.The user interface is always showing calculations. It show Looking forward to your reply~Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54595) Adding a new target is not working
Title: Message Title Aleksi Simell created an issue Jenkins / JENKINS-54595 Adding a new target is not working Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2018-11-13 08:51 Priority: Major Reporter: Aleksi Simell Adding a new InfluxDB target with non-default checkbox values when there is already a target defined will not add a new target, but instead update the existing target's boolean values with the new target's. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan assigned an issue to Xuezhong Yan Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Assignee: Xuezhong Yan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan updated JENKINS-47014 Cannot Reproduce on P4 Plugin 1.9.4, hence close this issue. Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan updated JENKINS-47014 Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan updated an issue Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Comment: Cannot Reproduce on P4 Plugin 1.9.4, hence close this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan reopened an issue Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51838) P4-Plugin: No polling log if Lightweight checkout option is checked
Title: Message Title Xuezhong Yan updated JENKINS-51838 Jenkins / JENKINS-51838 P4-Plugin: No polling log if Lightweight checkout option is checked Change By: Xuezhong Yan Status: Closed Fixed but Unreleased Resolution: Fixed Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51838) P4-Plugin: No polling log if Lightweight checkout option is checked
Title: Message Title Xuezhong Yan closed an issue as Fixed Cannot Reproduce on P4 Plugin 1.9.4, hence close this issue. Jenkins / JENKINS-51838 P4-Plugin: No polling log if Lightweight checkout option is checked Change By: Xuezhong Yan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51838) P4-Plugin: No polling log if Lightweight checkout option is checked
Title: Message Title Xuezhong Yan updated JENKINS-51838 Jenkins / JENKINS-51838 P4-Plugin: No polling log if Lightweight checkout option is checked Change By: Xuezhong Yan Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title Dominik Bartholdi commented on JENKINS-54576 Re: hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder' Mez Pahlan thanks, that works for now Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-11-13-10-19-20-710.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Andrew a edited a comment on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
I've just ran a few regressions with that insanely huge timeout and the bad news is, the problem didn't completely go away. More, 2 different problems have emerged (I'm now not really sure if they are directly related to this issue, or I should open a new ticket. Posting everything here for now)*First one:* I'm now seeing a pipeline freezing AFTER all the tasks under parallel statement have completed. A restart of jenkins causes some of the steps under parallel to be rerun with the following warning:{code:java}Queue item for node block in SoC » RTL_REGRESSION #255 is missing (perhaps JENKINS-34281); rescheduling{code}But the pipeline completes. I'm also seeing runaway simulation processes that have to be killed by hand. Those kept running after the pipeline has been completed, - perhaps due to a master node restart - (and thus preventing further builds in that workspace). Not yet sure how I should debug this one. *Second one:*In an attempt to mitigate another the issue (now with old ctest on RHEL, not always handling timeouts correctly) I've added a timeout() block inside parallel, and that exposed another filesystem/timeout problem: {code :java } Cancelling nested steps due to timeoutSending interrupt signal to processCancelling nested steps due to timeoutAfter 10s process did not stop java.nio.file.FileSystemException: /home/jenkins/ws/BootromSignoff/build@tmp/durable-bcad1b03/.nfs29ee028d2716: Device or resource busy at sun.nio.fs.UnixException.translateToIOException(Unknown Source) at sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at sun.nio.fs.UnixFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source) at java.nio.file.Files.deleteIfExists(Unknown Source) at hudson.Util.tryOnceDeleteFile(Util.java:316) at hudson.Util.deleteFile(Util.java:272) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to taruca at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.deleteRecursive(FilePath.java:1266) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.cleanup(FileMonitoringTask.java:340) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$1.run(DurableTaskStep.java:382) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused: java.io.IOException: Unable to delete '/home/jenkins/ws/BootromSignoff/build@tmp/durable-bcad1b03/.nfs29ee028d2716'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at hudson.Util.deleteFile(Util.java:277) at hudson.FilePath.deleteRecursive(FilePath.java:1303
[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder commented on JENKINS-46715 Re: Error steps may change to show up as errors in pipeline view I have just seen that the same bug seems to pop up also in (one of my few) declarative pipelines: Besides not showing the failing stage in BO, it actually also manifests in stages with 0ms duration in the Stage View (see the three blue lightnings in the screenshot) Today's build (see the second build from top that is highlighted in yellow in the screenshot; mind it was just 2 hours ago) is still OK, but I assume/guess it will show up wrongly tomorrow The last/bottom one is also OK, because it actually failed due to a non-zero exit code in shell script (and not by calling "error" step): [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE => So I guess/claim this bug is somehow related to calling the "error" step explicitly in the pipeline; in my case this happens within a shared pipeline library, but in the example of issue description this was not the case Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/opto
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title py zhu created an issue Jenkins / JENKINS-54596 can't parse argument number: changelog.url Issue Type: Task Assignee: Unassigned Components: core Created: 2018-11-13 09:44 Priority: Minor Reporter: py zhu org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.150.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title py zhu updated an issue Jenkins / JENKINS-54596 can't parse argument number: changelog.url Change By: py zhu Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Oleksandr Perepelytsya commented on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves We're experiencing same issue on Jenkins - v. 2.138.2 / WS-Cleanup plugin - v. 0.34 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54241) Log parser not displaying full log
Title: Message Title Martin Stolle commented on JENKINS-54241 Re: Log parser not displaying full log Looks like the latest update resolved this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54574) Err message if not waiting for job to complete
Title: Message Title Alexander Shcherbakov closed an issue as Fixed Jenkins / JENKINS-54574 Err message if not waiting for job to complete Change By: Alexander Shcherbakov Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54241) Log parser not displaying full log
Title: Message Title Martin Stolle closed an issue as Fixed Jenkins / JENKINS-54241 Log parser not displaying full log Change By: Martin Stolle Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54597) helloooooo
Title: Message Title reu REDDY created an issue Jenkins / JENKINS-54597 helloo Issue Type: Bug Assignee: reu REDDY Components: active-choices-plugin, git-plugin, maven-plugin Created: 2018-11-13 10:16 Priority: Minor Reporter: reu REDDY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54597) helloooooo
Title: Message Title reu REDDY started work on JENKINS-54597 Change By: reu REDDY Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54597) helloooooo
Title: Message Title reu REDDY updated JENKINS-54597 Jenkins / JENKINS-54597 helloo Change By: reu REDDY Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54597) helloooooo
Title: Message Title reu REDDY updated JENKINS-54597 Jenkins / JENKINS-54597 helloo Change By: reu REDDY Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54292) Align/fix the codebase to use flavor everywhere instead of environment
Title: Message Title Baptiste Mathus started work on JENKINS-54292 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54598) Explore JDK11 Upgrade for Evergreen
Title: Message Title Baptiste Mathus assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-54598 Explore JDK11 Upgrade for Evergreen Change By: Baptiste Mathus Assignee: Baptiste Mathus Adrien Lecharpentier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54598) Explore JDK11 Upgrade for Evergreen
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54598 Explore JDK11 Upgrade for Evergreen Issue Type: Task Assignee: Baptiste Mathus Components: evergreen Created: 2018-11-13 10:35 Labels: evergreen Priority: Critical Reporter: Baptiste Mathus The Jenkins Project has started digging more deeply into what is needed to make Jenkins work on JDK11. We should see what it takes to make Evergreen work on JDK11 too. It makes much sense because contrary to the usual Jenkins distro, we can easily specific specific plugin versions, where for instance there's only incremental releases but not common-maven type releases. We most probably want to implement this using a new flavor, like docker-cloud-jdk11 for instance so that we can actually even deploy in production and test it in a normal way without disturbing the other existing flavors. If this proves successful, we can then see how/if we want to propage this to the existing docker-cloud and/or aws-ec2-cloud flavors. Acceptance criteria: A docker-cloud on JDK 11 flavor available for testing using the usual way of starting an Evergreen instance (but using a different Docker image tag) (https://jenkins.io/projects/evergreen/)
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54599 Update Jetty version in Maven Jenkins Dev Plugin (Jetty) Issue Type: Improvement Assignee: Unassigned Components: core, maven-hpi-plugin Created: 2018-11-13 10:38 Priority: Minor Reporter: Oleg Nenashev Apparently Maven Jenkins Dev Plugin still uses old version of Jetty: https://github.com/jenkinsci/maven-hudson-dev-plugin . It is unclear how it impacts Jenkins test suites, but it definitely causes a lot of warnings while developing for Java 11 Add Comment
[JIRA] (JENKINS-54598) Explore JDK11 Upgrade for Evergreen
Title: Message Title Baptiste Mathus commented on JENKINS-54598 Re: Explore JDK11 Upgrade for Evergreen Going to tackle JENKINS-54292 in expedite. Though not technically blocking, it's small enough that it should be done quickly before more people start losing time understanding this "environment" thing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54600) Show a warning when creating a user with a dot
Title: Message Title Marcel Meschenmoser created an issue Jenkins / JENKINS-54600 Show a warning when creating a user with a dot Issue Type: Improvement Assignee: Unassigned Attachments: CreateUser.png, SignUp.png Components: authentication-tokens-plugin Created: 2018-11-13 10:51 Environment: 2.138.1 Priority: Minor Reporter: Marcel Meschenmoser Log in as admin "manage jenkins" "manage users" "Create user" add a username with a dot "hans.muster", fill all other fields click on "create user" -> nothing happens -> better to show the same warning as when a user can sign up: "Username - User name must only contain alphanumeric characters, underscore and dash" Further problem: when a user is auto-detected (after a commit) a dot is allowed, and in our case wanted. -> perhabs it is better to allow dots Add Comment
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54599 Update Jetty version in Maven Jenkins Dev Plugin (Jetty) Change By: Oleg Nenashev Labels: java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54292) Align/fix the codebase to use flavor everywhere instead of environment
Title: Message Title Baptiste Mathus commented on JENKINS-54292 Re: Align/fix the codebase to use flavor everywhere instead of environment Tackling this now to hopefully make things a bit clearer for Adrien Lecharpentier in JENKINS-54598. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54601) Include some changes from 1.9.40
Title: Message Title Evaristo Gutierrez updated an issue Jenkins / JENKINS-54601 Include some changes from 1.9.40 Change By: Evaristo Gutierrez Summary: Include some security fixes changes from 1.9.40 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54601) Include some security fixes from 1.9.40
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-54601 Include some security fixes from 1.9.40 Issue Type: Task Assignee: Evaristo Gutierrez Components: async-http-client-plugin Created: 2018-11-13 11:08 Priority: Minor Reporter: Evaristo Gutierrez 1.9.40 included some incompatible changes that breaks some components. It would be nice to have some of those changes without all the actually breaking ones. Add Comment This message was sent by Atlassian Jira (v7.11.2#71100
[JIRA] (JENKINS-54292) Align/fix the codebase to use flavor everywhere instead of environment
Title: Message Title Baptiste Mathus updated JENKINS-54292 Jenkins / JENKINS-54292 Align/fix the codebase to use flavor everywhere instead of environment Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54602) Pipeline post action should support conditions
Title: Message Title
Kamil Grabowski created an issue
Jenkins / JENKINS-54602
Pipeline post action should support conditions
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-13 11:16
Environment:
Jenkins ver. 2.138.2 Pipeline: Model API 1.3.2
Priority:
Minor
Reporter:
Kamil Grabowski
Hello, Would be nice to add a when conditions to pipeline post actions. Here is an example:
pipeline {
agent any;
stages { ... }
// run only for master branch
post {
when { branch 'master' }
failure {
// send slack notification about failure build
}
}
// run without any additional conditions (it works now)
post {
success { ... }
cleanup { ... }
}
}
I don't have a good idea how to implement this without breaking-changes. In this example there is an idea that we can add multiple pipeline post blocks (one for every when condition) Motivation: I would like to send notification about failed builds, but only for releases braches. We don't want to receive notifications about failed pull requests builds.
[JIRA] (JENKINS-51986) Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave
Title: Message Title Baptiste Mathus updated JENKINS-51986 Jenkins / JENKINS-51986 Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46521) Non-multibranch pipelines do not have any changeset information
Title: Message Title Drew Easley commented on JENKINS-46521 Re: Non-multibranch pipelines do not have any changeset information +1, We're seeing the same issue in our Jenkins instance. Standard views show commit information, but Blue Ocean shows a hyphen for commit and branch being built. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-54297 Failing to report build status to BitBucket server Change By: Joseph Petersen Priority: Major Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-54297 Failing to report build status to BitBucket server Change By: Joseph Petersen Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54588) Docker jenkins can't create first user
Title: Message Title
safkhsd khdfldsh updated an issue
Jenkins / JENKINS-54588
Docker jenkins can't create first user
Change By:
safkhsd khdfldsh
Hi,I just started jenkins inside a docker cotainer container , by using docker-compose with following yml {code:java}jenkins: image: 'jenkinsci/blueocean:latest' restart: always volumes: - 'jenkins_data:/var/jenkins_home' - '$HOME/jenkins:/var/jenkins_home' - '/var/run/docker.sock:/var/run/docker.sock' ports: - "17908:8080" expose: - "8080"{code}the container is running, got the password for the default admin account, installed the default recommended plugins. The next step should allow me to create a new admin user, i completed all the data and i get the following error{code:java}Stack tracejava.lang.IllegalArgumentException: Invalid indexed property '["password1",' on bean class 'class hudson.security.HudsonPrivateSecurityRealm$SignupInfo' Missing End Delimiter at org.apache.commons.beanutils.PropertyUtilsBean.getIndexedProperty(PropertyUtilsBean.java:397) at org.apache.commons.beanutils.PropertyUtilsBean.getNestedProperty(PropertyUtilsBean.java:768) at org.apache.commons.beanutils.BeanUtilsBean.getNestedProperty(BeanUtilsBean.java:715) at org.apache.commons.beanutils.BeanUtilsBean.getProperty(BeanUtilsBean.java:741) at org.apache.commons.beanutils.BeanUtils.getProperty(BeanUtils.java:382) at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:580) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:391) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:383) at hudson.security.HudsonPrivateSecurityRealm$SignupInfo.(HudsonPrivateSecurityRealm.java:566) at hudson.security.HudsonPrivateSecurityRealm.validateAccountCreationForm(HudsonPrivateSecurityRealm.java:399) at hudson.security.HudsonPrivateSecurityRealm.createAccountFromSetupWizard(HudsonPrivateSecurityRealm.java:319) at jenkins.install.SetupWizard.doCreateAdminUser(SetupWizard.java:257) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) 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:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass data-model-type="hudson.model.Hudson" id="jenkins" class="yui-skin-sam two-column jenkins-2.138.3" data-version="2.138.3".doDispatch(MetaClass.java:130) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:212) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatche
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Definitely not a bug, this is the intended error message you should handle as Jenkins admins. Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server. Perhaps the error message could be improved? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen edited a comment on JENKINS-54297 Re: Failing to report build status to BitBucket server Definitely not a bug, this is the intended error message you should handle as Jenkins admins.Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server requirements .Perhaps the error message could be improved? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54599 Update Jetty version in Maven Jenkins Dev Plugin (Jetty) Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54603) Memory leak in remoting causes Jenkins to crash
Title: Message Title Benjamin Martens created an issue Jenkins / JENKINS-54603 Memory leak in remoting causes Jenkins to crash Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-11-13 11:51 Environment: Operating System: Arch Linux Java: OpenJDK 8 Jenkins: 2.151 Plugins: Git client plugin Folders Plugin Docker Commons Plugin GitHub API Plugin JSch dependency plugin Token Macro Plugin Branch API Plugin Windows Slaves Plugin Slave SetupPlugin Pipeline: Declarative MapDB API Plugin Pipeline: Multibranch Icon Shim Plugin Gradle Plugin Git plugin Matrix Project Plugin Email Extension Plugin GIT server Plugin Plain Credentials Plugin Pipeline: Basic Steps Subversion Plug-in Build Authorization Token Root Plugin LDAP Plugin Mercurial plugin Pipeline: Shared Groovy Libraries Mailer Plugin Active Directory plugin HTML Publisher plugin Resource Disposer Plugin _javascript_ GUI Lib: Handlebars bundle plugin Phabricator Differential Plugin Pipeline: Stage Tags Metadata Pipeline Build Timeout Pipeline Graph Analysis Plugin SCM API Plugin Pipeline: Supporting APIs PAM Authentication plugin Pipeline: Declarative Agent API OWASP Markup Formatter Plugin Durable Task Plugin HTTP Request Plugin Pipeline: API Apache HttpComponents Client 4.x API Plugin Pipeline: Model API Timestamper Jackson 2 API Plugin Pipeline: Declarative Extension Points API Authentication Tokens API Plugin Doxygen Plug-in Pipeline: Nodes and Processes Pipeline: Groovy Script Security Plugin Pipeline: Job Simple Theme Plugin Pipeline: Milestone Step Display URL API Matrix Authorization Strategy Plugin Permissive Script Security Plugin GitHub Branch Source Plugin Pipeline: Input Step Structs Plugin _javascript_ GUI Lib: Moment.js bundle plugin Docker Pipeline Credentials Plugin build-name-setter GitHub plugin SSH Credentials Plugin Command Agent Launcher Plugin _javascript_ GUI Lib: ACE Editor bundle plugin Test Results Analyzer Plugin JUnit Plugin Pipeline: Step API Credentials Binding Plugin _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin Pipeline: REST API Plugin Pipeline: Stage Step Pipeline: Stage View Plugin Javadoc Plugin Pipeline: Build Step External Monitor Job Type Plugin File Operations Plugin
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Oleg Nenashev started work on JENKINS-54599 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Oleg Nenashev commented on JENKINS-54599 Re: Update Jetty version in Maven Jenkins Dev Plugin (Jetty) https://github.com/jenkinsci/maven-hudson-dev-plugin/pull/7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54292) Align/fix the codebase to use flavor everywhere instead of environment
Title: Message Title Baptiste Mathus updated JENKINS-54292 Jenkins / JENKINS-54292 Align/fix the codebase to use flavor everywhere instead of environment Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus updated JENKINS-54266 Jenkins / JENKINS-54266 fails to start agent because of missing label Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54266 fails to start agent because of missing label Change By: Baptiste Mathus Released As: (towards) 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use https
Title: Message Title Iurii Sergiichuk created an issue Jenkins / JENKINS-54604 checkUpdatesServer fails to use https Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-13 12:04 Environment: Jenkins 2.138.3, CentOS 7, Java 8u191 Priority: Blocker Reporter: Iurii Sergiichuk Jenkins is not able to connect to any outside resource that should work with SSL. It is not possible to obtain a list of plugins, connect to remote slaves using SSH, etc. Here is what I can fish out: ``` java.lang.NoSuchFieldError: state at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:198) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:185) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1648) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.ja
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use https
Title: Message Title Iurii Sergiichuk updated an issue Jenkins / JENKINS-54604 checkUpdatesServer fails to use https Change By: Iurii Sergiichuk Jenkins is not able to connect to any outside resource that should work with SSL. It is not possible to obtain a list of plugins, connect to remote slaves using SSH, etc. Here is what I can fish out when I try to update the list of plugins :```java.lang.NoSuchFieldError: state at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:198) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:185) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1648) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) 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:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:188) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use SSL
Title: Message Title Iurii Sergiichuk updated an issue Jenkins / JENKINS-54604 checkUpdatesServer fails to use SSL Change By: Iurii Sergiichuk Summary: checkUpdatesServer fails to use https SSL Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54543) Jenkins job doesn't show commits from perforce
Title: Message Title Michal Kolas updated an issue Jenkins / JENKINS-54543 Jenkins job doesn't show commits from perforce Change By: Michal Kolas Environment: Master on Centos 7.564bit with openjdk 1.8.0_181Generic Java package Slave on win7 64bit with Java 8 Jenkins: 2.149 Java 8 perforce p4v/ntx64/2017.1 Google chrome v70 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use SSL
Title: Message Title Iurii Sergiichuk updated an issue Jenkins / JENKINS-54604 checkUpdatesServer fails to use SSL Change By: Iurii Sergiichuk Update:Downgrading Java version to 8u181 fixed the problem. So, it looks to me that only 8u191 is affected. Jenkins is not able to connect to any outside resource that should work with SSL. It is not possible to obtain a list of plugins, connect to remote slaves using SSH, etc. Here is what I can fish out when I try to update the list of plugins:```java.lang.NoSuchFieldError: state at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:198) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:185) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1648) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) 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:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:188) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet
[JIRA] (JENKINS-54604) checkUpdatesServer fails to use SSL
Title: Message Title Iurii Sergiichuk updated an issue Jenkins / JENKINS-54604 checkUpdatesServer fails to use SSL Change By: Iurii Sergiichuk Priority: Blocker Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47014) Groovy Pipeline Use an assignment within a "while" condition error
Title: Message Title Xuezhong Yan updated an issue Jenkins / JENKINS-47014 Groovy Pipeline Use an assignment within a "while" condition error Change By: Xuezhong Yan Priority: Minor Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54593) jenkins is hanging after clean the system cache
Title: Message Title tang alby commented on JENKINS-54593 Re: jenkins is hanging after clean the system cache It is normal when I cancel use ldap login. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54605) Default stage for post section
Title: Message Title
Kamil Grabowski created an issue
Jenkins / JENKINS-54605
Default stage for post section
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-13 12:45
Environment:
Jenkins ver. 2.138.2 Pipeline: Model API 1.3.2
Priority:
Minor
Reporter:
Kamil Grabowski
At the moment all pipeline post steps will be displayed in the latest defined stage. For example:
pipeline {
agent;
stages {
stage('first stage') { ... }
stage('last stage') { ... }
}
post {
always { echo 'Hello World' }
}
}
The echo step will be assigned to the "last stage". Would be nice to have a new, "virtual" stage e.g. ("post actions") for all that things.
[JIRA] (JENKINS-54543) Jenkins job doesn't show commits from perforce
Title: Message Title Michal Kolas commented on JENKINS-54543 Re: Jenkins job doesn't show commits from perforce I seems that I have found rout cause of such "behaviour". I have set Manual (custom view) in job (pipeline script from SCM > perforce software), which each new build generates new worspace name (jenksTempxx-) - and in this case he doens't see commits. In case of replay it keeps old/unchanged workspace name and then see commits/changes. I don't know why he generates all the times new workspace names and I will try to test it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54606) Make container warning more intelligent
Title: Message Title
Steven Deal created an issue
Jenkins / JENKINS-54606
Make container warning more intelligent
Issue Type:
Improvement
Assignee:
Unassigned
Components:
maven-plugin
Created:
2018-11-13 12:54
Priority:
Minor
Reporter:
Steven Deal
The plugin issues the following warning message when used in a container: [withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST... Please add a check to suppress this warning if either of the recommended remediations have been implemented. Otherwise, it gives the impression that the MUST chosen was not successful.
Add Comment
[JIRA] (JENKINS-54597) helloooooo
Title: Message Title Oleg Nenashev closed an issue as Not A Defect Please do not vandalize JIRA. We have a lot of real tickets to process Jenkins / JENKINS-54597 helloo Change By: Oleg Nenashev Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Uma Shankar sorry, I have no idea what is happening on your machine. You may want to install the Support Core plugin, which captures much richer diagnostics, and either attach a generated support bundle here or send it to me privately. (If attaching publicly, I recommend using the anonymization option, unless this is just a test server with no confidential projects.) Josh Soref I cannot even guess what might be causing your build failure. If you manage to narrow it down to a minimal, reproducible test case, please file a bug report and Link to it from here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Samuel Hervé commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Setting a FQDN as Jenkins URL fixed it indeed. It used to work with a non-FQDN hostname at plugin version 2.2.12 though (maybe by accident ?), a better error message would help for sure. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54543) Jenkins job doesn't show commits from perforce
Title: Message Title Michal Kolas edited a comment on JENKINS-54543 Re: Jenkins job doesn't show commits from perforce I seems that I have found rout root cause of such " behaviour ".I have set Manual (custom view) in job (pipeline script from SCM > perforce software), which each new build generates new worspace name (jenksTempxx-) - and in this case he doens't see commits. In case is checkbox of replay it keeps old/unchanged workspace name and then see commits/changes. I don't know why he generates all the times new workspace names and I will try to test it. lightweight checkout Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54543) Jenkins job doesn't show commits from perforce
Title: Message Title Michal Kolas closed an issue as Not A Defect Jenkins / JENKINS-54543 Jenkins job doesn't show commits from perforce Change By: Michal Kolas Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54599) Update Jetty version in Maven Jenkins Dev Plugin (Jetty)
Title: Message Title Baptiste Mathus updated JENKINS-54599 Jenkins / JENKINS-54599 Update Jetty version in Maven Jenkins Dev Plugin (Jetty) Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Stefano Pogliani commented on JENKINS-54428 Re: ECS plugin fails if task definition ARN is used Unfortunately after upgrading to 1.18-beta-5 we still see null pointer exceptions that prevent tasks from being created: INFO: Started provisioning ECS Slave ecs-agent from ecs-sidekicks with 1 executors. Remaining excess workload: 0 Nov 13, 2018 1:42:13 PM hudson.slaves.NodeProvisioner$2 run INFO: ECS Slave node-8-12-ecs-agent provisioning successfully completed. We have now 2 computer(s) Nov 13, 2018 1:42:13 PM com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher runECSTask INFO: [ecs-sidekicks-l47vr]: Starting agent with task definition arn:aws:ecs:x:xxx:task-definition/Node812SidekickTaskDefinition:1} Nov 13, 2018 1:42:13 PM com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher launch WARNING: [ecs-sidekicks-l47vr]: Error in provisioning; agent=com.cloudbees.jenkins.plugins.amazonecs.ECSSlave[ecs-sidekicks-l47vr] java.lang.NullPointerException at com.cloudbees.jenkins.plugins.amazonecs.ECSTaskTemplate.isAwsVpcNetworkMode(ECSTaskTemplate.java:353) at com.cloudbees.jenkins.plugins.amazonecs.ECSService.runEcsTask(ECSService.java:347) at com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher.runECSTask(ECSLauncher.java:221) at com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher.launch(ECSLauncher.java:108) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Nov 13, 2018 1:42:13 PM com.cloudbees.jenkins.plugins.amazonecs.ECSSlave _terminate INFO: [ecs-sidekicks-l47vr]: Terminating ECS Task: null Add Comment
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Stefano Pogliani commented on JENKINS-54428 Re: ECS plugin fails if task definition ARN is used To confirm, the package version: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Stefano Pogliani updated an issue Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Stefano Pogliani Attachment: image-2018-11-13-13-52-32-961.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4951) JUnit report doesn't distinguish between test failures and errors
Title: Message Title Jesse Glick commented on JENKINS-4951 Re: JUnit report doesn't distinguish between test failures and errors For what it’s worth, errors are by no means limited to “third-party” code. This category would include, for example, a NullPointerException either in your test or in the code being tested. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Stefano Pogliani updated JENKINS-54428 Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Stefano Pogliani Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Sergey Avseyev as discussed above, I doubt anyone is planning to spend time on this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54607) Timeout step ignores "Grace Period" before force killing
Title: Message Title
Michael Werner created an issue
Jenkins / JENKINS-54607
Timeout step ignores "Grace Period" before force killing
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2018-11-13 13:57
Priority:
Minor
Reporter:
Michael Werner
The timeout step does not use the defined grace period. Which is 5s in testing and 60s in production. Instead it reuses the timeout which results enormous waiting times if the job is unkillable. This example takes 20 minutes to complete instead of 11 minutes (10 minute timeout + 1 minute grace period):
timeout(time: 10, unit: 'MINUTES') {
unkillable()
}
Add Comment
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Nick Carpenter commented on JENKINS-54428 Re: ECS plugin fails if task definition ARN is used Your right Stefano Pogliani. I think the fix for that line didnt get in until beta-6 – https://github.com/jenkinsci/amazon-ecs-plugin/blob/amazon-ecs-1.18-beta-6/src/main/java/com/cloudbees/jenkins/plugins/amazonecs/ECSService.java#L347 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54607) Timeout step ignores "Grace Period" before force killing
Title: Message Title Michael Werner commented on JENKINS-54607 Re: Timeout step ignores "Grace Period" before force killing PR to fix this issue: https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/76 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title
Aimeri Baddouh commented on JENKINS-41845
Re: Suppress default pipeline output
For me what worked was: .pipeline-new-node { display: none; }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title
Aimeri Baddouh edited a comment on JENKINS-41845
Re: Suppress default pipeline output
For me what worked was: {code:java} .pipeline-new-node { display: none; } {code }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Depends on the version of Bitbucket server your using New version limits the build status API to FQDN hostnames. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. fisnik hajredini I suspect the browser error is the clue—for some reason the script which displays branch annotations is not loaded. It is hard to be sure from your screenshot since it is only from a region of the screen, not the whole browser window. See if your console page contains something like and whether the loaded script file contains a line 37 var branch = label.substring(8) Also you may need to force a page reload. Judging by the frequency of branch transitions, you likely want to run with the startup option -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=true to get better performance. This mode is currently disabled pending some unreleased fixes related to coloration and some field reports of failures, but it is intended to be the default mode going forward. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Stefano Pogliani commented on JENKINS-54428 Re: ECS plugin fails if task definition ARN is used Oh, sorry Nick Carpenter. I did not realise a beta-6 was available. I can confirm that v1.18-beta-6 works correctly. Thanks for the fix! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Sergey Avseyev commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Jesse Glick, but last comment a month ago was about working hard on it. So I thought there might be some progress, or at least assignee for the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-52279 Create Dockerfiles for Java 11 jenkins/ssh-slave images Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52279) Create Dockerfiles for Java 11 jenkins/ssh-slave images
Title: Message Title Baptiste Mathus started work on JENKINS-52279 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51986) Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave
Title: Message Title Baptiste Mathus commented on JENKINS-51986 Re: Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave Untested in real condition yet, will test these I think once I get to have official Docker image for Jenkins with Java 11 (JENKINS-51985) I did a very simple check in https://github.com/jenkinsci/docker-jnlp-slave/pull/72#issuecomment-438286824 that at least the generated image does contain a JDK11. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51986) Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave
Title: Message Title Baptiste Mathus updated JENKINS-51986 Jenkins / JENKINS-51986 Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script No, the last comment was about working on a completely different execution engine that would not suffer from this class of bugs by design. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Samuel Hervé commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Good to know, thank you for the clarification ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Jesse Glick reopened an issue Yes the CSS was completely changed recently (see JENKINS-38381). Note however that if you hide the pipeline-new-node lines, you also lose the ability to collapse sections with the hide links. It ought to be possible to enhance NewNodeConsoleNote/script.js to have an option to hide all of these lines from the GUI, and recoverably. Jenkins / JENKINS-41845 Suppress default pipeline output Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54587) Upon restart, MySql driver not registered
Title: Message Title Cyrille Le Clerc updated JENKINS-54587 Jenkins / JENKINS-54587 Upon restart, MySql driver not registered Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54437) Add support for MySql database
Title: Message Title Cyrille Le Clerc updated JENKINS-54437 Delivered in 3.6.0 Jenkins / JENKINS-54437 Add support for MySql database Change By: Cyrille Le Clerc Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53953) Downstream projects are not triggered if dependencies have a non null classifier
Title: Message Title Cyrille Le Clerc updated JENKINS-53953 Delivered in 3.6.0 Jenkins / JENKINS-53953 Downstream projects are not triggered if dependencies have a non null classifier Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54559) Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE)
Title: Message Title Cyrille Le Clerc updated JENKINS-54559 Delivered in 3.6.0 Jenkins / JENKINS-54559 Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE) Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Cyrille Le Clerc commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Delivered in pipeline-maven-plugin 3.6.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
