[JIRA] (JENKINS-53337) Empty entry in "add build step" list in job configuration
Title: Message Title Daniel Gront commented on JENKINS-53337 Re: Empty entry in "add build step" list in job configuration diewu qin, are you positive those are added after the plugin is 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-53050) Empty "depth" parameter for shallow cloning is not handled correctly
Title: Message Title René Scheibe updated JENKINS-53050 resolved with https://github.com/jenkinsci/git-plugin/pull/614 Jenkins / JENKINS-53050 Empty "depth" parameter for shallow cloning is not handled correctly Change By: René Scheibe Status: In Progress Fixed but Unreleased Assignee: René Scheibe 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-53383) [Octane UFT integration] Create function that converts the testToRun to a parameter of a job
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-53383 [Octane UFT integration] Create function that converts the testToRun to a parameter of a job Change By: Radi Berkovich we will create builder that will allow converting tests in raw format from octane - to be converted to appropriate format I In first stage we will support convertion to UFT and JUnit formats 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-53383) [Octane UFT integration] Create function that converts the testToRun to a parameter of a job
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-53383 [Octane UFT integration] Create function that converts the testToRun to a parameter of a job Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-09-03 04:10 Priority: Minor Reporter: Radi Berkovich we will create builder that will allow converting tests in raw format from octane - to be converted to appropriate format I first stage we will support convertion to UFT and JUnit formats Add Comment
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered actually, the upstream log eventually shows the downstream triggers, but it took about 40min :( after the completion. Will do more test to find the pattern 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered the delay is real 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-52215) Jenkins authentication issue with Azure ADDS
Title: Message Title Jie Shen commented on JENKINS-52215 Re: Jenkins authentication issue with Azure ADDS Badal Kotecha also writes an awesome blog on how to use Azure-ad-plugin. You can get it from here . Thanks again for his great contribution! 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-53382) Add option to trigger downstream even when current upstream's parent is active
Title: Message Title dan tran assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-53382 Add option to trigger downstream even when current upstream's parent is active Change By: dan tran Assignee: Alvaro Lobato Cyrille Le Clerc 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-53382) Add option to trigger downstream even when current upstream's parent is active
Title: Message Title dan tran created an issue Jenkins / JENKINS-53382 Add option to trigger downstream even when current upstream's parent is active Issue Type: New Feature Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-09-03 00:28 Priority: Major Reporter: dan tran initial discussion is at https://groups.google.com/forum/#!searchin/jenkinsci-users/dan$20tran%7Csort:date/jenkinsci-users/BcT_mSkxvE4/QyvYwsMKDAAJ Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-52856) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Mark Waite updated JENKINS-52856 Resolved the warning about anonymous class serialization in git client plugin 3.0.0beta4. Cannot duplicate the "Unable to serialize" failure. Jenkins / JENKINS-52856 Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Change By: Mark Waite Status: Open 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-52856) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Mark Waite updated JENKINS-52856 Jenkins / JENKINS-52856 Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Change By: Mark Waite Status: Fixed but Unreleased Resolved 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-52856) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Mark Waite commented on JENKINS-52856 Re: Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Changes were made in git client plugin 3..0.0-beta4 which should resolve this issue (or at least will resolve the warning about serializing anonymous classes). 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-44526) "Poll Now" broken in transition from 2.46.2 to 2.46.3
Title: Message Title Mark Waite updated JENKINS-44526 Jenkins / JENKINS-44526 "Poll Now" broken in transition from 2.46.2 to 2.46.3 Change By: Mark Waite 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-44526) "Poll Now" broken in transition from 2.46.2 to 2.46.3
Title: Message Title Mark Waite updated JENKINS-44526 Jenkins / JENKINS-44526 "Poll Now" broken in transition from 2.46.2 to 2.46.3 Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered don't see anything obvious at both build actually, the upstream log eventually shows the downstream triggers , jenkins but it took about 40min :( logs after the completion . will need some time Will do more test to find a consistent the pattern 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered don't see anything obvious at both build log, jenkins logs. will need some time to find a consistent pattern 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-52641) Implemtation Hubot
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-52641 Implemtation Hubot Change By: Naresh Rayapati Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered > sorry, the trigger is intermittent. I forced another upstream build and here is the end of upstream log Are there any messages in the logs of the build or in Jenkins logs? I would expect a stacktrace in the logs > I have about 300 Ack, it's way beyond what I anticipated for this feature. I am not aware of technical limitation, the UI is definitively not thought for such number. I'll discuss with colleagues of the multi Cause design. 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending end of upstream log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelinesdont even see Finished: SUCCESS 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checks out upstream source tree and run maven clean install. This has a large log entry of at upstream log since this downstream builds the same set of dependencies at upstream * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile profil both downstream jobs shows lots of upstream trigger entries for many maven gav 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered yes, i see the same screen shot you posted . I have about 300 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered yes, i see the same screen shot you posted 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelinesdont event even see Finished: SUCCESS 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelines dont event see Finished: SUCCESS 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-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title Cyrille Le Clerc closed an issue as Cannot Reproduce Closing as cannot reproduce. Please reopen a bug if needeed Jenkins / JENKINS-51232 Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files. Change By: Cyrille Le Clerc Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc started work on JENKINS-51404 Change By: Cyrille Le Clerc 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-51680) Infinity Build Loop
Title: Message Title Cyrille Le Clerc updated JENKINS-51680 Jenkins / JENKINS-51680 Infinity Build Loop Change By: Cyrille Le Clerc 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-51680) Infinity Build Loop
Title: Message Title Cyrille Le Clerc started work on JENKINS-51680 Change By: Cyrille Le Clerc 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-51953) Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger
Title: Message Title Cyrille Le Clerc started work on JENKINS-51953 Change By: Cyrille Le Clerc 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-51953) Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger
Title: Message Title Cyrille Le Clerc commented on JENKINS-51953 Re: Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger Fixed in 3.5.12-beta-2 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered Fixed in 3.5.12-beta-2 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-51680) Infinity Build Loop
Title: Message Title Cyrille Le Clerc commented on JENKINS-51680 Re: Infinity Build Loop Fixed in 3.5.12-beta-2 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-51953) Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger
Title: Message Title Cyrille Le Clerc updated JENKINS-51953 Jenkins / JENKINS-51953 Better pipeline Upstream Cause with details of the Maven artifact that caused the trigger Change By: Cyrille Le Clerc 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-53380) Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies
Title: Message Title Cyrille Le Clerc commented on JENKINS-53380 Re: Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies Fixed in 3.5.12-beta-2 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc started work on JENKINS-53148 Change By: Cyrille Le Clerc 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-53380) Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies
Title: Message Title Cyrille Le Clerc updated JENKINS-53380 Jenkins / JENKINS-53380 Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies Change By: Cyrille Le Clerc 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-53380) Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies
Title: Message Title Cyrille Le Clerc started work on JENKINS-53380 Change By: Cyrille Le Clerc 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc updated JENKINS-53148 Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc 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-52657) [withMaven] IllegalArgumentException: Cannot relativize relatively to
Title: Message Title Cyrille Le Clerc started work on JENKINS-52657 Change By: Cyrille Le Clerc 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran thanks for the good news. Regarding the rendering problem, can you confirm that your problem is similar to the attached screenshot? How many dependencies do you have listed as cause? 5? 10? 50? 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc Attachment: pipeline-maven-plugin-1-cause-per-dependency.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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checkout checks out upstream source tree and run maven clean install to ensure . This has a large log entry of at upstream log since this downstream builds the same set of dependencies at upstream * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile both downstream jobs shows lots of upstream trigger entries for many maven gav 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checkout upstream source tree and run maven clean install to ensure * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile both downstream jobs shows lots of upstream trigger entries for many maven gav 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-53110) Incorporate the version of the backend container into the homepage
Title: Message Title Baptiste Mathus commented on JENKINS-53110 Re: Incorporate the version of the backend container into the homepage \o/ 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now show shows entries of the next job jobs , with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of second item, it is just too verbose 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose ? 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-53381) Evergreen backend should embed the SHA of the build to help assess its version
Title: Message Title R. Tyler Croy closed an issue as Duplicate Jenkins / JENKINS-53381 Evergreen backend should embed the SHA of the build to help assess its version Change By: R. Tyler Croy Status: Open Closed Resolution: Duplicate 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it works, the upstream log now show entries of the next job, with a long list of maven dependencies 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-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Rafael Pestano updated JENKINS-51762 Jenkins / JENKINS-51762 NullPointerException in some jobs when listing last changes Change By: Rafael Pestano Status: Open 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-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Rafael Pestano updated JENKINS-51762 Jenkins / JENKINS-51762 NullPointerException in some jobs when listing last changes Change By: Rafael Pestano 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-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Rafael Pestano commented on JENKINS-51762 Re: NullPointerException in some jobs when listing last changes Thank you for the feedback Emil Wypych. 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-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Dominik Bartholdi commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin Nicolas De Loof the plugin is now up to Java8, but I'm not sure about the PersistedList - I need a bit of time to investigate this, Its a while ago since I changed that implementation to what it is now and I remember there where many issues about it. But there is already an Getter: org.jenkinsci.plugins.configfiles.GlobalConfigFiles#getConfigs() - ist this OK, do you only need a Setter in addition to this one? What about the config files on folders level? There is also a org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty which has about the same functionality as the GlobalConfigFiles, but can exist on each folder. Do you need the same there too? ...what 'component' are you talking about to add a '@Symbol'? - three are already two: configFileProvider -> org.jenkinsci.plugins.configfiles.buildwrapper.ConfigFileBuildWrapper.DescriptorImpl configFile -> org.jenkinsci.plugins.configfiles.buildwrapper.ManagedFile.DescriptorImpl 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-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Status: In Progress 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-53148 Re: downstream job nolonger triggered I [~dantran] can reproduce you please try https://github . I am working on it com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.12-beta-2 ?The reasons why downstream pipelines are triggered or are not triggered are clearly explained in the build logs and are visible as build causeshttps://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.12-beta-2/pipeline-maven-3.5.12-beta-2.hpi 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-51928) Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Title: Message Title
Amir Barkal commented on JENKINS-51928
Re: Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Another simple reproduction of the timeout() step not throwing an exception:
node() {
try {
timeout(time: 3 as Integer, unit: 'SECONDS') {
int result = sh(returnStatus: true, script:'sleep 5')
}
}
catch(e) {
println "TIMEOUT" // Will never get here
throw e
}
}
Env details: Jenkins 2.138 workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {code :java }node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }}catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:{code}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5')} } catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:{code}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }}catch(e) { println "TIMEOUT" // Will never get here throw e }}{code} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: { quote code } node() { try{ {quote} {quote} timeout(time : 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus: true, script:'sleep 5') }} catch(e) { {quote} {quote} println "TIMEOUT" // will Will never get here ! throw e } } { quote code } Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {quote}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') {quote} {quote} int result = sh timeout ( returnStatus time }} catch(e) { {quote} Unknown macro: \ { quote} println "TIMEOUT" // will never get here! throw e }} {quote} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal edited a comment on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception: {quote}node() { try { timeout(time: 3 as Integer, unit: 'SECONDS') { int result = sh(returnStatus : true, script: 'sleep 5') } }catch(e) { Unknown macro: \{ println "TIMEOUT" // will never get here! throw e }}{quote} Env details:Jenkins [2.138|https://jenkins.io/]workflow-basic-steps 2.9
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-40839) pipeline timeout doesn't kill the job
Title: Message Title
Amir Barkal commented on JENKINS-40839
Re: pipeline timeout doesn't kill the job
Another simple reproduction of the timeout() step not throwing an exception:
node() { try { timeout(time: 3 as Integer, unit: 'SECONDS')
Unknown macro: { int result = sh(returnStatus}
} catch(e)
Unknown macro: { println "TIMEOUT" // will never get here! throw e }
}
Env details: Jenkins 2.138 workflow-basic-steps 2.9
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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered I can reproduce. I am working on 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-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title Baptiste Mathus commented on JENKINS-53345 Re: The evergreen UI constantly redirects to http:/// instead of http://:8080 Just adjusted the title, it's actually more cumbersome than what I described initially. This happens (almost?) after each save from the UI anywhere. 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-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53345 The evergreen UI constantly redirects to http:/// instead of http://:8080 Change By: Baptiste Mathus Summary: Log in page The evergreen UI constantly redirects to http:// localhost / instead of http:// localhost :8080 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-51762) NullPointerException in some jobs when listing last changes
Title: Message Title Emil Wypych commented on JENKINS-51762 Re: NullPointerException in some jobs when listing last changes Hi, Rafael Pestano - sorry, I had very crazy last days... I confirm that the problem has been solved after updating via the Update Center. Thank you very much! I checked many jobs and all work fine. There are no alarming logs, so I think you may close this 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-53381) Evergreen backend should embed the SHA of the build to help assess its version
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53381 Evergreen backend should embed the SHA of the build to help assess its version Change By: Baptiste Mathus As a developer, I want to have need a way to check the version that is deployed at https://evergreen.jenkins.io/To be able to know if I can expect features or bugs to be present yet or not---The version to be expected is described in the jenkins-infra hieradata: https://github.com/jenkins-infra/jenkins-infra/blob/staging/hieradata/common.yaml#L351 but it would be nice to have an easy in the app itself to check the version is actually the one we think. 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-53381) Evergreen backend should embed the SHA of the build to help assess its version
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53381 Evergreen backend should embed the SHA of the build to help assess its version Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-02 12:12 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus As a developer, I want to have a way to check the version that is deployed at https://evergreen.jenkins.io/ To be able to know if I can expect features or bugs to be present yet or not — The version to be expected is described in the jenkins-infra hieradata: https://github.com/jenkins-infra/jenkins-infra/blob/staging/hieradata/common.yaml#L351 but it would be nice to have an easy in the app itself to check the version is actually the one we think. Add Comment
[JIRA] (JENKINS-53374) file permissions are lost after unstashing on windows node
Title: Message Title
Nenad Miksa updated an issue
Jenkins / JENKINS-53374
file permissions are lost after unstashing on windows node
Change By:
Nenad Miksa
Consider the following script:{code:java}node( 'macos' ) { sh 'rm -rf *' sh 'echo "int main() { return 0; }" > test.cpp' sh 'mkdir bin && gcc test.cpp -o bin/test' sh "ls -l bin" stash name:'test', includes: "bin/*"}node( 'windows' ) {unstash 'test'stash name:'test2', includes: 'bin/*'}node( 'linux' ) { sh 'rm -rf *' unstash 'test2' sh "ls -l bin"}{code}It produces the following output:{code:java}Started by user Nenad MikšaRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] nodeRunning on macpro2 in /opt/jenkins/workspace/Test[Pipeline] {[Pipeline] sh[Test] Running shell script+ rm -rf bin test.cpp[Pipeline] sh[Test] Running shell script+ echo 'int main() { return 0; }'[Pipeline] sh[Test] Running shell script+ mkdir bin+ gcc test.cpp -o bin/test[Pipeline] sh[Test] Running shell script+ ls -l bintotal 16-rwxr-xr-x 1 pero staff 4248 Aug 31 20:40 test[Pipeline] stashStashed 1 file(s)[Pipeline] }[Pipeline] // node[Pipeline] nodeRunning on Jabba in C:\Jenkins\workspace\Test[Pipeline] {[Pipeline] unstash[Pipeline] stashStashed 1 file(s)[Pipeline] }[Pipeline] // node[Pipeline] nodeRunning on blade in /opt/jenkins/root/workspace/Test[Pipeline] {[Pipeline] sh[Test] Running shell script+ rm -rf test.sh[Pipeline] unstash[Pipeline] sh[Test] Running shell script+ ls -l bintotal 8-rw-r--r-- 1 jenkins users 4248 Aug 31 20:40 test[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}So, after unstashing the unix binary on windows node and stashing it back, it loses its unix file permissions. Since windows does not have unix file permissions, I would expect that on windows would treat all files in 777 mode, especially after stashing back. In case if you are wondering why is this important to me, here is the rationale:I use Jenkins to build Conan packages of my software. The binaries are first built on various nodes for various platforms (windows, linux, macos, android and ios) and after binaries for every platform have been built successfully, they are all collected on first available node using the stash/unstash mechanism and there they are packaged and uploaded to Conan repository.Due to this issue this causes for binaries that are built on unix nodes lose their file permissions if they are packaged on windows node. A possible workaround would be to enforce packaging on unix node or to perform some partial packaging on nodes that have created the binaries. As these workarounds work for me, I've set priority of this issue as "minor".
[JIRA] (JENKINS-53374) file permissions are lost after unstashing on windows node
Title: Message Title
Nenad Miksa updated an issue
Jenkins / JENKINS-53374
file permissions are lost after unstashing on windows node
Change By:
Nenad Miksa
Consider the following script:{code:java}node( 'macos' ) { sh 'rm -rf *' sh 'echo "int main() { return 0; }" > test.cpp' sh 'mkdir bin && gcc test.cpp -o bin/test' sh "ls -l bin" stash name:'test', includes: "bin/*"}node( 'windows' ) {unstash 'test'stash name:'test2', includes: 'bin/*'}node( 'linux' ) { sh 'rm -rf *' unstash 'test2' sh "ls -l bin"}{code}It produces the following output:{code:java}Started by user Nenad MikšaRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] nodeRunning on macpro2 in /opt/jenkins/workspace/Test[Pipeline] {[Pipeline] sh[Test] Running shell script+ rm -rf bin test.cpp[Pipeline] sh[Test] Running shell script+ echo 'int main() { return 0; }'[Pipeline] sh[Test] Running shell script+ mkdir bin+ gcc test.cpp -o bin/test[Pipeline] sh[Test] Running shell script+ ls -l bintotal 16-rwxr-xr-x 1 pero staff 4248 Aug 31 20:40 test[Pipeline] stashStashed 1 file(s)[Pipeline] }[Pipeline] // node[Pipeline] nodeRunning on Jabba in C:\Jenkins\workspace\Test[Pipeline] {[Pipeline] unstash[Pipeline] stashStashed 1 file(s)[Pipeline] }[Pipeline] // node[Pipeline] nodeRunning on blade in /opt/jenkins/root/workspace/Test[Pipeline] {[Pipeline] sh[Test] Running shell script+ rm -rf test.sh[Pipeline] unstash[Pipeline] sh[Test] Running shell script+ ls -l bintotal 8-rw-r--r-- 1 jenkins users 4248 Aug 31 20:40 test[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}So, after unstashing the unix binary on windows node and stashing it back, it loses its unix file permissions. Since windows does not have unix file permissions, I would expect that on windows would treat all files in 777 mode, especially after stashing back. In case if you are wondering why is this important to me, here is the rationale explanation :I use Jenkins to build Conan packages of my software. The binaries are first built on various nodes for various platforms (windows, linux, macos, android and ios) and after binaries for every platform have been built successfully, they are all collected on first available node using the stash/unstash mechanism and there they are packaged and uploaded to Conan repository.Due to this issue this causes for binaries that are built on unix nodes lose their file permissions if they are packaged on windows node. A possible workaround would be to enforce packaging on unix node or to perform some partial packaging on nodes that have created the binaries. As these workarounds work for me, I've set priority of this issue as "minor".
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it works, but this is what i see [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelines [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-1 » master#275 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-SNAPSHOT) ... [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-2 » master#976 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-20180902.102143-2087) ... [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-3 » master#1177 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-20180902.102219-2086) ... Finished: SUCCESS ie, only one maven GAV shows up ending with '...' 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-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: custom-to-junit.xsl 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-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: input.xsl 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-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: input.xsl 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-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Nikolas Falco updated JENKINS-53186 released in 2.2.4 Jenkins / JENKINS-53186 NUnit 2.x test cases with result Error are reported as Success Change By: Nikolas Falco Status: Fixed but Unreleased Resolved 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-53148) downstream job nolonger triggered
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-53148
Re: downstream job nolonger triggered
[~dantran] can you please try with the branch https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53380You will have this de-duplication. Message of downstream pipeline scheduling with multiple causes (i.e. dependencies) will look like{noformat}[withMaven] Scheduling downstream pipeline my-downstream-pipeline#62 due to dependency on \ com.example:my-jar:jar:0.7-SNAPSHOT(0.7-20180902.093122-80), \ com.example:my-other-jar:jar:0.7-SNAPSHOT(0.7-20180902.093137-80)...{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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran can you please try with the branch https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53380 You will have this de-duplication. Message of downstream pipeline scheduling with multiple causes (i.e. dependencies) will look like [withMaven] Scheduling downstream pipeline my-downstream-pipeline#62 due to dependency on com.example:my-jar:jar:0.7-SNAPSHOT(0.7-20180902.093122-80), com.example:my-other-jar:jar:0.7-SNAPSHOT(0.7-20180902.093137-80)... 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-53379) Source code not shown when using folders plugin
Title: Message Title Oleg Nenashev assigned an issue to Jeff Pearce Jenkins / JENKINS-53379 Source code not shown when using folders plugin Change By: Oleg Nenashev Assignee: Devin Nusbaum Jeff Pearce 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-53380) Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-53380 Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies Change By: Cyrille Le Clerc Summary: Trigger downstream pipelines only once when multiple generated artifacts of upstream are dependencies 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered my upstream job now has this type of log [withMaven] Scheduling downstream pipeline folder-x» project-x» repo-x » master#273 due to dependency on groupId:artifactid:type:version the list matches with upstream's Maven report's downstream job Perhaps you can detect this condition and trigger downstream job once? 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered I started another build with the latest source this plugin latest source . So what are you looking for from the 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered I started another build with the latest source this plugin. So what are you looking for from the 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-53380) Trigger downstream pipelines once when multiple generated artifacts of upstream are dependencies
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-53380 Trigger downstream pipelines once when multiple generated artifacts of upstream are dependencies Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-09-02 08:25 Priority: Major Reporter: Cyrille Le Clerc Trigger downstream pipelines once when multiple generated artifacts of upstream are dependencies Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-53378) Better message in build logs when the trigger of downstream pipeline is skipped
Title: Message Title Cyrille Le Clerc updated JENKINS-53378 Jenkins / JENKINS-53378 Better message in build logs when the trigger of downstream pipeline is skipped Change By: Cyrille Le Clerc 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-53378) Better message in build logs when the trigger of downstream pipeline is skipped
Title: Message Title Cyrille Le Clerc started work on JENKINS-53378 Change By: Cyrille Le Clerc 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-53148 Re: downstream job nolonger triggered [~dantran] can you try to reproduce with the improved message https://github.com/jenkinsci/pipeline-maven-plugin/commit/c65ec72a02a15ab5a1171d435fdb7af887207e18. You just have to build master branch. I suspect that you see multi triggers of some downstream pipelines because these downstream pipelines depend on multiple artifacts generated by your upstream pipeline.I will ASAP improve the trigger of downstream pipelines to replace multi-trigger of downstream pipelines when they depend on multiple dependencies by mono trigger with multi-causes. 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-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran can you try to reproduce with the improved message https://github.com/jenkinsci/pipeline-maven-plugin/commit/c65ec72a02a15ab5a1171d435fdb7af887207e18 I suspect that you see multi triggers of some downstream pipelines because these downstream pipelines depend on multiple artifacts generated by your upstream pipeline. I will ASAP improve the trigger of downstream pipelines to replace multi-trigger of downstream pipelines when they depend on multiple dependencies by mono trigger with multi-causes. 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-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it seems to me, the multiple trigger entries coming from all transitive dependencies found at the upstream's Maven report. The first one triggers a first downstream job, and then the rest follow up with another jobSo my private build , with the change at https://issues.jenkins-ci.org/browse/JENKINS-51953, solves my original issue, but introduce a new one a little less severe must fix 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-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it seems to me, the multiple trigger entries coming from all transitive dependencies found at the upstream's Maven report. The first one triggers a first downstream job, and then the rest follow up with another job So my private build solves my original issue, but introduce a new one a little less severe must fix 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-47227) failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.p
Title: Message Title Tapio Reijonen closed an issue as Fixed Jenkins / JENKINS-47227 failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.plugins.robot.RobotPublisher Change By: Tapio Reijonen Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
