[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jan Bottek commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node we also saw this kind of issue with the AWS EC2 plugin by creating a new EC2 instance/slave on the fly - most of the times we get this error on windows machine when the slave is started via WinRM - on unix machines where the slave is started via SSH we never saw this issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54995) Jenkins Upgrade plugins without restart
Title: Message Title zhao ying commented on JENKINS-54995 Re: Jenkins Upgrade plugins without restart I meet this too！ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54997) Deprecated calls to Run.getLogFile
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-54997
Deprecated calls to Run.getLogFile
Change By:
Reinhold Füreder
Like in See JENKINS-54128 (and others like JENKINS-54840 ) {noformat}2018-12-01 04:00:45 WARNING [org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile] Avoid calling getLogFile on Recovery/ACME #129java.lang.UnsupportedOperationExceptionat org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082)at hudson.plugins.emailext.AttachmentUtils.attachSingleLog(AttachmentUtils.java:200)at hudson.plugins.emailext.AttachmentUtils.attachBuildLog(AttachmentUtils.java:238)at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:766)at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451)at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:224)at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:163)at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)at hudson.security.ACL.impersonate(ACL.java:290)at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)2018-12-01 04:00:45 WARNING [org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile] Avoid calling getLogFile on Recovery/ACME #129java.lang.UnsupportedOperationExceptionat org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082)at hudson.plugins.emailext.AttachmentUtils$LogFileDataSource.getContentType(AttachmentUtils.java:113)at javax.activation.DataHandler.getContentType(DataHandler.java:205)at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1318)at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1021)at javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:419)at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1345)at javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:2106)at javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:2074)at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1769)at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099)at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:484)at
[JIRA] (JENKINS-54997) Deprecated calls to Run.getLogFile
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-54997 Deprecated calls to Run.getLogFile Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-12-04 07:51 Environment: workflow-job 2.29 email-ext 2.63 Priority: Minor Reporter: Reinhold Füreder Like in JENKINS-54128 (and others) 2018-12-01 04:00:45 WARNING [org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile] Avoid calling getLogFile on Recovery/ACME #129 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1082) at hudson.plugins.emailext.AttachmentUtils.attachSingleLog(AttachmentUtils.java:200) at hudson.plugins.emailext.AttachmentUtils.attachBuildLog(AttachmentUtils.java:238) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:766) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:224) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:163) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at
[JIRA] (JENKINS-54593) jenkins is hanging after clean the system cache
Title: Message Title tang alby updated JENKINS-54593 I guess it has to do with the cache being remove. It's normal to use ldap when Jenkins runs for a while, Jenkins / JENKINS-54593 jenkins is hanging after clean the system cache Change By: tang alby Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54996) automatically setup of triggers on main repo
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54996
automatically setup of triggers on main repo
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-12-04 07:30
Priority:
Major
Reporter:
Dominik Bartholdi
currently webhooks (e.g. github or bitbucket) are only active after the first run of the pipeline. e.g. the following pipeline will not be triggered by a bitbucket commit hook until the build was kicked of manually at least once:
pipelineJob("install") {
triggers {
bitbucketPush()
}
definition {
cpsScm {
scm {
git {
remote {
url('https://bitbucket.org/myorg/myrepo')
credentials('BITBUCKET_CRED')
}
branches('develop')
scriptPath(’install.groovy')
lightweight(true)
extensions {
localBranch()
cleanCheckout()
}
}
}
}
}
}
This issue requests to automatically setup triggers for the main repo at job creation/ modification. This would ease the setup of such jobs with the job-dsl plugin a lot. No further manual triggering would be required.
[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Kirill Gostaf commented on JENKINS-54974 Re: Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Hi Oleg, As per your comment, I've attached report_threads1.log In addition, removing the claim plugin does not solve the issue. Startup then complained about the Radiator view plugin dependency on claim. Disabling the Radiator view plugin does not help. There was still a deadlock after having claim removed and radiatorviewplugin disabled. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2
Title: Message Title Kirill Gostaf updated an issue Jenkins / JENKINS-54974 Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2 Change By: Kirill Gostaf Attachment: report_threads1.log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42069) Upgrade plugins without restart
Title: Message Title shang yuzhe commented on JENKINS-42069 Re: Upgrade plugins without restart I met the same problem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54995) Jenkins Upgrade plugins without restart
Title: Message Title shang yuzhe assigned an issue to Daniel Beck Jenkins / JENKINS-54995 Jenkins Upgrade plugins without restart Change By: shang yuzhe Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42069) Upgrade plugins without restart
Title: Message Title zhao ying commented on JENKINS-42069 Re: Upgrade plugins without restart is there a plan to implement such in the near future？ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54995) Jenkins Upgrade plugins without restart
Title: Message Title shang yuzhe created an issue Jenkins / JENKINS-54995 Jenkins Upgrade plugins without restart Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-12-04 06:43 Environment: Jenkins version-2.107.3 Priority: Major Reporter: shang yuzhe Now I use Jenkins for CI. when I upgrade the plugins, jenkins needs to restart, then the plugins take effect. Is there a way in which we could upgrade plugins without restarting Jenkins? Or is there a plan to implement such in the near future? Thanks~ Add Comment
[JIRA] (JENKINS-45488) Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110)
Title: Message Title Olivier Lamy commented on JENKINS-45488 Re: Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110) possible related to JENKINS-51057 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54994) Jenkins always hang few hours
Title: Message Title yongwen zhao created an issue Jenkins / JENKINS-54994 Jenkins always hang few hours Issue Type: Bug Assignee: Unassigned Attachments: dump20181128.txt Components: core Created: 2018-12-04 05:48 Environment: Jenkins version: 1.642.4 OS: centOS 6.5 Java: 1.8.0_66 Priority: Critical Reporter: yongwen zhao Our Jenkins always hang every few hours, when it hanged all the threads in BLOCK or NATIVE status. Attached file is dump file when Jenkins hanged. Add Comment
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Nirmal Kumar commented on JENKINS-52669 Re: IndexOutOfBoundsException after upgrade to 1.2.3 Do we have any recent update on this issue? Looks the 1.2 version has some issues with resolving the artifacts. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title
Daniel Gront commented on JENKINS-54632
Re: dsl job doesn't create a build step for Performance Center using Jenkins API
Eduard Karlin, is the dsl file contains newly generated configuration from the pipeline syntax generator? Daniel Danan, for some reason he has this line which doesn't make sense project / builders << {'com.hp.application.automation.tools.run.PcBuilder'(plugin: 'hp-application-automation-tools-plugin@5.5'), would replacing all the com.hp to com.microfocus solve this?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Daniel Gront Environment: Windows 2012 Server, groovy dsl scripts are in BitBucket , plugin version 5.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Daniel Gront Labels: PerformanceCenter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Daniel Gront Component/s: hp-application-automation-tools-plugin Component/s: micro-focus-performance-center-integration-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Daniel Gront Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54993) Valgrind result: plugin crash with JellyTagException
Title: Message Title Colton Saska created an issue Jenkins / JENKINS-54993 Valgrind result: plugin crash with JellyTagException Issue Type: Bug Assignee: Johannes Ohlemacher Attachments: stack_trace.rtf Components: valgrind-plugin Created: 2018-12-04 05:02 Environment: Attempting to use Valgrind publisher plugin. Labels: valgrind publisher Priority: Major Reporter: Colton Saska Attached is the stack trace from the failed build. Add Comment
[JIRA] (JENKINS-45488) Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110)
Title: Message Title Olivier Lamy commented on JENKINS-45488 Re: Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110) do you still have the issue with last blue ocean version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45488) Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110)
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-45488 Pipeline: StackOverflowError at io.jenkins.blueocean.events.PipelineEventListener$StageEventPublisher.getParentBlock(PipelineEventListener.java:110) Change By: Olivier Lamy Assignee: Vivek Pandey Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54776) Node stays suspended after node is started
Title: Message Title Jie Shen commented on JENKINS-54776 Re: Node stays suspended after node is started Niels Oke Schmäschke Thanks for providing your configuration. I was unable to reproduce this issue in my environment before. I will use your configuration to check whether I could get any luck. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title
trejkaz commented on JENKINS-46831
Re: Not able to use a normal agent on stage when agent docker is declared globally
We hit this one today, but the issue linked in the description (JENKINS-33510) is marked as resolved. I assume it's now a different issue? I get the same error as above ("No such container: --").
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Michael Neale commented on JENKINS-54992 Re: Terrifying message makes me think Jenkins will delete my github repo proposed fix: https://github.com/jenkinsci/github-branch-source-plugin/pull/195 (many other options "delete" is used elsewhere so maybe it isn't a problem, other than in this case). It is deleteing something, just not the repository. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Michael Neale Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Issue Type: Bug Assignee: Francisco Fernández Attachments: image-2018-12-04-11-12-50-073.png Components: cloudbees-folder-plugin Created: 2018-12-04 00:12 Priority: Minor Reporter: Michael Neale When you go to delete a multibranch folder that is using Github as a branch source - you will see a message "delete repository". This is usually alarming as the access token used often has permissions to actually do this, but this is not the intent. This is due to the Pronoun for GithubSCMSource being "Repository". see https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.4.1/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L544 and the wording: https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.4.1/src/main/resources/org/jenkinsci/plugins/github_branch_source/Messages.properties#L40 This is then used in https://github.com/jenkinsci/cloudbees-folder-plugin/blob/cloudbees-folder-6.7/src/main/resources/com/cloudbees/hudson/plugins/folder/AbstractFolder/tasks-new.properties which ends up with the scary looking:
[JIRA] (JENKINS-54518) Multibranch pipeline: Incorrect branch sort order for plain Git sources
Title: Message Title Ivan Meredith commented on JENKINS-54518 Re: Multibranch pipeline: Incorrect branch sort order for plain Git sources I have no opinions here really. It does seem reasonable that master is at the top though, although it breaks ordering. Ideally there would be several ways to sort but there is not, so whatever you think is best is probably ok Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47996) Don't record dependencies to self-generated artifacts
Title: Message Title
Cyrille Le Clerc commented on JENKINS-47996
Re: Don't record dependencies to self-generated artifacts
Markus Dlugi, rhierlmeier we are introducing a change in the way we prevent triggering side branches of multi-module projects. We revisited this code because Thorsten Langer reported JENKINS-54515 and because we have more flexibility to query the database now that we support MySQL as a backend in addition to H2.
Would you mind testing the beta version 3.6.4-beta-1 https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
To verify, please enable logs org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener at the FINE level and see message such as
[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 for
MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) }
because it generates artifact with same groupId:artifactId
MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }
Please ensure that you use a MySQL database instead of the embedded H2 database as documented in "Using a MySQL Database"
To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-54515
Re: master triggers own branches
* Please test beta version 3.6.4-beta-1* To verify, please enable logs {{org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener}} at the FINE level and see message such as {noformat}[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 for MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) } because it generates artifact with same groupId:artifactId MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }{noformat}* Please ensure that you use a MySQL database instead of the embedded H2 database as documented in " [Using a MySQL Database|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)] " To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50931) EC2 Instance cap is not respected
Title: Message Title A B commented on JENKINS-50931 Re: EC2 Instance cap is not respected An update - the problem is definitely getting worse. With an instance cap of 1, I am routinely getting 10 or more slaves starting up. Only thing that has changed is AWS (I haven't changed the Jenkins configuration at all). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jesse Glick commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node If reporter/commenters are running the Docker Slaves plugin, that may be to blame. I do not think this plugin is maintained. CC Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Jesse Glick Component/s: docker-slaves-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jesse Glick commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node John Lengeling’s issue sounds like a garden-variety Remoting channel outage, which could have any of a host of root causes. Other reports sound a bit like JENKINS-41854, though there is not enough detail to tell. I was not familiar with that particular error message; from full-text search I can find this (plus an apparently copied usage in a much more obscure plugin). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Jesse Glick Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Jesse Glick Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin commented on JENKINS-54632 Re: dsl job doesn't create a build step for Performance Center using Jenkins API and on my old server I had the older version: Micro Focus Application Automation Tools This plugin allows integration with HP ALM, HP Unified Functional Testing, HP LoadRunner and HP Performance cente 4.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54463) add JCasC pipeline step
Title: Message Title Daniel Garzon commented on JENKINS-54463 Re: add JCasC pipeline step Ewelina Wilkosz Dominik Bartholdi I have started implementing this here: https://github.com/jenkinsci/configuration-as-code-plugin/pull/670. Comments welcomed! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin commented on JENKINS-54632 Re: dsl job doesn't create a build step for Performance Center using Jenkins API Daniel Gront Micro Focus Application Automation Tools This plugin enables integration with ALM, ALM Octane, Unified Functional Testing, LoadRunner, and Performance Center. 5.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Stephen Connolly The workaround described by users above results in the invocation of the DataBoundConstructor. Your "refactoring" of moving the Authenticator creation into that results in it not being called on Jenkins startup, so it's null until the ProxyConfiguration is saved. Does that look about right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54637) Create a servlet filter to prepopulate audit log attributes
Title: Message Title David Olorundare stopped work on JENKINS-54637 Change By: David Olorundare Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54089) Create an audit log destination global configuration
Title: Message Title David Olorundare stopped work on JENKINS-54089 Change By: David Olorundare Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54991) Verify Log4j Audit 1.0.1-rc1 works with plugin
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-54991 Verify Log4j Audit 1.0.1-rc1 works with plugin Issue Type: Task Assignee: David Olorundare Components: audit-log-plugin Created: 2018-12-03 19:52 Priority: Minor Reporter: Matt Sicker Vote thread here: https://lists.apache.org/thread.html/3047258d5d367185c70a4cc3a84d1c4f4ab2ec31a2cf1156ff1c222c@%3Cdev.logging.apache.org%3E Test that this 1.0.1 version works fine with the audit log plugin. If there are compatibility issues, report them upstream before the vote closes. Add Comment
[JIRA] (JENKINS-52784) Github Oauth Plugin Commit Authorization Strategy breaks only for one github scan org job surprisingly. The scan job only gets the authenticated user / hudson.model.Item read pe
Title: Message Title Pruthvi Raj Reddy Chukkannagari closed an issue as Fixed Jenkins / JENKINS-52784 Github Oauth Plugin Commit Authorization Strategy breaks only for one github scan org job surprisingly. The scan job only gets the authenticated user / hudson.model.Item read permissions in the acl failing org. Change By: Pruthvi Raj Reddy Chukkannagari Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54990) 404 on jenkins lts 2.138.2/3 github org workflow/multibranch jobs with github authorization
Title: Message Title Pruthvi Raj Reddy Chukkannagari created an issue Jenkins / JENKINS-54990 404 on jenkins lts 2.138.2/3 github org workflow/multibranch jobs with github authorization Issue Type: Bug Assignee: Sam Gleske Components: credentials-plugin, github-oauth-plugin Created: 2018-12-03 18:49 Labels: Jenkins github-branch-source Credentials Priority: Critical Reporter: Pruthvi Raj Reddy Chukkannagari When: The LTS versions 2.138.2 and above are causing 404 on Jenkins for Github Organization and multibranch workflow jobs. Authorization strategy is Github commit authorization strategy. Last Stable: 404 's do not occur in 2.138.1. version Logs: could see an anonymous class exception for credentials.jar file Add Comment
[JIRA] (JENKINS-54989) "No valid crumb was included in the request" just watching a log
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-54989 "No valid crumb was included in the request" just watching a log Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-03 17:58 Environment: Jenkins ver. 2.121.2 Priority: Blocker Reporter: Brian J Murrell I have been seeing various random No valid crumb was included in the request errors lately but as annoying as they are, a page refresh would typically make it go away. Today, many times while doing nothing more than just watching a job's Console log scroll by I will get one of these and no amount of refreshing the page will resolve it. This is making Jenkins pretty much useless to use, hence the Blocker status. Add Comment
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Ramon Leon commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Daniel Beck Also CC Ramon Leon who got JENKINS-54459 merged, but I'd be more surprised if this is the cause than the other., The code involved in JENKINS-54459 has nothing to do with the problem, it doesn't touch the way we use proxy or get the json, IMO. What's going on is that now, this code is trying to get the update center for the number of times specified, therefore the error log shows each attempt. But the error is the same as without the retries, that is, a 407 in the update site defined. I cannot understand why the proxy was unset. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump{noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066)
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump{noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066)
[JIRA] (JENKINS-54731) Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts
Title: Message Title Ramon Leon updated JENKINS-54731 Jenkins / JENKINS-54731 Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts Change By: Ramon Leon Status: In Review Resolved Resolution: Fixed Released As: https://jenkins.io/changelog/#v2.153 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54988 jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck Change By: Alexey Grigorov Attachment: 2018-12-01 23_13_46-Jenkins.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-54988 jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-12-03 17:38 Priority: Critical Reporter: Alexey Grigorov Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262 Here is a stacktrace from a threadddump "jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190)
[JIRA] (JENKINS-54964) Add debugging documentation to the ATH repo
Title: Message Title Ramon Leon updated JENKINS-54964 Merged Jenkins / JENKINS-54964 Add debugging documentation to the ATH repo Change By: Ramon Leon Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54975) Add java 11 documentation to the ATH repo
Title: Message Title Ramon Leon updated JENKINS-54975 Merged documentation at https://github.com/jenkinsci/acceptance-test-harness/pull/463 Jenkins / JENKINS-54975 Add java 11 documentation to the ATH repo Change By: Ramon Leon Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-54515
Re: master triggers own branches
* Please test beta version 3.6.4-beta-1* To verify, please enable logs {{org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener}} at the FINE level and see message such as{noformat}[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 forMavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) }because it generates artifact with same groupId:artifactIdMavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }{noformat}* Please ensure that you use a MySQL database instead of the embedded H2 database as documented in [Using a MySQL Database|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)]To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc commented on JENKINS-54515
Re: master triggers own branches
Please test beta version 3.6.4-beta-1
To verify, please enable logs org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener at the FINE level and see message such as
[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 for MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) } because it generates artifact with same groupId:artifactId MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }
Please ensure that you use a MySQL database instead of the embedded H2 database as documented in Using a MySQL Database
To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen edited a comment on JENKINS-53030 Re: Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Sorry updating the wrong job. I Internally we have had to the same problem with the changelog files being read before the writer has finished. For the moment we work around this issue in the `p4-plugin` by catching the exception, logging the error and returning an empty ChangeLogSet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen commented on JENKINS-53030 Re: Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Sorry updating the wrong job. I have had to work around this issue in the `p4-plugin` by catching the exception, logging the error and returning an empty ChangeLogSet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Philip Johnson commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Rick Liu - I've run into this issue recently and it seems to occur when I up the polling time from 30 seconds to 300. If I use 30, it works again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54987) BlueOcean not opening builds created within folders
Title: Message Title Nelu Vasilica created an issue Jenkins / JENKINS-54987 BlueOcean not opening builds created within folders Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-12-03 17:02 Priority: Major Reporter: Nelu Vasilica Pipeline builds created within folders cannot be accessed directly via BlueOcean. Link when clicking on BlueOcean icon for a pipeline build looks like: blue/organizations/jenkins/testing%2Ftesting and troughs an http 400 error. Freestyle builds within folders don't seem to be affected by this issue. Add Comment
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen updated JENKINS-53030 Jenkins / JENKINS-53030 Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Change By: Paul Allen Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-53030 Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Change By: Paul Allen Labels: P4_A SAXParseException ioexception2 parallel Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen stopped work on JENKINS-53030 Change By: Paul Allen Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52209) [Cancelling nested steps due to timeout] aborts a job prematurely
Title: Message Title Adam Carroll commented on JENKINS-52209 Re: [Cancelling nested steps due to timeout] aborts a job prematurely I had this happen to me as well, the last 6 function calls of the OP match my last 6. It appears that deleteRecursive times out, as I have a number of agents that I was looping over to clean up and one of them got the java.lang.InterruptedException after exactly 5 minutes and 0 seconds of runtime. There is no timeout wrapper around this stage (other timeouts in the pipeline are 10 minutes anyway). This is in a cleanup stage using a multibranch pipeline (I unfortunately cannot share my Jenkinsfile). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_A P4_VERIFY SAXParseException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_A P4_VERIFY SAXParseException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen started work on JENKINS-52661 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated JENKINS-52661 Ready for release. Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-54841 Invalid characters in changelist triggers SAXParseException Change By: Paul Allen Labels: P4_VERIFY P4_A Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Paul Allen updated JENKINS-54841 Ready for release. Jenkins / JENKINS-54841 Invalid characters in changelist triggers SAXParseException Change By: Paul Allen Status: In Progress Fixed but Unreleased Assignee: Paul Allen Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54841) Invalid characters in changelist triggers SAXParseException
Title: Message Title Paul Allen started work on JENKINS-54841 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Mark Waite edited a comment on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) [~swtch3k] worspace workspace polling for Freestyle jobs does not require the same workspace for each build. If a workspace does not exist on the agent performing the poll, then a complete workspace is created for it. I have not performed deep checks of the behavior of Pipelines (that are not multibranch) with workspace based polling. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Mark Waite commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Cenk Tosun worspace polling for Freestyle jobs does not require the same workspace for each build. If a workspace does not exist on the agent performing the poll, then a complete workspace is created for it. I have not performed deep checks of the behavior of Pipelines (that are not multibranch) with workspace based polling. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45942) Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy
Title: Message Title Jen Varela Lijó commented on JENKINS-45942 Re: Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy Oleg Nenashev I would like to give it a go as a first time contribution, if I get to reproduce the issue : ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title
Nicolas MENETRIER edited a comment on JENKINS-54557
Re: hudson.AbortException: Ansible playbook execution failed
We are experiencing the same issue as [~aulius] when using the ansible plugin (since the beginning or middle of November too).At the same time we noticed that the last log lines of the ansible playbook were missing when the playbook was exiting in error state when played on a jenkins non master jenkins node.And it is really complicated to understand the playbooks issues without the last log lines.We found a dirty fix by adding a Thread.Sleep in AnsiblePlaybookBuilder.java, before throwing the exceptions in the perform function.{code:java}public void perform(@Nonnull Run run, @Nonnull Node node, @Nonnull FilePath ws, @Nonnull Launcher launcher, @Nonnull TaskListener listener, EnvVars envVars)throws InterruptedException, IOException{try {CLIRunner runner = new CLIRunner(run, ws, launcher, listener);String exe = AnsibleInstallation.getExecutable(ansibleName, AnsibleCommand.ANSIBLE_PLAYBOOK, node, listener, envVars);AnsiblePlaybookInvocation invocation = new AnsiblePlaybookInvocation(exe, run, ws, listener, envVars);invocation.setPlaybook(playbook);invocation.setInventory(inventory);invocation.setLimit(limit);invocation.setTags(tags);invocation.setSkippedTags(skippedTags);invocation.setStartTask(startAtTask);invocation.setBecome(become, becomeUser);invocation.setSudo(sudo, sudoUser);invocation.setForks(forks);invocation.setCredentials(StringUtils.isNotBlank(credentialsId) ?CredentialsProvider.findCredentialById(credentialsId, StandardUsernameCredentials.class, run) : null,copyCredentialsInWorkspace);invocation.setVaultCredentials(StringUtils.isNotBlank(vaultCredentialsId) ?CredentialsProvider.findCredentialById(vaultCredentialsId, StandardCredentials.class, run) : null);invocation.setExtraVars(extraVars);invocation.setAdditionalParameters(additionalParameters);invocation.setDisableHostKeyCheck(disableHostKeyChecking);invocation.setUnbufferedOutput(unbufferedOutput);invocation.setColorizedOutput(colorizedOutput);if (!invocation.execute(runner)) {throw new AbortException("Ansible playbook execution failed");}} catch (IOException ioe) {Thread.sleep(1);Util.displayIOException(ioe, listener);ioe.printStackTrace(listener.fatalError(hudson.tasks.Messages.CommandInterpreter_CommandFailed()));throw ioe;} catch (AnsibleInvocationException aie) {Thread.sleep(1);listener.fatalError(aie.getMessage());throw new AbortException(aie.getMessage());}}{code}
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title
Nicolas MENETRIER commented on JENKINS-54557
Re: hudson.AbortException: Ansible playbook execution failed
We are experiencing the same issue as Paulius Bulotas when using the ansible plugin (since the beginning or middle of November too). At the same time we noticed that the last lines of the ansible playbook were missing when the playbook was exiting in error state when played on a jenkins non master node. And it is really complicated to understand the playbooks issues without the last log lines. We found a dirty fix by adding a Thread.Sleep in AnsiblePlaybookBuilder.java, before throwing the exceptions in the perform function.
public void perform(@Nonnull Run run, @Nonnull Node node, @Nonnull FilePath ws, @Nonnull Launcher launcher, @Nonnull TaskListener listener, EnvVars envVars)
throws InterruptedException, IOException
{
try {
CLIRunner runner = new CLIRunner(run, ws, launcher, listener);
String exe = AnsibleInstallation.getExecutable(ansibleName, AnsibleCommand.ANSIBLE_PLAYBOOK, node, listener, envVars);
AnsiblePlaybookInvocation invocation = new AnsiblePlaybookInvocation(exe, run, ws, listener, envVars);
invocation.setPlaybook(playbook);
invocation.setInventory(inventory);
invocation.setLimit(limit);
invocation.setTags(tags);
invocation.setSkippedTags(skippedTags);
invocation.setStartTask(startAtTask);
invocation.setBecome(become, becomeUser);
invocation.setSudo(sudo, sudoUser);
invocation.setForks(forks);
invocation.setCredentials(StringUtils.isNotBlank(credentialsId) ?
CredentialsProvider.findCredentialById(credentialsId, StandardUsernameCredentials.class, run) : null,
copyCredentialsInWorkspace);
invocation.setVaultCredentials(StringUtils.isNotBlank(vaultCredentialsId) ?
CredentialsProvider.findCredentialById(vaultCredentialsId, StandardCredentials.class, run) : null);
invocation.setExtraVars(extraVars);
invocation.setAdditionalParameters(additionalParameters);
invocation.setDisableHostKeyCheck(disableHostKeyChecking);
invocation.setUnbufferedOutput(unbufferedOutput);
invocation.setColorizedOutput(colorizedOutput);
if (!invocation.execute(runner)) {
throw new AbortException("Ansible playbook execution failed");
}
} catch (IOException ioe) {
Thread.sleep(1);
Util.displayIOException(ioe, listener);
ioe.printStackTrace(listener.fatalError(hudson.tasks.Messages.CommandInterpreter_CommandFailed()));
throw ioe;
} catch (AnsibleInvocationException aie) {
Thread.sleep(1);
listener.fatalError(aie.getMessage());
throw new AbortException(aie.getMessage());
}
}
[JIRA] (JENKINS-50532) Failing nested parallel stages are marked green
Title: Message Title Daniel Kurzynski commented on JENKINS-50532 Re: Failing nested parallel stages are marked green Pull Request is open: https://github.com/jenkinsci/blueocean-plugin/pull/1886 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Paulius Bulotas commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed I can add that we are also experiencing such issue with Jenkins master/slave on latest Centos 7, running Jenkins 2.138.3. Thread dump looks like: FATAL: command execution failed hudson.AbortException: Ansible playbook execution failed at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:262) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:400) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:321) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) This started happening in middle of November after some plugin update. All runs fail in less than 4 minutes (not sure if it's related to some timeout). ansible 2.7.2 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/.../.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are
[JIRA] (JENKINS-54986) Pull request build fails with NullPointer exception
Title: Message Title
Vladimir Nemergut created an issue
Jenkins / JENKINS-54986
Pull request build fails with NullPointer exception
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
2018-12-03 15:49
Priority:
Blocker
Reporter:
Vladimir Nemergut
We configured Service Hooks in Azure DevOps to invoke Jenkins job when a pull request is created. The service hook fails with the following response: Status Code: 400 Reason Phrase: Bad Request HTTP Version: 1.1 Headers: { Connection: keep-alive X-Content-Type-Options: nosniff X-Error-Message: Object is null (through reference chain: net.sf.json.JSONObject["team-event"]->net.sf.json.JSONObject["resource"]->net.sf.json.JSONObject["repository"]->net.sf.json.JSONObject["project"]->net.sf.json.JSONObject["defaultTeamImageUrl"]->net.sf.json.JSONNull["empty"]) Date: Mon, 03 Dec 2018 15:37:36 GMT Server: nginx/1.8.1 Content-Length: 10316 Content-Type: text/plain; charset=utf-8 }
Add Comment
[JIRA] (JENKINS-42136) shared-library abstraction causing RejectedExecutionException when running sh() commands
Title: Message Title
Hayden Ball edited a comment on JENKINS-42136
Re: shared-library abstraction causing RejectedExecutionException when running sh() commands
I'm seeing this intermittently when using a shared declarative pipeline (i.e. [https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines)].{code:java}Task okhttp3.RealCall$AsyncCall@29e44de7 rejected from java.util.concurrent.ThreadPoolExecutor@19b44afc[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 77]{code}I 'm should be running at well under "Max connections to Kubernetes API" (although I have just bumped that to see if it makes a difference), so I'm not convinced this is the issue. I'm seeing this with 3 concurrent jobs, with max connections set to 48.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42136) shared-library abstraction causing RejectedExecutionException when running sh() commands
Title: Message Title Hayden Ball commented on JENKINS-42136 Re: shared-library abstraction causing RejectedExecutionException when running sh() commands I'm seeing this intermittently when using a shared declarative pipeline (i.e. https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines). Task okhttp3.RealCall$AsyncCall@29e44de7 rejected from java.util.concurrent.ThreadPoolExecutor@19b44afc[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 77] I'm running at well under "Max connections to Kubernetes API" (although I have just bumped that to see if it makes a difference), so I'm not convinced this is the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54862) PCT: Add support of passing plugin version overrides
Title: Message Title Adrien Lecharpentier updated JENKINS-54862 Jenkins / JENKINS-54862 PCT: Add support of passing plugin version overrides Change By: Adrien Lecharpentier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54985) Trigger email alerts to multiple mail id in Jenkins
Title: Message Title sreedevi v created an issue Jenkins / JENKINS-54985 Trigger email alerts to multiple mail id in Jenkins Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-12-03 14:56 Environment: below version of 2.138.3 Priority: Major Reporter: sreedevi v not able to add multiple mail id;s in reply list while configuring e-mail for jenkins. 1.tried comma seperation, 2.also comma seperation with one space. but issue not resolved. please help Add Comment
[JIRA] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin
Title: Message Title mike bayer commented on JENKINS-54415 Re: jep-200 issue w/ matrix reloaded plugin im on jenkins 2.138.3 now, have re-installed the matrix reloaded plugin after not having it for a few weeks and not seeing any of those errors, for some reason, and matrix builds are coming out fine including reloaded ones. but i dont know under what circumstances this serialization occurred. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22774) Crowd2 does not honor Crowd's Session Timeout
Title: Message Title Martin Spielmann updated JENKINS-22774 will be handled in more current task JENKINS-51734 that also has more details Jenkins / JENKINS-22774 Crowd2 does not honor Crowd's Session Timeout Change By: Martin Spielmann Status: In Review Resolved Assignee: Kanstantsin Shautsou Martin Spielmann Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22774) Crowd2 does not honor Crowd's Session Timeout
Title: Message Title Martin Spielmann closed an issue as Incomplete Jenkins / JENKINS-22774 Crowd2 does not honor Crowd's Session Timeout Change By: Martin Spielmann Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22774) Crowd2 does not honor Crowd's Session Timeout
Title: Message Title Martin Spielmann updated JENKINS-22774 Jenkins / JENKINS-22774 Crowd2 does not honor Crowd's Session Timeout Change By: Martin Spielmann Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54984) PipelineJob() publishers deprecated - how to send a notifications
Title: Message Title Constantin Bugneac updated an issue Jenkins / JENKINS-54984 PipelineJob() publishers deprecated - how to send a notifications Change By: Constantin Bugneac Hi,I'm using a jobs DSL plugin (1.70) & Jenkins (2.152) to create a bunch of pipelineJobs (via seed job).Now I need to be able to send a Slack notifications in case the of build failure.Looking at this doc [https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-publishers] it seems that publishers is deprecated for pipelineJob() but still OK for job() calls.I don't want to use a functionality which is going to be removed in feature and thus break Jenkins jobs. Could you please advise how can I trigger some sort pf of postBuild script/job in pipelineJob() to send a notification ?Is there any replacement/equivalent for publishers in pipelineJob() ? PS: I've got slackSend (slack plugin) working fine in a test scripted Pipeline job but cannot figure out how to add it to the seed job which calls pipelineJob() to create all the other jobs (many in number). Thanks,Constantin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Oleg Nenashev commented on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account Historical reasons. I believe that part of the code was originally written for Sun JVMs, maybe before OpenJDK was formalized and established Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-53030 Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Change By: Paul Allen Labels: P4_A SAXParseException ioexception2 parallel Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52124) Jenkins Crowd2 plugin does not return all groups from CROWD
Title: Message Title Martin Spielmann closed an issue as Fixed got no further feedback. please reopen if problem persists. Jenkins / JENKINS-52124 Jenkins Crowd2 plugin does not return all groups from CROWD Change By: Martin Spielmann Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen updated JENKINS-53030 Jenkins / JENKINS-53030 Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Paul Allen started work on JENKINS-53030 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54984) PipelineJob() publishers deprecated - how to send a notifications
Title: Message Title Constantin Bugneac created an issue Jenkins / JENKINS-54984 PipelineJob() publishers deprecated - how to send a notifications Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-12-03 14:41 Priority: Minor Reporter: Constantin Bugneac Hi, I'm using a jobs DSL plugin (1.70) & Jenkins (2.152) to create a bunch of pipelineJobs (via seed job). Now I need to be able to send a Slack notifications in case the of build failure. Looking at this doc https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-publishers it seems that publishers is deprecated for pipelineJob() but still OK for job() calls. I don't want to use a functionality which is going to be removed in feature and thus break Jenkins jobs. Could you please advise how can I trigger some sort pf postBuild script/job in pipelineJob() to send a notification ? Is there any replacement/equivalent for publishers in pipelineJob() ? PS: I've got slackSend (slack plugin) working fine in a test scripted Pipeline job but cannot figure out how to add it to the seed job which calls pipelineJob() to create all the other jobs (many in number). Thanks, Constantin Add Comment
[JIRA] (JENKINS-16703) Too many periodic requests to Crowd server
Title: Message Title Martin Spielmann closed an issue as Fixed got no further feedback. please reopen if problem persists Jenkins / JENKINS-16703 Too many periodic requests to Crowd server Change By: Martin Spielmann Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Benoit Le Gall commented on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account Question: why isn't a default installer for open-jdk ? Cause there is a plugin, but no more upgraded (openJDK-native-plugin) :/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54983) Hitting Bitbucket API Rate limit quite easily
Title: Message Title Mathias Immerkær created an issue Jenkins / JENKINS-54983 Hitting Bitbucket API Rate limit quite easily Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-12-03 14:19 Environment: Jenkins ver. 2.138.1 Bitbucket Branch Source Plugin 2.2.12 Priority: Minor Reporter: Mathias Immerkær For a while our branching indexing took a while to finish and now I decided to look into why. The console output isn't very helpful so I had to stumble into a rather random log message from com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient. It says: "Bitbucket Cloud API rate limit reached, sleeping for 5 sec then retry..." So I figured this was the issue. If I put in a new user, the indexing is fast for some time, then it slows down and the log messages reappear so this sort of confirms my suspicion. We have a repo with ~300 branches that is periodically scanned every 5 minutes. I looked at the rates at https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html - Only three categories are limited to 1000 per hour but to me neither of them looks like it would limit checking of branch SHA's. Can somebody verify whether or not the branching is using the optimal calls to get branch SHA's? I have tried to see if I could figure out which HTTP(S) requests are used but I can't find anything useful in the logs.
[JIRA] (JENKINS-47776) sonarqube integration doesn't authenticate
Title: Message Title Christoph Forster edited a comment on JENKINS-47776 Re: sonarqube integration doesn't authenticate I managed it to send the Authentication using a "Jenkins Global Environment Variable" named "SONAR_AUTH_TOKEN".Also it is important (using SonarQube 7.4 and InfluxDB Plugin 1.20.1) to set an Environment Variable "SONAR_HOST_URL".Nevertheless I receive a JSonException now, but I don't receive JSon Content but the loading page of SonarQube this is another Problem ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
