[JIRA] (JENKINS-49943) memory issue (RAM)with jenkins server
Title: Message Title Kunal Jha created an issue Jenkins / JENKINS-49943 memory issue (RAM)with jenkins server Issue Type: Story Assignee: Rob Petti Attachments: jenkin.PNG Components: perforce-plugin Created: 2018-03-06 07:13 Priority: Critical Reporter: Kunal Jha Hi Team, i've using jenkins version 2.89.1 since last few months but i'm facing the memory utilization issue with the same as its keep increasing even we are not using server or no job is running. attaching few screenshot for same. Add Comment
[JIRA] (JENKINS-45634) Table action buttons hidden until hover
Title: Message Title Nicolae Pascu updated JENKINS-45634 Jenkins / JENKINS-45634 Table action buttons hidden until hover Change By: Nicolae Pascu 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Madhava Kulkarni commented on JENKINS-49196 Re: java.io.IOException: Premature EOF when shutdown CLI command is used Hi Emilio Escobar , I am not sure if you have provided the right jenkins name here(127.0.0.1), but I assume the reason for the error seems to be the client connection timeout set on the system(or a proxy, if there is one). At least this was true in my case. The proxy had a client timeout set to 1m. You can check that and reconfirm if this error is really not because of timeout. Best Regards, Madhav 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-48854) P4 sync code and display 'change' more than once.
Title: Message Title Shanghai Fu commented on JENKINS-48854 Re: P4 sync code and display 'change' more than once. Anyone meet the same issue? the same change report twice. 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-48854) P4 sync code and display 'change' more than once.
Title: Message Title Shanghai Fu updated an issue Jenkins / JENKINS-48854 P4 sync code and display 'change' more than once. Change By: Shanghai Fu Attachment: image-2018-03-06-14-25-27-880.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala updated an issue Jenkins / JENKINS-49942 Pending script approvals even though signatures are approved Change By: Aswini Vayyala Priority: Minor Major 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-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala updated an issue Jenkins / JENKINS-49942 Pending script approvals even though signatures are approved Change By: Aswini Vayyala I have a function that updates a file on master. The pipeline fails when this function is executed on an agent with multipleCompilationErrors and the logs report unsigned signatures errors.As attached, even though the signatures are approved, the errors show that the signatures are still pending every time the pipeline is run. I have another jenkins instance with same 2.89.4 but script-security version is 1.33 and the function works as expected in that combination. Please help me resolve this issue on the first setup . 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,
[JIRA] (JENKINS-49941) IE stage name cut off
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 IE stage name cut off Change By: Jared Kauppila Summary: Allow for longer IE stage names name cut off 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49941) Allow for longer stage names
Title: Message Title Jared Kauppila commented on JENKINS-49941 Re: Allow for longer stage names Actually, it looks like that's just an IE 11 browser (11.953.14393.0) display bug, looking at the same BlueOcean view in Chrome (64.0.3282.186) gets me the following: 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Priority: Minor Trivial 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-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala updated an issue Jenkins / JENKINS-49942 Pending script approvals even though signatures are approved Change By: Aswini Vayyala Labels: security 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Attachment: image-2018-03-05-23-32-28-487.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Attachment: image-2018-03-05-23-31-53-888.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala created an issue Jenkins / JENKINS-49942 Pending script approvals even though signatures are approved Issue Type: Bug Assignee: Oliver Gondža Attachments: Screen Shot 2018-03-06 at 4.22.14 pm.png, Screen Shot 2018-03-06 at 4.23.31 pm.png Components: permissive-script-security-plugin, script-security-plugin Created: 2018-03-06 05:31 Environment: Jenkins 2.89.4 Script Security Plugin 1.41 Permissive Script Security Plugin 0.3 Priority: Minor Reporter: Aswini Vayyala I have a function that updates a file on master. The pipeline fails when this function is executed on an agent with multipleCompilationErrors and the logs report unsigned signatures errors. As attached, even though the signatures are approved, the errors show that the signatures are still pending every time the pipeline is run. I have another jenkins instance with same 2.89.4 but script-security version is 1.33 and the function works as expected in that combination. Please help me resolve this issue on the first setup
[JIRA] (JENKINS-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Attachment: image-2018-03-05-23-31-53-888.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48274) Saving to Github/GHE requires email with user or it fails
Title: Message Title Ivan Meredith updated JENKINS-48274 Jenkins / JENKINS-48274 Saving to Github/GHE requires email with user or it fails Change By: Ivan Meredith 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila It would be great if the Blueocean view could handle longer stage names.This is what we see in the Stage View:!image-2018-03-05-21-09-17-909.png|width=1251,height=200!And this is what we see with BlueOcean:!image-2018-03-05-21-09-48-698.png|width=1057,height=224!While I could shorten up the stage names a bit, it still doesn't leave a whole lot of room to play around with. This is just a snippet of a much larger pipeline. 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila It would be great if the Blueocean view could handle longer stage names.This is what we see in the Stage View:!image-2018-03-05-21-09-17-909.png |width=1251,height=200 !And this is what we see with BlueOcean:!image-2018-03-05-21-09-48-698.png |width=1057,height=224 !While I could shorten up the stage names a bit, it still doesn't leave a whole lot of room to play around with. This is just a snippet of a much larger pipeline. 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila updated an issue Jenkins / JENKINS-49941 Allow for longer stage names Change By: Jared Kauppila Attachment: long-stage-name-Jenkinsfile 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila commented on JENKINS-49941 Re: Allow for longer stage names Attached the Jenkinsfile for this example. 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-49941) Allow for longer stage names
Title: Message Title Jared Kauppila created an issue Jenkins / JENKINS-49941 Allow for longer stage names Issue Type: Improvement Assignee: Unassigned Attachments: image-2018-03-05-21-09-17-909.png, image-2018-03-05-21-09-48-698.png Components: blueocean-plugin Created: 2018-03-06 03:11 Environment: Windows Server 2012R2 Jenkins 2.89.4 Blue Ocean 1.4.2 Priority: Minor Reporter: Jared Kauppila It would be great if the Blueocean view could handle longer stage names. This is what we see in the Stage View: And this is what we see with BlueOcean: While I could shorten up the stage names a bit, it still doesn't leave a whole lot of room to play around with. This is just a snippet of a much larger pipeline. Add Comment
[JIRA] (JENKINS-41074) UX Issue with Polling in Multibranch Pipeline
Title: Message Title
Justin Vallon commented on JENKINS-41074
Re: UX Issue with Polling in Multibranch Pipeline
Jesse Glick: I am trying to get github/repoA/Jenkinsfile to use github/repoB. The sample code that you provided works (polling, on a schedule). Is it possible to get it to work on-push for rebuild of repoA when repoB is pushed? When I use pollSCM("# on push"), nothing happens (either on push or at any later point). I am guessing that the $Jenkins/github-webhook is not triggering the immediate pollSCM? If I use githubPush() trigger, it double-triggers the main-repo (sometimes the builds are coalesced, sometimes not if concurrent builds are allowed); but I think this ticket implies that the githubPush() trigger should not be used in org/repo/branch jobs. Alternately, I suppose I could add upstream-downstream relationships, but I have been trying to keep the triggers based on SCM vs jobs. Note though that my Jenkins is at 2.60.1, and GitHub Branch Source 2.0.7 (a few months old), so maybe I should try upgrading, but it is probably my expectation that is wrong (user error, not a bug).
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44541) Test Results Analyzer plugin 500 Internal Error
Title: Message Title thoni56 edited a comment on JENKINS-44541 Re: Test Results Analyzer plugin 500 Internal Error I have this too. Jenkins 2.109 and Test Result Analyzer 0.3.4. I get a 502. EDIT: I increased the memory for Jenkins (in jenkins.xml) and now 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-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Josh McDonald started work on JENKINS-49929 Change By: Josh McDonald 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-47247) Allow roundtrip editing for http/https repositories
Title: Message Title Josh McDonald stopped work on JENKINS-47247 Change By: Josh McDonald 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-49940) Concurrent build limits not honored on kubernetes container environment with Jenkins 2.89.4
Title: Message Title Akshay Chaknalwar commented on JENKINS-49940 Re: Concurrent build limits not honored on kubernetes container environment with Jenkins 2.89.4 Tried following scenario Set limit to 3 for concurrent jobs Started 6 jobs at once 3 jobs started and 3 jobs were in queue As soon as 2 jobs from currently running jobs completed, 3 remaining jobs started and total current jobs are 4 now. Expected was to start only 1 job from queue Started provisioning Kubernetes Pod Template from k8s with 1 executors. Remaining excess workload: 1.97 Mar 05, 2018 11:27:02 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl apply Started provisioning Kubernetes Pod Template from k8s with 1 executors. Remaining excess workload: 0.97 Mar 05, 2018 11:27:02 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl apply Started provisioning Kubernetes Pod Template from k8s with 1 executors. Remaining excess workload: -0.03 Mar 05, 2018 11:27:13 PM INFO hudson.slaves.NodeProvisioner$2 run Kubernetes Pod Template provisioning successfully completed. We have now 4 computer(s) Mar 05, 2018 11:27:13 PM INFO hudson.slaves.NodeProvisioner$2 run Kubernetes Pod Template provisioning successfully completed. We have now 5 computer(s) Mar 05, 2018 11:27:13 PM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect qa-testslave9 Mar 05, 2018 11:27:13 PM INFO hudson.slaves.NodeProvisioner$2 run Kubernetes Pod Template provisioning successfully completed. We have now 6 computer(s) Mar 05, 2018 11:27:13 PM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision Excess workload after pending Kubernetes agents: 0 Add Comment
[JIRA] (JENKINS-47744) xcodebuild export step fails due to empty exportPlist
Title: Message Title Tony Ru commented on JENKINS-47744 Re: xcodebuild export step fails due to empty exportPlist We also have this problem but I found out that in the github repository the exportOptions.plist is already updated with new needed fields ... months ago ... but I wonder why the changes becomes not deployed? Is it possible to build the plugin manually? See this commit: https://github.com/jenkinsci/xcode-plugin/commit/3937e54f3c0a761528e038668471ef65a545aa99 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-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container I think I have found a solution for this - we can use override the computer getEnvironment to drop the computer level properties(JAVA_HOME, etc) and use the built in variables without issue. This would avoid the need for workarounds. 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-49896) Support integration-test goal for the Invoker Publisher
Title: Message Title Cyrille Le Clerc commented on JENKINS-49896 Re: Support integration-test goal for the Invoker Publisher We should try to mimic what we have done in org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher handling both "maven-surefire-plugin:test" and "maven-failsafe-plugin:integration-test". See https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.3.2/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher.java 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-49898) Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
Title: Message Title
Cyrille Le Clerc commented on JENKINS-49898
Re: Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
benoit guerin Do you see a risk to assume that, for any value that is not an absolute path, we can prepend with ${basedir}? I didn't find examples in your commit (here). Do you have a sample of that you use in your projects?
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-49940) Concurrent build limits not honored on kubernetes container environment with Jenkins 2.89.4
Title: Message Title Akshay Chaknalwar created an issue Jenkins / JENKINS-49940 Concurrent build limits not honored on kubernetes container environment with Jenkins 2.89.4 Issue Type: Bug Assignee: Unassigned Components: throttle-concurrent-builds-plugin Created: 2018-03-05 22:58 Environment: Jenkins : 2.89.4 Throttle Concurrent Builds : 2.0.1 Kubernetes : 1.3.1 Priority: Critical Reporter: Akshay Chaknalwar After upgrading to Jenkins to 2.89.4 we noticed the throttle plugin 2.0.1 doesn't always prevent jobs from running in parallel as expected. Steps to reproduce: 1. Create a Throttle category with Maximum Total Concurrent Builds -> 0 Maximum Concurrent Builds Per Node -> 3 Maximum Concurrent Builds Per Node Labeled As Above -> 3. 2. Created Kubernetes Pod Template with Max number of instances -> 3 Container Cap -> 3 3. Create 3 jobs using the category, restricted to a node with two executors 4. Request builds of all 3 jobs. What should happen: 4. Jobs run in sequence; 1 then 2 then 3. What actually happens: 5. Job 1 starts building, jobs 2 and 3 wait in queue (OK). 6. After job 1 finishes, both job 2 and 3 start running (not OK). Setup Details: Jenkins : 2.89.4 Throttle Concurrent Builds : 2.0.1 Kubernetes : 1.3.1
[JIRA] (JENKINS-44430) p4 authenticity of 'perforce:1666' can't be established
Title: Message Title Alister Hatt edited a comment on JENKINS-44430 Re: p4 authenticity of 'perforce:1666' can't be established [~p4paul] We've been running this change into in our Jenkins instance for about a week and so far haven't seen the p4trust issue, so looking good! 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-44430) p4 authenticity of 'perforce:1666' can't be established
Title: Message Title Alister Hatt commented on JENKINS-44430 Re: p4 authenticity of 'perforce:1666' can't be established Paul Allen We've been running this change into our Jenkins instance for about a week and so far haven't seen the p4trust issue, so looking good! 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-49896) Support integration-test goal for the Invoker Publisher
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49896 Support integration-test goal for the Invoker Publisher Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49632 Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/jobMain.jelly http://jenkins-ci.org/commit/pipeline-maven-plugin/abcb33aa751790affd26ccecf32e25c99c4f8397 Log: JENKINS-49632 uncomment the code 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-46809) Allow sequencial stages inside parallel in Declarative syntax
Title: Message Title Andrew Bayer commented on JENKINS-46809 Re: Allow sequencial stages inside parallel in Declarative syntax Before anyone gets too excited, this isn't actually merged yet - I just pushed to a branch in the main repo so that JENKINS-45455's PR and someone's work-in-progress on matrix syntax can target that branch directly. 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-47950) 0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException
Title: Message Title Gibson Fahnestock reopened an issue I have now reproduced with OpenJDK 8 openjdk version "1.8.0_161" OpenJDK Runtime Environment (build 1.8.0_161-b14) OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode) so I think this is an actual issue with this update. Jenkins / JENKINS-47950 0.28.1 update breaks GHE auth - javax.net.ssl.SSLHandshakeException Change By: Gibson Fahnestock Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-46809) Allow sequencial stages inside parallel in Declarative syntax
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46809 Re: Allow sequencial stages inside parallel in Declarative syntax Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/RuntimeASTTransformer.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeUpgradeTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/EnvironmentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/PostStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ToolsTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ExecuteConvertedTest.java pipeline-model-definition/src/test/resources/agentOnGroup.groovy pipeline-model-definition/src/test/resources/environmentInGroup.groovy pipeline-model-definition/src/test/resources/errors/emptyStagesInGroup.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/topLevelStageGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/json/agentOnGroup.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/topLevelStageGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/parallelStagesGroupsAndStages.json pipeline-model-definition/src/test/resources/json/topLevelStageGroup.json
[JIRA] (JENKINS-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Devin Nusbaum updated JENKINS-49906 Jenkins / JENKINS-49906 Form validation considers the rename "no op" to be an error Change By: Devin Nusbaum 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-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Devin Nusbaum started work on JENKINS-49906 Change By: Devin Nusbaum 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Stephen Connolly commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1163-L1218 matches PR-... https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1219-L1226 matches branches https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1227-L1254 matches tags 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Stephen Connolly commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries The only issue with using GitHub Branch Source is that you cannot checkout shared libraries by hash as https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java#L782-L804 does not implement hash resolution. 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Stephen Connolly commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
If you want to checkout pull requests, why are you using Git for the pipeline shared library... Something like: Should allow checking out the shared library by PR, e.g. library("PSL@pr-111") should checkout the PR.
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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-48061 git plugin 3.6.4 regression with shared libraries Change By: Stephen Connolly Attachment: Screen Shot 2018-03-05 at 21.58.01.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Zviki K reopened an issue Node and label plug-in 1.7.3 is not released yet. Jenkins / JENKINS-38105 Fail to set reference parameters with different type of drop down list Change By: Zviki K 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
[JIRA] (JENKINS-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Zviki K commented on JENKINS-38105 Re: Fail to set reference parameters with different type of drop down list The problem still exists. How can I take and create my own plug-in from the sources, I need to work with slaves and active choice plug-in? 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-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title Ivan Meredith commented on JENKINS-48027 Re: Blue Ocean dashboard showing no Pipelines Might have to implement that rawEncode on the client side. And pray that it doesnt break other things 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-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title Ivan Meredith started work on JENKINS-48027 Change By: Ivan Meredith 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-49939) Validation of Dry Parsers is broken in Snippet Generator
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-49939 Validation of Dry Parsers is broken in Snippet Generator Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-05 22:09 Priority: Minor Reporter: Ulli Hafner 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
[JIRA] (JENKINS-49895) When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-49895
When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Change By:
Cyrille Le Clerc
Failure to retrieve any file in build workspace when When "withMaven" is invoked in a "dir('my-folder ' ) \ {...}" step .The cause is that "withMaven" makes a mistake using {{StepContext#get(FilePath.class)}} to get the "build.workspace" when {{StepContext#get(FilePath.class)}} is changed when running inside a "{{dir( , it cannot retrieve files located outside of 'my-folder' )\{ . ..}}}" step. {code:java}node { dir('sub-folder') { // calls to StepContext#get(FilePath.class) returns "$buildWorkspace/sub-folder" withMaven() { sh "mvn verify" // withMaven will be confused because it will assume the the root folder cannot retrieve files located outside of the build workspace is"$buildWorkspace/ ' sub-folder " ', even if a Maven reactor produced some files elsewhere } }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49938) Check that steps are compatible with Declarative Pipeline
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-49938 Check that steps are compatible with Declarative Pipeline Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-05 22:08 Priority: Minor Reporter: Ulli Hafner 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
[JIRA] (JENKINS-49895) When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Title: Message Title
Cyrille Le Clerc closed an issue as Not A Defect
Jenkins / JENKINS-49895
When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Change By:
Cyrille Le Clerc
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 this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49895) When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-49895
When "withMaven" is invoked in a "dir('my-folder'){...}" step, it cannot retrieve files located outside of 'my-folder'
Change By:
Cyrille Le Clerc
Summary:
Failure to retrieve files in build workspace when When "withMaven" is invoked in a "dir('my-folder ' ){...}" step , it cannot retrieve files located outside of 'my-folder'
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-49536) java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory
Title: Message Title Cyrille Le Clerc closed an issue as Not A Defect Jenkins / JENKINS-49536 java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory Change By: Cyrille Le Clerc 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 this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49536) java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory
Title: Message Title
Cyrille Le Clerc commented on JENKINS-49536
Re: java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory
Mirko Streckenbach I synced up with Jesse Glick. When "withMaven(){...}" is executing in a "dir('my-sub-folder'){...}", it cannot see the files located outside of "my-sub-folder". The recommended approach, if your Maven pom.xml file is not located in the root folder of your Maven reactor, is to run the "mvn" call from the root folder of your Maven reactor specifying the path of your Maven pom.xml using the "--file" argument. Sample
node {
dir("my-maven-reactor-root-folder") {
withMaven() {
sh "mvn --file path/to/pom.xml clean verify"
}
}
}
Not that the step "dir('my-sub-folder'){...}" and "withMaven(){...}" can be switched around.
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-49937) Bundle JS libraries into the plug-in (or use a JS dependency)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-49937 Bundle JS libraries into the plug-in (or use a JS dependency) Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-05 22:01 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-49933) Getting stack trace after poll scm(****)
Title: Message Title Mark Waite resolved as Not A Defect Jenkins / JENKINS-49933 Getting stack trace after poll scm() Change By: Mark Waite 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-49536) java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49536 java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-49895) Failure to retrieve files in build workspace when "withMaven" is invoked in a "dir('my-folder){...}" step
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-49895
Failure to retrieve files in build workspace when "withMaven" is invoked in a "dir('my-folder){...}" step
Change By:
Cyrille Le Clerc
Summary:
Failure to retrieve any file files in build workspace when "withMaven" is invoked in a "dir('my-folder){...}" step
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49895) Failure to retrieve any file in build workspace when "withMaven" is invoked in a "dir('my-folder){...}" step
Title: Message Title
Jesse Glick commented on JENKINS-49895
Re: Failure to retrieve any file in build workspace when "withMaven" is invoked in a "dir('my-folder){...}" step
As designed. Not sure what exactly you think the bug is.
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-49936) Support for uno-choice plugin sandboxing feature
Title: Message Title Timo Naroska commented on JENKINS-49936 Re: Support for uno-choice plugin sandboxing feature Patch is available here: https://github.com/jenkinsci/job-dsl-plugin/pull/1110 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-49898) Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49898 Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-49842) Publish jenkins/evergreen docker image
Title: Message Title R. Tyler Croy started work on JENKINS-49842 Change By: R. Tyler Croy 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-49936) Support for uno-choice plugin sandboxing feature
Title: Message Title Timo Naroska created an issue Jenkins / JENKINS-49936 Support for uno-choice plugin sandboxing feature Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-03-05 21:22 Priority: Minor Reporter: Timo Naroska Add support for sandboxed script execution to activeChoiceParam, activeChoiceReactiveParam and activeChoiceReactiveReferenceParam elements. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49933) Getting stack trace after poll scm(****)
Title: Message Title harish nair commented on JENKINS-49933 Re: Getting stack trace after poll scm() great its working now, thanks Mark Waite Looks like it was the scheduling job format issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35422) Valgrind plugin failed to parse (String index out of range) for complex C++ trace.
Title: Message Title Ian Norton edited a comment on JENKINS-35422 Re: Valgrind plugin failed to parse (String index out of range) for complex C++ trace. Is this the longest outstanding contributed bugfix in history? I fixed this when my son was still in primary school - https://github.com/jenkinsci/valgrind-plugin/pull/10 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-35422) Valgrind plugin failed to parse (String index out of range) for complex C++ trace.
Title: Message Title Ian Norton commented on JENKINS-35422 Re: Valgrind plugin failed to parse (String index out of range) for complex C++ trace. Is this the longest outstanding contributed bugfix in history? 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-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Daniel Beck commented on JENKINS-49906 Re: Form validation considers the rename "no op" to be an error Warning (or unstyled info) would be fine, but it needs to be more specific than "name already taken". "Please specify a different name than the current one" or similar perhaps. 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-49933) Getting stack trace after poll scm(****)
Title: Message Title Mark Waite commented on JENKINS-49933 Re: Getting stack trace after poll scm() That looks like a user error in the definition of the schedule. Refer to the online help for the allowed schedule formats. 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-44541) Test Results Analyzer plugin 500 Internal Error
Title: Message Title thoni56 commented on JENKINS-44541 Re: Test Results Analyzer plugin 500 Internal Error I have this too. Jenkins 2.109 and Test Result Analyzer 0.3.4. I get a 502. 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-49935) Console View links do not work
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-49935 Console View links do not work Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-05 21:09 Priority: Minor Reporter: Ulli Hafner When the maven parser is activated then the warnings view is broken. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49906) Form validation considers the rename "no op" to be an error
Title: Message Title Devin Nusbaum commented on JENKINS-49906 Re: Form validation considers the rename "no op" to be an error It feels wrong to me to not show a message or to have an info message if it causes an error during submission. Would you be ok with just changing it from an error to a warning, and making the message more specific, or do you feel strongly that there should be no warnings or errors when the page is opened? 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-49934) Add editor ATH coverage for reordering of steps in a pipeline
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-49934 Add editor ATH coverage for reordering of steps in a pipeline Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-03-05 20:59 Priority: Minor Reporter: Karl Shultz Summary: Reordering of steps within a stage, as described in JENKINS-38323 (a.k.a. "Drag and Drop"), is a useful new feature in the Pipeline editor. ATH tests which verify this functionality would be a welcome improvement to editor test coverage. Add Comment
[JIRA] (JENKINS-49658) One JCloud node type can starve another in Jenkins
Title: Message Title Darrel Vuncannon commented on JENKINS-49658 Re: One JCloud node type can starve another in Jenkins Hey Fritz Elfert, Andrew Bayer, and Vijay Kiran: Don't forget me, please. 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-49933) Getting stack trace after poll scm(****)
Title: Message Title harish nair created an issue Jenkins / JENKINS-49933 Getting stack trace after poll scm() Issue Type: Bug Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin Created: 2018-03-05 20:47 Environment: localhost:8080 Labels: scm Priority: Blocker Reporter: harish nair I am getting a stack trace after adding every minute build job() using poll scm. Please help. Stack trace line 1:2: unexpected token: * at hudson.scheduler.CrontabParser.term(CrontabParser.java:291) at hudson.scheduler.CrontabParser.expr(CrontabParser.java:180) at hudson.scheduler.CrontabParser.startRule(CrontabParser.java:58) at hudson.scheduler.CronTab.set(CronTab.java:118) at hudson.scheduler.CronTab.(CronTab.java:100) at hudson.scheduler.CronTabList.create(CronTabList.java:121) Caused: antlr.ANTLRException: Invalid input: "***" at hudson.scheduler.CronTabList.create(CronTabList.java:123) at hudson.scheduler.CronTabList.create(CronTabList.java:96) at hudson.triggers.Trigger.(Trigger.java:170) at hudson.triggers.SCMTrigger.(SCMTrigger.java:107) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) Caused: java.lang.IllegalArgumentException at
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47584 Result screen not refreshing with error "Cannot read property 'self' of undefined" Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.5 - beta 3 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-44195) Add timestamps to the log
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-44195 Add timestamps to the log Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47584 Result screen not refreshing with error "Cannot read property 'self' of undefined" Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44195) Add timestamps to the log
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-44195 Add timestamps to the log Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 3 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-49615) multibranchPipelineJob: add property strategy & script path options
Title: Message Title
Daniel Spilker commented on JENKINS-49615
Re: multibranchPipelineJob: add property strategy & script path options
All these options (and many more) are already supported by the Dynamic DSL:
multibranchPipelineJob('example-1') {
branchSources {
branchSource {
source {
git {
id('3d9bee85-412a-47ab-b081-541981dde14a')
remote('https://github.com/jenkinsci/job-dsl-plugin.git')
credentialsId('github-ci')
}
}
strategy {
defaultBranchPropertyStrategy {
props {
noTriggerBranchProperty()
}
}
}
}
}
}
multibranchPipelineJob('example-2') {
branchSources {
branchSource {
source {
git {
id('3d9bee85-412a-47ab-b081-541981dde14a')
remote('https://github.com/jenkinsci/job-dsl-plugin.git')
credentialsId('github-ci')
}
}
strategy {
namedExceptionsBranchPropertyStrategy {
defaultProperties {
noTriggerBranchProperty()
}
namedExceptions {
named {
name('master')
}
}
}
}
}
}
}
multibranchPipelineJob('example-3') {
branchSources {
branchSource {
source {
git {
id('3d9bee85-412a-47ab-b081-541981dde14a')
remote('https://github.com/jenkinsci/job-dsl-plugin.git')
credentialsId('github-ci')
}
}
}
}
factory {
workflowMultiBranchProjectFactory {
scriptPath('pipelines/entryPoint.groovy')
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49615) multibranchPipelineJob: add property strategy & script path options
Title: Message Title Daniel Spilker resolved as Fixed Jenkins / JENKINS-49615 multibranchPipelineJob: add property strategy & script path options Change By: Daniel Spilker Status: In Progress Resolved Assignee: matthew snoddy Daniel Spilker 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-49519) Limit the amount of analytics data being collected
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49519 Limit the amount of analytics data being collected Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 3 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-49519) Limit the amount of analytics data being collected
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49519 Limit the amount of analytics data being collected Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46571 Update URL scheme to remove URL encoding issues Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48524) Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48524 Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build. Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3 , Blue Ocean 1.5 - beta 3 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-46571) Update URL scheme to remove URL encoding issues
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46571 Update URL scheme to remove URL encoding issues Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 3 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-48524) Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48524 Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build. Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3 , Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48524) Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build.
Title: Message Title Vivek Pandey commented on JENKINS-48524 Re: Misc infrastructure errors are missing from step view. Blue ocean should default to showing a log tail at end of failed build. Michael Neale Tailing Jenkins log might not show the right error as it might be buried deep in the main jenkins log. Maybe if we have a way to associated failed FlowNode (stage/step/parallel-branch) with other system wide exception, such as failed stage and then associated exception stack trace in that stage/step log. Sam Van Oort is your log optimization touches on these areas or any suggestion on what blueocean can use from pipeline infra? 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-49798) Scan Organization Folder not detecting code changes
Title: Message Title Mark Waite commented on JENKINS-49798 Re: Scan Organization Folder not detecting code changes Unfortunately, I don't have any experience with Bitbucket webhooks. You might ask on the Internet Relay Chat channel or on the Jenkins Users mailing list. The number of people who read git plugin bug reports is much smaller than the number of people who read either of those channels. 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-49798) Scan Organization Folder not detecting code changes
Title: Message Title Kevin Ford commented on JENKINS-49798 Re: Scan Organization Folder not detecting code changes In my attempts, it appears that webhooks and Bitbucket team projects do not work together. Any advise to what i am missing 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Sam Van Oort commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters Assigned to Emilio Escobar because I think he has a fix already almost done for it. 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-35422) Valgrind plugin failed to parse (String index out of range) for complex C++ trace.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35422 Re: Valgrind plugin failed to parse (String index out of range) for complex C++ trace. Code changed in jenkins User: Ian Norton Path: src/test/resources/org/jenkinsci/plugins/valgrind/parser/simple.xml http://jenkins-ci.org/commit/valgrind-plugin/f20948a9594bd1f209ee70aebe48fe49c1230c79 Log: update parser test data wrt JENKINS-35422 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-49932) Add editor ATH coverage for changing an existing stage in a Jenkinsfile
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-49932
Add editor ATH coverage for changing an existing stage in a Jenkinsfile
Issue Type:
Improvement
Assignee:
Unassigned
Components:
blueocean-pipeline-editor-plugin
Created:
2018-03-05 19:10
Priority:
Minor
Reporter:
Karl Shultz
Summary: Changing an existing stage is an important feature available in the editor, but none of our existing tests cover this path. A simple ATH test (or even an addition to another, existing test) would be a nice coverage improvement. Ideas: An offline test could create a repository including an existing Jenkinsfile, stored in our resources directory, like we're doing here. This existing Jenkinsfile might include something like:
stage ("do-one-thing) {
echo "Do one thing"
}
which we could then use the editor to change into
stage ("do-two-things) {
echo "Do two things"
sh "netstat -a"
}
And then verify that we went from doing just one thing, to doing two things. The same test could delete a step as well:
stage ("back-to-one-thing) {
echo "back to doing only one thing"
}
[JIRA] (JENKINS-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-49928
Add editor ATH coverage for changing agent settings in a Jenkinsfile
Change By:
Karl Shultz
*Summary:*Making changes to build agent settings in a Jenkinsfile is an important feature available in the editor, but none of our existing tests cover this path. A simple ATH test (or even an addition to another, existing test) would be a nice coverage improement improvement .*Ideas:*An offline test could create a repository including an existing Jenkinsfile, stored in [our resources directory|https://github.com/jenkinsci/blueocean-plugin/tree/master/acceptance-tests/src/test/resources/io/blueocean/ath/offline], like we're doing [here|https://github.com/jenkinsci/blueocean-plugin/tree/master/acceptance-tests/src/test/resources/io/blueocean/ath/offline/multibranch/ParallelNavigationTest]. This existing Jenkinsfile might include something like:{code:none}agent {label ("linux")}{code}which we could then use the editor to change into {code:none}agent any{code}And then verify that the changes were made correctly.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-49931 Heap Histogram Collection Destabilizes Masters Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-03-05 19:08 Priority: Critical Reporter: Sam Van Oort When we added Heap Stats collection (https://issues.jenkins-ci.org/browse/JENKINS-22791) in v2.42 it appears that we inadvertently caused a major performance-stability regression if the histogram is collected regularly. How? Well, this gathers a live heap histogram. This appears to triggers a Full GC. This is visible in GC logs because they show the following cause: > [Full GC (Heap Inspection Initiated GC). Now, because this is a FullGC and not a concurrent or young-gen GC, and we're generally using G1 GC, the slow Serial garbage collector is used for FullGC. This is a NON-concurrent GC mode, meaning the application is fully paused until it completes, and it is SINGLE-threaded, meaning rather than 1 GB/s per CPU of GC throughput, we get <1 GB/s total. It also cleans and compacts the entire heap rather than just part of it as with other modes. So, with 15 GB of used heap that means a pause of up ~15s. This matches behavior observed in the wild. I am rating this as critical because on larger-scale production masters a hang that long can cause job failures, visible UI hangs, HTTP request timeouts, and other issues – it should result in Surable Task failures for Pipelines, for example. Proposed solution: only gather the live heap histogram when a user is explicitly requesting a support bundle (disable it by default).
[JIRA] (JENKINS-48562) Inline Environment Variables not replaced in config file
Title: Message Title Andrew Bayer commented on JENKINS-48562 Re: Inline Environment Variables not replaced in config file First, give it a try with just a Scripted Pipeline with the variables in withEnv - Declarative's environment just maps to withEnv behind the scenes. And then if it turns out that doesn't work either, we need to figure that 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-49930) Add editor ATH coverage for setting and changing environment variables
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-49930
Add editor ATH coverage for setting and changing environment variables
Issue Type:
Improvement
Assignee:
Unassigned
Components:
blueocean-pipeline-editor-plugin
Created:
2018-03-05 18:51
Priority:
Minor
Reporter:
Karl Shultz
Making changes to environment settings in a Jenkinsfile is an important feature available in the editor, but none of our existing tests cover this path. A simple ATH test (or even an addition to another, existing test) would be a nice coverage improvement. Ideas: An offline test could create a repository including an existing Jenkinsfile, stored in our resources directory, like we're doing here. This existing Jenkinsfile might include something like:
environment {
SOME_VARIABLE = "old-boring-setting"
}
which we could then use the editor to change into
environment {
SOME_VARIABLE = "new-awesome-setting"
NEW_VARIABLE = "another-new-thing"
}
And then verify that the changes were made correctly.
[JIRA] (JENKINS-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Vivek Pandey commented on JENKINS-49929 Re: Regression: Log fails to auto update in karaoke mode Josh McDonald something broke this behavior, PTAL. cc: Nicolae Pascu. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Vivek Pandey assigned an issue to Josh McDonald Jenkins / JENKINS-49929 Regression: Log fails to auto update in karaoke mode Change By: Vivek Pandey Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
