[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Hi Oleg Nenashev, Sam Van Oort, Thank you for the quick reply! Please find the build.xml in attachment. I hope this helps reproducing the issue. I can load an visualize the build in the Jenkins web interface without any problem. The issue occurs when trying to change the config (e.g. "Don't keep this build forever" or change its description.) Thank you in advance! With best regards, Tom. 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck updated an issue Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Tom Ghyselinck Attachment: build.xml 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck updated an issue Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Tom Ghyselinck Attachment: build.xml 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-49178) Comment trigger is no longer supported in JIRA Cloud
Title: Message Title Wisen Tanasa started work on JENKINS-49178 Change By: Wisen Tanasa 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-50736) Calling another vars step in inheritance context fails with MissingMethodException
Title: Message Title Reinhold Füreder commented on JENKINS-50736 Re: Calling another vars step in inheritance context fails with MissingMethodException Frankly, I don't think so: as def acme is already public, changing it to protected def acme should not help. Sorry for the very lengthy and potentially confusing issue description; maybe due to getting doubts whether or not this is a bug, I made some re-writes and adaptions later on, which may not made the issue description clearer... => I'll try to properly re-produce it and then I'll try your protected guess as well... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Mark Waite Hi Mark, I found some hint [1] however I use Ubuntu and not Windows, but this forced me to ask you about git credentials and some other question. Maybe the pull request can be extended with some more logs. How credentials are passed to these commands and each of them? Can we see them and is this real command executed in sub-process? Is Git running in a non-interactive mode? Can we detect that Git is interactively asking for some input on STD/IN? I guess Jenkins plugin runs Git in Java sub-process. Can we see std/err as well as std/out in the console including the error code returned by the sub-process? Why timeout 10 minutes is not applied however it is seen in the console log after the command (# timeout=10)? [1]: https://support.cloudbees.com/hc/en-us/articles/221046888-Build-Hang-or-Fail-with-Git-for-Windows 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-31507) docker.build throw IOExceptions with some sources
Title: Message Title YJ Hwang commented on JENKINS-31507 Re: docker.build throw IOExceptions with some sources Same here. I just removed the tab in front of the image name, then works. please patch 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-26107) Allow stage to operate as a labelled block
Title: Message Title Marcello de Sales commented on JENKINS-26107 Re: Allow stage to operate as a labelled block Baptiste Mathus I actually used other CI solutions where it naming an "sh" operation was very useful. 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-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Martin d'Anjou commented on JENKINS-50887 Re: Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Torsten Kleiber, see the GSoC schedule. In 2018 projects are announced on April 23, and the GSoC program ends on August 22. 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-50777) Exported API for SCMRevisionAction
Title: Message Title Jesse Glick updated JENKINS-50777 Jenkins / JENKINS-50777 Exported API for SCMRevisionAction 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50777 Exported API for SCMRevisionAction & SCMSource Change By: Jesse Glick Summary: Exported API for SCMRevisionAction & SCMSource 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-50777) Exported API for SCMRevisionAction
Title: Message Title Jesse Glick started work on JENKINS-50777 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-50777) Exported API for SCMRevisionAction
Title: Message Title Jesse Glick updated JENKINS-50777 Jenkins / JENKINS-50777 Exported API for SCMRevisionAction 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-50852) Maven report: remove duplicate dependencies list
Title: Message Title dan tran commented on JENKINS-50852 Re: Maven report: remove duplicate dependencies list It works!!! 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project it works * The Upstreams build content is correct * The downtream job shows it same project one once. Used to be 2. And teh build does not rebuild itself again. Awesome Thanks again 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-50777) Exported API for SCMRevisionAction
Title: Message Title Jesse Glick reopened an issue Also need reliable access to the repository identity; again, using BuildData is unreliable. Jenkins / JENKINS-50777 Exported API for SCMRevisionAction Change By: Jesse Glick Resolution: Fixed Status: Resolved 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:/
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Vetting the getOrNull uses: The multibranch one is indeed an issue, so is the parallelTestExecutor, and the Pipeline Timings, others are OK Replay needs to fully fetch executions if you are fetching execution info (addressing via PR). We do need to address the use of getOrNull in ReplayAction as well Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker commented on JENKINS-13128 Re: Artifacts Permissions Stripped The simple approach to fixing this is to preserve posix file permissions by default along with mtimes. A umask option could also be added to allow for reverting to the old behavior (umask of 133). Whether or not attempting to preserve file and group ownership is worthwhile may be another story. 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Steve Todorov edited a comment on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker ++[~acejam] try reverting to an older version of Docker Pipeline. I have been using the older version since this issue hit me in [ JENKINS-47805 |https://issues . jenkins-ci.org/browse/JENKINS-47805]. It seems that you can fix this either by using a mvnw, downgrade to an older version of Docker Pipeline or wait for [ JENKINS-48050 |https://issues which looks like it will fix it for good . jenkins-ci.org/browse/JENKINS-48050]. 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Steve Todorov commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker ++Joshua Noble try reverting to an older version of Docker Pipeline. I have been using the older version since this issue hit me in JENKINS-47805. It seems that you can fix this either by using a mvnw, downgrade to an older version of Docker Pipeline or wait for JENKINS-48050. 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-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-13128 Artifacts Permissions Stripped Change By: Matt Sicker Assignee: Matt Sicker 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 Thanks! 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-50736) Calling another vars step in inheritance context fails with MissingMethodException
Title: Message Title Andrew Bayer commented on JENKINS-50736 Re: Calling another vars step in inheritance context fails with MissingMethodException So I've been looking at something similar to this - it seems that this is due to JENKINS-31484. It looks like if you switch to protected def acme, it may work? 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Andrew Bayer commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 Yeah, that'll be fine. 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 This change appears to have caused a lot of "CannotResolveClassException: org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTValue$1" warnings to show up for old WorkflowRun objects in /adminstrativeMonitor/OldData/manage ; is it okay to discard all the data here? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco edited a comment on JENKINS-22268 Re: Boost C++ unit tests and the xUnit plugin - Not working core-159 on current version in master produce a correct junit xml report. The older one the validation fails because: An invalid XML character (Unicode: 0x1) was found in the CDATA section. Maybe the file uploaded is not exactly the same produced by the boosttest. If yes that it's not a problem of this plugin if the XML is not valid. 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Joshua Noble commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker Any updates on 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-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco edited a comment on JENKINS-22268 Re: Boost C++ unit tests and the xUnit plugin - Not working Both file core-159 on current version in master produce a correct junit xml report. The older one the validation fails because: An invalid XML character (Unicode: 0x1) was found in the CDATA section. 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-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco stopped work on JENKINS-22268 Change By: Nikolas Falco Status: In Progress 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-50906) Assigning variable to WorkflowScript property breaks Callable sugar in restricted sandbox
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar in restricted sandbox
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox:{{def func = \{ 1 }; }} {{this.func2 = \{ 1 }; }} {{assert 1 == func(); }} {{assert 1 == func2.call(); }} {{assert 1 == func2(); // this line fails }}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{this}}). N Given that this works outside of restricted sandbox, it appears as if this is *maybe* by design, but in my uninformed opinion this is not the correct behavior.
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 receiv
[JIRA] (JENKINS-50906) Assigning variable to WorkflowScript property breaks Callable sugar in restricted sandbox
Title: Message Title Fred Spieler updated an issue Jenkins / JENKINS-50906 Assigning variable to WorkflowScript property breaks Callable sugar in restricted sandbox Change By: Fred Spieler Summary: Assigning variable to WorkflowScript property breaks Callable sugar in restricted sandbox 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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox:{{def func = \{ 1 }; }}{{this.func2 = \{ 1 }; }}{{assert 1 == func(); }}{{assert 1 == func2.call(); }}{{assert 1 == func2(); // this line fails }}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{this}}). N
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-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-22268 Boost C++ unit tests and the xUnit plugin - Not working Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco 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-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco edited a comment on JENKINS-22268 Re: Boost C++ unit tests and the xUnit plugin - Not working Both file on current version in master produce a correct junit xml report . 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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title Fred Spieler reopened an issue Sorry, on second thought, I believe this is still a bug; if it's possible to overwrite WorkflowScript variables in restricted sandbox it should be fine to make the callable syntax functional. I'm clearly on the fence between bug and feature, but leaning towards bug. Jenkins / JENKINS-50906 Assigning variable to WorkflowScript property breaks Callable sugar Change By: Fred Spieler Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-50784 "Replay" pipeline button/link is not (always?) available (anymore?) Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort started work on JENKINS-50784 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title Fred Spieler resolved as Not A Defect It seems that this is by design of restricted sandbox. Jenkins / JENKINS-50906 Assigning variable to WorkflowScript property breaks Callable sugar Change By: Fred Spieler Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) So, we were right that it's related to the lazy load functionality, but wrong about why... it has to do with the FlowExecutionOwner doing The Wrong Thing. AFAICT the ReplayAction actually works in testing currently if we apply the workflow-job patch proposed in the linked PR – my guess is something upstream triggers the full execution loading (looking into what, though). 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-22268) Boost C++ unit tests and the xUnit plugin - Not working
Title: Message Title Nikolas Falco commented on JENKINS-22268 Re: Boost C++ unit tests and the xUnit plugin - Not working Both file on current version in master produce a correct junit xml report 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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox:{{def func = \{ 1 }; }}{{ this.func2 = \{ 1 }; }}{{ assert 1 == func(); }}{{ assert 1 == func2.call(); }}{{ assert 1 == func2(); // this line fails }}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox:{{def func = \{ 1 } ; }}{{ this.func2 = \{ 1 } ; }}{{ assert 1 == func() ; }}{{ assert 1 == func2.call() ; }}{{ assert 1 == func2() ; // this line fails}}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox: {{ def func = \{ 1 } }} {{ this.func2 = \{ 1 } }} {{ assert 1 == func() }} {{ assert 1 == func2.call() }} {{ assert 1 == func2() // this line fails }} It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox: {{ def func = \{ 1 } }} {{ this.func2 = \{ 1 } }} {{ assert 1 == func() }} {{ assert 1 == func2.call() }} {{ assert 1 == func2() // this line fails }} It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile: \ { \ {def func = \{ 1 }}} \ { \ { this.func2 = \{ 1 }}} \ { \ { assert 1 == func()}} \ { \ { assert 1 == func2.call()}} \ { \ { assert 1 == func2() // this line fails}}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler updated an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Change By:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile in restricted sandbox :{{ def func = \{ 1 } }}{{ this.func2 = \{ 1 } }}{{ assert 1 == func() }}{{ assert 1 == func2.call() }}{{ assert 1 == func2() // this line fails }}It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript ({{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-50906) Assigning variable to WorkflowScript property breaks Callable sugar
Title: Message Title
Fred Spieler created an issue
Jenkins / JENKINS-50906
Assigning variable to WorkflowScript property breaks Callable sugar
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-04-19 20:23
Environment:
Jenkins v2.84, Pipeline: Groovy v2.41
Priority:
Minor
Reporter:
Fred Spieler
Here's a minimal example that works when running in groovysh but fails when running in Jenkinsfile: {{def func = { 1 }}} {{ this.func2 = { 1 }}} {{ assert 1 == func()}} {{ assert 1 == func2.call()}} {{ assert 1 == func2() // this line fails}} It appears as if the it.call() -> it() syntactic sugar, which afaik is part of the language spec, is not honored when assigning callable properties to WorkflowScript (this).
Add Comment
[JIRA] (JENKINS-11294) xUnit boost test cases are assigned to bogus package called "(root)"
Title: Message Title Nikolas Falco resolved as Fixed The current code in master produce a JUnit report where all testcase has the classname attribute that starts with "basic" Jenkins / JENKINS-11294 xUnit boost test cases are assigned to bogus package called "(root)" Change By: Nikolas Falco Status: Open 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-issu
[JIRA] (JENKINS-11294) xUnit boost test cases are assigned to bogus package called "(root)"
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-11294 xUnit boost test cases are assigned to bogus package called "(root)" Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco 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-11294) xUnit boost test cases are assigned to bogus package called "(root)"
Title: Message Title Nikolas Falco stopped work on JENKINS-11294 Change By: Nikolas Falco Status: In Progress 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-50885) BlueOcean should have an optional dependency on JIRA plugin
Title: Message Title Vivek Pandey edited a comment on JENKINS-50885 Re: BlueOcean should have an optional dependency on JIRA plugin PR https://github.com/jenkinsci/blueocean-plugin/pull/1719#pullrequestreview-113742435.I tested this PR. I could not directly uninstall blueocean-jira plugin even though its optional. Uninstall button next to blueocean-jira was disabled. Looks like we can't do it directly from Update Center till we fix https://issues.jenkins-ci.org/browse/JENKINS-33843.As mentioned in this ticket, this is how you uninstall an optional plugin:- touch $JENKINS_HOME/plugins/blueocean-jira.hpi.disabled- Restart Jenkins Still a pain to uninstall but at least its way forward.EDIT:[~michaelneale] There is also a downside making anything optional - Go In future if we decide to UpdateCenter, make blueocean-jira plugin should have enabled `uninstall` button. Click on mandatory then its going to cause blueocean upgrade issues as blueocean will fail to load as it will detect blueocean-jira is mandatory dependency - will require user intervention to uninstall enable blueocean-jira plugin by going to update center . Still a pain Basically if we decide to uninstall but at least its keep it optional, better to keep it this way forward forever otherwise there is going to be upgrade pains should we decide to make it non-optional . 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...@googlegroup
[JIRA] (JENKINS-50905) Number of failed Tests tops out at 99 - could be misleading?
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50905 Number of failed Tests tops out at 99 - could be misleading? Issue Type: Bug Assignee: Unassigned Attachments: image-2018-04-19-15-38-20-880.png Components: blueocean-plugin Created: 2018-04-19 19:39 Priority: Minor Reporter: Karl Shultz Summary For a job that has test failures, Blue Ocean puts up a number in the "Tests" tab for a particular run, which presumably corresponds to the number of failures. But it appears this number caps out at 99. If there are more than that number of test failures, the user either won't know by looking, or will see inconsistent information once they're viewing the Tests tab. Steps to recreate 1. Build a job that has a LOT of test failures - over 100. 2. Look at the Tests tab, and note the "99" shown. 3. Once you click on the Tests tab, you'll see the real number.: Suggestion If the concern was one of space, and not wanting to show "400" test failures for example, maybe something like >99, or 100+ could be shown, if the number is larger than 99?
[JIRA] (JENKINS-50904) allow system level max on number of retries
Title: Message Title DI2E SysAdmin created an issue Jenkins / JENKINS-50904 allow system level max on number of retries Issue Type: Bug Assignee: Nicolas De Loof Components: naginator-plugin Created: 2018-04-19 19:38 Priority: Minor Reporter: DI2E SysAdmin We've a heavily used Jenkins environment. We'd like there to be a system-wide naginator setting for the max number of retries that can be configured in any one job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d
[JIRA] (JENKINS-50885) BlueOcean should have an optional dependency on JIRA plugin
Title: Message Title Vivek Pandey started work on JENKINS-50885 Change By: Vivek Pandey 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-50885) BlueOcean should have an optional dependency on JIRA plugin
Title: Message Title Vivek Pandey commented on JENKINS-50885 Re: BlueOcean should have an optional dependency on JIRA plugin PR https://github.com/jenkinsci/blueocean-plugin/pull/1719#pullrequestreview-113742435. I tested this PR. I could not directly uninstall blueocean-jira plugin even though its optional. Uninstall button next to blueocean-jira was disabled. Looks like we can't do it directly from Update Center till we fix https://issues.jenkins-ci.org/browse/JENKINS-33843. As mentioned in this ticket, this is how you uninstall an optional plugin: touch $JENKINS_HOME/plugins/blueocean-jira.hpi.disabled Restart Jenkins Go to UpdateCenter, blueocean-jira plugin should have enabled `uninstall` button. Click on it to uninstall. Still a pain to uninstall but at least its way forward. 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 Jenkins / JENKINS-50885 BlueOcean should have an optional dependency on JIRA plugin Change By: Vivek Pandey 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-50085) Integration Test for Module Detector
Title: Message Title Frank Christian Geyer assigned an issue to Frank Christian Geyer Jenkins / JENKINS-50085 Integration Test for Module Detector Change By: Frank Christian Geyer Assignee: Ulli Hafner Frank Christian Geyer 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-50428) Adjust support-core to the now configurable location for tasks logging
Title: Message Title Baptiste Mathus commented on JENKINS-50428 Re: Adjust support-core to the now configurable location for tasks logging Thanks Devin Nusbaum 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Oleg Nenashev commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API I am going to ship https://github.com/jenkinsci/ownership-plugin/pull/73 by the weekend. Meanwhile you can take https://ci.jenkins.io/job/Plugins/job/ownership-plugin/job/PR-73/2/artifact/target/ownership.hpi and try it out 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-48456) Add support for Sun OS platforms (such as solaris)
Title: Message Title Nikolas Falco updated JENKINS-48456 Jenkins / JENKINS-48456 Add support for Sun OS platforms (such as solaris) Change By: Nikolas Falco 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-29913) Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
Title: Message Title
Sverre Moe commented on JENKINS-29913
Re: Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
A much needed feature. A solution has been made for the Pipeline Maven Plugin and its PipelineGraphPublisher, but that will not helps us where the majority of our projects are C/C++. For C/C++ projects where build requirements are stored in RPM spec files we must implement some solution in our pipeline shared library. In our pipeline we iterate through all projects in Jenkins build view, check out and parse their RPM spec file, find all downstream dependencies from the extracted build requirements. Then executes verification builds on each of them. This adds unnecessary complexity and build time to our build pipeline. However this does only give us direct dependencies, and not all transitive dependencies, so I even considered taking the code from DependencyGraph to use in our Pipeline, but it was not feasible. If we had the DependencyGraph for Pipeline and Multibranch Pipeline projects we could just at every SCM change update the projects upstream dependencies. Then later in the pipeline trigger build of all transitive dependencies.
stage("checkout") {
checkout scm
def downstreamProjects = findAllDownstreamProjects()
currentBuild.setDownstreamProjects(downstreamProjects)
build()
}
stage("verify") {
def deps = currentBuild.getTransitiveDownstream()
deps.each { dep -> build name: dep }
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50882) Declarative Directive Generator is a 404 in multibranch Pipeline
Title: Message Title Andrew Bayer updated JENKINS-50882 Jenkins / JENKINS-50882 Declarative Directive Generator is a 404 in multibranch Pipeline Change By: Andrew Bayer 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-50882) Declarative Directive Generator is a 404 in multibranch Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-50882 Re: Declarative Directive Generator is a 404 in multibranch Pipeline PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/267 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-50823) Unable to download latest artifact from snapshot repository
Title: Message Title Eyal Ben Moshe commented on JENKINS-50823 Re: Unable to download latest artifact from snapshot repository We don't yet have an ETA for this, but it is definitely on our roadmap. JFrog CLI supports sort-by, sort-order and linit bith as File Spec properties and command options. That's the way to get the latest artifact. The File Spec schema for Jenkins will eventually match JFrog CLI's. The File Spec you shared will not work. 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-50882) Declarative Directive Generator is a 404 in multibranch Pipeline
Title: Message Title Andrew Bayer started work on JENKINS-50882 Change By: Andrew Bayer 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-26246) Publish over ssh on multiple nodes
Title: Message Title Alex Earl commented on JENKINS-26246 Re: Publish over ssh on multiple nodes Ok, I just recently took over maintaining this plugin and so I am going back through old issues. I'll just close it out for now. 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-26246) Publish over ssh on multiple nodes
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-26246 Publish over ssh on multiple nodes Change By: Alex Earl Status: Open Closed Resolution: Incomplete 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-49668) Root CAs component appears broken
Title: Message Title Devin Nusbaum commented on JENKINS-49668 Re: Root CAs component appears broken Released in 2.47. See the changelog. 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-50428) Adjust support-core to the now configurable location for tasks logging
Title: Message Title Devin Nusbaum commented on JENKINS-50428 Re: Adjust support-core to the now configurable location for tasks logging Released in 2.47. See the changelog. 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-50765) Harden support-core against XXE attacks
Title: Message Title Devin Nusbaum updated JENKINS-50765 Released in 2.47. See the changelog. Jenkins / JENKINS-50765 Harden support-core against XXE attacks Change By: Devin Nusbaum 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-26246) Publish over ssh on multiple nodes
Title: Message Title Jan Kowalski commented on JENKINS-26246 Re: Publish over ssh on multiple nodes Me too. It was 2 years ago, I don't remember 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-50903) Confluence publisher plugin fails to render Wiki Markup Replacements
Title: Message Title Steven Deal created an issue Jenkins / JENKINS-50903 Confluence publisher plugin fails to render Wiki Markup Replacements Issue Type: Task Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 2018-04-19 17:37 Environment: confluence-publisher-plugin version 2.0.1 Priority: Minor Reporter: Steven Deal If you 'Add Replacements' to your job configuration, they each appear on the job configuration page. If you save your changes and reopen the job configuration, they do not appear even though they have been saved in the job's config.xml. Add Comment
[JIRA] (JENKINS-50700) Fix maven-hpi-plugin to use hudson.util.VersionNumber
Title: Message Title Jesse Glick updated JENKINS-50700 Jenkins / JENKINS-50700 Fix maven-hpi-plugin to use hudson.util.VersionNumber 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-46392) Class Not Found error when testing WAS 8.5 Connection
Title: Message Title Greg Peters commented on JENKINS-46392 Re: Class Not Found error when testing WAS 8.5 Connection You must restart jenkins after copying the jar files into the "WEB-INF/lib" path. 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-47563) Websphere Deployer fails to deploy to multiple servers
Title: Message Title Greg Peters reopened an issue I'm taking another look at this Jenkins / JENKINS-47563 Websphere Deployer fails to deploy to multiple servers Change By: Greg Peters Resolution: Won't Fix 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-49252) (JAVA:783)Getting issues while configure WAS
Title: Message Title Greg Peters closed an issue as Not A Defect This is related to not copying the jars in the correct location as specified in the WDP configuration page. You must place the JAR files in the "JENKINS_HOME/plugins/websphere-deployer/WEB-INF/lib" folder. Jenkins / JENKINS-49252 (JAVA:783)Getting issues while configure WAS Change By: Greg Peters Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from t
[JIRA] (JENKINS-49252) (JAVA:783)Getting issues while configure WAS
Title: Message Title Greg Peters assigned an issue to Greg Peters Jenkins / JENKINS-49252 (JAVA:783)Getting issues while configure WAS Change By: Greg Peters Assignee: Greg Peters 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-21863) WebSphere deployer: deploy to cluster
Title: Message Title Greg Peters commented on JENKINS-21863 Re: WebSphere deployer: deploy to cluster Failure to upload error is caused by issue related to JENKINS-31450. 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-50902) shell pipeline step cannot use relative path to shell
Title: Message Title akostadinov created an issue Jenkins / JENKINS-50902 shell pipeline step cannot use relative path to shell Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-04-19 16:53 Priority: Major Reporter: akostadinov There is some difference between free-style project shell build step and the pipeline `sh` step. If I set in jenkins global configuration `bash` as the "Shell Executable", then free-style project works and calls `bash` from the PATH on the slave. The pipeline `sh` step fails like this though: [pipeline-test-job] Running shell script sh: /home/jenkins/workspace/pipeline-test-akostadi@tmp/durable-2ff6e6ae/script.sh: bash: bad interpreter: No such file or directory [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 126 Finished: FAILURE The use case is that some systems like MacOS ship with an old bash version under /bin/sh. And we want to not be limited in shell scripts by that version. Since proper bash should be installed in other locations on such slaves, we need to run `bash` from PATH. But also can't hardcode `bash` absolute path because it is still `/bin/bash` on normal linux slaves. I'm reading through ShellStep.java and BourneShellScript.java. It looks like it launches `sh -c cmd` but I don't see how the global setting is applied, even less I understand why it fails. At the same time free-style projects work fine with this setting on all slaves. I think this difference between free-style and pipeline might be related to JENKINS-44341 also. Any clue what exactly might be the difference and how it could be fixed?
[JIRA] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Title: Message Title Greg Peters closed an issue as Fixed Closing, Duplicate of JENKINS-31450. This is not a bug, rather it's an issue with mismatched DNS/IP setting in jenkins job + SSL DNS name from the admin console. Jenkins / JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Change By: Greg Peters Status: Resolved Closed 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-31685) failure to upload artifact with custom Keystore and Truststores on websphere
Title: Message Title Greg Peters closed an issue as Not A Defect Closing Duplicate Jenkins / JENKINS-31685 failure to upload artifact with custom Keystore and Truststores on websphere Change By: Greg Peters Status: Resolved Closed 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-31685) failure to upload artifact with custom Keystore and Truststores on websphere
Title: Message Title Greg Peters updated JENKINS-31685 Duplicate issue, is fixed by using FQDN or matching DNS name in the SSL cert for the administration console. Jenkins / JENKINS-31685 failure to upload artifact with custom Keystore and Truststores on websphere Change By: Greg Peters Status: In Review Resolved 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-31685) failure to upload artifact with custom Keystore and Truststores on websphere
Title: Message Title Greg Peters updated JENKINS-31685 Jenkins / JENKINS-31685 failure to upload artifact with custom Keystore and Truststores on websphere Change By: Greg Peters Status: Closed In 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-30265) Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment)
Title: Message Title Greg Peters closed an issue as Duplicate Closing, duplicate of JENKINS-31450 Jenkins / JENKINS-30265 Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment) Change By: Greg Peters Status: Resolved Closed 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-31685) failure to upload artifact with custom Keystore and Truststores on websphere
Title: Message Title Greg Peters assigned an issue to Greg Peters Jenkins / JENKINS-31685 failure to upload artifact with custom Keystore and Truststores on websphere Change By: Greg Peters Assignee: Greg Peters 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-30265) Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment)
Title: Message Title Greg Peters resolved as Duplicate Jenkins / JENKINS-30265 Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment) Change By: Greg Peters Status: Reopened Resolved Resolution: Duplicate 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-30265) Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment)
Title: Message Title Greg Peters reopened an issue This is caused by the DNS/IP setting in the jenkins job. This setting should match the DNS name specified in the SSL cert that is used in cacerts (as specified in the plugin documentation) Jenkins / JENKINS-30265 Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment) Change By: Greg Peters Resolution: Fixed Status: Resolved 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
[JIRA] (JENKINS-30265) Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment)
Title: Message Title Greg Peters assigned an issue to Greg Peters Jenkins / JENKINS-30265 Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment) Change By: Greg Peters Assignee: Josu Bengoa Greg Peters 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-34070) NoStaplerConstructorException on UserMergeOptions.mergeStrategy
Title: Message Title Jesse Glick updated JENKINS-34070 Jenkins / JENKINS-34070 NoStaplerConstructorException on UserMergeOptions.mergeStrategy 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-31450) org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: Failure uploading archive to server
Title: Message Title Greg Peters commented on JENKINS-31450 Re: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: Failure uploading archive to server Specifically to this issue, you must use the fully qualified domain name (FQDN) that the SSL certificate specifies. If you're deploying on WAS ND, use the DMGR SSL certificate, if you're deploying to a standalone WAS instance, use the administration consoles SSL certificate. The setting in the jenkins job for the DNS/IP of the server should match the server listed in the SSL certificate. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Mark Waite edited a comment on JENKINS-48357
Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
[~tibor17] the message{noformat}16:25:09 > git rev-list --no-walk 3bb1f0fc92a0cdb29c6df7cd1eb109dbd372929d # timeout=10{noformat}is logged by the git client plugin.I suspect that the git plugin is not the cause of the hang. I can't see the hang myself, so have no way to diagnose it. I've submitted a git client plugin pull request that logs the conclusion of a command line git call so that we can see if the `git rev-list` command hangs or if execution proceeds beyond that point.You'll need to download and install the [ git-client-plugin.hpi |https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi] from the [pull request artifacts|https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi] when that build completes . That will be roughly 20-30 minutes from now.
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-50457) Attempt to (de-)serialize anonymous class
Title: Message Title Strajan Sebastian started work on JENKINS-50457 Change By: Strajan Sebastian 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-50823) Unable to download latest artifact from snapshot repository
Title: Message Title Kiran Kumar commented on JENKINS-50823 Re: Unable to download latest artifact from snapshot repository Eyal Ben Moshe So, you are saying that the AQL doesn't support the way Artifactory supports to download the SNAPSHOT Artifact ? File Specs would need to be changed in order to support fetching the latest artifact. Could you please let us know when can we expect this change ? Also, with JFrog CLI the above filespec pattern work ? 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-50899) JEP-200 compatibility
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-50899 JEP-200 compatibility Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate 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-50457) Attempt to (de-)serialize anonymous class
Title: Message Title Strajan Sebastian commented on JENKINS-50457 Re: Attempt to (de-)serialize anonymous class I think this isn't an isolated issue to a specific plugin. After upgrading today to the latest version of jenkins I started receiving similar messages. Please check below: Apr 19, 2018 4:08:00 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.model.ParametersDefinitionProperty$1 in file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.117.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Apr 19, 2018 4:10:00 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader$1 in file:/var/lib/jenkins/plugins/envinject/WEB-INF/lib/envinject.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Apr 19, 2018 4:10:00 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.service.EnvInjectActionSetter$1 in file:/var/lib/jenkins/plugins/envinject/WEB-INF/lib/envinject.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Apr 19, 2018 4:10:01 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in file:/var/lib/jenkins/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Apr 19, 2018 4:10:03 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.FilePath$11 in file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.117.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Thanks, Sebastian Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50823) Unable to download latest artifact from snapshot repository
Title: Message Title Eyal Ben Moshe commented on JENKINS-50823 Re: Unable to download latest artifact from snapshot repository When using File Specs to download artifacts, the pattern defined in the File Spec is translated into AQL to fetch the list of artifacts. The artifacts are then downloaded one by one. Maven's snapshot convention is supported by Artifactory, but only for maven builds. We are planning to enhance the File Specs schema with new sort-by, sort-order and limit properties. These properties are already supported by JFrog CLI. This will allow downloading, among other things, the latest published artifact, which matchers the pattern. 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-50899) JEP-200 compatibility
Title: Message Title Oleg Nenashev commented on JENKINS-50899 Re: JEP-200 compatibility It duplicates JENKINS-50216, fix is pending 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-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title
ritica r updated an issue
Jenkins / JENKINS-50605
Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Change By:
ritica r
{{Jenkins}} version 2. 114 117 (upgraded from 2.107.1 to try to resolve issue) is running builds but they seem to disappear from the Dashboard after a restart. I have Jenkins setup on {{Linux}} and all the log is present under {{$\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds}}I have tried Reload Configuration from Disk with following set in {{/etc/sysconfig/jenkins}}\{\{JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true }}Below is build and workspace directory settings:Workspace Root Directory :$\{JENKINS_HOME}/workspace/$\{ITEM_FULL_NAME}Build Record Root Directory: $\{ITEM_ROOTDIR}/buildsBelow you can see the build number 117 and 118 for one of my jobs, but still, the lastFailedBuild, lastStableBuild , lastSuccessfulBuild are set to -1, which doesn't existdrwxr-xr-x 4 jenkins jenkins 4096 Apr 2 20:17 117 drwxr-xr-x 4 jenkins jenkins 4096 Apr 3 20:17 118 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 11:09 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 10:44 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 03:21 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnsuccessfulBuild -> -1 I have also set the{{Discard Old Builds Slicer - Days to keep artifacts as 30 Discard Old Builds Slicer - Max # of builds to keep as 40}}I ran the jenkins-job-checker[ [https://github.com/docwhat/jenkins-job-checker] ] on one of the jobs and found the following : Problem: NOTLINK: The number link builds/1 is not a symlink! Problem: NOTLINK: The number link builds/2 is not a symlink! Problem: NOTLINK: The number link builds/3 is not a symlink! Proposal: Archive non-link builds/1 Proposal: Archive non-link builds/2 {{Proposal: Archive non-link builds/3}} Really appreaciate some help
Add Comment
[JIRA] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title ritica r updated an issue Jenkins / JENKINS-50605 Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server Change By: ritica r Environment: Jenkins on Linux ver 2. 114 117 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-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title ritica r updated an issue Jenkins / JENKINS-50605 Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server Change By: ritica r Priority: Critical Blocker 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.
