[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title Oleg Nenashev commented on JENKINS-56315 Re: Add "docker" alias for DockerTool relatively easy to do. The only problem might be with JCasC Plugin compatibility. AFAIK he does not filter by extension type when looking for aliases, so such change may cause regressions there. CC Nicolas De Loof Ewelina Wilkosz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56315 Add "docker" alias for DockerTool Change By: Oleg Nenashev Labels: newbie-friendly pipeline-improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47046) s3Upload with includePathPattern does not upload files
Title: Message Title
Oliver Schoenborn edited a comment on JENKINS-47046
Re: s3Upload with includePathPattern does not upload files
The only thing that works for me is {code:java}s3Upload( bucket: 'BUCKET', path: "PATH_TO_FOLDER", // no trailing slash file: "FOLDER", workingDir: "PARENT_OF_FOLDER" ){code} With includePath, the only one that worked *partially* was using "**/*.yaml" as path; other patterns like "*.yaml", "**/*" did not work. I say partially because it uploaded only one file eventhough there were several (there is a bug related to this). Also findFiles is an option, as documented https://github.com/jenkinsci/pipeline-aws-plugin/issues/83.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47046) s3Upload with includePathPattern does not upload files
Title: Message Title Oliver Schoenborn commented on JENKINS-47046 Re: s3Upload with includePathPattern does not upload files The only thing that works for me is s3Upload( bucket: 'BUCKET', path: "PATH_TO_FOLDER", // no trailing slash file: "FOLDER", workingDir: "PARENT_OF_FOLDER" ) With includePath, the only one that worked partially was using "*/.yaml" as path; other patterns like ".yaml", "/" did not work. I say partially because it uploaded only one file eventhough there were several (there is a bug related to this). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-56271 xUnit produce an empty report for NUnit3 type Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56271 xUnit produce an empty report for NUnit3 type Change By: Nikolas Falco Summary: WARNING: All test reports are xUnit produce an empty . report for NUnit3 type Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Wadeck Follonier commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Glenn Herbert Thank you for the report. I will not have the time to investigate this case further this week. Could you try using the WAR provided in JENKINS-56114 ? As they were also using Windows Server, that could the same root cause. In addition, did you try with the escape hatch: java.exe -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true -jar jenkins.war ? (in both your current version and in the WAR provided in the other ticket) Then could you give me more information about your configuration, like are you using Docker inside your Windows Server, or just running java -jar ..., or using the service? If you can provide also additional information from the log of the build, that could be useful. Also, what is the content of the userContent in your instance (in terms of type, not the real files, but to know if there are symlinks, what are their targets, or just image files?) Thank you in advance for your next answer that will help me helping you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) The WAR is now available from the build on https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-3914/3/artifacts, search for jenkins-war-2.167-rc28022.09203244c3f8.war. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) WARNING: All test reports are empty.
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56271 WARNING: All test reports are empty. Change By: Nikolas Falco When running Unity3d tests in playmode and generating results xml file e.g(https://pastebin.com/BfhaJj0M) we get the message that all the reports are empty. Is there anything else xunit needs to actually parse these results? Do you see any problem with the resulting xml file?Worth noting that reports generated using editmore are being read properly by the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56271) WARNING: All test reports are empty.
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-56271 WARNING: All test reports are empty. Change By: Nikolas Falco Environment: When running Unity3d tests in playmode and generating results xml file e.g(https://pastebin.com/BfhaJj0M) we get the message that all the reports are empty. Is there anything else xunit needs to actually parse these results? Do you see any problem with the resulting xml file?Worth noting that reports generated using editmore are being read properly by the plugin. Using 2.3.2 xunit plugin, Jenkins ver. 2.165 on a AWS Centos box. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56293) Unable to update or install plugins
Title: Message Title Nikolas Falco assigned an issue to Unassigned Jenkins / JENKINS-56293 Unable to update or install plugins Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. #{quote} # Replace number in category with text (resolved now) {quote} # {quote} Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). {quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. #{quote}Replace number in category with text (resolved now) {quote} # {quote}Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). {quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Morten Brekkevold commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Forgot to actually attach the file, here it is: pylint-messages.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. # {quote} # Replace number in category with text (resolved now) # Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type).{quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. # {quote} # Replace number in category with text (resolved now) # Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type).{quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. #{quote} # Replace number in category with text (resolved now) {quote} # {quote} Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). {quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35093) Moving a Build Job to a Folder results in Exception and loss of build history
Title: Message Title Edgars Batna commented on JENKINS-35093 Re: Moving a Build Job to a Folder results in Exception and loss of build history Just happened to a large job for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Morten Brekkevold commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Forgot to actually attach the file, here it is: pylint-messages.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title
Morten Brekkevold edited a comment on JENKINS-44915
Re: Pylint Warnings: Details table could provide summary string with category
{quote}Which version of analysis-model-api do you have installed?{quote} Hi [~drulli], I have version 2.1.2 of that plugin. #{quote}Replace number in category with text (resolved now) {quote} # {quote}Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). {quote} On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of {{pylint --list-msgs}} is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation * (R) refactor, for bad code smell * (W) warning, for python specific problems * (E) error, for much probably bugs in the code * (F) fatal, if an error occurred which prevented pylint from doingEach message emitted has one of these types and a four digit integer code to identify it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Morten Brekkevold updated an issue Jenkins / JENKINS-44915 Pylint Warnings: Details table could provide summary string with category Change By: Morten Brekkevold Attachment: pylint-messages.json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Morten Brekkevold commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Which version of analysis-model-api do you have installed? Hi Ulli Hafner, I have version 2.1.2 of that plugin. # Replace number in category with text (resolved now) Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). On my end, I cannot confirm that #1 is resolved (which is what I was most hoping for). #2 is not that important to me, as there is a detailed message attached to each reported code line anyway. However, the output of pylint --list-msgs is easily converted to JSON. See attached file. I'm not sure I understand your distinction between "type" and "category", with regards to warnings-ng, but pylint establishes 5 different message types: * (C) convention, for programming standard violation (R) refactor, for bad code smell (W) warning, for python specific problems (E) error, for much probably bugs in the code (F) fatal, if an error occurred which prevented pylint from doing Each message emitted has one of these types and a four digit integer code to identify it. Add Comment
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Component/s: hubot-steps-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Roger Wang commented on JENKINS-55462 Re: "shelve project" button missing for all non-admin users Hi Pierre Beitz, Thanks for your help. Sorry to keep bothering you when you are busy. Please let us know when the fix is done. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Andrew Nicols commented on JENKINS-49278 Re: cat command in docker agents not detected correctly I suspect that this is the same as JENKINS-54389, and also JENKINS-39748. Any longer-running entrypoint will cause the job to fail because the cat command doesn't run until the end of the entrypoint. Additionally, requiring an image to run cat could break the image. For example, if I wish to start an image whose CMD is apache-foreground then I expect apache to be running, not cat. I'm not going to serve any web responses with cat. I think the docker-workflow plugin either needs to: respect HEALTHCHECKs allow for either no CMD override, or a specified CMD override to be provided when running the image allow for a wait period before checking that the expected command is running Basically, don't run cat by default, instead respect the healthcheck. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Andrew Nicols commented on JENKINS-39748 Re: Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing This issue is also duplicated yb 49278 and 54389. What can we do to work towards getting this issue resolved? The ENTRYPOINT and CMD in the Dockerfile should be respected. The docker-workflow plugin should be running the images, not changing their nature. Can we instead look at using the Docker healthcheck functionality if a healthcheck is provided? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54389) Containers with ENTRYPOINT is not started correctly
Title: Message Title Andrew Nicols commented on JENKINS-54389 Re: Containers with ENTRYPOINT is not started correctly This could also be solved if Jenkins were to respect a healthcheck and the plugin changed to check the health of the container. This could also be specified on the CLI: docker run -u 501:501 -t --health-cmd '[ -f /tmp/ready ]' --health-start-period 1s --health-interval 100s myimage sh -c 'touch /tmp/ready && cat' Either way we do need a way to allow slower entrypoints to do their job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54389) Containers with ENTRYPOINT is not started correctly
Title: Message Title Andrew Nicols updated an issue Jenkins / JENKINS-54389 Containers with ENTRYPOINT is not started correctly Change By: Andrew Nicols Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56320) Job DSL 1.71 unable to process DSLs
Title: Message Title Joe Roberts created an issue Jenkins / JENKINS-56320 Job DSL 1.71 unable to process DSLs Issue Type: Bug Assignee: Daniel Spilker Attachments: image-2019-02-27-20-46-38-417.png Components: job-dsl-plugin Created: 2019-02-28 02:47 Environment: JNLP slave running on Kubernetes Priority: Minor Reporter: Joe Roberts Jenkins ver. 2.150.3 Upgraded to Jobs DSL 1.71 and all attempts to process dsl scripts from a freestyle job failed. Reverting to 1.70 resolved the issue. groovy.lang.GroovyRuntimeException: Could not find matching constructor for: javaposse.jobdsl.dsl.ScriptRequest(java.lang.String, [Ljava.net.URL;, java.lang.Boolean, java.lang.String, java.lang.String) at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1732) at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1532) at org.codehaus.groovy.runtime.callsite.MetaClassConstructorSite.callConstructor(MetaClassConstructorSite.java:49) at javaposse.jobdsl.plugin.ScriptRequestGenerator$_getScriptRequests_closure2.doCall(ScriptRequestGenerator.groovy:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-56319) The console is output, but the job already shows that it is finished.
Title: Message Title tang alby created an issue Jenkins / JENKINS-56319 The console is output, but the job already shows that it is finished. Issue Type: Bug Assignee: Unassigned Attachments: console.png Components: _unsorted Created: 2019-02-28 02:33 Environment: jenkins-war:2.134 Priority: Major Reporter: tang alby This job performs the automated tests, and when the "BUILD SUCCESSFUL" is displayed, the job's status is that the execution is complete, but the console shows that there are other steps to load. Add Comment
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Jean-Christophe Morin commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Or actually, I could simply look at the unit tests in the repo. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Jean-Christophe Morin commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Ulli Hafner I'm not too sure what you mean by description/type... Do you have an example for let's say Java or PMD or other tools that integrates properly the type, category, message, severity, description, etc? I might be able to help you to see if pylint in analysis-model uses the right properties. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56317) Download from File Shares Seems to Not Use Ant Syntax
Title: Message Title Jie Shen commented on JENKINS-56317 Re: Download from File Shares Seems to Not Use Ant Syntax Thanks Jason Davis, I will look into this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56317) Download from File Shares Seems to Not Use Ant Syntax
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-56317 Download from File Shares Seems to Not Use Ant Syntax Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-55388 multibranch pipeline deleting history and building unexpectedly Change By: Vivek Pandey Labels: pipeline-triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Ahmed Kamel commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN For those impacted by this problem; I downgraded to a previous version of the plugin. Luckily that fixed the problem for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56318) GitHub initial push triggers 2 builds from Multibranch pipeline
Title: Message Title chirs damour commented on JENKINS-56318 Re: GitHub initial push triggers 2 builds from Multibranch pipeline also it'd be REALLY nice if that log included the X-GitHub-Delivery request header to help trace issues back to github. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56318) GitHub initial push triggers 2 builds from Multibranch pipeline
Title: Message Title
chirs damour updated an issue
Jenkins / JENKINS-56318
GitHub initial push triggers 2 builds from Multibranch pipeline
Change By:
chirs damour
we have a pipeline setup to build all branches. on an initial push of a branch two builds are kicked off for the branch that is pushed at the same time. at 12:57 i pushed here's the output from the push log in jenkins {noformat}[Tue Feb 26 11:26:11 MST 2019] Push event to branch master in repository commerce/catalog UPDATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Tue Feb 26 11:26:05 MST 2019 processed in 0.47 sec[Wed Feb 27 12:57:21 MST 2019] Received Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog CREATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Wed Feb 27 12:57:16 MST 201912:57:21 Connecting to http://github.body.prod/api/v3 using Jenkins_Github/** (Github collaborator account for Jenkins)Examining commerce/catalog Checking branches... Getting remote branch BBECOM-18919-Shipping-79... [Wed Feb 27 12:57:21 MST 2019] Received Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog CREATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Wed Feb 27 12:57:16 MST 201912:57:21 Connecting to http://github.body.prod/api/v3 using Jenkins_Github/** (Github collaborator account for Jenkins)Examining commerce/catalog Checking branches... Getting remote branch BBECOM-18919-Shipping-79... Checking branch BBECOM-18919-Shipping-79 ‘Jenkinsfile’ foundMet criteriaChecking branch BBECOM-18919-Shipping-79 ‘Jenkinsfile’ foundMet criteriaScheduled build for branch: BBECOM-18919-Shipping-79 1 branches were processed (query completed) 1 branches were processed Finished examining commerce/catalog [Wed Feb 27 12:57:23 MST 2019] Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog CREATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Wed Feb 27 12:57:16 MST 2019 processed in 2.4 secChanges detected: BBECOM-18919-Shipping-79 (null → f5190721fcc185d03a1eb7f6e83729a5d4b10135)Scheduled build for branch: BBECOM-18919-Shipping-79 1 branches were processed (query completed) 1 branches were processed Finished examining commerce/catalog [Wed Feb 27 12:57:24 MST 2019] Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog CREATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Wed Feb 27 12:57:16 MST 2019 processed in 2.5 sec C [Wed Feb 27 13:02:18 MST 2019] Received Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog UPDATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Wed Feb 27 13:02:13 MST 201913:02:18 Connecting to http://github.body.prod/api/v3 using Jenkins_Github/** (Github collaborator account for Jenkins)Examining commerce/catalog
[JIRA] (JENKINS-56318) GitHub initial push triggers 2 builds from Multibranch pipeline
Title: Message Title chirs damour created an issue Jenkins / JENKINS-56318 GitHub initial push triggers 2 builds from Multibranch pipeline Issue Type: Bug Assignee: Kirill Merkushev Attachments: Screen Shot 2019-02-27 at 1.23.19 PM.png, Screen Shot 2019-02-27 at 1.24.00 PM.png, Screen Shot 2019-02-27 at 1.24.22 PM.png, Screen Shot 2019-02-27 at 1.25.01 PM.png Components: github-plugin Created: 2019-02-27 23:20 Environment: Jenkins ver. 2.150.1 github plugin 1.29.0 github enterprise 2.15 Labels: jenkins plugin github-plugin multi-branch pipeline Priority: Minor Reporter: chirs damour we have a pipeline setup to build all branches. on an initial push of a branch two builds are kicked off for the branch that is pushed at the same time. at 12:57 i pushed here's the output from the push log in jenkins [Tue Feb 26 11:26:11 MST 2019] Push event to branch master in repository commerce/catalog UPDATED event from 10.0.17.214 ⇒ http://ci-m1.body.prod:8080/github-webhook/ with timestamp Tue Feb 26 11:26:05 MST 2019 processed in 0.47 sec [Wed Feb 27 12:57:21 MST 2019] Received Push event to branch BBECOM-18919-Shipping-79 in repository commerce/catalog CREATED event from 10.0.17.214
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Mike Kozell commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines I upgraded Pipeline: Job (workflow-job) plugin from 2.25 to 2.31 and now see the issue. I'm running durable-task 1.27. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Ulli Hafner commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Seems that this issue actually is about two different things: Replace number in category with text (resolved now) Provide descriptions of category (still open) - (btw: actually category is the wrong property, it should be type). So I suggest: if your are still interested in 2, we should create a new issue that describes that part. If someone of you (i.e. a pylint user) can provide me with a file that contains a mapping type -> description I will add the code to the plugin The file could be a properties file or JSON. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55503) Warnings trend graph (type distribution) portlet
Title: Message Title Ulli Hafner started work on JENKINS-55503 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55742) New vs. fixed warnings trend chart
Title: Message Title Ulli Hafner started work on JENKINS-55742 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55741) Customizable number of builds in trend chart
Title: Message Title Ulli Hafner started work on JENKINS-55741 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Ulli Hafner started work on JENKINS-48802 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56303) Existing user loses build history and other views
Title: Message Title Daniel Beck closed an issue as Not A Defect Jenkins / JENKINS-56303 Existing user loses build history and other views Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56303) Existing user loses build history and other views
Title: Message Title Daniel Beck commented on JENKINS-56303 Re: Existing user loses build history and other views the user had said You must be new to IT Glad it was so simple! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56303) Existing user loses build history and other views
Title: Message Title Andrew Palmer commented on JENKINS-56303 Re: Existing user loses build history and other views Daniel Beck Sorry, that was exactly it, the user had said the entire history box was gone but when I was able to get a screen from them saw that the heading was still there. "Collapsed" should have given it away... but thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53094) Option to expand variables in yamlFile
Title: Message Title Marc De Leenheer commented on JENKINS-53094 Re: Option to expand variables in yamlFile Yes would love to see this feature! Including yaml in the jenkinsfile is very inconvenient. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56317) Download from File Shares Seems to Not Use Ant Syntax
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-56317
Download from File Shares Seems to Not Use Ant Syntax
Issue Type:
Bug
Assignee:
Azure DevOps
Attachments:
steps-doc.png
Components:
windows-azure-storage-plugin
Created:
2019-02-27 20:05
Environment:
Plugin: 0.3.13 Jenkins Version: 2.150.3
Priority:
Minor
Reporter:
Jason Davis
Not sure if this is a bug, but the docs might be confusing me. I'm trying a simple test to see if I can download specific files directly from a specific location in a storage account. I created a storage account and manually uploaded a foo.txt file to an "artifacts" File Share under a subfolder called Secrets. I uploaded a copy off another in a different subfolder (Azure-Storage-Upload) of the same File Share The pipeline syntax step suggests that downloading from the File Share is possible and that files can be downloaded using ant fileset syntax (I attached a screenshot of the syntax help) I created a simple pipeline:
pipeline{
agent any
stages{
stage ('Do Something'){
steps{
echo 'download'
azureDownload downloadType: 'share',
fileShare: 'artifacts',
includeFilesPattern: 'Secrets/foo.txt',
storageCredentialId: 'jenkins-devops-test-02'
}
}
}
}
[JIRA] (JENKINS-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener
Title: Message Title David Olorundare updated JENKINS-56008 Jenkins / JENKINS-56008 Update HudsonPrivateSecurityRealm.Details use of SecurityListener Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56316) Unable to build blueocean-plugin\jenkins-design-language on Windows
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-56316 Unable to build blueocean-plugin\jenkins-design-language on Windows Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-02-27 19:45 Environment: Windows 10 Priority: Minor Reporter: Stuart Rowe [INFO] @jenkins-cd/design-language@0.0.163 \blueocean-plugin\jenkins-design-language [ERROR] npm ERR! Windows_NT 10.0.17763 [INFO] `-- (empty) [ERROR] npm ERR! argv "\\blueocean-plugin\\jenkins-design-language\\node\\node.exe" "\\blueocean-plugin\\jenkins-design-language\\node\\node_modules\\npm\\bin\\npm-cli.js" "install" [INFO] [ERROR] npm ERR! node v6.4.0 [ERROR] npm ERR! npm v3.10.3 [ERROR] npm ERR! code ELIFECYCLE [ERROR] [ERROR] npm ERR! node-sass@4.5.3 postinstall: `node scripts/build.js` [ERROR] npm ERR! Exit status 1 [ERROR] npm ERR! [ERROR] npm ERR! Failed at the node-sass@4.5.3 postinstall script 'node scripts/build.js'. [ERROR] npm ERR! Make sure you have the latest version of node.js and npm installed. [ERROR] npm ERR! If you do, this is most likely a problem with the node-sass package, [ERROR] npm ERR! not with npm itself. [ERROR] npm ERR! Tell the author that this fails on your system: [ERROR] npm ERR! node scripts/build.js [ERROR] npm ERR! You can get information on how to open an issue for this project with: [ERROR] npm ERR! npm bugs node-sass [ERROR] npm ERR! Or if that isn't available, you can get their info via: [ERROR] npm ERR! npm owner ls node-sass [ERROR] npm ERR! There is likely additional logging output above. [ERROR] [ERROR] npm ERR! Please include the
[JIRA] (JENKINS-44915) Pylint Warnings: Details table could provide summary string with category
Title: Message Title Ulli Hafner commented on JENKINS-44915 Re: Pylint Warnings: Details table could provide summary string with category Which version of analysis-model-api do you have installed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56310) Error-Prone warnings trend spikes because of Gradle incremental build
Title: Message Title Ulli Hafner resolved as Not A Defect I don't see what I can do here. Jenkins / JENKINS-56310 Error-Prone warnings trend spikes because of Gradle incremental build Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12793) Why the Post Steps and Post-build Actions are not executed after the build finished
Title: Message Title Priyanka Marthi commented on JENKINS-12793 Re: Why the Post Steps and Post-build Actions are not executed after the build finished Even i am facing the same issue. Log text does not match with the build log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title
Narayanan Singaram commented on JENKINS-55392
Re: java.util.concurrent.RejectedExecutionException AGAIN
We also do not use {containerLog} and still are impacted by this issue.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe created an issue Jenkins / JENKINS-56315 Add "docker" alias for DockerTool Issue Type: Improvement Assignee: Unassigned Components: docker-commons-plugin Created: 2019-02-27 18:43 Labels: pipeline-improvement Priority: Minor Reporter: James Howe Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. Add Comment
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt edited a comment on JENKINS-55453 Re: Github PR creating job but not building For posterity - https://issues.jenkins-ci.org/browse/JENKINS-54864?focusedCommentId=355479=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-355479 did resolve the problem. cc [~lanwen] do you want to resolve and link to that ticket? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56314) File parameter throw null pointer exception
Title: Message Title ke liu created an issue Jenkins / JENKINS-56314 File parameter throw null pointer exception Issue Type: Bug Assignee: Unassigned Attachments: build-1-success.png, build-2-failed.png Components: core, parameterized-trigger-plugin Created: 2019-02-27 18:42 Environment: Jenkins ver. 2.146 Labels: jenkins concurrent-build file-parameter Priority: Blocker Reporter: ke liu We are using Jenkins REST APIs to submit jobs (create: server/createItem, launch: server/job//buildWithParameters). Each job runs with a file parameter: abc.yaml, the content of the file submitted with the REST API. We been experienced lots of job crashes at the very beginning of the run with he following null pointer exceptions: 6:28:05 Started by user admin 16:28:05 Building in workspace /.../workspace 16:28:05 FATAL: null 16:28:05 java.lang.NullPointerException 16:28:05 at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:159) 16:28:05 at hudson.model.Build$BuildExecution.doRun(Build.java:157) 16:28:05 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 16:28:05 at hudson.model.Run.execute(Run.java:1810) 16:28:05 at hudson.model.Build.run(Build.java:114) 16:28:05 at hudson.model.ResourceController.execute(ResourceController.java:97) 16:28:05 at hudson.model.Executor.run(Executor.java:429) The crashes happened randomly among
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt commented on JENKINS-55453 Re: Github PR creating job but not building For posterity - https://issues.jenkins-ci.org/browse/JENKINS-54864?focusedCommentId=355479=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-355479 did resolve the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32619) Javadoc link displays only documentation frame with no content
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32619 Javadoc link displays only documentation frame with no content Change By: Oleg Nenashev Labels: java11-compatibility javadoc jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56303) Existing user loses build history and other views
Title: Message Title Daniel Beck commented on JENKINS-56303 Re: Existing user loses build history and other views There should be a "+" icon in the part of the widget that is still visible. If there's nothing, please provide screen shots and a log of HTTP requests and responses when loading affected pages. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56306) Jenkins run script with different scree resolution which causes it to fail
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Try chat, or Stack Overflow. Jenkins / JENKINS-56306 Jenkins run script with different scree resolution which causes it to fail Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56293) Unable to update or install plugins
Title: Message Title Daniel Beck closed an issue as Not A Defect If this were a Jenkins or Jenkins project infra issue, it would be widespread. Probably an issue with your network. Check whether you can access plain HTTP URLs at all. Jenkins / JENKINS-56293 Unable to update or install plugins Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Daniel Beck commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Wadeck Follonier FYI Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati updated JENKINS-56304 Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Naresh Rayapati Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely No problem! Thank you for using this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati updated JENKINS-56304 Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Naresh Rayapati Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated JENKINS-56304 work-around found. Invocation of step from method is illegal. Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated JENKINS-56304 Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt edited a comment on JENKINS-55453 Re: Github PR creating job but not building [~jglick] or [~rsandell] - Could either of you weigh in on this please? Perhaps related to: https://issues.jenkins-ci.org/browse/JENKINS-54864? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely OK resolved it - many thanks. Indeed, you have to build an array of Jiras to update in a method, then do the updating back in the stage (inside a script marker). I added my final code to output-final.txt in the hopes maybe it will benefit the next person. Naresh Rayapati Thank you for the help! Issue can be closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-final.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt commented on JENKINS-55453 Re: Github PR creating job but not building Jesse Glick or rsandell - Could either of you weigh in on this please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title Luke Southwell edited a comment on JENKINS-43556 Re: Stage View shows incorrect build result I am also seeing this issue with 2.150.3 which has caused great confusion. Has anyone got a reliable work around? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Naresh Rayapati Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55568) CWP: Add support of passing Jenkins Core version from pom.xml
Title: Message Title Francisco Fernández updated JENKINS-55568 Jenkins / JENKINS-55568 CWP: Add support of passing Jenkins Core version from pom.xml Change By: Francisco Fernández Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Michael Sanders commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Getting this when restarting after updating a plugin. Clicking the checkbox for restarting jenkins when no jobs are running, will immediately produce this error. However, if I wait for Jenkins to restart, it will eventually restart properly. This is on a brand new Jenkins installation using the official docker image on an Ubuntu 18.04 EC2 instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely I'm inferring that if I use the @NonCPS method to build an array of Jiras to update (ID + Comment), pass the array back to the stage, iterate and call jiraAddComment for each element in the array (from the stage), it would work. I think? My groovy skills are weak. Built an array in the method, but cannot figure out how to get it back to the stage Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely yeah, as I mentioned in the above comments, pipeline steps has be outside the @NonCPS function. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title
pjdarton commented on JENKINS-51004
Re: slave.jar -loggingConfig argument not working as documented
FYI, since I originally logged this bug, I uploaded the script that I use to run slave.jar onto the Jenkins wiki (as an example JNLP launcher script for use with the vSphere plugin, as folks kept getting stuck on this bit). This script shows how I was invoking slave.jar, which should help with reproducing the bug (if the bug is still present in the current version of the code). You can find it by going to the vSphere Cloud Plugin wiki page and looking for JenkinsSlaveStartup.cmd. That has a line (485) saying
@SET _cmdLine=%JAVA_HOME%bin\java -Djava.util.logging.config.file=jenkins-slave.logging.properties %SLAVE_JVM_ARGS% -jar slave.jar -jnlpUrl %SLAVE_JNLP_URL% %SLAVE_PARAMS%
where SLAVE_JVM_ARGS are typically "-Xms256M -Xmx4096M -Dhudson.remoting.RemoteClassLoader.force=com.sun.jna.Native", the SLAVE_JNLP_URL is what you'd expect and SLAVE_PARAMS typically contains "{{-secret }}" and little else. ...and the next but-one line runs %_cmdLine% to invoke .../bin/java ... -jar slave.jar ...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #4: calling jiraAddComment twice directly from steps(), i.e. no method call, definitely works. Just verified that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56313) stage process fails after accessing parsed xml childNodes
Title: Message Title
Sam Stephenson created an issue
Jenkins / JENKINS-56313
stage process fails after accessing parsed xml childNodes
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin
Created:
2019-02-27 16:22
Environment:
latest 2.150
Labels:
pipeline groovy-script serialization
Priority:
Critical
Reporter:
Sam Stephenson
It appears that if you execute a function in stage and that function accesses a child node that has been form by parsing XML the stage will fail after the function is complete and successful Example:
def xmlData = "" +
"" +
"" +
"foo" +
"" +
"" +
""
node() {
stage( 'read' ) {
echo "Testing nodeChildren"
outputData()
}
}
@NonCPS
def getLatestXML() {
echo "Before parsed"
def data = "" class="code-keyword" style="color: #91">new XmlSlurper().parseText(xmlData)
echo "parsed "
value = "${data.parent.child}-0.4.0-"
echo "I can access value" + value.getClass()
return value
}def outputData () {
def value = getLatestXML()
echo "I can echo but I can't do anything with it"
println "value: ${value}"
}
This will fail with a java.io.NotSerializableException: groovy.util.slurpersupport.NodeChildren even though the process was successful This happens regardless if
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-56304
Re: jiraAddComment terminates the step prematurely
But the code is still in @NonCPS method with Experiment #3, try invoking these steps outside that method.https://jenkins.io/blog/2017/02/01/pipeline-scalability-best-practice/3. c{noformat}@NonCPS functions should not use Pipeline steps internally, however you can store the result of a Pipeline step to a variable and use it that as the input to a @NonCPS function.Gotcha: It’s not guaranteed that use of a step will generate an error (there is an open RFE to implement that), but you should not rely on that behavior. You may see improper handling of exceptions, in particular.{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title Jeff Thompson commented on JENKINS-51004 Re: slave.jar -loggingConfig argument not working as documented I tested it with a Jenkins instance running on Mac and an agent on Windows. I tried to follow the documentation and the defect report, though I don't recall the details now. Things seemed to work the way I expected. If you could file a PR that would be great. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely But the code is still in @NonCPS method with Experiment #3, try invoking these steps outside that method. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #3: Complete replacement of the method with a trivial invocation that invokes jiraAddComment twice - Failure (in same manner as original issue) See output-truncatedCall.txt. The stage succeeds (green and not red). However, logs indicate that we only invoked the first jiraAddComment and no further steps were performed (like the original bug). Inspection in Jira confirms that only the FIRST jiraAddComment was received. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title Sergiy Tupchiy commented on JENKINS-54250 Re: Disable restarting stages in jenkinsfile optionally +1 Within k8s environment, using kubernetes-plugin, and running dynamic agents makes having this option obsolete. Also took some time, and still the case, to explain people in our company, how to properly restart the job, every time, that you should actually use "replay" in this case instead. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-56304
Re: jiraAddComment terminates the step prematurely
With Experiment #1, you got to deal with the variables those are non serializable in that method to get through that. And from the design you can't invoke pipeline steps from a method with @NonCPS annotation, I don't see any problem with the jiraAddComment step. {panel:title=https://github.com/jenkinsci/workflow-cps-plugin#technical-design }You may not call regular (CPS-transformed) methods, or Pipeline steps, from a {{@NonCPS}} method, so they are best used for performing some calculations before passing a summary back to the main script. {panel}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely With Experiment #1, you got to deal with the variables those are non serializable in that method to get through that. And from the design you can't invoke pipeline steps from a method with @NonCPS annotation, I don't see any problem with the jiraAddComment step. https://github.com/jenkinsci/workflow-cps-plugin#technical-design You may not call regular (CPS-transformed) methods, or Pipeline steps, from a @NonCPS method, so they are best used for performing some calculations before passing a summary back to the main script. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-truncatedCall.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56312) PCT not taking into account
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56312 PCT not taking into account Issue Type: Bug Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-02-27 16:02 Priority: Minor Reporter: Raul Arabaolaza Since JENKINS-55681 splits can be JVM version dependent, but the PCT is not able to detect the JDK version field on the splits file and is adding those plugins always. As a result the PCT is incorrectly adding `jaxb` plugin even to java 8 runs Add Comment
[JIRA] (JENKINS-49394) Allow to specify visibility on addComment
Title: Message Title Naresh Rayapati updated JENKINS-49394 Jenkins / JENKINS-49394 Allow to specify visibility on addComment Change By: Naresh Rayapati Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #2: (restored @NonCPS) replace invocation of jiraAddComment with echo instead - qualified success The Stage succeeds. The log messages indicate it goes through the expected pathways - looping and recursing as expected. Message payload looks correct. No errors. Obviously, we are NOT sending anything to Jira with this approach, but it verifies syntax. See output-stubCall.txt for details This seems to firmly point the finger at the call to jiraAddComment as the culprit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-stubCall.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56311) github-coverage-reporter-plugin missing pipeline instructions
Title: Message Title Jack Newcombe moved an issue Jenkins / JENKINS-56311 github-coverage-reporter-plugin missing pipeline instructions Change By: Jack Newcombe Project: Infrastructure Jenkins Key: INFRA JENKINS - 2036 56311 Workflow: classic default workflow JNJira + In-Review Component/s: github-coverage-reporter-plugin Component/s: plugins.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title Luke Southwell commented on JENKINS-43556 Re: Stage View shows incorrect build result I am also seeing this issue which has caused great confusion. Has anyone got a reliable work around? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56310) Error-Prone warnings trend spikes because of Gradle incremental build
Title: Message Title Andrea me created an issue Jenkins / JENKINS-56310 Error-Prone warnings trend spikes because of Gradle incremental build Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-02-27-15-26-18-072.png Components: warnings-ng-plugin Created: 2019-02-27 14:41 Environment: Jenkins: 2.150.3 warnings-ng-plugin: 3.0.3 gradle: 5.2.1 java: 1.8 Priority: Minor Reporter: Andrea me As you can see in the attached image, error prone warnings trend graph presents spikes. The problem is that Gradle's builds do not recompile all java files because of its incremental build. Is there something that I can do to avoid this behavior? I can't clean my build each time Add Comment
[JIRA] (JENKINS-56309) MultiBranch Pipeline fails when searching for Pull Requests - java.lang.NullPointerException
Title: Message Title Andre Oliveira updated an issue Jenkins / JENKINS-56309 MultiBranch Pipeline fails when searching for Pull Requests - java.lang.NullPointerException Change By: Andre Oliveira Attachment: 2.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #1: Remove @NonCPS - Failed The stage now fails (red instead of green stage). The log messages indicate it went into jiraAddComment and then hit a "Failed in branch Update Jira". There is a stack-trace later in the log that indicates "java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
