[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Damien Viniere updated an issue Jenkins / JENKINS-50210 Kubernetes agent provisioned regardless of container cap Change By: Damien Viniere Attachment: Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Damien Viniere updated an issue Jenkins / JENKINS-50210 Kubernetes agent provisioned regardless of container cap Change By: Damien Viniere Attachment: Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50060) Workspace error when setting stage level agent when global agent specified.
Title: Message Title
M C commented on JENKINS-50060
Re: Workspace error when setting stage level agent when global agent specified.
Trying the above results in the same issue. What did work was this:
podTemplate(label: buildId(),
containers: [.]) {
node(buildId()) {
container('node') {
...
}
}
}
node('docker1') {
...
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41569) Pipeline hangs waiting for resume on an agent which never was
Title: Message Title Chenyang Liu closed an issue as Fixed Jenkins / JENKINS-41569 Pipeline hangs waiting for resume on an agent which never was Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49582) uninformative "Failure" error message when publish-over-ssh fails due to disk space on destination
Title: Message Title Alex Earl commented on JENKINS-49582 Re: uninformative "Failure" error message when publish-over-ssh fails due to disk space on destination There really isn't anything in the call stack that would allow me to tell the user that the disk space is low. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Alex Earl commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together Richard Wilkinson The code you were referencing is from a very old version of email-ext. What is the expected output that you are looking for from the err.txt you posted? ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion some_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed A MESSAGE ncsim: *E,ASRTST (some_string): (some_time) Assertion yet_another_location has failed ncsim: *W,ASRTST (some_other_string): (some_time) Assertion some_other_location has failed
[JIRA] (JENKINS-32568) Add custom-data to Azure slave deployment
Title: Message Title Chenyang Liu closed an issue as Fixed It's a very old issue. If there's also a problem in the latest plugin, please feel free to reopen and leave commends. Jenkins / JENKINS-32568 Add custom-data to Azure slave deployment Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Chenyang Liu closed an issue as Fixed It's a very old problem. If there's also a issue in the latest plugin, please feel free to reopen and leave commends Jenkins / JENKINS-30014 Builds hang, Jenkins still browseable Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-49986) Pipeline 'bat' hangs on ws with forward slash path separator
Title: Message Title Wade Baglin commented on JENKINS-49986 Re: Pipeline 'bat' hangs on ws with forward slash path separator Possibly a duplicate of JENKINS-50025 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48253) Empty list of existing Storage Account Names
Title: Message Title Chenyang Liu commented on JENKINS-48253 Re: Empty list of existing Storage Account Names Billy Sheppard You need to do some change in storageAccountType or ResourceGroupName to let Jenkins UI to reload the existing storage account. Or you can save your configuration and reopen the global configuration, then the account will also be reloaded. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49107) Deployments to resource groups are never cleaned up, resource group eventually refuses further deployments, plugin stops working
Title: Message Title Chenyang Liu closed an issue as Fixed It should be fixed in 0.6.0. If the issue also exists, please leave comment. Jenkins / JENKINS-49107 Deployments to resource groups are never cleaned up, resource group eventually refuses further deployments, plugin stops working Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-49473) Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure
Title: Message Title Chenyang Liu commented on JENKINS-49473 Re: Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure Seems you had deleted the cloud in configuration at that time, so got a NullPointerException. Did you meet the same issue later. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Carlos Sanchez commented on JENKINS-50210 Re: Kubernetes agent provisioned regardless of container cap There's already another issue going into detail of overprovisioning Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Carlos Sanchez edited a comment on JENKINS-50210 Re: Kubernetes agent provisioned regardless of container cap There's already another issue going into detail of overprovisioning iirc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort started work on JENKINS-49686 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Mike Kozell The NPEs you see look like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-49686 which I am investigating right now. May I please request the following diagnostic information: 1. Please can you attach both the config.xml for the job and a build.xml for one or more Pipelines that experienced this issue. 2. In the build's 'workflow' directory, there's a flownodeStore.xml file - please can you GZIP it and attach it. 3. Can I request the last part of the build log for these builds (the final parts indicating build completed and anything after that). 4. Are all the Pipelines experiencing issues making use of parallels? 5. Do you have any fairly simple pipelines that will reproduce the issues, which you can provide code for? There's also fix in workflow-cps plugin 2.46 for some issues with Resume Disabled - without that fix there may be odd behaviors if the Resume Disable flag is modified after the build begins. If this has happened, the fix there will help and after gathering the above information, I would suggest installing this update and seeing if issues recur when Resume Disabled in on. If that does not resolve the resume issue, it may be necessary to toggle this option OFF for the meantime: Do not allow the pipeline to resume if the master restarts": Enabled on all jobs We hope to have a hotfix available soon to at least try out. Thank you Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50210) Kubernetes agent provisioned regardless of container cap
Title: Message Title Damien Viniere created an issue Jenkins / JENKINS-50210 Kubernetes agent provisioned regardless of container cap Issue Type: Bug Assignee: Carlos Sanchez Attachments: Jenkinsfile, jenklogs.txt Components: kubernetes-plugin Created: 2018-03-16 02:20 Environment: kubernetes v1.6.1 Jenkins: v2.89.4 & v2.89.2 kubernetes-plugin: v1.3.2 & v1.3.1 Priority: Major Reporter: Damien Viniere Hi, My teams and I are currently facing an issue with the provisioning of slaves with the kubernetes-plugin using podTemplate that always go higher than the limitation we try to set. We need to run multiple (tens to hundreds depending on the job) slaves in parallel, that will be doing the same task, and thus we create them with the same pod template. Those slaves will run with a heavy CPU workload, so we need to limit the amount of attributed CPU to each of them, but also to set a "container cap" to limit the number of them running at the same time. (because we can not lower the CPU limit too much). We then decided a Container cap of 7 for our first runs, to see what happens. That where the problems arose. First, we saw that the cap was not respected strictly, as sometimes, 8 or 9 of them were running at the same time. This is not critical, we can always work with that if we remember it. Where is the real issue I want to address: We figured that after our first batch of ~7 finish, Jenkins will provision, at the same time, a huge amount of slaves, without consideration of the container cap. To illustrate that, I recreated a simple scenario to replicate the issue,
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Andrew Bayer assigned an issue to Sam Van Oort Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Andrew Bayer Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Edin Brodlic commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches Can also confirm, having an identical issue. Seems to revolve around Git parameter plugin. Weirdly enough I've tracked the git ls-remote process as well as temporary sh file that triggers the ssh, and it's all executed on the Jenkins main, not sure why it happens only when the actual build is supposed to take place on a Windows agent (we have two, with different configurations and both suddenly started having the issue). Also not sure why there is an ssh command executing `git-upload-pack` right after the ls-remote action only when it's being executed via parameter plugin. Git Plugin -->3.3.0 Git Parameter Plugin-->0.8.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50054) Dependencies trigger not working when depend on none primary packaging type
Title: Message Title Cyrille Le Clerc started work on JENKINS-50054 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50054) Dependencies trigger not working when depend on none primary packaging type
Title: Message Title Cyrille Le Clerc commented on JENKINS-50054 Re: Dependencies trigger not working when depend on none primary packaging type Bing Shiao did you test with pipeline-maven-3.4.1 or more recent? Your problem should be fixed. Thank you very much for the detailed issue with the maven-spy logs, it was very easy for me to capture the context. https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.4.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50209) Cobertura Plugin Succeeds When It Should Fail
Title: Message Title Brian Auron created an issue Jenkins / JENKINS-50209 Cobertura Plugin Succeeds When It Should Fail Issue Type: Bug Assignee: Unassigned Components: cobertura-plugin Created: 2018-03-16 00:01 Environment: Jenkins 2.99 Cobertura Plugin 1.12 Priority: Major Reporter: Brian Auron When the coverage report is generated, it only fails a job for a given code state once if the coverage values are outside of the configured levels and `Mark Unhealthy as failed` is checked. For example, a coverage of git sha abcdef with Package Coverage set to Unhealthy below 80% and actual coverage at 73% will fail once. If the job is run again targeting the same git sha (abcdef) without changing the Coverage acceptance levels, the job will succeed even though Package Coverage is still at 73% and should be marked as Unhealthy (and fail). Add Comment
[JIRA] (JENKINS-50128) LDAP permissions working for users but not groups
Title: Message Title Steven Gardner closed an issue as Not A Defect Jenkins / JENKINS-50128 LDAP permissions working for users but not groups Change By: Steven Gardner Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50208) 10min timeout for user built plugins
Title: Message Title Jason Hodges created an issue Jenkins / JENKINS-50208 10min timeout for user built plugins Issue Type: Bug Assignee: Unassigned Components: plugin-proposals Created: 2018-03-15 23:18 Labels: jenkins pipeline plugin timeout Priority: Minor Reporter: Jason Hodges We are building a plugin for Jenkins to call a blue/green deployer that we created. For some of our larger Node apps we are running into a hard 10min timeout when calling our plugin. We are able to adjust the timeout from 0-10 mins but anything after that we get a failed pipeline. I've seen a similar issue with the Git plugin but they were able to get around the issues. We've tried several different libraries for handling the call to our blue/greener but we run in to the same issue. Any help would be great, thanks. Add Comment
[JIRA] (JENKINS-46612) jobDSL doesn't adds shared libraries to folder when in pipeline
Title: Message Title Daniel Spilker resolved as Not A Defect Jenkins / JENKINS-46612 jobDSL doesn't adds shared libraries to folder when in pipeline Change By: Daniel Spilker Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49199) Job DSL Authorizarion Matrix cannot manage the folder inheritance
Title: Message Title Daniel Spilker assigned an issue to Daniel Beck Jenkins / JENKINS-49199 Job DSL Authorizarion Matrix cannot manage the folder inheritance Change By: Daniel Spilker Assignee: Daniel Spilker Beck Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title Carlos Sanchez commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry Fine with me for starters Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49199) Job DSL Authorizarion Matrix cannot manage the folder inheritance
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-49199 Job DSL Authorizarion Matrix cannot manage the folder inheritance Change By: Daniel Spilker Component/s: matrix-auth-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort commented on JENKINS-49686 Re: NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead So here's what I've got from digging (mostly to save my notes and provide transparency in case someone else sees something): The build nominally completed with a failure (tests failed, and you ran an Error step which was not caught) in FlowEndNode ID 1692 But somehow the build.xml shows: 1696 1693:1696 (flowHead id : flowNodeId for that head) And there are no flowNodes after 1692 in the storage. So what I'm trying to figure out is: How did the iota, head, and finalFlowNode ID get bumped above 1692? Does this occur with simpler builds? Or does it only happen when there's some specific structure including parallels (as with this one)? Why are we even trying to resume the build? We're done, kaput, finished, finito! The FlowEndNode has been written, and build ended with Failure result (as it should). This points to an issue specifically with the closedown of the build or checks on whether we need to resume the build (i.e. finished build showing as incomplete). The second part first: there's a 'done' flag on the CpsFlowExecution which if true marks the execution as complete. ODDLY this is absent in the persisted build record, and that appears to be normal somehow (going back to v2.0 of this plugin it is not persisted by the ConverterImpl that does marshall/unmarshall). Failing that, we look for having just a single head FlowNode (check!) and that head being a FlowEndNode (should have been the case?) Now for the end-of-build log: the execution sets itself to 'done' (which is not persisted, since that logic was not changed), sets the stored heads to just the first head (should be the FlowEndNode), and the flushes FlowNode storage. However, the WorkflowRun saves itself when done. Possible solutions: 1. Explicitly save 'done' in the flowExecution 2. Figure out why the FlowEndNode isn't ending up as the final head for the CpsFlowExecution thus signalling we're done done done. Add Comment
[JIRA] (JENKINS-49787) Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()
Title: Message Title Daniel Spilker assigned an issue to Stefan Brausch Jenkins / JENKINS-49787 Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save() Change By: Daniel Spilker Assignee: Daniel Spilker Stefan Brausch Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38397) Regarding aws device farm error
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Provide a minimal script that reproduced the problem. Use markup to properly format the script so that it's human readable. Jenkins / JENKINS-38397 Regarding aws device farm error Change By: Daniel Spilker Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50014) Failed to retrieve git references (java.lang.NullPointerException on git parameter)
Title: Message Title Boguslaw Klimas commented on JENKINS-50014 Re: Failed to retrieve git references (java.lang.NullPointerException on git parameter) I can't reproduce this issue. You really don't have any interested information after 'Caused by: java.lang.NullPointerException'? Eg. Caused by: java.lang.NullPointerException at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:) Could you atached some more logs or configuration the job, in which this problem occurred? I understud that this issue occured after update git-parameter plugin? have you update any other plugin? (git-plugin, git-client-plugin, ...)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50198) node config gets overridden when spinning up node via Ec2 plugin
Title: Message Title Dan Marshall commented on JENKINS-50198 Re: node config gets overridden when spinning up node via Ec2 plugin Yes, every job has either the ‘general’ or ‘devops’ label, but because we share this jenkins instance with developers who shouldn’t be able to run on the ‘devops’ node we need to restrict it at the node level. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Stephen Connolly commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up Now if we have the order different: $ git remote add origin g...@git.example.com:/development.git $ git remote add production g...@git.example.com:/production.git $ git fetch origin feature-1 $ git push origin :feature-1 $ git push production feature-1 In this case, it is even more critical that we do not delete the branch immediately as if we followed Joshua Noble's suggestion the job history would be erased by the origin branch being deleted and then the production branch would be starting from build #1 again. If the user actually wants the build history reset, then all they need to do is use the Jenkins UI to delete the dead branch before doing the push of the branch to production Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Stephen Connolly resolved as Not A Defect It is not possible with the design of the API to know if the event means that the job should be deleted or if a lower priority source in the multibranch project has already received an event for the same branch being created because the branch is being moved from one source to another. e.g. if you configure two sources in the same multibranch: g...@git.example.com:/development.git g...@git.example.com:/production.git Now suppose you do something like: $ git remote add origin g...@git.example.com:/development.git $ git remote add production g...@git.example.com:/production.git $ git fetch origin feature-1 $ git push production feature-1 $ git push origin :feature-1 So what happens if we follow Joshua Noble's suggestion is Jenkins gets the event from "production" saying "new branch 'feature-1'" and we say: "cool, but development is higher in the list of sources and already owns that branch name... I'll just drop that event on the floor" Jenkins gets the event from "development" saying "branch 'feature-1' has been deleted" and we'd delete the job and its history. So you would lose all the job history of feature-1 being developed. What happens currently is as follows: Jenkins gets the event from "production" saying "new branch 'feature-1'" and we say: "cool, but development is higher in the list of sources and already owns that branch name... I'll just drop that event on the floor" Jenkins gets the event from "development" saying "branch 'feature-1' has been deleted" and we mark the branch as dead. If there is a subsequent event from "production" we let that event "take over" the branch, and all is good, history retained. When the scan comes along, we get the full list of branches from each source in priority order and we assign the branch to "production" as a live branch, because the revision is the same, we don't trigger a rebuild Jenkins / JENKINS-42519 Closed pull requests, branch jobs are not cleaned up
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Stephen Connolly closed an issue as Fixed Resolution: Install Basic Branch Build Strategies plugin and add the "Change Requests" with "Ignore rebuilding merge branches when only the target branch changed" selected to your build strategies Jenkins / JENKINS-37491 Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes Change By: Stephen Connolly Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Stephen Connolly commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes For the record, if you want to avoid triggering rebuilds when just the target branch of the PR has changed then you want https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc#change-requests IMHO this problem is closed by the feature "Ignore rebuilding merge branches when only the target branch changed" in the Basic Branch Build Strategy plugin's "Change Requests" strategy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45693) Apply ConsoleLogFilter
Title: Message Title
Markus Winter edited a comment on JENKINS-45693
Re: Apply ConsoleLogFilter
The drawback of doing it in {{LogActionImpl.stream}} is that this will not capture the complete output. What is missing is the started and finished messages from the listener and the intermediate output with the prefix. While the prefixed output is probably not that important, having the started by and the finished message when for example using the logstash plugin I would consider important . Not sure if JENKINS-38381 would solve that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Andrew Bayer commented on JENKINS-49893 Re: Declarative directive snippet generator So the stage form asks you to choose either steps or parallel, and then outputs something similar to that. We can tweak the commented help text if desired. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-49893 Declarative directive snippet generator Change By: Alex Taylor Attachment: Screen Shot 2018-03-15 at 4.59.02 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor commented on JENKINS-49893 Re: Declarative directive snippet generator Andrew Bayer One other suggestion towards this issue would be to not have required "generated code" but maybe have inline help for the basics of the generation much like the Parallel step inside of the current Snippet Generator Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50207) Transient error "container [*] does not exist in pod"
Title: Message Title
Michael Maletich created an issue
Jenkins / JENKINS-50207
Transient error "container [*] does not exist in pod"
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-03-15 20:57
Priority:
Minor
Reporter:
Michael Maletich
About 1 in every 4 of our builds dies with the error "container [] does not exist in pod []". Rerunning the build usually fixes the error.
podTemplate(label: 'docker-node',
containers: [
containerTemplate(name: 'python2', image: 'python:2.7.14', ttyEnabled: true, command: 'cat')
]
) {
node('docker-node') {
container('python2') {
checkout scm
stage("Setup") {
sh("pip install -r dev-requirements.txt")
}
stage("Lint") {
sh("make pep8")
}
stage("Tests") {
sh("make tests")
}
switch (env.BRANCH_NAME) {
case "master":
stage('Publish Package') {
withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: 'artifactory_jenkins',
usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
sh("printf '[distutils]\nindex-servers = local\n\n[local]\nusername: $USERNAME\npassword: %s' '$PASSWORD' > ~/.pypirc")
sh("python setup.py bdist_wheel upload -r local")
}
}
}
}
}
}
Running version 1.1.3 of the kubernetes plugin on Jenkins 2.89.4.
Happy to append any logs that might be necessary.
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title Cyrille Le Clerc commented on JENKINS-50099 Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay Thanks for the kind word Hartmut Benz. I don't know yet how we will be able to discover these runtime dependencies as they seem to not be catch by the org.apache.maven.project.DependencyResolutionResult event we are tracking. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Tom Skrainar commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Observing the same issue as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title guillermo casco commented on JENKINS-50131 Re: git parameter ok will try that, thank you for for your help! Regards.- Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Jay Spang edited a comment on JENKINS-41940 Re: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Just commenting that this is a feature we want as well. We used to use the [Heavy Job Plugin|https://plugins.jenkins.io/heavy-job], which did exactly what we need. We had to leave it behind when moving to pipelines. :(Our Jenkins instance has ~30 jobs, and almost all of them are relatively lightweight and can run in parallel with other jobs. However, 2-3 of them are large C++ compiles, which are very resource intensive and should NOT share the node with other jobs. In this situation, my choices are...1) Give my nodes only 1 executor. This results in lots of wasted capacity, as I have to spin up LOTS of nodes to ensure I can meet peak demand. 2) Give my nodes multiple executors. This results in frequent "slow builds" as Jenkins occasionally decides to run 2 compiles on the same node.Being able to say "this job is heavy and cannot share a node" would mitigate these pain points. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Jay Spang commented on JENKINS-41940 Re: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Just commenting that this is a feature we want as well. We used to use the Heavy Job Plugin, which did exactly what we need. We had to leave it behind when moving to pipelines. Our Jenkins instance has ~30 jobs, and almost all of them are relatively lightweight and can run in parallel with other jobs. However, 2-3 of them are large C++ compiles, which are very resource intensive and should NOT share the node with other jobs. In this situation, my choices are... 1) Give my nodes only 1 executor. This results in lots of wasted capacity, as I have to spin up LOTS of nodes to ensure I can meet peak demand. 2) Give my nodes multiple executors. This results in frequent "slow builds" as Jenkins occasionally decides to run 2 compiles on the same node. Being able to say "this job is heavy and cannot share a node" would mitigate these pain points. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50095) Remoting should check the "Remoting-Minimum-Version" header when connecting to the master
Title: Message Title Abhishek Gautam assigned an issue to Abhishek Gautam Jenkins / JENKINS-50095 Remoting should check the "Remoting-Minimum-Version" header when connecting to the master Change By: Abhishek Gautam Assignee: Abhishek Gautam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Mike Kozell updated an issue
Jenkins / JENKINS-50199
Failed pipeline jobs stuck running after incorrect resume
Change By:
Mike Kozell
h2. SetupJenkins v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Pipeline Groovy Plugin: 2.45 Script Security Plugin: 1.41Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobsh2. ProblemI logged into a Jenkins master and saw no builds running but there was a queue of about 10 jobs. When mousing over the queued jobs, I saw "pending - Already running 2 builds across all nodes". This is strange because no jobs were showing as running and no Jenkins agents or executors were showing any running builds.I then ran "http://xx.xxx.xxx.xxx:8080/computer/api/xml?tree=computer[executors[currentExecutable[url]],oneOffExecutors[currentExecutable[url]]]=//url=builds" which did show 5 builds were running. I checked these builds and they were red (failure) and were not running.h2. ResearchI checked the console log of a build that showed as running but isn't and saw the line below near the top of the log._*Resume disabled by user, switching to high-performance, low-durability mode.*_At the end of the of the log I saw the following:*_Finished: FAILURE_* *_Resuming build at Tue Mar 13 23:04:52 UTC 2018 after Jenkins restart_*h2. Why Resume Build?The build failed on *Mar 12, 2018 6:02:37 PM*. +Why did the build try to resume almost a day later+? The job and system durability are configured to not resume builds. Below are some details taken from the API for the build._class "hudson.model.OneOffExecutor" id "41" keepLog false number 41 queueId 7178 result "FAILURE" timestamp 1520877757466I checked the Java process on the server and it was last restarted on *March 02 2018*.+What triggered the "Jenkins restart" identified on Mar 13 23:04:52 UTC 2018 since the Java process was not restarted?++Why does this get the build stuck in a "running" state when it's not running?+h2. ScopeThis issue can be seen across many of our Jenkins masters. In each case we see "Resuming build at x after Jenkins restart" occur a few days after the build failure or abort even though Java was not restarted. This issue didn't occur on Jenkins 2.60.3 running the older (pre-durability configurable) Pipeline plugins.h2. LogsI checked the jenkins.log file and saw the following when the build was attempting to be resumed. {code:java}Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution onLoad WARNING: Pipeline state not properly persisted, cannot resume job/JENKINS-JOB-NAME1/42/ Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[OwnerJENKINS-JOB-NAME1/42:JENKINS-JOB-NAME1 #42] java.lang.NullPointerException at
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title Hartmut Benz commented on JENKINS-50099 Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay The work-around certainly makes the war-overlay being triggered after the war.jar has been built - thank you for that already. During the weekend, I will study which other effects the change from 'runtime' to 'compile' has on the generated artifact and post the results here. Thanks again for your support Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite edited a comment on JENKINS-50131 Re: git parameter [~yiyito] multi-branch Pipelines do not require docker and are much less messy than a single job which switches between different branches. Refer to the [simpler multi-branch Pipeline tutorial| tutorial https://jenkins.io/doc/book/pipeline/multibranch/#creating-a-multibranch-pipeline ] for an example of how easy it is. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite commented on JENKINS-50131 Re: git parameter guillermo casco multi-branch Pipelines do not require docker and are much less messy than a single job which switches between different branches. Refer to the [simpler multi-branch Pipeline tutorial|tutorial] for an example of how easy it is. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title guillermo casco commented on JENKINS-50131 Re: git parameter ok and the last one: Use a Freestyle job instead of a single Pipeline job and allow it to manage the branch checkout. Then the user can select from a pick list to choose the branch they want to build Is this better? is the branch checkout management UI configured through jenkins console? first option you said involves docker and other stuff to configure and looks a little bit messy. Doable, but messy thanks budy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45693) Apply ConsoleLogFilter
Title: Message Title Markus Winter commented on JENKINS-45693 Re: Apply ConsoleLogFilter The drawback of doing it in LogActionImpl.stream is that this will not capture the complete output. What is missing is the started and finished messages from the listener and the intermediate output with the prefix. While the prefixed output is probably not that important, having the started by and the finished message when for example using the logstash plugin. Not sure if JENKINS-38381 would solve that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite commented on JENKINS-50131 Re: git parameter Refer to the "Build a multibranch project" tutorial to see the difference between the job you have defined which uses a single job and switches between branches with that single job, and a multi-branch Pipeline which automatically creates a job per branch. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title guillermo casco commented on JENKINS-50131 Re: git parameter what do you mean multibranch? Is already a multibranch pipeline. Master branch has a groovy file which perform some steps inside the job (compile, build, etc), and the branch I created has another groovy which implement those same steps as master and also others I´m adding (compile, build, run tests, etc). Maybe yo refer to this option? adding more branches in there? check image. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title guillermo casco updated an issue Jenkins / JENKINS-50131 git parameter Change By: guillermo casco Attachment: br.JPG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50206) Allow plain text for credentialsId field.
Title: Message Title
Oscar Romero created an issue
Jenkins / JENKINS-50206
Allow plain text for credentialsId field.
Issue Type:
Improvement
Assignee:
Colin
Components:
marathon-plugin
Created:
2018-03-15 19:34
Priority:
Minor
Reporter:
Oscar Romero
Allow plain text for credentialsId field. instead of doing this: credentialsId: 'my_cred_id' I could do: credentialsId: '{"login_endpoint":"http://leader.mesos/acs/api/v1/auth/login","private_key":"-BEGIN PRIVATE KEY\n\n---END PRIVATE KEY\n","scheme":"RS256","uid":"jenkins-principal"}',
Add Comment
[JIRA] (JENKINS-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information
Title: Message Title suryatej yaramada commented on JENKINS-50005 Re: WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information After upgrading jenkins to LTS version along with plugin updates we are not seeing those errors so far Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50099 Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay [~benzht] problem identified ^^. Workaround: declare the war dependency of your overlay project with a scope "compile" instead of a scope "runtime". could this be acceptable for you? Solving JENKINS-50205 will solve this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50205) "runtime" scope dependencies are not tracked
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-50205 "runtime" scope dependencies are not tracked Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-03-15 18:52 Priority: Minor Reporter: Cyrille Le Clerc "runtime" scope dependencies are not tracked. See https://issues.jenkins-ci.org/browse/JENKINS-50099?focusedCommentId=332160=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-332160 * https://gist.github.com/cyrille-leclerc/bcb8e7d078570b7f7867eb55d0ed647c Add Comment
[JIRA] (JENKINS-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-50194 Build userId missing for a job being built by other Jobs Change By: Naresh Rayapati Summary: Child Builds Build userId missing for a job being built by other Jobs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title Cyrille Le Clerc commented on JENKINS-50099 Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay Hartmut Benz problem identified ^^. Workaround: declare the war dependency of your overlay project with a scope "compile" instead of a scope "runtime". could this be acceptable for you? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title Naresh Rayapati updated JENKINS-50194 Jenkins / JENKINS-50194 Child Builds Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title Naresh Rayapati commented on JENKINS-50194 Re: Child Builds PR: https://github.com/jenkinsci/jira-steps-plugin/pull/65 Matvey Kondratev Thanks for reporting this, it is been a while that I wanted to fix this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title Naresh Rayapati started work on JENKINS-50194 Change By: Naresh Rayapati Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-50099
Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Reproducing a test case with* [ https://github.com/cyrille-leclerc/my-war-overlay.git ] * [ https://github.com/cyrille-leclerc/my-war.git ] The runtime dependency of the overlay does NOT appear in the list of resolved dependencies of the maven project. Probably because it is flagged as a runtime dependency. [ https://gist.github.com/cyrille-leclerc/bcb8e7d078570b7f7867eb55d0ed647c ]The maven-war-plugin overlay docs clearly recommends to use a "runtime" scopehttps://maven.apache.org/plugins/maven-war-plugin/overlays.html{code:xml} com.example.projects documentedprojectdependency 1.0-SNAPSHOT war runtime... {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50099) Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50099 Re: Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay Reproducing a test case with* https://github.com/cyrille-leclerc/my-war-overlay.git* https://github.com/cyrille-leclerc/my-war.git The runtime dependency of the overlay does NOT appear in the list of resolved dependencies of the maven project. Probably because it is flagged as a runtime dependency.https://gist.github.com/cyrille-leclerc/bcb8e7d078570b7f7867eb55d0ed647c Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50204) Visualization of the credentials backed by Kubernetes secrets in Jenkins Credentials UI
Title: Message Title James Nord created an issue Jenkins / JENKINS-50204 Visualization of the credentials backed by Kubernetes secrets in Jenkins Credentials UI Issue Type: New Feature Assignee: James Nord Components: kubernetes-credentials-provider-plugin Created: 2018-03-15 18:33 Priority: Minor Reporter: James Nord We want to know which credentials have been loaded by the credentials-provider-for-kubernetes-secrets. The UI should display the available credentials (in read only mode) Add Comment
[JIRA] (JENKINS-50203) plugiun bundles jackson stuff
Title: Message Title James Nord created an issue Jenkins / JENKINS-50203 plugiun bundles jackson stuff Issue Type: Task Assignee: James Nord Components: kubernetes-credentials-provider-plugin Created: 2018-03-15 18:27 Priority: Minor Reporter: James Nord the following jars are bundled inside the plugin, they should really be removed and replaced with the jackson2-api plugin jackson-annotations-2.7.0.jar jackson-core-2.7.7.jar jackson-databind-2.7.7.jar jackson-dataformat-yaml-2.7.7.jar jackson-module-jaxb-annotations-2.7.5.jar Add Comment
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite edited a comment on JENKINS-50131 Re: git parameter [~yiyito] until that bug is fixed, I think your choices are:* Use a multi-branch Pipeline instead of a single Pipeline job and allow it to manage the branch checkout. Multi-branch Pipeline will create a job for each branch that contains a Jenkinsfile and will remove those jobs when the branch is deleted. Then there is no need to select from pick lists are to choose values branches since all the branches that contain a Jenkinsfile are always built * Use a Freestyle job instead of a single Pipeline job and allow it to manage the branch checkout. Then the user can select from a pick list to choose the branch they want to build Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title Mark Waite commented on JENKINS-50131 Re: git parameter guillermo casco until that bug is fixed, I think your choices are: Use a multi-branch Pipeline instead of a single Pipeline job and allow it to manage the branch checkout. Multi-branch Pipeline will create a job for each branch that contains a Jenkinsfile and will remove those jobs when the branch is deleted. Then there is no need to select from pick lists are choose values Use a Freestyle job instead of a single Pipeline job and allow it to manage the branch checkout. Then the user can select from a pick list to choose the branch they want to build Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50131) git parameter
Title: Message Title guillermo casco commented on JENKINS-50131 Re: git parameter Ok, so if this can´t be done with the plug in, how can I achieve running a JOB but instead of running master branch from repo, to be run from a different branch. I don´t want to modify master because is being used for the today´s deploys. I created a different branch, Now How can I do a checkout to that branch and using it when running the job in jenkins? Has to be a way or not? Mark Waite, Boguslaw Klimas ? I don´t know how to do this, please help! Thank you Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49682) Blue Ocean - hangs after selecting github organization
Title: Message Title
Alex Kravetz commented on JENKINS-49682
Re: Blue Ocean - hangs after selecting github organization
Vivek Pandey, Thank you this is very helpful. The curl request you was successful and returned my profile info. I then tried the repo list api via curl:
curl -v -H 'Authorization: token XXX' https://api.github.com/orgs/my_employer/repos
This is where I get a 403 error and the following JSON:
{
"message": "Resource protected by organization SAML enforcement. You must grant your personal token access to this organization.",
"documentation_url": "https://help.github.com/articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization"
}
This was my mistake - we use federated authentication and I hadn't granted access to the org via the SSO button in github. After granting that authorization, everything worked just fine. This is obviously a user error, but a more useful error message would be helpful. I am happy to contribute this bug fix. Where should I implement the error checking? Is it githubscm::connect? Thank you, Alex.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50201) include jackson-module-jaxb-annotations in the plugin
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-50201 include jackson-module-jaxb-annotations in the plugin Change By: Devin Nusbaum Labels: team-pre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50201) include jackson-module-jaxb-annotations in the plugin
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-50201
include jackson-module-jaxb-annotations in the plugin
Change By:
James Nord
The jackson-module-jaxb-annotations module is somewhat tied to the lifecycle of jackson and as such should ideally be provided in the plugin.Hence please include it in the plugin.{code:xml}com.fasterxml.jackson.modulejackson-module-jaxb-annotations{code} https://github.com/FasterXML/jackson-modules-base / https://github.com/FasterXML/jackson-module-jaxb-annotations (older versions)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50202) include jackson-dataformat-yaml in the plugin
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-50202 include jackson-dataformat-yaml in the plugin Change By: Devin Nusbaum Labels: team-pre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50202) include jackson-dataformat-yaml in the plugin
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-50202 include jackson-dataformat-yaml in the plugin Change By: Devin Nusbaum Labels: team-pre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50202) include jackson-dataformat-yaml in the plugin
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-50202
include jackson-dataformat-yaml in the plugin
Change By:
James Nord
The jackson- module dataformat - jaxb-annotations yaml module is somewhat tied to the lifecycle of jackson and as such should ideally be provided in the plugin.Hence please include it in the plugin.{code:xml}com.fasterxml.jackson. module dataformat jackson- module dataformat - jaxb-annotations yaml {code} https://github.com/FasterXML/jackson-dataformats-text / https://github.com/FasterXML/jackson-dataformat-yaml (older versions)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50201) include jackson-module-jaxb-annotations in the plugin
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-50201 include jackson-module-jaxb-annotations in the plugin Change By: Devin Nusbaum Labels: team-pre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50202) include jackson-dataformat-yaml in the plugin
Title: Message Title James Nord created an issue Jenkins / JENKINS-50202 include jackson-dataformat-yaml in the plugin Issue Type: Task Assignee: Devin Nusbaum Components: jackson2-api-plugin Created: 2018-03-15 17:38 Priority: Minor Reporter: James Nord The jackson-module-jaxb-annotations module is somewhat tied to the lifecycle of jackson and as such should ideally be provided in the plugin. Hence please include it in the plugin. com.fasterxml.jackson.module jackson-module-jaxb-annotations Add Comment
[JIRA] (JENKINS-50201) include jackson-module-jaxb-annotations in the plugin
Title: Message Title James Nord created an issue Jenkins / JENKINS-50201 include jackson-module-jaxb-annotations in the plugin Issue Type: Task Assignee: Devin Nusbaum Components: jackson2-api-plugin Created: 2018-03-15 17:37 Priority: Minor Reporter: James Nord The jackson-module-jaxb-annotations module is somewhat tied to the lifecycle of jackson and as such should ideally be provided in the plugin. Hence please include it in the plugin. com.fasterxml.jackson.module jackson-module-jaxb-annotations Add Comment
[JIRA] (JENKINS-49842) Publish jenkins/evergreen docker image
Title: Message Title R. Tyler Croy commented on JENKINS-49842 Re: Publish jenkins/evergreen docker image And we have our image automatically being published here Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49842) Publish jenkins/evergreen docker image
Title: Message Title R. Tyler Croy updated JENKINS-49842 Jenkins / JENKINS-49842 Publish jenkins/evergreen docker image Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Mike Kozell updated an issue
Jenkins / JENKINS-50199
Failed pipeline jobs stuck running after incorrect resume
Change By:
Mike Kozell
h2. SetupJenkins v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Pipeline Groovy Plugin: 2.45 Script Security Plugin: 1.41Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobsh2. ProblemI logged into a Jenkins master and saw no builds running but there was a queue of about 10 jobs. When mousing over the queued jobs, I saw "pending - Already running 2 builds across all nodes". This is strange because no jobs were showing as running and no Jenkins agents or executors were showing any running builds.I then ran "http://xx.xxx.xxx.xxx:8080/computer/api/xml?tree=computer[executors[currentExecutable[url]],oneOffExecutors[currentExecutable[url]]]=//url=builds" which did show 5 builds were running. I checked these builds and they were red (failure) and were not running.h2. ResearchI checked the console log of a build that showed as running but isn't and saw the line below near the top of the log._*Resume disabled by user, switching to high-performance, low-durability mode.*_At the end of the of the log I saw the following:*_Finished: FAILURE_* *_Resuming build at Tue Mar 13 23:04:52 UTC 2018 after Jenkins restart_*h2. Why Resume Build?The build failed on *Mar 12, 2018 6:02:37 PM*. +Why did the build try to resume almost a day later+? The job and system durability are configured to not resume builds. Below are some details taken from the API for the build._class "hudson.model.OneOffExecutor" id "41" keepLog false number 41 queueId 7178 result "FAILURE" timestamp 1520877757466I checked the Java process on the server and it was last restarted on *March 02 2018*.+What triggered the "Jenkins restart" identified on Mar 13 23:04:52 UTC 2018 since the Java process was not restarted?++Why does this get the build stuck in a "running" state when it's not running?+h2. ScopeThis issue can be seen across many of our Jenkins masters. In each case we see "Resuming build at x after Jenkins restart" occur a few days after the build failure or abort even though Java was not restarted. This issue didn't occur on Jenkins 2.60.3 running the older (pre-durability configurable) Pipeline plugins.h2. LogsI checked the jenkins.log file and saw the following when the build was attempting to be resumed. {code:java}Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution onLoad WARNING: Pipeline state not properly persisted, cannot resume job/JENKINS-JOB-NAME1/42/ Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[OwnerJENKINS-JOB-NAME1/42:JENKINS-JOB-NAME1 #42] java.lang.NullPointerException
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Mike Kozell updated an issue
Jenkins / JENKINS-50199
Failed pipeline jobs stuck running after incorrect resume
Change By:
Mike Kozell
h2. SetupJenkins v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Script Security Plugin: 1.41Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobsh2. ProblemI logged into a Jenkins master and saw no builds running but there was a queue of about 10 jobs. When mousing over the queued jobs, I saw "pending - Already running 2 builds across all nodes". This is strange because no jobs were showing as running and no Jenkins agents or executors were showing any running builds.I then ran "http://xx.xxx.xxx.xxx:8080/computer/api/xml?tree=computer[executors[currentExecutable[url]],oneOffExecutors[currentExecutable[url]]]=//url=builds" which did show 5 builds were running. I checked these builds and they were red (failure) and were not running.h2. ResearchI checked the console log of a build that showed as running but isn't and saw the line below near the top of the log._*Resume disabled by user, switching to high-performance, low-durability mode.*_At the end of the of the log I saw the following:*_Finished: FAILURE_* *_Resuming build at Tue Mar 13 23:04:52 UTC 2018 after Jenkins restart_*h2. Why Resume Build?The build failed on *Mar 12, 2018 6:02:37 PM*. +Why did the build try to resume almost a day later+? The job and system durability are configured to not resume builds. Below are some details taken from the API for the build._class "hudson.model.OneOffExecutor" id "41" keepLog false number 41 queueId 7178 result "FAILURE" timestamp 1520877757466I checked the Java process on the server and it was last restarted on *March 02 2018*.+What triggered the "Jenkins restart" identified on Mar 13 23:04:52 UTC 2018 since the Java process was not restarted?++Why does this get the build stuck in a "running" state when it's not running?+h2. ScopeThis issue can be seen across many of our Jenkins masters. In each case we see "Resuming build at x after Jenkins restart" occur a few days after the build failure or abort even though Java was not restarted. This issue didn't occur on Jenkins 2.60.3 running the older (pre-durability configurable) Pipeline plugins.h2. LogsI checked the jenkins.log file and saw the following when the build was attempting to be resumed. {code:java}Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution onLoad WARNING: Pipeline state not properly persisted, cannot resume job/JENKINS-JOB-NAME1/42/ Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[OwnerJENKINS-JOB-NAME1/42:JENKINS-JOB-NAME1 #42] java.lang.NullPointerException at
[JIRA] (JENKINS-50198) node config gets overridden when spinning up node via Ec2 plugin
Title: Message Title Francis Upton commented on JENKINS-50198 Re: node config gets overridden when spinning up node via Ec2 plugin Are you using labels to associate the AMI with the desired jobs? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Mike Kozell updated an issue
Jenkins / JENKINS-50199
Failed pipeline jobs stuck running after incorrect resume
Change By:
Mike Kozell
h2. SetupJenkins v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Script Security Plugin: 1.41Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobsh2. ProblemI logged into a Jenkins master and saw no builds running but there was a queue of about 10 jobs. When mousing over the queued jobs, I saw "pending - Already running 2 builds across all nodes". This is strange because no jobs were showing as running and no Jenkins agents or executors were showing any running builds.I then ran "http://xx.xxx.xxx.xxx:8080/computer/api/xml?tree=computer[executors[currentExecutable[url]],oneOffExecutors[currentExecutable[url]]]=//url=builds" which did show 5 builds were running. I checked these builds and they were red (failure) and were not running.h2. ResearchI checked the console log of a build that showed as running but isn't and saw the line below near the top of the log._*Resume disabled by user, switching to high-performance, low-durability mode.*_At the end of the of the log I saw the following:*_Finished: FAILURE_* *_Resuming build at Tue Mar 13 23:04:52 UTC 2018 after Jenkins restart_*h2. Why Resume Build?The build failed on *Mar 12, 2018 6:02:37 PM*. +Why did the build try to resume almost a day later+? The job and system durability are configured to not resume builds. Below are some details taken from the API for the build._class "hudson.model.OneOffExecutor" id "41" keepLog false number 41 queueId 7178 result "FAILURE" timestamp 1520877757466I checked the Java process on the server and it was last restarted on *March 02 2018*.+What triggered the "Jenkins restart" identified on Mar 13 23:04:52 UTC 2018 since the Java process was not restarted?++Why does this get the build stuck in a "running" state when it's not running?+h2. ScopeThis issue can be seen across many of our Jenkins masters. In each case we see "Resuming build at x after Jenkins restart" occur a few days after the build failure or abort even though Java was not restarted. This issue didn't occur on Jenkins 2.60.3 running the older (pre-durability configurable) Pipeline plugins.h2. LogsI checked the jenkins.log file and saw the following when the build was attempting to be resumed. {code:java}Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution onLoad WARNING: Pipeline state not properly persisted, cannot resume job/JENKINS-JOB-NAME1/42/ Mar 13, 2018 9:29:56 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[OwnerJENKINS-JOB-NAME1/42:JENKINS-JOB-NAME1 #42] java.lang.NullPointerException at
[JIRA] (JENKINS-50200) Label accepts 2 groovy variables when using && but not || operator
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-50200
Label accepts 2 groovy variables when using && but not || operator
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-15 17:20
Priority:
Minor
Reporter:
Alex Taylor
When running a pipeline, the label expects a string with the option of an operator. Apparently the && operator with 2 groovy variables will evaluate correctly but not a || operator. So this pipeline runs correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 && groovyLabel2){
echo "hello"
}
But this code does not run correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 || groovyLabel2){
echo "hello"
}
because it fails with this error:
java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStep.label expects class java.lang.String but received class java.lang.Boolean
I think that groovy is doing some funky parsing here and causing the error because what should be the only thing allowed would be something
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell created an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-api-plugin, workflow-cps-plugin Created: 2018-03-15 17:18 Priority: Critical Reporter: Mike Kozell Setup Jenkins v2.89.4 LTS Pipeline API Plugin: 2.26 Pipeline Nodes and Processes Plugin: 2.19 Durable Task Plugin: 1.18 Pipeline Job Plugin: 2.17 Pipeline Shared Groovy Libraries Plugin: 2.9 Pipeline Supporting APIs Plugin: 2.18 Script Security Plugin: 1.41 Pipeline Default Speed/Durability Level: Performance-Optimized "Do not allow the pipeline to resume if the master restarts": Enabled on all jobs Problem I logged into a Jenkins master and saw no builds running but there was a queue of about 10 jobs. When mousing over the queued jobs, I saw "pending - Already running 2 builds across all nodes". This is strange because no jobs were showing as running and no Jenkins agents or executors were showing any running builds. I then ran "http://xx.xxx.xxx.xxx:8080/computer/api/xml?tree=computer[executors[currentExecutable[url]],oneOffExecutors[currentExecutable[url]]]=//url=builds" which did show 5 builds were running. I checked these builds and they were red (failure) and were not running. Research I checked the console log of a build that showed as running but isn't and saw the line below near the top of the log. Resume disabled by user, switching to high-performance, low-durability mode. At the end of the of the log I saw the following: Finished: FAILURE Resuming build at Tue Mar 13 23:04:52 UTC 2018 after Jenkins restart Why Resume Build? The build failed on Mar 12, 2018 6:02:37 PM. Why did the build try to resume almost a day later? The job and system durability are configured to not resume builds. Below are some details taken from the API for the build. _class "hudson.model.OneOffExecutor" id "41" keepLog false number 41 queueId 7178 result "FAILURE" timestamp 1520877757466 I
[JIRA] (JENKINS-50198) node config gets overridden when spinning up node via Ec2 plugin
Title: Message Title
Dan Marshall created an issue
Jenkins / JENKINS-50198
node config gets overridden when spinning up node via Ec2 plugin
Issue Type:
Bug
Assignee:
Francis Upton
Attachments:
image-2018-03-15-17-09-26-148.png
Components:
ec2-plugin
Created:
2018-03-15 17:18
Environment:
Jenkins v2.73.3 ec2 1.38 job-restrictions 0.6
Labels:
ec2-plugin
Priority:
Minor
Reporter:
Dan Marshall
We have ephemeral nodes created by the EC2 plugin when needed by jobs. Since some jobs require elevated AWS permissions, we have created 2 cloud configurations ('general' and 'devops') with the latter having permissions to carry out actions such as create AMI etc. The problem we are trying to solve is that any of the other users can tell their job to use these nodes. The aim is to restrict the jobs that can be run on this node by using the job restrictions plugin to only allow jobs in a particular directory. The issue we are facing is that there doesn't appear to be a way to easily integrate the EC2 and Job Restrictions plugins with each other such that the necessary config is applied to the node as it is spun up. The workaround is currently an init script (on the node) which utilises jenkins-cli.jar to manipulate the node's config on the master. This works perfectly when the node is spun up manually via the configure nodes page (as seen below), but does not when a
[JIRA] (JENKINS-50197) Incorporate "pre-release" builds of plugins into Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50197 Incorporate "pre-release" builds of plugins into Jenkins Essentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50197) Incorporate "pre-release" builds of plugins into Jenkins Essentials
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50197 Incorporate "pre-release" builds of plugins into Jenkins Essentials Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-03-15 17:03 Priority: Minor Reporter: R. Tyler Croy At some point in the very near future, we'll want to incorporate some "pre-release" builds of various components, plugins, and core. From Carlos Sanchez, the following pull requests would be good first versions to support. https://github.com/jenkinsci/jenkins/pull/3302 https://github.com/jenkinsci/workflow-api-plugin/pull/67 https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/60 https://github.com/jenkinsci/workflow-step-api-plugin/pull/33 Add Comment
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-50195 Create a non root user for running Jenkins and the evergreen-client Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Shital Savekar commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" I would like to increase the Priority of this issue to "Major" since this issue is affecting a lot of users. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Patrik Boström commented on JENKINS-50178 Re: Unable to manually trigger builds because play button is not visible No problem, happy to help! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look closed an issue as Not A Defect Did not see "Enable manual builds" button. Issue resolved after enabling Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look commented on JENKINS-50178 Re: Unable to manually trigger builds because play button is not visible That worked. I was working on this issue all day yesterday and did notice that button. I appreciate your help and apologize for any inconvenience. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Patrik Boström edited a comment on JENKINS-50178 Re: Unable to manually trigger builds because play button is not visible Have you enabled Enable "Enable manual triggers" in the view configuration ? . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
