[JIRA] (JENKINS-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title chirs damour commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user so you didnt do what ive suggested at all. by default build strategies are or'd. you need to wrap them in an all match to make them AND'd 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title dan tran commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user uploaded my current build strategy settings 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title dan tran updated an issue Jenkins / JENKINS-48296 Multibranch pipeline - ignore commits from certain user Change By: dan tran Attachment: screenshot-1.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-56881) Jenkins job stuck without any error message
Title: Message Title Aravind Reddy assigned an issue to Oleg Nenashev Jenkins / JENKINS-56881 Jenkins job stuck without any error message Change By: Aravind Reddy 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title chirs damour commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user are you using the allmatch strategy to wrap two sub strategies? got a screen shot? 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title dan tran commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user chirs damour not working. Once i add the ignore committer email, it triggers all my PRs builds (many) to rebuild 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-41791) Build cannot be resumed if parallel was used with Kubernetes plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41791 Build cannot be resumed if parallel was used with Kubernetes plugin Have a fix for the workflow-cps problem, and it seems to correct the symptom as reported here. JENKINS-37998 is still valid, since it could affect other scenarios, but this seems to be the important fix. Change By: Jesse Glick Summary: Pipeline waiting for user input does not survive Jenkins restart Build cannot be resumed if parallel was used with Kubernetes plugin Component/s: kubernetes-plugin Component/s: pipeline-input-step-plugin Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated JENKINS-41791 Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title chirs damour commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user my pr got merged so you can use the all match with nested https://github.com/jenkinsci/ignore-committer-strategy-plugin and whatever your normal strategy is. im doing this in our builds with much success jenkins commits and no build happens 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick started work on JENKINS-41791 Change By: Jesse Glick 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick Assignee: Jesse Glick 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-53218) Docker builds should use volumes for workspace/JIRA sidecar with SCM tools
Title: Message Title Nattaphon Bubmee started work on JENKINS-53218 Change By: Nattaphon Bubmee 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-56893) docker
Title: Message Title Nattaphon Bubmee created an issue Jenkins / JENKINS-56893 docker Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-04-05 04:10 Priority: Trivial Reporter: Nattaphon Bubmee 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-56892) Add support for include what you use (IWYU)
Title: Message Title David van Laatum created an issue Jenkins / JENKINS-56892 Add support for include what you use (IWYU) Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-04-05 04:07 Priority: Minor Reporter: David van Laatum https://include-what-you-use.org/ example output src/common/url/URL.h should add these lines: #include // for shared_ptr::operator!, shared_ptr, shared_ptr::operator bool #include // for string_view #include // for uint16_t #include // for ostream #include // for declval src/common/url/URL.h should remove these lines: - #include // lines 9-9 - #include // lines 15-15 - #include // lines 10-10 - #include "../CompilerAttributes.h" // lines 16-16 The full include-list for src/common/url/URL.h: #include // for path #include // for lexical_cast #include // for shared_ptr::operator!, shared_ptr, shared_ptr::operator bool #include // for BOOST_THROW_EXCEPTION #include // for string_view #include // for uint16_t #include // for ostream #include // for multimap, multimap<>::value_compare #include // for string #include // for declval #include // for vector #include "../Exceptions.h"// for BaseException --- src/common/url/URL.cpp should add these lines: #include // for isxdigit, isdigit #include// for size_t, strtol #include // for operator<<, error_info #include // for errinfo_file_name #include //
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart JENKINS-53709 was a similar 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-53199) Docker plugin should be configured to be capable of running Docker-in-docker
Title: Message Title Nattaphon Bubmee started work on JENKINS-53199 Change By: Nattaphon Bubmee 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-53199) Docker plugin should be configured to be capable of running Docker-in-docker
Title: Message Title Nattaphon Bubmee assigned an issue to Nattaphon Bubmee Jenkins / JENKINS-53199 Docker plugin should be configured to be capable of running Docker-in-docker Change By: Nattaphon Bubmee Assignee: Baptiste Mathus Nattaphon Bubmee 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title Mohammad Norouzi commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user We need this feature. We can't automatically bump up our libraries version as they get stuck in a loop 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Digging into the program state confirms that all kinds of stuff including the ContainerExecDecorator is still there even after the container step exited. Seems like a bug in ParallelStep. 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-53904) SEVERE: Failed to save build record
Title: Message Title Owen Mehegan closed an issue as Incomplete Not enough information to do anything with this. Jenkins / JENKINS-53904 SEVERE: Failed to save build record Change By: Owen Mehegan Status: Open Closed Resolution: Incomplete 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart I was hoping that my proposed fix of JENKINS-41854 would solve the symptom in at least some cases, by allowing a PickleDynamicContext to be saved in program.dat rather than the actual FilePath in a DryCapsule. Unfortunately it does not seem to work—something is apparently still trying to rehydrate the bogus pickle—though at least the override of TryRepeatedly.getOwner from FilePathPickle makes the problem a bit more apparent, as the resumed build will repeatedly print Still trying to load Looking for path named ‘/home/jenkins/workspace/workaround’ on computer named ‘jenkins-input-repro-48e88ac1-40ab-4d74-9ba2-1f25e728be3c--3h6s8’ 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-56891) EC2 Plugin using Spot Instances fails
Title: Message Title Serban Nicusor created an issue Jenkins / JENKINS-56891 EC2 Plugin using Spot Instances fails Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-04-04 23:53 Environment: Jenkins ver. 2.150.3 Ubuntu 18.04 Host Amazon EC2 plugin 1.42 Labels: ec2-plugin aws spot Priority: Major Reporter: Serban Nicusor Hey. The plugin works perfectly without Spot instances! I've tried to use the `Amazon EC2 plugin` with Spot Instances ( m5d.12xlarge ). The AMI image was configured correctly as of https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin steps. My jobs needs one Instance based on Label ( linux ). The Instance Count Limit is set to 4/this instance and 4/Global. The problem starts to happen when Jenkins is trying to create a Spot Instance to serve my builds queue. In AWS i get around 7-8 Spot Instances created at an interval of 3~30 seconds when i only need one ... Jenkins only sees only one Agent online, doesn't even see the others as offline ... Am i missing something? Did I do something wrong ? Thanks!
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Cody Casterline created an issue Jenkins / JENKINS-56890 IOException: "cannot find current thread" Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-04-04 23:07 Priority: Minor Reporter: Cody Casterline Our server has intermittently been raising an exception which fails builds: java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE It happens across different projects, and we can't find any commonality between them that might explain how we're ending up in this state. The error is not repeatable – kicking off the build again usually results in a successful build. Jenkins ver. 2.164.1 (Relevant?) plugin versions: Pipeline Multibranch: 2.20 Pipeline: Groovy 2.63 I found the line that is throwing the exception in the source code, which seems straightforward, but I don't know why that value is sometimes null. I'm happy to provide more information to
[JIRA] (JENKINS-54524) Improper Encoding of Sync Status
Title: Message Title David Marley commented on JENKINS-54524 Re: Improper Encoding of Sync Status I echo previous commenters here. The fact that there is an (awkward) workaround involving typing into the browser console doesn't seem like a sound basis for closing issue as "Won't 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Haha awesome, well maybe I can workaround for now by just removing any usage or parallel. I'll give that a shot on the actual workflow. 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-36087) Set stage result manually
Title: Message Title Kamesh Velu commented on JENKINS-36087 Re: Set stage result manually I don't see a fix or resolution for this issue? but the issue's status is Resolved, should this be open instead? 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Removing the parallel step and running the same sh steps sequentially does work around the issue, confirming that on top of everything else there is a serial form leak bug in workflow-cps. Change By: Jesse Glick Component/s: workflow-cps-plugin 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-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title Jesse Glick resolved as Not A Defect This is just how Groovy works I am afraid. Java 8 allows for effectively-final variables, and signals a compilation error if the variable is not effectively final, but Groovy merrily compiles an incorrect program. Jenkins / JENKINS-50307 While running in parallel for a loop, the index is wrong for each iteration Change By: Jesse Glick Status: Open Resolved 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-49426) parallel steps only show branchname as prefix in console output
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49426 parallel steps only show branchname as prefix in console output Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: workflow-cps-plugin Labels: jenkins parallel pipeline 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-47157) Jenkins pipeline hangs with "cannot start writing logs to a finished node"
Title: Message Title Jesse Glick resolved as Cannot Reproduce Jenkins / JENKINS-47157 Jenkins pipeline hangs with "cannot start writing logs to a finished node" Change By: Jesse Glick Status: Open Resolved 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{ Hmm interesting. My pods have definitely been destroying and recreating anew for each {{node { () }} } scope block, whether that's expected/intended or not.. As you said though, that could well be related to the 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{Hmm interesting. My pods have definitely been destroying and recreating anew for each {{ node{} }} scope block, whether that's expected/intended or not.. As you said though, that could well be related to the 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{ Hmm interesting. My pods have definitely been destroying and recreating anew for each ` node{} ` scope block, whether that's expected/intended or not.. As you said though, that could well be related to the 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Hmm interesting. My pods have definitely been destroying and recreating anew for each `node{}` scope block, whether that's expected/intended or not.. As you said though, that could well be related to the 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-33628) Support bundle corrupt via UI
Title: Message Title Félix Belzunce Arcos assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-33628 Support bundle corrupt via UI Change By: Félix Belzunce Arcos Assignee: Carlos Rodríguez López Félix Belzunce Arcos 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-33628) Support bundle corrupt via UI
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33628 Support bundle corrupt via UI Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/support-core-plugin/pull/167 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-33628) Support bundle corrupt via UI
Title: Message Title Félix Belzunce Arcos commented on JENKINS-33628 Re: Support bundle corrupt via UI The job is done here https://github.com/jenkinsci/support-core-plugin/pull/167 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
I had assumed that a workaround in this case would be to actually release the pod before pausing the input (as you ought to do anyway):
def endToEndTests(target) {
stage('End to end tests') {
container('ci') {
parallel '1': {
sh 'sleep 10'
}, '2': {
sh 'sleep 10'
}, '3': {
sh 'sleep 10'
}
}
}
}
def deploy(target) {
stage("Deploy to ${target}") {
container('ci') {
sh 'sleep 10'
}
}
}
def everything(target) {
def label = "jenkins-input-repro-${UUID.randomUUID().toString()}"
podTemplate(label: label, podRetention: onFailure(), activeDeadlineSeconds: 600, yaml: '''
apiVersion: v1
kind: Pod
spec:
containers:
- name: ci
image: golang:latest
tty: true
''') {
node(label) {
deploy(target)
endToEndTests(target)
}
}
}
everything 'staging'
stage('Approve prod') {
input message: 'Deploy to prod?'
}
everything 'prod'
Unfortunately it does not seem to work. The virtual thread dump shows that the program load is trying to deserialize a FilePath from jenkins-input-repro-390fc568-acbd-434d-9083-8de662760e28-khwqp, while the currently active agent is named jenkins-input-repro-390fc568-acbd-434d-9083-8de662760e28-5l5jr. Why the kubernetes plugin is reconstructing this agent, I have no idea (it should have been deleted as soon as the first node block exited, and in fact the second agent does disconnect on its own after a while); but that is less important than the fact that program.dat includes a FilePathPickle for a node block which has already closed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56889) Kubernetes creates too many slaves
Title: Message Title Raf Nijskens created an issue Jenkins / JENKINS-56889 Kubernetes creates too many slaves Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-04-04 20:41 Environment: Jenkins LTS 2.164.1 Kubernetes plugin 1.14.9 Priority: Major Reporter: Raf Nijskens The kubernetes plugin creates multiple containers for each job in queue. Second to wait for pod to be running is set to 600, but seems to be ignored. INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 Apr 04, 2019 5:46:50 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) Apr 04, 2019 5:46:50 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: kube-molecule-489gg in namespace jenkins-test Apr 04, 2019 5:47:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Apr 04, 2019 5:47:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label kube-molecule-pod: Kubernetes Pod Template Apr 04, 2019 5:47:00 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 Apr 04, 2019 5:47:02 PM hudson.TcpSlaveAgentListener$ConnectionHandler run WARNING: Connection #1379 failed java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick Component/s: kubernetes-plugin Component/s: pipeline-input-step-plugin Component/s: pipeline-stage-view-plugin 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
The pod does actually go away though outside of the node blocks.
Not in my experience, although I did see it get killed later for unknown reasons. Not sure if that is related to the bug. Finally managed to reproduce. FTR:
Run Microk8s.
Run: java -Dhudson.Main.development=true -jar jenkins-war-2.164.1.war --prefix=/jenkins --httpPort=8090 --httpListenAddress=10.1.1.1
Load Jenkins via http://10.1.1.1:8090/jenkins/ which should also set its default URL (needed by the Kubernetes jnlp container callback).
Install {blueocean}}, pipeline-stage-view, and kubernetes plugins.
Add a Kubernetes cloud (no further configuration needed).
Create a Pipeline job based on yours but with that stuff uncommented, and with the resources section removed, to wit:
def label = "jenkins-input-repro-${UUID.randomUUID().toString()}"
def scmVars;
def endToEndTests(target) {
stage('End to end tests') {
container('ci') {
parallel '1': {
sh 'sleep 10'
}, '2': {
sh 'sleep 10'
}, '3': {
sh 'sleep 10'
}
}
}
}
def deploy(target) {
stage("Deploy to ${target}") {
container('ci') {
sh 'sleep 10'
}
}
}
podTemplate(label: label, podRetention: onFailure(), activeDeadlineSeconds: 600, yaml: """
apiVersion: v1
kind: Pod
spec:
containers:
- name: ci
image: golang:latest
tty: true
"""
) {
node(label) {
this.deploy('staging')
this.endToEndTests('staging')
}
stage('Approve prod') {
input message: 'Deploy to prod?'
}
node(label) {
this.deploy('prod')
this.endToEndTests('prod')
}
}
Start a build.
Wait for it to get to approval.
/safeRestart
When Jenkins comes back up, try to Proceed.
Not sure exactly how the endToEndTests plays into this, but anyway compared to the passing case, there is no Ready to run at … message, http://10.1.1.1:8090/jenkins/job/p/1/threadDump/ displays
Program is not yet loaded
Looking for path named ‘/home/jenkins/workspace/p’ on computer named ‘jenkins-input-repro-15556b06-275f-494f-84d3-4ba9c006f0c1--8b27g’
[JIRA] (JENKINS-50053) The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy
Title: Message Title Gary Moore commented on JENKINS-50053 Re: The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy This was resolved in version 2.2 of our plugin. 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-50053) The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy
Title: Message Title Gary Moore closed an issue as Fixed Jenkins / JENKINS-50053 The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy Change By: Gary Moore 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-50053) The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy
Title: Message Title Gary Moore resolved as Fixed Jenkins / JENKINS-50053 The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy Change By: Gary Moore Status: In Progress 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-50053) The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy
Title: Message Title Gary Moore assigned an issue to Gary Moore Jenkins / JENKINS-50053 The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy Change By: Gary Moore Assignee: Max Gelman Gary Moore 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-50053) The contrast-continuous-application-security-plugin doesn't accept the Jenkins proxy
Title: Message Title Gary Moore started work on JENKINS-50053 Change By: Gary Moore 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-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Evan Bluhm commented on JENKINS-56888 Re: Unexpected cgroup syntax when using docker-in-docker slave launched via SSH I've opened https://github.com/jenkinsci/docker-workflow-plugin/pull/169 as a potential 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-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title
Evan Bluhm updated an issue
Jenkins / JENKINS-56888
Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Change By:
Evan Bluhm
In our configuration, we use the Docker plugin as a build cloud to dynamically spawn Jenkins slaves ( [ https://wiki.jenkins.io/display/JENKINS/Docker+Plugin ] . In some cases, we need a sandboxed docker environment for building images, so the slaves start a docker-in-docker daemon when they're launched. The slaves are connected via SSH using the Docker plugin's normal "Connect with SSH" launch method. The result is that the default `agent` environment is a remote slave connected via SSH that's running in a docker container. The slave has a docker client installed, and the default docker host is the docker-in-docker daemon running within the slave container. When using the dockerfile type of agent parameter ( [ https://jenkins.io/doc/book/pipeline/syntax/#agent-parameters ] ), the withDockerContainer step fails with error message: { { noformat} java.io.IOException: Unexpected cgroup syntax /docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/docker/a913fc1766a972d99ae545d6ba2508fe797c2df9b6371ff0be629436a30502a4/user/jenkins/0 }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) }} {{ at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) }} {{ at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) }} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:134) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:122) }} {{ at
[JIRA] (JENKINS-56888) Unexpected cgroup syntax when using docker-in-docker slave launched via SSH
Title: Message Title Evan Bluhm created an issue Jenkins / JENKINS-56888 Unexpected cgroup syntax when using docker-in-docker slave launched via SSH Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-04-04 19:36 Environment: Operating System: Docker 17.09.0-ce on Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-127-generic x86_64) Java Runtime: OpenJDK Runtime Environment 1.8.0_181-8u181-b13-2~deb9u1-b13 How Jenkins was installed: docker run -v /jenkins-data-mount:/var/jenkins_home jenkins/jenkins:lts Jenkins + Plugin Versions: Jenkins: 2.164.1 docker-workflow: 1.18 docker-plugin: 1.1.6 docker-java-api: 3.0.14 docker-commons: 1.14 ssh-slaves: 1.29.4 Reverse proxy: None Slave nodes: Launching nodes using the Docker plugin via the SSH connection method (https://wiki.jenkins.io/display/JENKINS/Docker+Plugin). More info in the description Priority: Minor Reporter: Evan Bluhm In our configuration, we use the Docker plugin as a build cloud to dynamically spawn Jenkins slaves (https://wiki.jenkins.io/display/JENKINS/Docker+Plugin. In some cases, we need a sandboxed docker environment for building images, so the slaves start a docker-in-docker daemon when they're launched. The slaves are connected via SSH using the Docker plugin's normal "Connect with SSH" launch method. The result is that the default `agent` environment is a remote slave connected via SSH that's running in a docker container. The slave has a docker client installed, and the default docker host is the docker-in-docker daemon running within the slave container. When using the dockerfile type of agent parameter (https://jenkins.io/doc/book/pipeline/syntax/#agent-parameters), the withDockerContainer step fails with error message: java.io.IOException:
[JIRA] (JENKINS-56887) Role Strategy Plugin
Title: Message Title Jerome Denechaud commented on JENKINS-56887 Re: Role Strategy Plugin Hi my mind thank you ... 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-56887) Role Strategy Plugin
Title: Message Title Jerome Denechaud updated JENKINS-56887 Jenkins / JENKINS-56887 Role Strategy Plugin Change By: Jerome Denechaud Status: Open Fixed but Unreleased 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Possibly only with kubernetes, haven't tried otherwise. The pod does actually go away though outside of the node blocks. It doesn't hang around while waiting on input. 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-56887) Role Strategy Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-56887 Re: Role Strategy Plugin Hi. Role strategy plugin uses regular _expression_ patterns, not wildcards. "test.*" is probably what you want to achieve 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-56887) Role Strategy Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56887 Role Strategy Plugin Change By: Oleg Nenashev Component/s: role-strategy-plugin Component/s: _unsorted 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart So does this happen only when using the kubernetes plugin? (I will set aside the advice that an input step ought not be used inside podTemplate, as it forces the pod to stick around while waiting for a human to come back from vacation or whatever.) Anyway, I will see if I am able to reproduce locally. 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-19887) Allow time zone to be set on a per user basis
Title: Message Title Adam Gent commented on JENKINS-19887 Re: Allow time zone to be set on a per user basis I briefly looked around and this would not be that hard to implement if only you could get the root JellyContext. Once you have the JellyContext then just you just intercept the calls: JellyContext.getVariable(Config.FMT_TIME_ZONE); Or set the variable since the context is mutable. The JellyContext is already bound to a request via a ThreadLocal in ExpressionFactory2 so you just need to setup the parent JellyContext to look at user config. The problem is that Stapler makes its own JellyContext called CustomJellyContext in DefaultScriptInvoker per request (which is good)! So in theory a custom DefaultScriptInvoker that pulls user configuration logic and sets the context with that user logic should be able to set the correct time zone variable. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Thanks, I was able to get tests running (took a bit as I'm not familiar with Java tooling). I am still trying to get a unit test that replicates the failure, however in the meantime, here is a fairly minimal Jenkinsfile of some interest: https://gist.github.com/timmyers/bcdcecce1095e5e4d94bc39d9bdcf018 As is, there are no issues. If I uncomment the `endToEndTests` lines though, the error occurs. Seems very odd to me. 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. Is there already somewhere another ticket out there If it is not Link ed here, then I would presume not. what we would need is to be able to completely hide all branches (completely, all occurrences) except the chosen one. Only that would make the search obsolete. Is that / will that be possible? It could be, using some CSS/JS manipulations, as suggested here. That would of course deserve its own (linked) 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Joerg Schwaerzler edited a comment on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Since this ticket is closed I have to ask: Is there already somewhere another ticket out there about the branch names not being searchable anymore? Doesn't work with Chrome or Firefox. And you clearly do not want to use IE or Edge with Jenkins - so I didn't even gave give them a shot.In addition to that Chrome used to be the only browser being able to highlight all occurrences of a particular branch in the scroll bar - that way one could easily find an issue related to one branch only. Especially for bigger pipelines with lots of branches we still need this.The show/hide feature is quite nice. However what we would need is to be able to completely hide all branches (completely, all occurrences) except the chosen one. Only that would make the search obsolete. Is that / will that be possible? 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 Joerg Schwaerzler commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Since this ticket is closed I have to ask: Is there already somewhere another ticket out there about the branch names not being searchable anymore? Doesn't work with Chrome or Firefox. And you clearly do not want to use IE or Edge with Jenkins - so I didn't even gave them a shot. In addition to that Chrome used to be the only browser being able to highlight all occurrences of a particular branch in the scroll bar - that way one could easily find an issue related to one branch only. Especially for bigger pipelines with lots of branches we still need this. The show/hide feature is quite nice. However what we would need is to be able to completely hide all branches (completely, all occurrences) except the chosen one. Only that would make the search obsolete. Is that / will that be possible? 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-54514) Document parallel step failure logic
Title: Message Title Jesse Glick assigned an issue to Craig Ringer Jenkins / JENKINS-54514 Document parallel step failure logic Change By: Jesse Glick Assignee: Craig Ringer 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-54514) Document parallel step failure logic
Title: Message Title Jesse Glick started work on JENKINS-54514 Change By: Jesse Glick 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-54514) Document parallel step failure logic
Title: Message Title Jesse Glick updated JENKINS-54514 Jenkins / JENKINS-54514 Document parallel step failure logic Change By: Jesse Glick 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart mvn test -Dtest=InputStepRestartTest\#whatever if you do not have anything better in your IDE. 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-56858) unable to load plugins
Title: Message Title Yufen Kuo commented on JENKINS-56858 Re: unable to load plugins the help text says: v (-version) VAL : jenkins version to use. Defaults to latest LTS. w (-jenkins-war) FILE : path to jenkins.war or exploded jenkins war directory So it seems if you use -w option and pass path to jenkins.war, it would not work. Using -v option does not work either Both seems to be bugs to me, or help text needs to be updated. 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-56886) Missing test reports when using xUnit plugin
Title: Message Title Charles Lechasseur commented on JENKINS-56886 Re: Missing test reports when using xUnit plugin I'll try to get that as soon as possible. They might contain some sensitive data so I have to check them first. 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-33255) Largefiles do not work with distributed repository caching
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33255 Largefiles do not work with distributed repository caching Change By: Jesse Glick Labels: cache distributed mercurial stalled-pr 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-33255) Largefiles do not work with distributed repository caching
Title: Message Title Jesse Glick stopped work on JENKINS-33255 Change By: Jesse Glick Status: In Progress Open 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-56702) Use LookaheadParser for YuiCompressorParser
Title: Message Title Andreas Moser assigned an issue to Andreas Moser Jenkins / JENKINS-56702 Use LookaheadParser for YuiCompressorParser Change By: Andreas Moser Assignee: Andreas Moser 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-56791) Provide custom read/write serialization methods for Report
Title: Message Title Andreas Moser assigned an issue to Unassigned Jenkins / JENKINS-56791 Provide custom read/write serialization methods for Report Change By: Andreas Moser Assignee: Andreas Moser 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder Peter Hannon sorry, I've replied something unrelated. You have to pass an argument to enable the cleanup `--extractedFilesFolder=FOLDER_PATH` https://github.com/kuisathaverat/extras-executable-war/blob/8f00f05c22cb4953ed0a034e0d7ef35c0076f99f/src/main/java/Main.java#L229-L232 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-22088 Disk space leak with multiple copies of winstone-.jar in TEMP folder Change By: Ivan Fernandez Calvo Comment: ~if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything~ 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder ~ if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything ~ 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-56791) Provide custom read/write serialization methods for Report
Title: Message Title Andreas Moser assigned an issue to Andreas Moser Jenkins / JENKINS-56791 Provide custom read/write serialization methods for Report Change By: Andreas Moser Assignee: Andreas Moser 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-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Andreas Moser assigned an issue to Unassigned Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Andreas Moser Assignee: Andreas Moser 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-42224) Need ability to create reusable chunks of Declarative Pipeline
Title: Message Title Nick Roosevelt commented on JENKINS-42224 Re: Need ability to create reusable chunks of Declarative Pipeline I would like this as well. But also, it seems like we can make some of those blocks one line, and we could use a preprocessor, if necessary. Just starting to get into this, but seems like groovy should support this already. 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-42224) Need ability to create reusable chunks of Declarative Pipeline
Title: Message Title Nick Roosevelt commented on JENKINS-42224 Re: Need ability to create reusable chunks of Declarative Pipeline I would like this as well. But also, it seems like we can make some of those blocks one line, and we could use a preprocessor, if necessary. Just starting to get into this, but seems like groovy should support this already. 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-56886) Missing test reports when using xUnit plugin
Title: Message Title Nikolas Falco edited a comment on JENKINS-56886 Re: Missing test reports when using xUnit plugin I need the report unittest reports of two different build that report different count of total tests or I'm not able to reproduce 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart I feel like I may be on to something. I think I have narrowed down to a fairly specific addition to my pipeline that seems to trigger the issue (at least in my case). Re: tests, is there any documentation how to run them locally for the `pipeline-input-step-plugin` repo. Or is the best bet to open a PR and let the CI run them for me? 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-56887) Role Strategy Plugin
Title: Message Title Jerome Denechaud created an issue Jenkins / JENKINS-56887 Role Strategy Plugin Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-04-04 16:07 Environment: Jenkins ver. 2.170 Role-based Authorization Strategy 2.10 Priority: Minor Reporter: Jerome Denechaud Role are created for restricted user Overall read is check and that s it in Global role I add a patter for project role: test for pattern test* I tick build and read for job when I m connected with my restricted user I can only see the folder test and not the jobs insides with the same prefix to see correctly I have to tick in global role read to job Add Comment
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
It should go without saying that a bug report with a minimal, self-contained, reproducible test case is far more likely to be addressed. For the more adventurous, we also welcome pull requests contributing a test case demonstrating the bug like
@Ignore("TODO times out at line such-and-such after printing such-and-such warning")
@Issue("JENKINS-41791")
@Test public void whatever() {…}
which in this case would presumably live in InputStepRestartTest. Such a PR is eligible for immediate merge, with a future fix ideally just deleting the @Ignore in the same commit.
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-56884) Vsphere plugin : Convert Template to a VM
Title: Message Title Philippe LIMOUZY commented on JENKINS-56884 Re: Vsphere plugin : Convert Template to a VM I added a logger on all org.jenkinsci.plugins.vsphere* library with the level ALL ... nothing is written when I use the action Convert Template to a VM The logger works fine as I have some log inputs when I call a job that do a POWER ON on a VM . 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Peter Hannon commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder Ivan Fernandez Calvo thanks for the reply, if you see my comment (the shell script), I'm running this in linux, so the windows service change is not applicable for me. Are you saying for a linux environment, this generated winstone jar file needs to be cleaned manually? 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-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Gil Br updated an issue Jenkins / JENKINS-56747 Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Change By: Gil Br [Jenkins ver. 2. 168 170 |https://jenkins.io/]Running from shell:java -jar jenkins.war --httpPort=-1 --httpsPort=8443 --httpsKeyStore=jenkin.jks --httpsKeyStorePassword=TopSecret Opening from Browser getting an error:Chrome: ERR_SSL_VERSION_OR_CIPHER_MISMATCHFireFox: Error code: SSL_ERROR_NO_CYPHER_OVERLAP IE: Your TLS security settings aren’t set to the defaults 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-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Gil Br updated an issue Jenkins / JENKINS-56747 Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Change By: Gil Br Environment: Jenkins ver. 2. 168 170 Linux, Chrome 73.0.3683.86, IE 11.112.17134.0, Firefox 67.0b4 (64-bit) 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-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Gil Br commented on JENKINS-56747 Re: Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Any suggestion? other ways to use the certificate? 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Okay I'll see what I can come up with, thanks. I have one simple Jenkinsfile that seems to be immune, and one more complicated one that it occurs with. Both do very similar things, have no `input`s in have `node{}`, very odd. I'll see if I can come up with a minimal example that reproduces.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Okay I'll see what I can come up with, thanks. I have one simple Jenkinsfile that seems to be immune, and one more complicated one that it occurs with. Both do very similar things, have no `input`s in have `node{}`, very odd.I'll see if I can come up with a minimal example that reproduces.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Tim Myers no, it should not. If the situation described here happens, it is a bug. If we have a way to reproduce it from scratch, we can investigate a 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Jesse Glick Sam Van Oort Is this something that requires https://github.com/jenkinsci/pipeline-input-step-plugin/pull/3 to truly fix? I am running into the issue with `input` steps, using the kubernetes plugin. Pipelines that are currently waiting when the master is restarted become broken, unable to continue. This also affects being able to even load any blue ocean view which references the broken jobs. I have made sure that all of the `input` steps are not in `node{}` blocks, but the issue seems to still occur.
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-56872) Mulit job doesn´t show job details when using folder plugin
Title: Message Title Francisco Fernández commented on JENKINS-56872 Re: Mulit job doesn´t show job details when using folder plugin It looks like the Multi Job Plugin is not honoring the folder when it's collecting the actions to show. I don't see a bug in Folders Plugins, so I will un-assign the issue. According to the wiki page of the plugin, the best place to open the issue is https://github.com/jenkinsci/tikal-multijob-plugin/issues, so my recommendation is to file an issue there. 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-56872) Mulit job doesn´t show job details when using folder plugin
Title: Message Title Francisco Fernández updated an issue Jenkins / JENKINS-56872 Mulit job doesn´t show job details when using folder plugin Change By: Francisco Fernández Component/s: cloudbees-folder-plugin 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-51765) PRs are not rebuilt after their target branch is updated
Title: Message Title Kyle Fernald edited a comment on JENKINS-51765 Re: PRs are not rebuilt after their target branch is updated [~viceice]: is there a particular version of Jenkins or the plugin in which that option became available? I'm having this issue as well and don't see the checkbox.Running a Multi-branch pipeline on Jenkins 2.138.2, Bitbucket Source Plugin 2.4.2 with Bitbucket Server. 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-56886) Missing test reports when using xUnit plugin
Title: Message Title Nikolas Falco commented on JENKINS-56886 Re: Missing test reports when using xUnit plugin I need the report unittest of two different build 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-51765) PRs are not rebuilt after their target branch is updated
Title: Message Title Kyle Fernald commented on JENKINS-51765 Re: PRs are not rebuilt after their target branch is updated Michael Kriese: is there a particular version of Jenkins or the plugin in which that option became available? I'm having this issue as well and don't see the checkbox. Running a Multi-branch pipeline on Jenkins 2.138.2, Bitbucket Source Plugin 2.4.2 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-56886) Missing test reports when using xUnit plugin
Title: Message Title Charles Lechasseur created an issue Jenkins / JENKINS-56886 Missing test reports when using xUnit plugin Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2019-04-04 14:36 Environment: Jenkins 2.164.1, xUnit plugin 2.3.3 Priority: Major Reporter: Charles Lechasseur We use the xUnit plugin to parse Unittest++ output files. On many of our projects, the number of tests reported in Jenkins fluctuates from build to build. I have verified that all our test output files are properly converted to jUnit test files, but either the plugin does not report them correctly to Jenkins or something is up in Jenkins itself. Not sure exactly what is needed to diagnose this - many of the data we have in our Jenkins is internal and cannot be shared, but if I can help with something I will. Add Comment
[JIRA] (JENKINS-56885) hostnameMatches -> NullPointerException
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-56885 Re: hostnameMatches -> NullPointerException It is weird this is tested on the unit test and does not fail, and I have a bunch of agent in both ways configured, Did it happens after an upgrade? if so Did you restarted Jenkins to get the new plugin? Could you attach the JENKINS_HOME/nodes/NODE_NAME/config.xml? 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-51966) Pluggable XMLFile Storage for Jenkins Core
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51966 Pluggable XMLFile Storage for Jenkins Core Change By: Baptiste Mathus Labels: stalled stalled-pr 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-51278) Add support of running PCT as a part of the Jenkins Core build
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51278 Add support of running PCT as a part of the Jenkins Core build Change By: Baptiste Mathus Labels: evergreen stalled stalled-pr 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-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Labels: P4_A P4_B 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.
