[JIRA] (JENKINS-42821) Include some plugin dev documentation
Title: Message Title Michael Neale started work on JENKINS-42821 Change By: Michael Neale 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-42857) Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable
Title: Message Title Andrew Bayer commented on JENKINS-42857 Re: Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable This is a dupe of JENKINS-42771, isn't 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-42870) Fragment remains part of the URL when navigating away from a build after showing full log of a build step
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42870 Fragment remains part of the URL when navigating away from a build after showing full log of a build step Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/17 3:51 AM Environment: OS X Firefox 45.8.0 BO b25 Priority: Minor Reporter: Daniel Beck When showing a build step's full log by clicking the link/button "Show full log", the following is added to the URL: ?start=0#step-35-log-0 This fragment remains part of the URL after 'closing' build build by pressing Esc. Add Comment
[JIRA] (JENKINS-42869) Navigating away from a build showing a very long 'full build log' freezes Firefox
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42869 Navigating away from a build showing a very long 'full build log' freezes Firefox Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/17 3:49 AM Environment: OS X Firefox 45.8.0 BO b25 Priority: Minor Reporter: Daniel Beck Firefox freezes for 10+ seconds when navigating away (by pressing Esc) from a build showing the full console output of a 1+ line build step. Examples of affected builds can be found here: https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fbackend-update-center2/activity/ Add Comment
[JIRA] (JENKINS-42868) The dropdown indicator for the branch filter looks like a wifi signal indicator
Title: Message Title
Daniel Beck created an issue
Jenkins / JENKINS-42868
The dropdown indicator for the branch filter looks like a wifi signal indicator
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2017-03-17 at 04.43.35.png, Screen Shot 2017-03-17 at 04.43.41.png
Components:
blueocean-plugin
Created:
2017/Mar/17 3:44 AM
Priority:
Minor
Reporter:
Daniel Beck
The dropdown indicator ("triangle") for the "Branch" column on the activity page looks like a stylized wifi signal indicator. Or a 'handle' indicator for a UI element that can be dragged/moved perhaps? What it doesn't look like is a dropdown indicator.
Add Comment
[JIRA] (JENKINS-42867) Repeatedly updating the branch filter to the same value creates browser navigatione entries
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42867 Repeatedly updating the branch filter to the same value creates browser navigatione entries Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/17 3:42 AM Priority: Minor Reporter: Daniel Beck The new filter for branch names on the 'activity' URL results in new browser navigation entries even if the URL doesn't change. Just repeatedly select the same PR from the dropdown (possibly by typing for autocompletion) and you can press "back" a lot before anything actually changes. Add Comment
[JIRA] (JENKINS-42866) Bogus line numbers shown for truncated output
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42866 Bogus line numbers shown for truncated output Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/17 3:41 AM Priority: Minor Reporter: Daniel Beck Completed builds with long build log output get truncated to only show the end. Nevertheless, BO shows line numbers for that output, starting at 1, when it's not in fact the first line of the build output of the step. Add Comment This message
[JIRA] (JENKINS-42865) 4+ digit line numbers for console output wrap when the related line wraps
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42865 4+ digit line numbers for console output wrap when the related line wraps Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/17 3:40 AM Priority: Minor Reporter: Daniel Beck When lines in a build log (shell script) are so long they get wrapped, then the line numbers also start getting wrapped from 4 or 5 digits. Can be seen e.g. in build logs to https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fbackend-update-center2/ Add Comment
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title James Dumay commented on JENKINS-41200 Re: Developer can see ANSI color in log file Prepare for imgur integration 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-41200) Developer can see ANSI color in log file
Title: Message Title Michael Neale commented on JENKINS-41200 Re: Developer can see ANSI color in log file It wil have MORE than ANSI colour. It will have so many colours, some that aren't even in the visible spectrum. More colour than you can handle! and tags should be supported. And animated gifs. 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay commented on JENKINS-42863 Re: Step that throws an error shows up as successful if error is caught later in the Jenkinsfile FYI Sam Van Oort something shifty is going on reporting a failure in this case. 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay edited a comment on JENKINS-42863 Re: Step that throws an error shows up as successful if error is caught later in the Jenkinsfile FYI [~svanoort] something shifty is going on reporting a step failure in this case. 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-41200) Developer can see ANSI color in log file
Title: Message Title James Dumay commented on JENKINS-41200 Re: Developer can see ANSI color in log file Something that we certainly would like to get to soon. Stay tuned! 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: James Dumay *Problem*On [this jenkins file|https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L60] it sometimes fails to do a docker pull. This results in a step that fails from time to time. This ends up as an exception that is caught and [prints out the error here|https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L135]. The problem is the actual failing step is reported as successful, which isn't helpful when highlighting where the problem is. *What should happen*The step that threw the exception should be marked as a failure. *Screenshot* !Screen Shot 2017-03-17 at 10.48.01 am.png|thumbnail! 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
[JIRA] (JENKINS-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: James Dumay 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: James Dumay – putting in blue ocean purely for triaging, I am not sure where the solution really should be – *Problem* On [ this jenkins file - it sometimes fails to do a docker pull: [ | https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L60] it sometimes fails to do a docker pull. This results in a step that fails from time to time. This ends up as an exception that is caught and [ prints out the error here : [ | https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L135] . The problem is the actual failing step is reported as successful, which isn't helpful when highlighting where the problem is. * What should happen : * The step that threw the exception should be marked as a failure. This may be an issue with docker pipeline... or design Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42864) Implement descriptions for BranchEventCause
Title: Message Title James Dumay assigned an issue to Stephen Connolly Jenkins / JENKINS-42864 Implement descriptions for BranchEventCause Change By: James Dumay Assignee: Stephen Connolly 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-42864) Implement descriptions for BranchEventCause
Title: Message Title James Dumay created an issue Jenkins / JENKINS-42864 Implement descriptions for BranchEventCause Issue Type: Story Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Mar/17 1:54 AM Priority: Major Reporter: James Dumay Following on from JENKINS-41736, we now need to implement good descriptions for BranchEventCause for Github. James Dumay has volunteered to review strings. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay commented on JENKINS-42863 Re: Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Vivek Pandey could you please investigate? Agree that this is really strange that the step isnt failed in 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: James Dumay Sprint: up next 1.0-rc1 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-41200) Developer can see ANSI color in log file
Title: Message Title Michael Neale commented on JENKINS-41200 Re: Developer can see ANSI color in log file yes not minor as in value - just minor relative to other issues right now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41200 Developer can see ANSI color in log file Change By: Michael Neale 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-41425) Refreshing page with / in job name results in 404
Title: Message Title Michael Neale commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Emmanuel Quincerot there is no fix on the blue ocean side - it requires a change to the config of the proxy (depends what is in use). 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-42776) Update version of Blue Ocean for creation flow
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-42776 Update version of Blue Ocean for creation flow Change By: James Dumay Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: Michael Neale Sprint: up next 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale commented on JENKINS-42863 Re: Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Vivek Pandey James Dumay - this needs triaging. I don't think this is specific to blue ocean (stage view shows even less helpful information) however as steps are front and centre in blue ocean - the impact is big: 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale edited a comment on JENKINS-42863 Re: Step that throws an error shows up as successful if error is caught later in the Jenkinsfile [~vivek] [~jamesdumay] - this needs triaging , maybe we need to rewrite this ticket for docker pipeline, or steps api, if this can be solved . I don't think this is specific to blue ocean (stage view shows even less helpful information) however as steps are front and centre in blue ocean - the impact is big: !Screen Shot 2017-03-17 at 10.48.01 am.png|thumbnail! 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: Michael Neale Attachment: Screen Shot 2017-03-17 at 10.48.01 am.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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Change By: Michael Neale Assignee: Vivek Pandey 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-42863) Step that throws an error shows up as successful if error is caught later in the Jenkinsfile
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-42863 Step that throws an error shows up as successful if error is caught later in the Jenkinsfile Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/16 11:33 PM Priority: Minor Reporter: Michael Neale – putting in blue ocean purely for triaging, I am not sure where the solution really should be – On this jenkins file - it sometimes fails to do a docker pull: https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L60 This results in a step that fails from time to time. This ends up as an exception that is caught and prints out the error here: https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile#L135 The problem is the actual failing step is reported as successful, which isn't helpful when highlighting where the problem is. What should happen: The step that threw the exception should be marked as a failure. This may be an issue with docker pipeline... or design Add Comment
[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Mark Thistlewaite updated an issue Jenkins / JENKINS-42862 Unable to view Performance Center Test Results - HP Application Automation Tools Change By: Mark Thistlewaite Using HPE SAAS Performance Center 12.53, with Jenkins 2.19.3, we are able to execute Performance Tests in HP SAAS ALM, but we are unable to view the test results link that are returned. Clicking on the link, shows the proper link for the dataset, but nothing shows in the browser. From the Console Log: /view/qa-environments/job/prefix-deploy-populate/161/artifact/performanceTestsReports/pcRun2665/Report.html - the site dnsname and port are removed.Console Log: [PCServer=' 74 xxx . 217 xxx . 213 xxx . 36 xxx ', User='jenkins .aws '] Login succeededRun started (TestID: 359, RunID: 2665, TimeslotID: 18313)Set HP_RUN_ID Env Variable to 2665 RunID: 2665 - State = Initializing RunID: 2665 - State = Running RunID: 2665 - State = Collating Results RunID: 2665 - State = Creating Analysis Data RunID: 2665 - State = Finished Publishing analysis report Adding run: 2665 to trend report: 24 Publishing run: 2665 on trend report: 24 Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Run: 2665 publishing status: Trended Downloading trend report: 24 in PDF format Trend report: 24 was successfully downloadedView Analysis Report of Run 2665View Trend Report 24 Logout succeeded Result Status (PC RunID: 2665): SUCCESS - - - Recording test results RunResultRecorder: no results xml File provided Add Comment
[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Mark Thistlewaite updated an issue Jenkins / JENKINS-42862 Unable to view Performance Center Test Results - HP Application Automation Tools Change By: Mark Thistlewaite Using HPE SAAS Performance Center 12.53, with Jenkins 2.19.3, we are able to execute Performance Tests in HP SAAS ALM, but we are unable to view the test results link that are returned. Clicking on the link, shows the proper link for the dataset, but nothing shows in the browser. From the Console Log: /view/qa-environments/job/prefix-deploy-populate/161/artifact/performanceTestsReports/pcRun2665/Report.html - the site dnsname and port are removed.Console Log:[PCServer='74.217.213.36', User='jenkins.aws']Login succeededRun started (TestID: 359, RunID: 2665, TimeslotID: 18313)Set HP_RUN_ID Env Variable to 2665RunID: 2665 - State = InitializingRunID: 2665 - State = RunningRunID: 2665 - State = Collating ResultsRunID: 2665 - State = Creating Analysis DataRunID: 2665 - State = FinishedPublishing analysis reportAdding run: 2665 to trend report: 24Publishing run: 2665 on trend report: 24Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Publishing...Run: 2665 publishing status: TrendedDownloading trend report: 24 in PDF formatTrend report: 24 was successfully downloaded [ View analysis report Analysis Report of run Run 2665 |http://jenkinsaws.corp.mirthcorp.com:8080/view/qa-environments/job/prefix-deploy-populate/161/artifact/performanceTestsReports/pcRun2665/Report.html] [ View trend report Trend Report 24 |http://jenkinsaws.corp.mirthcorp.com:8080/view/qa-environments/job/prefix-deploy-populate/161/artifact/performanceTestsReports/TrendReports/trendReport24.pdf] Logout succeededResult Status (PC RunID: 2665): SUCCESS- - -Recording test resultsRunResultRecorder: no results xml File provided Add Comment
[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Mark Thistlewaite created an issue Jenkins / JENKINS-42862 Unable to view Performance Center Test Results - HP Application Automation Tools Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2017/Mar/16 10:37 PM Priority: Minor Reporter: Mark Thistlewaite Using HPE SAAS Performance Center 12.53, with Jenkins 2.19.3, we are able to execute Performance Tests in HP SAAS ALM, but we are unable to view the test results link that are returned. Clicking on the link, shows the proper link for the dataset, but nothing shows in the browser. From the Console Log: /view/qa-environments/job/prefix-deploy-populate/161/artifact/performanceTestsReports/pcRun2665/Report.html - the site dnsname and port are removed. Console Log: [PCServer='74.217.213.36', User='jenkins.aws'] Login succeeded Run started (TestID: 359, RunID: 2665, TimeslotID: 18313) Set HP_RUN_ID Env Variable to 2665 RunID: 2665 - State = Initializing RunID: 2665 - State = Running RunID: 2665 - State = Collating Results RunID: 2665 - State = Creating Analysis Data RunID: 2665 - State = Finished Publishing analysis report Adding run: 2665 to trend report: 24 Publishing run: 2665 on trend report: 24 Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Run: 2665 publishing status: Trended Downloading trend report: 24 in PDF format Trend report: 24 was successfully downloaded View analysis report of run 2665 View trend report 24 Logout succeeded Result Status (PC RunID: 2665): SUCCESS - - Recording test results RunResultRecorder: no results xml File provided
[JIRA] (JENKINS-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Stephen Connolly commented on JENKINS-42856 Re: Unable to launch Windows slave with ssh: Unexpected termination of the channel The Microsoft OpenSSH port has some issue that I - after 2 days fighting - was unable to get around. There is currently no way to make this work with Jenkins. It does not work even using the `use a command on the command line` option to fire a native ssh client. I am not sure if it is CHCP code page related mangling of the streams (though ssh -T should avoid that, and that didn't work) I wish I had even a reproducible test case that I could provide to Microsoft to raise the issue. The state of affairs results in me having to post this here: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slave with ssh: Unexpected termination of the channel Change By: Stephen Connolly Attachment: image-2017-03-16-22-26-53-920.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-42861) Jenkins references shut down service stacktrace.jenkins-ci.org
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-42861 Jenkins references shut down service stacktrace.jenkins-ci.org Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-42730) declarative-linter don't work with shared library
Title: Message Title Boudoux Etienne commented on JENKINS-42730 Re: declarative-linter don't work with shared library hi, I don't see any doc for this new libraries directive. do you have a working example? thank 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-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Oleg Nenashev commented on JENKINS-42852 Re: JSONObject["administrativeMonitor"] is not a JSONArray. Mark Austin I meant that the error pattern is well known. Regarding this case, it is a new bug IIRC. Have not seen similar reports at least 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-42147) Deployment failed but console output shows success
Title: Message Title Raphael CHAUMIER commented on JENKINS-42147 Re: Deployment failed but console output shows success Hi vinod vinod Any update about this 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-42802) Add a friendly message for missing deployment policy
Title: Message Title Raphael CHAUMIER commented on JENKINS-42802 Re: Add a friendly message for missing deployment policy Good suggestion. 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Oleg Nenashev commented on JENKINS-42856 Re: Unable to launch Windows slave with ssh: Unexpected termination of the channel CC Stephen Connolly since he likely has some context 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-42713) Fresh install Exception at system config
Title: Message Title Oleg Nenashev commented on JENKINS-42713 Re: Fresh install Exception at system config Since it happens in LTS, it is not related to the latest Groovy update. Still needs investigation 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title
Nick Jones updated an issue
Jenkins / JENKINS-42856
Unable to launch Windows slave with ssh: Unexpected termination of the channel
Change By:
Nick Jones
As a first step to being able to use the VMware plugin to spawn slaves automatically, I'm trying to get ssh slave connectivity to work. Normally I use Java Web Start for permanent slaves, which works fine, but I have no way to use that with a dynamic slave (without turning off the connect security and forgoing having a secret in the JNLP command).I've installed the Microsoft SSH port (Win32-OpenSSH) for sshd, and Cygwin to get the "true" utility that Jenkins expects to call, but my attempts to launch the agent fail almost immediately (after copying the slave.jar file), with the following log:{noformat}[03/16/17 14:35:26] [SSH] Opening SSH connection to myserver:22.[03/16/17 14:35:31] [SSH] Authentication successful.[03/16/17 14:35:34] [SSH] The remote users environment is:[03/16/17 14:35:36] [SSH] Starting sftp client.[03/16/17 14:35:39] [SSH] Copying latest slave.jar...[03/16/17 14:36:00] [SSH] Copied 717,563 bytes.Expanded the channel window size to 4MB[03/16/17 14:36:00] [SSH] Starting slave process: cd "C:\Jenkins" && "C:\Program Files\Java\jre1.8.0_121\bin\java" -jar slave.jar<===[JENKINS REMOTING CAPACITY]===><===[JENKINS REMOTING CAPACITY]===>ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:888) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:92) at ..remote call to BuildBase myserver (Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:821) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:516) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:389) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:989) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:139) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:738) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:719) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at
[JIRA] (JENKINS-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Mark Austin commented on JENKINS-42852 Re: JSONObject["administrativeMonitor"] is not a JSONArray. Oleg Nenashev ah okay. I didn't see anything for this specific case when I searched the DB, so I wanted to make sure ya'll were aware about 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones commented on JENKINS-42856 Re: Unable to launch Windows slave with ssh: Unexpected termination of the channel I just updated to the latest version of the SSH Slaves plugin, 1.14, and tried again. The only difference is that now it correctly outputs the remote user's environment. It still fails immediately after slave.jar copying with: ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:888) etc. 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slave with ssh: Unexpected termination of the channel Change By: Nick Jones Environment: Windows 2012 R2 master and slaves, Jenkins 2.32.3 LTS, Win32-OpenSSH 0.0.10.0, Cygwin 2.7.0 , SSH Slaves plugin 1.14 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-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Oleg Nenashev commented on JENKINS-42852 Re: JSONObject["administrativeMonitor"] is not a JSONArray. It is a pretty well known issue. In such case you get JSON object instead of the JSONArray. CC Daniel Beck since he was working on this area recently 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-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Shannon Kerr edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection We are blocked by this as well. Using Subversion with a working copy that is ~6.5G. If we use the "Jenkins" sub-directory work-around, I think we'll lose the change tracking from build to build, which would be a big loss. Also, we want to be able to share a workspace between product branches (Client, Server, Web etc), so all Server branch builds share a common workspace, Client in a shared workspace etc. We don't want each Client branch to have a full 6.5G workspace + the build artifacts. If we go this shared workspace route, we need to be able to throttle Client branch builds so we only have one build at a time (per slave). I'm going to try a hybrid of job generator plugin and (non-multibranch) pipeline to see if I can make this work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42861) Jenkins references shut down service stacktrace.jenkins-ci.org
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-42861 Jenkins references shut down service stacktrace.jenkins-ci.org Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/16 9:26 PM Priority: Minor Reporter: Daniel Beck [2017-03-16 22:14:52] rtyler is stacktrace.jenkins-ci.org still a service we run? [2017-03-16 22:15:04] heh, no [2017-03-16 22:17:03] rtyler so we should probably remove it from Jenkins then? [2017-03-16 22:17:49] I'm struggling to remember what that even was Add Comment
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Shannon Kerr commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection We are blocked by this as well. Using Subversion with a working copy that is ~6.5G. If we use the "Jenkins" sub-directory work-around, I think we'll lose the change tracking from build to build, which would be a big loss. Also, we want to be able to share a workspace between product branches (Client, Server, Web etc), so all Server branch builds share a common workspace, Client in a shared workspace etc. We don't want each Client branch to have a full 6.5G workspace + the build artifacts. If we go this shared workspace route, we need to be able to throttle Client branch builds so we only have one build at a time (per slave). I'm going to try a hybrid of job generator plugin and (non-multibranch) pipeline to see if I can make this work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41996) Using a specific global library version in consumers sometimes causes notifications of build success/failure on the library that they consume
Title: Message Title
Mike Kobit commented on JENKINS-41996
Re: Using a specific global library version in consumers sometimes causes notifications of build success/failure on the library that they consume
I ran the following in the script console for one of these builds that exhibited this behavior:
import com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications
import hudson.plugins.git.util.BuildData
final jenkins = Jenkins.instance
final coreOrg = jenkins.getAllItems(jenkins.branch.OrganizationFolder).find {
it.displayName == 'CORE'
}
final translationService = coreOrg.getItem('translation-service')
final master = translationService.getItem('master')
final faultyBuild = master.getBuildByNumber(101)
faultyBuild.getActions(BuildData).each {
println(it)
}
println()
And the results that came out were like this:
hudson.plugins.git.util.BuildData@eb488be7[scmName=,remoteUrls=[ssh://g...@internal-git.company.com:7999/jenkins/jenkins-pipeline-utilities.git],buildsByBranchName={0.4.0=Build #70 of Revision ec78141895c015cb891d625e95cb3a35145a81c7 (0.4.0), master=Build #101 of Revision 9013619e45591ee4b8b4f3e411e0e810af30e5a2 (master)},lastBuild=Build #101 of Revision 9013619e45591ee4b8b4f3e411e0e810af30e5a2 (master)]
hudson.plugins.git.util.BuildData@ab0af0b6[scmName=,remoteUrls=[ssh://g...@internal-git.company.com:7999/core/translation-service.git],buildsByBranchName={master=Build #101 of Revision b9560e970a46546e2186758e602a7e1ac420de03 (master)},lastBuild=Build #101 of Revision b9560e970a46546e2186758e602a7e1ac420de03 (master)]
This seems like a bug in the place I mentioned above. If I change to:
println(faultyBuild.getAction(BuildData))
Then I get
hudson.plugins.git.util.BuildData@eb488be7[scmName=,remoteUrls=[ssh://g...@git.uptake.com:7999/blt/jenkins-pipeline-utilities.git],buildsByBranchName={0.4.0=Build #70 of Revision ec78141895c015cb891d625e95cb3a35145a81c7 (0.4.0), master=Build #101 of Revision 9013619e45591ee4b8b4f3e411e0e810af30e5a2 (master)},lastBuild=Build #101 of Revision 9013619e45591ee4b8b4f3e411e0e810af30e5a2 (master)]
Antonio Muñiz any advice on how I can fix this since I think I found the cause point would be appreciated. There are currently no tests for BitbucketBuildStatusNotifications so anything to help would be great.
[JIRA] (JENKINS-39243) image.inside() does not respect docker.withServer() settings
Title: Message Title Craig Rodrigues commented on JENKINS-39243 Re: image.inside() does not respect docker.withServer() settings Christian Fraenkel can you post an example of how you passed the value of DOCKER_HOST down so that image.inside() works with the settings specified in docker.withServer() ? I'm trying to do the same thing you are doing, where my Docker server is on a separate host from where my Jenkins job is running. 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-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Sorin Sbarnea Component/s: 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-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin, github-organization-folder-plugin Created: 2017/Mar/16 8:57 PM Environment: jenkins instance configured with github organization plugin and github authorization too. Priority: Critical Reporter: Sorin Sbarnea It seems that I get this exception which is NOT logged inside the script approver which means there is not way to approve it. org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches This happened with this pipeline https://github.com/pycontribs/powertape/blob/master/Jenkinsfile Now, the interesting thing is that if you configure a this project in jenkins using the pipeline type of of job and setting the source as SCM, it will work. So this problem is specific to this way of configuring the jobs.
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title
Abhinav Nallagundla updated an issue
Jenkins / JENKINS-42859
categorizedJobsView default "recurse" value is not honored
Change By:
Abhinav Nallagundla
Attachment:
Screen Shot 2017-03-16 at 1.38.19 PM.png
Hi thereI am using the job DSL plugin to create categorizedJobsView. [API Viewer|https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.categorizedJobsView] documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to falseThis can be validated by using the following{code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)}categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}{code}Look for the XML file generated and check for flag, you will notice something like false. But the documentation says default value for recurse is true The way to correct is to change above DSL code to following {code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)} recurse(true)categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}{code} Either this is This seems to be bug in documentation or the implementation itself.
Add Comment
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title
Abhinav Nallagundla updated an issue
Jenkins / JENKINS-42859
categorizedJobsView default "recurse" value is not honored
Change By:
Abhinav Nallagundla
Hi thereI am using the job DSL plugin to create categorizedJobsView. [API Viewer|https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.categorizedJobsView] documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to falseThis can be validated by using the following{code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)}categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}{code}Look for the XML file generated and check for flag, you will notice something like false. But the documentation says recurse default value for recurse is true The way to correct is to change above DSL code to following {code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)} recurse(true)categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}{code}Either this is bug in documentation or the implementation itself.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title
Abhinav Nallagundla updated an issue
Jenkins / JENKINS-42859
categorizedJobsView default "recurse" value is not honored
Change By:
Abhinav Nallagundla
Hi thereI am using the job DSL plugin to create categorizedJobsView. [API Viewer|https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.categorizedJobsView] documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to falseThis can be validated by using the following{code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)}categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}} {code}Look for the XML file generated and check for flag, you will notice something like false. But the documentation says recurse default is true The way to correct is to change above DSL code to following {code:java}categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)} recurse(true)categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}{code}Either this is bug in documentation or the implementation itself.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title
Abhinav Nallagundla updated an issue
Jenkins / JENKINS-42859
categorizedJobsView default "recurse" value is not honored
Change By:
Abhinav Nallagundla
Hi thereI am using the job DSL plugin to create categorizedJobsView. [API Viewer|https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.categorizedJobsView] documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to falseThis can be validated by using the following {code:java} categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)}categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}} {code} Look for the XML file generated and check for flag, you will notice something like false. But the documentation says recurse default is true The way to correct is to change above DSL code to following {code:java} categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)} recurse(true)categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}} {code} Either this is bug in documentation or the implementation itself.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title Abhinav Nallagundla updated an issue Jenkins / JENKINS-42859 categorizedJobsView default "recurse" value is not honored Change By: Abhinav Nallagundla Environment: job DSL plugin version 1.58Jenkins ver. 2.47 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-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title Abhinav Nallagundla updated an issue Jenkins / JENKINS-42859 categorizedJobsView default "recurse" value is not honored Change By: Abhinav Nallagundla Summary: categorizedJobsView default " recurse " value is not honored 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-42859) categorizedJobsView default recurse value is not honored
Title: Message Title
Abhinav Nallagundla updated an issue
Jenkins / JENKINS-42859
categorizedJobsView default recurse value is not honored
Change By:
Abhinav Nallagundla
Hi thereI am using the job DSL plugin to create categorizedJobsView. [API Viewer|https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.categorizedJobsView] documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to falseThis can be validated by using the followingcategorizedJobsView('example') \{jobs \{regex(/configuration_.*/)}categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}Look for the XML file generated and check for flag , you will notice something like false. But the documentation says recurse default is true The way to correct is to change above DSL code to following categorizedJobsView('example') \{jobs \{regex(/configuration_.*/)} recurse(true)categorizationCriteria \{regexGroupingRule(/^configuration_([^_]+).*$/)}columns \{status()categorizedJob()buildButton()}}Either this is bug in documentation or the implementation itself.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42859) categorizedJobsView default recurse value is not honored
Title: Message Title Abhinav Nallagundla updated an issue Jenkins / JENKINS-42859 categorizedJobsView default recurse value is not honored Change By: Abhinav Nallagundla Summary: categorizedJobsView recurse=true default recurse value is not honored 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-42859) categorizedJobsView recurse=true default is not honored
Title: Message Title Abhinav Nallagundla updated an issue Jenkins / JENKINS-42859 categorizedJobsView recurse=true default is not honored Change By: Abhinav Nallagundla Summary: [DSL Plugin] categorizedJobsView recurse=true default is not honored 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-42859) [DSL Plugin] categorizedJobsView recurse=true default is not honored
Title: Message Title
Abhinav Nallagundla created an issue
Jenkins / JENKINS-42859
[DSL Plugin] categorizedJobsView recurse=true default is not honored
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2017/Mar/16 8:23 PM
Priority:
Major
Reporter:
Abhinav Nallagundla
Hi there I am using the job DSL plugin to create categorizedJobsView. API Viewer documentation for categorizedJobsView say default recurse value is true. However that is not the case. the default value is set to false This can be validated by using the following categorizedJobsView('example') { jobs { regex(/configuration_.*/) } categorizationCriteria { regexGroupingRule(/^configuration_([^_]+).*$/) } columns { status() categorizedJob() buildButton() } } Look for the XML file generated and check for flag
Add Comment
[JIRA] (JENKINS-42858) Credentials environment variable isn't evaluated/available in the environment directive
Title: Message Title
Stephen Donner created an issue
Jenkins / JENKINS-42858
Credentials environment variable isn't evaluated/available in the environment directive
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/16 8:04 PM
Environment:
Jenkins 2.32.3 Pipeline Model Definition Plugin 1.1.1 (and associated/dependent plugins)
Priority:
Major
Reporter:
Stephen Donner
We'd like to do: pipeline { // snip // environment { VARIABLES = credentials('MOZILLIANS_VARIABLES') SAUCELABS_API_KEY = credentials('SAUCELABS_API_KEY') PYTEST_ADDOPTS = "--color=yes --driver=SauceLabs --variables=capabilities.json --variables=$ {VARIABLES}" } // snip // } But we get: WorkflowScript: 25: ""--variables" is not a valid identifier and cannot be used for an environment variable. Identifiers must start with a letter or underscore and can contain only letters, numbers or underscores. @ line 25, column 7. "--variables=${VARIABLES} " The workaround is to currently do: pipeline { // snip // environment { VARIABLES = credentials('MOZILLIANS_VARIABLES') SAUCELABS_API_KEY = credentials('SAUCELABS_API_KEY') } stages { stage('Test') { environment { PYTEST_ADDOPTS = "--color=yes --driver=SauceLabs --variables=capabilities.json --variables=$ {VARIABLES} " } // snip // }
[JIRA] (JENKINS-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Claudiu Guiman started work on JENKINS-42853 Change By: Claudiu Guiman 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-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Corey Groves commented on JENKINS-42853 Re: NPE on Virtual Machine Size when selecting Azure template The exception occurs when the Add Azure Virtual Machine Template section is loading, I don't have a chance to pick anything before the error occurs. 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-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Claudiu Guiman commented on JENKINS-42853 Re: NPE on Virtual Machine Size when selecting Azure template Have you selected the desired region before selecting the VM size? From the exception call stack it looks like the region was null. 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-42857) Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable
Title: Message Title
Stephen Donner created an issue
Jenkins / JENKINS-42857
Multi-line, concatenated-string values aren't parsed/passed in/to "environment" variable
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/16 7:54 PM
Environment:
Jenkins 2.32.2 Pipeline Model Definition Plugin 1.1.1 (and all associated/dependent plugins, same/greater versions)
Priority:
Minor
Reporter:
Stephen Donner
Given the following snippet of a Jenkinsfile: environment { PYTEST_ADDOPTS = "-n=10 " + "--color=yes " + "--tb=short " + "--driver=SauceLabs " + "--variables=capabilities.json" } When trying to run the above, we get: Actual Results: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 19: Environment variable values must either be strings or function calls. @ line 19, column 5. PYTEST_ADDOPTS = ^ The workaround is to do: environment { PYTEST_ADDOPTS = "-n=10 --color=yes --tb=short --driver=SauceLabs --variables=capabilities.json" }
[JIRA] (JENKINS-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Corey Groves commented on JENKINS-42853 Re: NPE on Virtual Machine Size when selecting Azure template If I ignore the error and fill out the other fields then save the configuration, when I return to the setup screen it populates the Virtual Machine Size list with no error. But the error occurs every time when clicking on the Add button for a new template for the first time. 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-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Corey Groves edited a comment on JENKINS-42853 Re: NPE on Virtual Machine Size when selecting Azure template If I ignore the error and fill out the other fields then save the configuration, when I return to the setup screen it populates the Virtual Machine Size list with no error. But the error occurs every time when clicking on the Add button for a new template for the first time. With this workaround it is no longer a blocker for us. 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slave with ssh: Unexpected termination of the channel Change By: Nick Jones 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-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-42856 Unable to launch Windows slave with ssh: Unexpected termination of the channel Change By: Nick Jones Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42856) Unable to launch Windows slave with ssh: Unexpected termination of the channel
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-42856 Unable to launch Windows slave with ssh: Unexpected termination of the channel Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 2017/Mar/16 7:49 PM Environment: Windows 2012 R2 master and slaves, Jenkins 2.32.3 LTS, Win32-OpenSSH 0.0.10.0, Cygwin 2.7.0 Priority: Major Reporter: Nick Jones As a first step to being able to use the VMware plugin to spawn slaves automatically, I'm trying to get ssh slave connectivity to work. Normally I use Java Web Start for permanent slaves, which works fine, but I have no way to use that with a dynamic slave (without turning off the connect security and forgoing having a secret in the JNLP command). I've installed the Microsoft SSH port (Win32-OpenSSH) for sshd, and Cygwin to get the "true" utility that Jenkins expects to call, but my attempts to launch the agent fail almost immediately (after copying the slave.jar file), with the following log: [03/16/17 14:35:26] [SSH] Opening SSH connection to myserver:22. [03/16/17 14:35:31] [SSH] Authentication successful. [03/16/17 14:35:34] [SSH] The remote users environment is: [03/16/17 14:35:36] [SSH] Starting sftp client. [03/16/17 14:35:39] [SSH] Copying latest slave.jar... [03/16/17 14:36:00] [SSH] Copied 717,563 bytes. Expanded the channel window size to 4MB [03/16/17 14:36:00] [SSH] Starting slave process: cd "C:\Jenkins" && "C:\Program Files\Java\jre1.8.0_121\bin\java" -jar slave.jar <===[JENKINS REMOTING CAPACITY]===><===[JENKINS REMOTING CAPACITY]===>ERROR: Unexpected error in launching a
[JIRA] (JENKINS-42853) NPE on Virtual Machine Size when selecting Azure template
Title: Message Title Claudiu Guiman commented on JENKINS-42853 Re: NPE on Virtual Machine Size when selecting Azure template Is this blocking you or you managed to go over the NPE and select a VM size? 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-42855) BUILD_ID not sequential for Pipeline jobs when hp-application-automation-tools is installed
Title: Message Title Tom Larrow commented on JENKINS-42855 Re: BUILD_ID not sequential for Pipeline jobs when hp-application-automation-tools is installed Thanks for tracking that down and getting it correctly assigned. Really appreciate your help. 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-35370) Workflow shell step ERROR: script returned exit code -1
Title: Message Title Craig Rodrigues commented on JENKINS-35370 Re: Workflow shell step ERROR: script returned exit code -1 Ben Mathews fair enough. I'm running into the same problem so was just curious. My understanding of the problem is that if your Jenkins server is running inside a Docker container, and then you try to start a docker container on the same server (so you are doing Docker container inside Docker container), then that doesn't work so well. The Durable Task plugin used by the pipeline **sh step has some complicated logic for how it figures out the process ID (pid) of the shell script that has been executed, and this logic gets confused when you do Docker inside Docker, and returns -1, even though your shell script is still running. I ran into the -1 problems in JENKINS-32264 , (not in a Docker context). 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-42855) BUILD_ID not sequential
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42855 BUILD_ID not sequential Change By: Andrew Bayer Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42855) BUILD_ID not sequential for Pipeline jobs when
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42855 BUILD_ID not sequential for Pipeline jobs when Change By: Andrew Bayer Summary: BUILD_ID not sequential for Pipeline jobs when 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-42855) BUILD_ID not sequential for Pipeline jobs when hp-application-automation-tools is installed
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42855 BUILD_ID not sequential for Pipeline jobs when hp-application-automation-tools is installed Change By: Andrew Bayer Summary: BUILD_ID not sequential for Pipeline jobs when hp-application-automation-tools is installed 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-42855) BUILD_ID not sequential
Title: Message Title Andrew Bayer assigned an issue to Ofir Shaked Bam! Got it - it's https://plugins.jenkins.io/hp-application-automation-tools-plugin - I disabled that and the numbering problem stopped. Jenkins / JENKINS-42855 BUILD_ID not sequential Change By: Andrew Bayer Component/s: hp-application-automation-tools-plugin Component/s: pipeline-model-definition-plugin Assignee: Andrew Bayer Ofir Shaked Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title
Nikolas Falco edited a comment on JENKINS-42675
Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Actually https://npm. + registry. nodejs. org + is the only actual default registry for global packages.The jenkins no proxy value is validated against the default npm registry URL, so if you add npm.registry.org in no proxy Jenkins settings the http_proxy and https_proxy are not set during npm install -g action.If I understand right only npm >= 3 support no_proxy, and only as enviroment variable ([details here|https://github.com/npm/npm/issues/7168])In real it's a little bit complicated becuase some global package could have scope that refer to a different registry:{noformat}@mycorporate:registry=mycorporaterepo.mycompany.com{noformat}I should support npmrc in global package and taking care about all registry and foreach one check against jenkins no proxy and make a mix behavior to support also old version of npm.Anyway remember that you could setup registry and no_proxy as global variable prefixed by *npm_config_* as described in my previous post. All enviroment variables with that prefix are considered by npm like written in a .npmrc file.
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-42855) BUILD_ID not sequential
Title: Message Title Andrew Bayer commented on JENKINS-42855 Re: BUILD_ID not sequential Woot! Something in that set of plugins is definitely causing the problem, 'cos I'm seeing it now. Time to disable them one by one until I find 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-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco commented on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page Actually https://npm.registry.org is the only actual default registry for global packages. The jenkins no proxy value is validated against the default npm registry URL, so if you add npm.registry.org in no proxy Jenkins settings the http_proxy and https_proxy are not set during npm install -g action. If I understand right only npm >= 3 support no_proxy, and only as enviroment variable (details here) In real it's a little bit complicated becuase some global package could have scope that refer to a different registry: @mycorporate:registry=mycorporaterepo.mycompany.com I should support npmrc in global package and taking care about all registry and foreach one check against jenkins no proxy and make a mix behavior to support also old version of npm. Anyway remember that you could setup registry and no_proxy as global variable prefixed by npm_config_ as described in my previous post. All enviroment variables with that prefix are considered by npm like written in a .npmrc file. 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
[JIRA] (JENKINS-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow commented on JENKINS-42855 Re: BUILD_ID not sequential plugins.txt added with that output 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-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow updated an issue Jenkins / JENKINS-42855 BUILD_ID not sequential Change By: Tom Larrow Attachment: plugins.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow commented on JENKINS-42855 Re: BUILD_ID not sequential Added an xml report of all plugins installed. We had been delaying updating packages while we pushed through a major release, so there were a large number of plugins updated this morning. 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-42855) BUILD_ID not sequential
Title: Message Title
Andrew Bayer commented on JENKINS-42855
Re: BUILD_ID not sequential
If at all possible, I'd love to get all the plugins/versions - try running this in the script console:
Jenkins.instance.pluginManager.plugins.sort { it.getShortName() }.each { p ->
println "${p.getShortName()}:${p.getVersion()}"
}
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-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow updated an issue Jenkins / JENKINS-42855 BUILD_ID not sequential Change By: Tom Larrow Attachment: plugins.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow commented on JENKINS-42855 Re: BUILD_ID not sequential Yes, I put together a quick scripted job and it is performing the same way. 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-42855) BUILD_ID not sequential
Title: Message Title Tom Larrow commented on JENKINS-42855 Re: BUILD_ID not sequential Any other plugins you need versions of? Is there an easy way to generate a report of what I have installed? 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-42855) BUILD_ID not sequential
Title: Message Title Andrew Bayer commented on JENKINS-42855 Re: BUILD_ID not sequential I'm failing to reproduce this on an up-to-date-everything set of plugins with core 2.50. Hrrrm. 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-42855) BUILD_ID not sequential
Title: Message Title Andrew Bayer commented on JENKINS-42855 Re: BUILD_ID not sequential Did you get this with a Scripted Pipeline job? I'd assume you will if you did for Declarative, but just to be sure... 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-42855) BUILD_ID not sequential
Title: Message Title
Tom Larrow created an issue
Jenkins / JENKINS-42855
BUILD_ID not sequential
Issue Type:
Bug
Assignee:
Andrew Bayer
Attachments:
jenkins count by 2.png, pasted_image_at_2017_03_16_12_56_pm_360.png
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/16 6:22 PM
Environment:
Jenkins 2.50 running on RHEL 7 linux Pipeline 2.5 Pipeline API 2.12 Pipeline Declarative Agent API 1.1.1 Pipeline Declarative Extension Points Api 1.1.1 Pipeline Groovy 2.29 Pipeline Job 2.10 Pipeline Model API 1.1.1 Pipeline Model Definition 1.1.1
Priority:
Minor
Reporter:
Tom Larrow
Most jobs have started incrementing their build numbers by 2. A few jobs have started counting by 3. I thought it may have been folder related as one of the jobs that was counting by 3 was a bit deeper in a folder, but in further testing, a test job was counting by 2 no matter if it was 5 folders deep, or in the root of Jenkins. Test job which is counting by 2 is built with this Jenkinsfile put directly in the editor in Jenkins so no SCM involved pipeline{ agent{ label 'master' } stages{ stage("test"){ steps{ echo "test" } } } } Testing a freestyle job which also just did an echo and everything was sequential
[JIRA] (JENKINS-39397) Updating Windows Slaves plugin fails
Title: Message Title Nicholas Geraedts commented on JENKINS-39397 Re: Updating Windows Slaves plugin fails Turns out our issue was with an overly aggressive network security filter that blocked downloads. Please disregard my error messages. 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-29144) SimpleBuildStep to receive EnvVars
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29144 SimpleBuildStep to receive EnvVars Change By: Jesse Glick Labels: api 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-29144) SimpleBuildStep to receive EnvVars
Title: Message Title Jesse Glick commented on JENKINS-29144 Re: SimpleBuildStep to receive EnvVars Without JENKINS-40070, Run.getEnvironment cannot be used as a workaround. 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-42854) Add description field to the "Computer" api
Title: Message Title D M commented on JENKINS-42854 Re: Add description field to the "Computer" api I have created a pull request for this issue here: https://github.com/jenkinsci/jenkins/pull/2807 Many thanks for looking into this in advance. 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-42190) Bitbucket branch source plugin creates wrong repo URL's for Bitbucket Server located in subdirectory
Title: Message Title Metin OSMAN commented on JENKINS-42190 Re: Bitbucket branch source plugin creates wrong repo URL's for Bitbucket Server located in subdirectory +1 also, works with 2.0.2, not with 2.1.0 Bitbucket Server version : 4.12.0 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-42561) Users should be able to custom configure the timeout on pipeline build wrappers/steps
Title: Message Title Lucas Machado commented on JENKINS-42561 Re: Users should be able to custom configure the timeout on pipeline build wrappers/steps This PR https://github.com/jenkinsci/workflow-cps-plugin/pull/115 can add this parameter to the server level. 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.
