[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51055 Re: Rebranding - HPE still appears in a few places in Job Configuration Code changed in jenkins User: Yafim Kazak Path: src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/a5e8ad19badaacb81e5d39685ef619c29ec52723 Log: Merge pull request #83 from danieldanan/latest JENKINS-51055: Rebranding - HPE still appears in a few places in Job … Compare: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/compare/956c745fa620...a5e8ad19bada *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51293) PCBuild pipeline gives java.lang.ClassCastException error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51293 Re: PCBuild pipeline gives java.lang.ClassCastException error Code changed in jenkins User: danieldanan Path: src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/91eef97e6f6805b303e1f0725c35ba255189ff39 Log: JENKINS-51293: PCBuild pipeline gives java.lang.ClassCastException error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51055 Re: Rebranding - HPE still appears in a few places in Job Configuration Code changed in jenkins User: danieldanan Path: src/main/java/com/hpe/application/automation/tools/model/ResultsPublisherModel.java src/main/resources/com/hpe/application/automation/tools/pipelineSteps/LoadRunnerTestStep/config.properties src/main/resources/com/hpe/application/automation/tools/pipelineSteps/SseBuildAndPublishStep/config.properties src/main/resources/com/hpe/application/automation/tools/pipelineSteps/UftScenarioLoadStep/config.properties src/main/resources/com/hpe/application/automation/tools/run/PcBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/PcBuilder/help-pcServerName.html src/main/resources/com/hpe/application/automation/tools/run/RunFromAlmBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/RunFromFileBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/SseBuilder/config.properties http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/4c329af0a786b87ac8221fe9eb1b5c891422de2a Log: Revert "JENKINS-51055: Rebranding - HPE still appears in a few places in Job Configuration" This reverts commit 86e1c2b57614e9369e4f4d941a6360645d51a8bb. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51055 Re: Rebranding - HPE still appears in a few places in Job Configuration Code changed in jenkins User: danieldanan Path: src/main/java/com/hpe/application/automation/tools/model/ResultsPublisherModel.java src/main/resources/com/hpe/application/automation/tools/pipelineSteps/LoadRunnerTestStep/config.properties src/main/resources/com/hpe/application/automation/tools/pipelineSteps/SseBuildAndPublishStep/config.properties src/main/resources/com/hpe/application/automation/tools/pipelineSteps/UftScenarioLoadStep/config.properties src/main/resources/com/hpe/application/automation/tools/run/PcBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/PcBuilder/help-pcServerName.html src/main/resources/com/hpe/application/automation/tools/run/RunFromAlmBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/RunFromFileBuilder/config.properties src/main/resources/com/hpe/application/automation/tools/run/SseBuilder/config.properties http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/86e1c2b57614e9369e4f4d941a6360645d51a8bb Log: JENKINS-51055: Rebranding - HPE still appears in a few places in Job Configuration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs Change By: Sunjoo Park Summary: A build job is over with incomplete build logs ( TBD) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs
Title: Message Title
Sunjoo Park updated an issue
Jenkins / JENKINS-51313
A build job is over with incomplete build logs
Change By:
Sunjoo Park
* (I'm updating a description now)** Problem* A normal build job is over with complete build logs including the last line like{code:java}Finished: SUCCESS{code}or{code:java}Finished: FAILURE{code} But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE).Also, They don't have log text after some time. * A build is in progress. But its logs has not been updated on the web UI * When I checked a build process on a agent at that time, it was a normal status and in-progess * A build process on a agent wasn't terminated . * There is no termination signal on a log text After a process was over on an agent, a build job was over on a master. But there is no additional message on it. Is there anyone who has an experience like this case?.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Change By: Sunjoo Park Attachment: agent-jvisual-vm-screen.png Attachment: partial-thread-tump.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Change By: Sunjoo Park Attachment: jenkins-thread-dump.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Change By: Sunjoo Park Attachment: jenkins-agent-thread-dump.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51316) NullPointerException when clicking 'Generate Key'
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-51316 NullPointerException when clicking 'Generate Key' Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-05-15 04:47 Environment: ec2 plugin 1.39 Priority: Minor Reporter: Owen Mehegan When I click 'Generate Key' in the plugin configuration UI, I get a NullPointerException: java.lang.NullPointerException at sun.invoke.util.ValueConversions.unboxBoolean(ValueConversions.java:103) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title
Sunjoo Park updated an issue
Jenkins / JENKINS-51313
A build job is over with incomplete build logs ( TBD)
Change By:
Sunjoo Park
*(I'm updating a description now)**Problem* A normal build job is over with complete build logs including the last line like{code:java}Finished: SUCCESS{code}or{code:java}Finished: FAILURE{code} But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE).Also, They don't have log text after some time. * A build is in progress. But its logs has not been updated on the web UI * When I checked a build process on a agent at that time, it was a normal status and in-progess * A build process on a agent wasn't terminated . * There is no termination signal on a log text After a process was over on an agent, a build job was over on a master. But there is no additional message on it. Is there anyone who has an experience like this case? .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51315) Region list not populated when using IAM roles/role assume
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-51315 Region list not populated when using IAM roles/role assume Change By: Owen Mehegan Environment: ec2 plugin 1.39 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Change By: Sunjoo Park Attachment: jenkins-agent-thread-dump.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title
Sunjoo Park updated an issue
Jenkins / JENKINS-51313
A build job is over with incomplete build logs ( TBD)
Change By:
Sunjoo Park
*(I'm updating a description now)**Problem* A normal build job is over with complete build logs including the last line like{code:java}Finished: SUCCESS{code}or{code:java}Finished: FAILURE{code} But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE).Also, They don't have log text after some time. * A build is in progress. But its logs has not been updated on the web UI * When I checked a build process on a agent at that time, it was a normal status and in-progess * A build process on a agent wasn't terminated . * There is no termination signal on a log text After a process was over on an agent, a build job was over on a master. But there is no additional message on it. Is there anyone who has an experience like this case?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park updated an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Change By: Sunjoo Park Environment: JDK- Oracle JDK 1.8.0_121- Oracle JDK 1.8.0_162 Jenkins Version:- 2.89.2 : A version that saw it at first- 2.107.2: Second Jenkins version. It shows a same problem Tomcat- 8.0.36 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title
Sunjoo Park updated an issue
Jenkins / JENKINS-51313
A build job is over with incomplete build logs ( TBD)
Change By:
Sunjoo Park
*(I'm updating a description now)**Problem* A normal build job is over with complete build logs including the last line like{code:java}Finished: SUCCESS{code}or{code:java}Finished: FAILURE{code} 1) But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE). 2) Also, They don't have log text after some time. Con * A build is in progress. But its logs has not been updated on the web UI * When I checked a build process on a agent at that time, it was a normal status and in-progess * A build process on a agent wasn't terminated . * There is no termination signal on a log text After a process was over on an agent, a build job was over on a master. But there is no additional message on it. Is there anyone who has an experience like this case?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51315) Region list not populated when using IAM roles/role assume
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-51315
Region list not populated when using IAM roles/role assume
Change By:
Owen Mehegan
My organization requires me to use IAM roles in order to access resources within AWS. When I add my credentials and IAM role and MFA token in the Jenkins Credentials UI, they are validated and I see a message saying that I have access to six regions. But then when I create a new "cloud" in the EC2 plugin configuration and choose those credentials, the region dropdown menu is never populated. Also, if I click the Test Connection button, I get this error:{{User: arn:aws:iam::[redacted] is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::[redacted]}} The full stack trace when I try to test connection is:{code:java}Failed to check EC2 credentialcom.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: User: arn:aws:iam::[redacted] is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::[redacted] (Service: AWSSecurityTokenService; Status Code: 403; Error Code: AccessDenied; Request ID: 44541dd4-57f4-11e8-bded-23dde271ec8b) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1639) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1304) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.doInvoke(AWSSecurityTokenServiceClient.java:1271) at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1247) at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.executeAssumeRole(AWSSecurityTokenServiceClient.java:454) at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.assumeRole(AWSSecurityTokenServiceClient.java:431) at com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl.getCredentials(AWSCredentialsImpl.java:124) at hudson.plugins.ec2.EC2Cloud.createCredentialsProvider(EC2Cloud.java:618) at hudson.plugins.ec2.EC2Cloud$DescriptorImpl.doTestConnection(EC2Cloud.java:757) at hudson.plugins.ec2.AmazonEC2Cloud$DescriptorImpl.doTestConnection(AmazonEC2Cloud.java:180) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at
[JIRA] (JENKINS-51315) Region list not populated when using IAM roles/role assume
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-51315
Region list not populated when using IAM roles/role assume
Change By:
Owen Mehegan
My organization requires me to use IAM roles in order to access resources within AWS. When I add my credentials and IAM role and MFA token in the Jenkins Credentials UI, they are validated and I see a message saying that I have access to six regions. But then when I create a new "cloud" in the EC2 plugin configuration and choose those credentials, the region dropdown menu is never populated. Also, if I click the Test Connection button, I get this error: {{ User: arn:aws:iam::[redacted] is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::[redacted] }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-51314) Console output show many http-outgoing strange code
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-51314 Console output show many http-outgoing strange code Issue Type: Story Assignee: Unassigned Components: core Created: 2018-05-15 03:51 Environment: OS: Linux. Jenkins ver. 2.107.1 Priority: Minor Reporter: Dennis Tran Hi, So far we have some job build, the console output show strange code like below, and we have to remove '-X' option in build goal configuration to get rid of. I think it happen after I upgrade Jenkins version. any idea? // [DEBUG] http-outgoing-0 >> "j[0x5]q4/J[0x18]^di[0x86][0xbf]C_[0xd6]G[0x1d][0xd4][0x7][0xf3] [0xc7][0x14][0xdf][0x8d][0xe1][0x13][0xd8]$y|#[0x1e][0xbf][0xe6][0x81]<[0xca][0x6][0xa1]~j[0x81]3[0xbc][0x98][0xd1][0x83][0xa7][0xc5]8[0xfa]>[0xd9]edZ[0xb2][0xc][0xe0][0x5][0xab][0xf3][0x1a]M[0xb3][0xe7][0x1][0xf4][\n]" [DEBUG] http-outgoing-0 >>
[JIRA] (JENKINS-51315) Region list not populated when using IAM roles/role assume
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-51315 Region list not populated when using IAM roles/role assume Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-05-15 03:51 Priority: Major Reporter: Owen Mehegan My organization requires me to use IAM roles in order to access resources within AWS. When I add my credentials and IAM role and MFA token in the Jenkins Credentials UI, they are validated and I see a message saying that I have access to six regions. But then when I create a new "cloud" in the EC2 plugin configuration and choose those credentials, the region dropdown menu is never populated. Also, if I click the Test Connection button, I get this error: User: arn:aws:iam::[redacted] is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::[redacted] Add Comment
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title
Sunjoo Park updated an issue
Jenkins / JENKINS-51313
A build job is over with incomplete build logs ( TBD)
Change By:
Sunjoo Park
* (I'm updating a description now)** Problem* A normal build job is over with complete build logs including the last line like{code:java}Finished: SUCCESS{code}or{code:java}Finished: FAILURE{code} 1) But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE).2) Also, They don't have log text after some time. Con
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51313) A build job is over with incomplete build logs ( TBD)
Title: Message Title Sunjoo Park created an issue Jenkins / JENKINS-51313 A build job is over with incomplete build logs ( TBD) Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-15 03:32 Priority: Minor Reporter: Sunjoo Park Problem A normal build job is over with complete build logs including the last line like Finished: SUCCESS or Finished: FAILURE 1) But I got a build job ended with incomplete build logs. That build logs don't have a last status message (SUCCESS/FAILURE). 2) Also, They don't have log text after some time. Con Add Comment
[JIRA] (JENKINS-48333) NumberFormatException when using CHOICE parameters
Title: Message Title
Aldira Raharja edited a comment on JENKINS-48333
Re: NumberFormatException when using CHOICE parameters
Hi [~rumble], I'm recently encounter this issue too. In my case, the logs also display the following line : {code:java}02:24:04 at jenkins.plugins.slack.ActiveNotifier$MessageBuilder.escape(ActiveNotifier.java:490)02:24:04 at jenkins.plugins.slack.ActiveNotifier$MessageBuilder.append(ActiveNotifier.java:369)02:24:04 at jenkins.plugins.slack.ActiveNotifier.started(ActiveNotifier.java:70)02:24:04 at jenkins.plugins.slack.SlackNotifier.prebuild(SlackNotifier.java:345){code} Seems like the plugins has conflict with [Jenkins Slack Plugin|https://github.com/jenkinsci/slack-plugin]. That's odd... Once I'm remove the plugins from the job, the scheduler works as expected. Maybe it helps
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48333) NumberFormatException when using CHOICE parameters
Title: Message Title Aldira Raharja commented on JENKINS-48333 Re: NumberFormatException when using CHOICE parameters Hi Phil Rumble, I'm recently encounter this issue too. In my case, the logs also display the following line : 02:24:04 at jenkins.plugins.slack.ActiveNotifier$MessageBuilder.escape(ActiveNotifier.java:490) 02:24:04 at jenkins.plugins.slack.ActiveNotifier$MessageBuilder.append(ActiveNotifier.java:369) 02:24:04 at jenkins.plugins.slack.ActiveNotifier.started(ActiveNotifier.java:70) 02:24:04 at jenkins.plugins.slack.SlackNotifier.prebuild(SlackNotifier.java:345) Once I'm remove the plugins from the job, the scheduler works as expected. Maybe it helps Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Justin Georgeson commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) the manual download workaround worked. If there is an open issue I can vote on, please give me the link. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Yasuo Nakanishi edited a comment on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
hi, I'm using AWS ESC Repository with withDockerRegistry.this pipeline is woking with 1.15.1{code:java}withDockerRegistry([credentialsId: 'AWS ECS Repository', url: 'https://my-repo-url']) {}{code}but I got NPE with 1.16. what happened? {code:java}java.lang.NullPointerExceptionat org.jenkinsci.plugins.docker.workflow.RegistryEndpointStep$Execution.newKeyMaterialFactory(RegistryEndpointStep.java:81)at org.jenkinsci.plugins.docker.workflow.AbstractEndpointStepExecution.start(AbstractEndpointStepExecution.java:44)at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229)at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153)at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157)at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133)at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129)at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)at WorkflowScript.run(WorkflowScript:19)at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:138)at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:569)at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:322)at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:320)at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:568)at
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Yasuo Nakanishi commented on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
hi, I'm using AWS ESC Repository with withDockerRegistry. this pipeline is woking with 1.15.1
withDockerRegistry([credentialsId: 'AWS ECS Repository', url: 'https://my-repo-url']) {
}
but I got NPE with 1.16. what happened?
java.lang.NullPointerException
at org.jenkinsci.plugins.docker.workflow.RegistryEndpointStep$Execution.newKeyMaterialFactory(RegistryEndpointStep.java:81)
at org.jenkinsci.plugins.docker.workflow.AbstractEndpointStepExecution.start(AbstractEndpointStepExecution.java:44)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:19)
at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:138)
at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:569)
at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(jar:file:/var/lib/jenkins/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:322)
at
[JIRA] (JENKINS-51274) Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories
Title: Message Title Josh McDonald commented on JENKINS-51274 Re: Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories What in the bejesus is that? And how are we supposed to normalise them? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Michael Krotscheck commented on JENKINS-48167 Re: Support gerrit trigger configuration in pipeline syntax Anytime! The rather tedious process that I used to figure out all the values, is to use the JobConfigHistory plugin, and manually examine the changes to the XML when I made changes. Of course, after a while that just got obnoxious and I just did a grep on the codebase. So, YMMV. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Graham Burgess commented on JENKINS-48167 Re: Support gerrit trigger configuration in pipeline syntax Argh sorry I didn't mean to assign that too me, turning off keyboard shortcuts for this site That method seems very messy compared to how other providers work, could we clean it up plase? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50885) BlueOcean should have an optional dependency on JIRA plugin
Title: Message Title Vivek Pandey updated JENKINS-50885 No more needed as https://issues.jenkins-ci.org/browse/JENKINS-48357 is fixed and integrated to blueocean. Jenkins / JENKINS-50885 BlueOcean should have an optional dependency on JIRA plugin Change By: Vivek Pandey Status: In Review Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Graham Burgess assigned an issue to Graham Burgess Jenkins / JENKINS-48167 Support gerrit trigger configuration in pipeline syntax Change By: Graham Burgess Assignee: rsandell Graham Burgess Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Graham Burgess assigned an issue to rsandell Jenkins / JENKINS-48167 Support gerrit trigger configuration in pipeline syntax Change By: Graham Burgess Assignee: Graham Burgess rsandell Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51312) Jira plugin core 2.60.1
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-51312 Jira plugin core 2.60.1 Issue Type: Task Assignee: Olivier Lamy Components: jira-plugin Created: 2018-05-14 23:13 Labels: jira-plugin-2.5.3 Priority: Minor Reporter: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51310) Update JIRA plugin to use jackson2-api-plugin
Title: Message Title Olivier Lamy started work on JENKINS-51310 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46368) PipelineGraphPublisher should also declare artifacts' parents as dependency
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-46368
Re: PipelineGraphPublisher should also declare artifacts' parents as dependency
[~markusdlugi], [~brenuart], [~falcon] 3.5.7-beta-1 is an optimisation of the SQL queries to find dependencies. Would you mind testing it on your environments to verify that there is no regression?Please don't hesitate to backup your H2 db before the test. ($ \ {jenkins_home \ }/jenkins-jobs/jenkins-jobs.mv.db)https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.7-beta-1
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46368) PipelineGraphPublisher should also declare artifacts' parents as dependency
Title: Message Title
Cyrille Le Clerc commented on JENKINS-46368
Re: PipelineGraphPublisher should also declare artifacts' parents as dependency
Markus Dlugi, Bertrand Renuart, benoit guerin 3.5.7-beta-1 is an optimisation of the SQL queries to find dependencies. Would you mind testing it on your environments to verify that there is no regression? Please don't hesitate to backup your H2 db before the test. ($ {jenkins_home} /jenkins-jobs/jenkins-jobs.mv.db) https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.7-beta-1
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51206) Blueocean-github-pipeline needs updated jackson-databind
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-51206 Blueocean-github-pipeline needs updated jackson-databind Change By: Olivier Lamy Sprint: Blue Ocean 1.6 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Nicolae Pascu started work on JENKINS-51230 Change By: Nicolae Pascu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Nicolae Pascu updated an issue Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Change By: Nicolae Pascu Sprint: Blue Ocean 1.6 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Change By: Nicolae Pascu Assignee: Josh McDonald Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting stages from a pipeline
Title: Message Title Jenn Briden updated JENKINS-50825 Jenkins / JENKINS-50825 Add editor ATH coverage for deleting stages from a pipeline Change By: Jenn Briden Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51290) Builds fail to start with: IOException: repo/branch #5 did not yet start
Title: Message Title Sam Van Oort commented on JENKINS-51290 Re: Builds fail to start with: IOException: repo/branch #5 did not yet start I cannot reproduce the issue with the latest workflow-job (2.21) and workflow-multibranch plugin – I suspect this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-50784 which is now-fixed by updates to those plugins. Christoph Obexer can you confirm? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner commented on JENKINS-50084 Re: Integration Test for ReferenceFinder recorder.setUnstableTotalAll(0); deaktiviert das QualityGate. Eine 1 aktiviert es bei mindestens einer Warnung. Issues fixed geht am einfachsten, durch Duplizieren der Datei und löschen einiger Warnungen. Dann den zweiten Build auf die andere Datei loslassen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Vivek Pandey commented on JENKINS-51230 Re: Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Michael Haskelsky Is the building going well? That is does it work well if used from classic? An HAR file will be useful. Josh McDonald Might be related to https://issues.jenkins-ci.org/browse/JENKINS-51161? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51311) job-dsl-plugin missing triggers added in gitlab-plugin 1.5.5
Title: Message Title Darin Pantley commented on JENKINS-51311 Re: job-dsl-plugin missing triggers added in gitlab-plugin 1.5.5 I'm guessing the solution to this will look something like: https://github.com/jenkinsci/job-dsl-plugin/pull/1127 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Vivek Pandey commented on JENKINS-5 Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab Looks similar to https://issues.jenkins-ci.org/browse/JENKINS-51110. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Vivek Pandey assigned an issue to Josh McDonald Jenkins / JENKINS-5 Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab Change By: Vivek Pandey Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Vivek Pandey assigned an issue to Josh McDonald Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Change By: Vivek Pandey Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51096) Support external H2 database
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51096 Re: Support external H2 database Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/db/migration/MigrationStep.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/db/migration/h2/MigrationStep10.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/db/migration/h2/MigrationStep8.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig/config.jelly jenkins-plugin/src/main/resources/sql/h2/08_migration.sql jenkins-plugin/src/main/resources/sql/h2/09_migration.sql jenkins-plugin/src/main/resources/sql/h2/10_migration.sql jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoInitializationTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/6730069b774192556475539c30ff1192a47090e7 Log: JENKINS-51096 Add support for a remote H2 database + support multiple masters being connected to this remote H2 database (#150) JENKINS-51096 Add support for a remote H2 database + support multiple masters being connected to this remote H2 database JENKINS-51096 Database query time optimisation: introduce jenkins_job.last_build and jenkins_job.last_successful_build *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment
[JIRA] (JENKINS-51311) job-dsl-plugin missing triggers added in gitlab-plugin 1.5.5
Title: Message Title Darin Pantley created an issue Jenkins / JENKINS-51311 job-dsl-plugin missing triggers added in gitlab-plugin 1.5.5 Issue Type: Bug Assignee: Owen Mehegan Components: gitlab-plugin, job-dsl-plugin Created: 2018-05-14 22:12 Environment: jenkins: 2.107.2 job-dsl-plugin: 1.69 gitlab-plugin: 1.5.5 GitLab: 10.7.1-ee Priority: Minor Reporter: Darin Pantley job-dsl-plugin 1.69 does not support new build triggers added in gitlab-plugin 1.5.5: triggerOnClosedMergeRequest triggerOnAcceptedMergeRequest triggerOnApprovedMergeRequest The gitlab-plugin works fine, so I'm able to manually configure these options in my Jenkins job configuration, but they do not exist in Job DSL, so I cannot set them programmatically.
[JIRA] (JENKINS-51290) Builds fail to start with: IOException: repo/branch #5 did not yet start
Title: Message Title Sam Van Oort commented on JENKINS-51290 Re: Builds fail to start with: IOException: repo/branch #5 did not yet start Christoph Obexer Are you on the absolute latest workflow-job and workflow-multibranch? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50953) Tool to offer incremental updates
Title: Message Title Jesse Glick updated JENKINS-50953 Jenkins / JENKINS-50953 Tool to offer incremental updates Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51206) Blueocean-github-pipeline needs updated jackson-databind
Title: Message Title Vivek Pandey assigned an issue to Olivier Lamy Jenkins / JENKINS-51206 Blueocean-github-pipeline needs updated jackson-databind Change By: Vivek Pandey Assignee: Vivek Pandey Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50856) Cannot connect to bitbucket server from Blueocean.
Title: Message Title Vivek Pandey commented on JENKINS-50856 Re: Cannot connect to bitbucket server from Blueocean. Manaswinee Mohanty Its hard to tell from attached image whats going on. Are there any server side log? Please also attach HAR file. If it has sensitive info, please send it to me directly over email. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title Craig Aiken commented on JENKINS-48167 Re: Support gerrit trigger configuration in pipeline syntax Thanks for updating this Michael! I'll definitely give this a try. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51310) Update JIRA plugin to use jackson2-api-plugin
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-51310 Update JIRA plugin to use jackson2-api-plugin Issue Type: Task Assignee: Olivier Lamy Components: jira-plugin Created: 2018-05-14 21:52 Labels: jira-plugin-2.5.3 Priority: Minor Reporter: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51309) Can't connect to TFS 2018 with TFS PLUGIN : Connection reset error
Title: Message Title HITESH VERMA created an issue Jenkins / JENKINS-51309 Can't connect to TFS 2018 with TFS PLUGIN : Connection reset error Issue Type: New Feature Assignee: redsolo Components: tfs-plugin Created: 2018-05-14 21:42 Environment: TFS plugin : 5.133.0 Jenkins : 2.107.2 Priority: Blocker Reporter: HITESH VERMA Hi, I am facing issue connecting Jenkins and TFS server 2018 (vsts online) using TFS plugin. Please can you suggest any fix? FATAL: com.microsoft.tfs.core.exceptions.TECoreException: Connection reset java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at sun.security.ssl.InputRecord.readFully(Unknown Source) at sun.security.ssl.InputRecord.read(Unknown Source) at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source) at sun.security.ssl.AppOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at com.microsoft.tfs.core.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:541) at com.microsoft.tfs.core.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2260) at com.microsoft.tfs.core.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1202) at com.microsoft.tfs.core.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:432) at com.microsoft.tfs.core.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:182) at com.microsoft.tfs.core.httpclient.HttpClient.executeMethod(HttpClient.java:428) at
[JIRA] (JENKINS-48167) Support gerrit trigger configuration in pipeline syntax
Title: Message Title
Michael Krotscheck commented on JENKINS-48167
Re: Support gerrit trigger configuration in pipeline syntax
This is already possible, though I had to dig a bit to figure out the appropriate syntax. Here's how we're using it in a declarative pipeline.
triggers {
gerrit(
gerritProjects: [[
compareType: 'PLAIN',
pattern: 'my-project',
branches : [[
compareType: 'PLAIN',
pattern: 'master'
]]
]],
triggerOnEvents: [[
$class : 'PluginPatchsetCreatedEvent',
excludeDrafts : true,
excludeTrivialRebase: false,
excludeNoCodeChange : false
]],
skipVote: [
onSuccessful: false,
onFailed: false,
onUnstable : false,
onNotBuilt : false
]
)
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-29641) JNLP slave agent on Mac disconnects very often
Title: Message Title Bill Davey commented on JENKINS-29641 Re: JNLP slave agent on Mac disconnects very often Seems like there was no resolution on this? Any updates here? I've run into the same issue with an OSX node. I've tried connecting via the jnlp agent and the slave.jar file. Both can connect but lose the connection very quickly thereafter. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title Gabriel Loewen commented on JENKINS-50840 Re: Powershell script execution broken in powershellHelper.ps1 It looks like this is an edge case that is triggered when streaming console output from a powershell script cannot be interpreted as serializable data. I will work on a fix for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Adam Voss commented on JENKINS-51229 Re: Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information "Original Poster", I think I might be showing my aged Internet usage... should have used `@` mentions and said Thy Dai's pull request. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title Gabriel Loewen assigned an issue to Gabriel Loewen Jenkins / JENKINS-50840 Powershell script execution broken in powershellHelper.ps1 Change By: Gabriel Loewen Assignee: Gabriel Loewen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51292) Random failure building GitContainer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51292 Re: Random failure building GitContainer Code changed in jenkins User: James Nord Path: src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/GitContainer/Dockerfile http://jenkins-ci.org/commit/acceptance-test-harness/2c233bbc78d634b78c6ad531292315d715cf67b8 Log: JENKINS-51292 attempt to fix random failures in GitCOntainer Should fix random issues where the cache was populated from a different build long ago such as that observed in the referenced issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51292) Random failure building GitContainer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51292 Re: Random failure building GitContainer Code changed in jenkins User: Oliver Gondža Path: src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/GitContainer/Dockerfile http://jenkins-ci.org/commit/acceptance-test-harness/d85692ac26b9a0511477cb3eceadd81c4a10e61b Log: Merge pull request #430 from jtnord/JENKINS-51292 JENKINS-51292 attempt to fix random failures in GitCOntainer Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/d74f39e5ac36...d85692ac26b9 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Justin Georgeson commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) Thanks for the quick response Martin! Did you link the right issue? When I click the link it takes me back to this issue (closed so I can't vote on it), when I type in URL for 3137 directly it loads "Allow permissions at batch task level" for the batch-task-plugin (seems unrelated, but also closed so I can't vote). I don't have that file on my server, have downloaded it manually and am quieting the server to reload config. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51281) [JEP-305] Incrementalify the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementalify the Essentials plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementals-ify Incrementalify the Essentials plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51281) [JEP-305] Incrementals-ify the Essentials plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51281 Re: [JEP-305] Incrementals-ify the Essentials plugin Code changed in jenkins User: Baptiste Mathus Path: .mvn/extensions.xml .mvn/maven.config pom.xml http://jenkins-ci.org/commit/essentials-plugin/40727b97794adf283d3b157ee0553502108316ba Log: Merge pull request #7 from batmat/JENKINS-51281 JENKINS-51281 Incrementals-ify the Essentials plugin Compare: https://github.com/jenkinsci/essentials-plugin/compare/adabca07cdbc...40727b97794a *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51281) [JEP-305] Incrementals-ify the Essentials plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51281 Re: [JEP-305] Incrementals-ify the Essentials plugin Code changed in jenkins User: Baptiste Mathus Path: .mvn/extensions.xml .mvn/maven.config pom.xml http://jenkins-ci.org/commit/essentials-plugin/e9a5b56689a7b798ed0069437766d17cce2be121 Log: JENKINS-51281 Incrementals-ify the Essentials plugin https://github.com/jenkins-infra/repository-permissions-updater/pull/693 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementalify the Metrics plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51308 [JEP-305] Incrementalify the Metrics plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementals-ify Incrementalify the Metrics plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementalify the Metrics plugin
Title: Message Title Baptiste Mathus updated JENKINS-51308 Jenkins / JENKINS-51308 [JEP-305] Incrementalify the Metrics plugin Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Frederic Rousseau updated an issue
Jenkins / JENKINS-51307
Declarative pipeline and docker entrypoint
Change By:
Frederic Rousseau
I write a dead simple Dockerfile{code:java}FROM openjdk:8-jdk-alpineENTRYPOINT "java"{code}I write a dead simple declarative pipeline{code:java}pipeline { agent { dockerfile true } stages { stage('Dead Simple') { steps { checkout scm } } } }{code}I get an error.I get the same error with {code:java}pipeline { agent { docker { image 'openjdk:8-jdk-alpine' } } stages { stage('Dead Simple') { steps { checkout scm } } }}{code}The error is{code:java}ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}I cannot pass --entrypoint to the run command, it's jenkins that calls ita bit more logs :{code:java}[Pipeline] withDockerContainerJenkins does not seem to be running inside a container$ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e 4d6ffe9d9713df374dd2670073b9ea32598df407 cat$ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,commERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}
[JIRA] (JENKINS-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49991 Clicking the "Jenkins" link in Blue Ocean is very slow Change By: Vivek Pandey Sprint: Blue Ocean 1.6 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Vivek Pandey assigned an issue to Joshua Holmer Jenkins / JENKINS-49991 Clicking the "Jenkins" link in Blue Ocean is very slow Change By: Vivek Pandey Assignee: Joshua Holmer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementals-ify the Metrics plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51308 [JEP-305] Incrementals-ify the Metrics plugin Change By: Baptiste Mathus Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementals-ify the Metrics plugin
Title: Message Title Baptiste Mathus started work on JENKINS-51308 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementals-ify the Metrics plugin
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-51308
[JEP-305] Incrementals-ify the Metrics plugin
Change By:
Baptiste Mathus
We need to add the necessary configuration in the essentials- metriscs plugin so that we can consume it easily on each merge (and also because well, it is clearly one of the plugins that ought to use {{incrementals}} :)).
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementals-ify the Metrics plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-51308 [JEP-305] Incrementals-ify the Metrics plugin Issue Type: Task Assignee: Baptiste Mathus Components: essentials, essentials-plugin Created: 2018-05-14 19:00 Labels: essentials essentials-triggered jep-305 Priority: Major Reporter: Baptiste Mathus We need to add the necessary configuration in the essentials-plugin so that we can consume it easily on each merge (and also because well, it is clearly one of the plugins that ought to use incrementals ). Add Comment
[JIRA] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Martin Weber commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) Justin Georgeson If you do not see a file hudson.plugins.cmake.CmakeInstaller.json in directory $JENKINS_HOME/updates, you are suffering from JENKINS-3137. If so, please vote there. As a workaround, you could manually download the file from https://updates.jenkins-ci.org/updates/hudson.plugins.cmake.CmakeInstaller.json Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Frederic Rousseau edited a comment on JENKINS-46636 Re: `dir` does not change working directory for contained steps dir never worked in +declarative+ pipelines , at least it does not since at least a year of releases . I didn't try in scripted pipeline. I do like Christopher, I prefix my commands with "cd my-directory && " and it's not sexy at all to see this in the Blue Ocean UI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Frederic Rousseau edited a comment on JENKINS-46636 Re: `dir` does not change working directory for contained steps dir never worked in +declarative+ pipelines , at least it does not since at least a year of releases. I do like Christopher, I prefix my commands with "cd my-directory" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick started work on JENKINS-51247 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick updated JENKINS-51247 Jenkins / JENKINS-51247 Move flattened POM into target directory Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Mike Kozell reopened an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Mike Kozell Resolution: Done Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick updated JENKINS-51247 Jenkins / JENKINS-51247 Move flattened POM into target directory Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51295) Project Page Timeout
Title: Message Title Thomas Trautner commented on JENKINS-51295 Re: Project Page Timeout Hi Oleg, sorry for missing this information. I'm running ver. 2.107.3. Followed your hint and uninstalled violations- and warnings-Plugin and now I can access my project settings Actually running an job to test the second issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Arne Schöntag edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Wenn ich folgendes laufen lasse:{code:java}FreeStyleProject project = createJobWithWorkspaceFile(jobName, "eclipse.txt");IssuesRecorder recorder = enableWarnings(project, publisher -> {publisher.setUnstableTotalAll(7);});AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE);assertThat(result).hasTotalSize(8);assertThat(result).hasOverallResult(Result.UNSTABLE);recorder.setUnstableTotalAll(0);result = scheduleBuildAndAssertStatus(project, Result.SUCCESS);assertThat(result).hasOverallResult(Result.UNSTABLE);assertThat(result).hasNewSize(0);{code}bekomme ich ein SUCCESS build beim zweiten Mal, dass 8 Issues hat. Warum kommt da ein SUCCESS zurück, obwohl der vorherige Build UNSTABLE (ignoreAnalysisResult ist standardmäßig false) war? Das assertThat danach schlägt demnach fehl.Wie kann ich noch die Issues "fixen", dass beim zweiten build weniger vorhanden sind?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Arne Schöntag commented on JENKINS-50084
Re: Integration Test for ReferenceFinder
Wenn ich folgendes laufen lasse:
FreeStyleProject project = createJobWithWorkspaceFile(jobName, "eclipse.txt");
IssuesRecorder recorder = enableWarnings(project, publisher -> {
publisher.setUnstableTotalAll(7);
});
AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE);
assertThat(result).hasTotalSize(8);
assertThat(result).hasOverallResult(Result.UNSTABLE);
recorder.setUnstableTotalAll(0);
result = scheduleBuildAndAssertStatus(project, Result.SUCCESS);
assertThat(result).hasOverallResult(Result.UNSTABLE);
assertThat(result).hasNewSize(0);
bekomme ich ein SUCCESS build beim zweiten Mal, dass 8 Issues hat. Warum kommt da ein SUCCESS zurück, obwohl der vorherige Build UNSTABLE (ignoreAnalysisResult ist standardmäßig false) war? Das assertThat danach schlägt demnach fehl. Wie kann ich noch die Issues "fixen", dass beim zweiten build weniger vorhanden sind?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50004) No more Oops!!! errors
Title: Message Title Ivan Fernandez Calvo updated JENKINS-50004 Jenkins / JENKINS-50004 No more Oops!!! errors Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Frederic Rousseau commented on JENKINS-46636 Re: `dir` does not change working directory for contained steps dir never worked, at least it does not since at least a year of releases. I do like Christopher, I prefix my commands with "cd my-directory" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick commented on JENKINS-51247 Re: Move flattened POM into target directory This blog leads me to a workaround to edit the usage of source:jar from the superpom. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50004) No more Oops!!! errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50004 Re: No more Oops!!! errors Code changed in jenkins User: Ivan Fernandez Calvo Path: src/main/java/org/jenkinsci/plugins/saml/SamlProfileWrapper.java http://jenkins-ci.org/commit/saml-plugin/1f346bceadc14f0675062308372d8d894bd403a9 Log: JENKINS-50004 No more Ooops error (#50) JENKINS-50004 No more Ooops error *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35905) Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout
Title: Message Title Adity Sreekumar commented on JENKINS-35905 Re: Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout We are facing this issue currently on our builds as well on occasion as we migrate jobs from one jenkins server to another which is accompanied with associated node relabeling and addition of new nodes. What I thought made sense was if the timeout could be applied to the pipeline as a whole and not just a step. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Frederic Rousseau updated an issue
Jenkins / JENKINS-51307
Declarative pipeline and docker entrypoint
Change By:
Frederic Rousseau
I write a dead simple Dockerfile {code:java}FROM openjdk:8-jdk-alpineENTRYPOINT "java"{code} I write a dead simple declarative pipeline{code:java}pipeline { agent { dockerfile true } stages { stage('Dead Simple') { steps { checkout scm } } } }{code}I get an error.I get the same error with {code:java}pipeline { agent { docker 'openjdk:8-jdk-alpine' } stages { stage('Dead Simple') { steps { checkout scm } } }}{code}The error is{code:java}ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}I cannot pass --entrypoint to the run command, it's jenkins that calls ita bit more logs :{code:java}[Pipeline] withDockerContainerJenkins does not seem to be running inside a container$ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e 4d6ffe9d9713df374dd2670073b9ea32598df407 cat$ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,commERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}
[JIRA] (JENKINS-31371) No tool download known for OS... (Crawler generates empty update file)
Title: Message Title Justin Georgeson commented on JENKINS-31371 Re: No tool download known for OS... (Crawler generates empty update file) I am seeing this error with v2.5.2 of cmake plugin and Jenkins core 2.60.2 installed. The Install from cmake.org option also doesn't give me a combobox pre-filled list of versions to select from but rather a simple text field, so I'm just entering the version number in that field. Is the lack of pre-filled list of versions indicative of some other issue? I am behind a proxy and proxy is configured for plugin management (and working at least for plugin upgrades/installs and listing available plugins). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title Frederic Rousseau updated an issue Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint Change By: Frederic Rousseau Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Frederic Rousseau updated an issue
Jenkins / JENKINS-51307
Declarative pipeline and docker entrypoint
Change By:
Frederic Rousseau
I write a dead simple Dockerfile {code:java}FROM openjdk:8-jdk-alpineENTRYPOINT "java"{code} I write a dead simple declarative pipeline{code:java}pipeline { agent { dockerfile true } stages { stage('Dead Simple') { steps { checkout scm } } } }{code}I get an error.I get the same error with {code:java}pipeline { agent { docker 'openjdk:8-jdk-alpine' } stages { stage('Dead Simple') { steps { checkout scm } } }}{code}The error is{code:java}ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}I cannot pass --entrypoint to the run command, it's jenkins that call calls ita bit more logs :{code:java}[Pipeline] withDockerContainerJenkins does not seem to be running inside a container$ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e 4d6ffe9d9713df374dd2670073b9ea32598df407 cat$ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,commERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.{code}
[JIRA] (JENKINS-49299) Documentation regarding Docker image ENTRYPOINT requirements lacking
Title: Message Title
Frederic Rousseau edited a comment on JENKINS-49299
Re: Documentation regarding Docker image ENTRYPOINT requirements lacking
For a declarative pipeline user, this issue is not a documentation problem but a real bug.If I specify *agent \{ dockerfile true }* or *agent \{ docker server:port/image }*and I have an ENTTRYPOINT defined in the docker image. I get the error systematically. I create issue JENKINS-51307
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Frederic Rousseau created an issue
Jenkins / JENKINS-51307
Declarative pipeline and docker entrypoint
Issue Type:
New Feature
Assignee:
vjuranek
Components:
docker-build-step-plugin
Created:
2018-05-14 18:11
Environment:
problem occurs on version 1.15 and above of the plugin
Priority:
Major
Reporter:
Frederic Rousseau
I write a dead simple Dockerfile
FROM openjdk:8-jdk-alpine
ENTRYPOINT "java"
I write a dead simple declarative pipeline
pipeline {
agent { dockerfile true }
stages {
stage('Dead Simple') {
steps {
checkout scm
}
}
}
}
I get an error. I get the same error with
pipeline {
agent { docker 'openjdk:8-jdk-alpine' }
stages {
stage('Dead Simple') {
steps {
checkout scm
}
}
}
}
The error is
[JIRA] (JENKINS-51295) Project Page Timeout
Title: Message Title Oleg Nenashev commented on JENKINS-51295 Re: Project Page Timeout Which Jenkins version do you use? Also see JENKINS-49392 which may be a root cause Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
