[JIRA] (JENKINS-38036) REGRESSION: read only access not working with github auth plugin and blue ocean
Title: Message Title Vivek Pandey updated JENKINS-38036 Jenkins / JENKINS-38036 REGRESSION: read only access not working with github auth plugin and blue ocean Change By: Vivek Pandey Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38016) Fresh install on 2.7.3 of blueocean requires a restart for API to work
Title: Message Title Vivek Pandey updated JENKINS-38016 Jenkins / JENKINS-38016 Fresh install on 2.7.3 of blueocean requires a restart for API to work Change By: Vivek Pandey Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38052) Pipeline parallel map not supporting curried closures
Title: Message Title Ben Fortuna updated an issue Jenkins / JENKINS-38052 Pipeline parallel map not supporting curried closures Change By: Ben Fortuna Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38052) Pipeline parallel map not supporting curried closures
Title: Message Title
Ben Fortuna updated an issue
Jenkins / JENKINS-38052
Pipeline parallel map not supporting curried closures
Change By:
Ben Fortuna
When executing a curried closure in parallel the output appears to be cached (see the output for the spam branch below).Example pipeline: {code} def example_c = { input -> node { echo "$input" } }def map = [:]map['spam'] = example_c.curry('spam')map['eggs'] = example_c.curry('eggs')parallel map {code} Output: {code} [Pipeline] parallel[Pipeline] [spam] { (Branch: spam)[Pipeline] [eggs] { (Branch: eggs)[Pipeline] [spam] node[spam] Running on java8-jenkins-ec2-slave (i-a541b5be) [Pipeline] [eggs] node[Pipeline] [spam] {[eggs] Running on java8-jenkins-ec2-slave (i-a541b5be) [Pipeline] [spam] echo[spam] eggs[Pipeline] }[Pipeline] [eggs] {[Pipeline] // node[Pipeline] }[Pipeline] [eggs] echo[eggs] eggs[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // parallel[Pipeline] End of Pipeline {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38052) Pipeline parallel map not supporting curried closures
Title: Message Title
Ben Fortuna created an issue
Jenkins / JENKINS-38052
Pipeline parallel map not supporting curried closures
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
pipeline
Created:
2016/Sep/08 5:51 AM
Priority:
Minor
Reporter:
Ben Fortuna
When executing a curried closure in parallel the output appears to be cached (see the output for the spam branch below). Example pipeline: def example_c = { input -> node { echo "$input" } } def map = [:] map['spam'] = example_c.curry('spam') map['eggs'] = example_c.curry('eggs') parallel map Output: [Pipeline] parallel [Pipeline] [spam] { (Branch: spam) [Pipeline] [eggs] { (Branch: eggs) [Pipeline] [spam] node [spam] Running on java8-jenkins-ec2-slave (i-a541b5be) [Pipeline] [eggs] node [Pipeline] [spam] { [eggs] Running on java8-jenkins-ec2-slave (i-a541b5be) [Pipeline] [spam] echo [spam] eggs [Pipeline] } [Pipeline] [eggs] { [Pipeline] // node [Pipeline] } [Pipeline] [eggs] echo [eggs] eggs [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // parallel [Pipeline] End of Pipeline
Add Comment
[JIRA] (JENKINS-38036) REGRESSION: read only access not working with github auth plugin and blue ocean
Title: Message Title Vivek Pandey updated JENKINS-38036 Jenkins / JENKINS-38036 REGRESSION: read only access not working with github auth plugin and blue ocean Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38036) REGRESSION: read only access not working with github auth plugin and blue ocean
Title: Message Title Vivek Pandey started work on JENKINS-38036 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38016) Fresh install on 2.7.3 of blueocean requires a restart for API to work
Title: Message Title Vivek Pandey updated JENKINS-38016 Jenkins / JENKINS-38016 Fresh install on 2.7.3 of blueocean requires a restart for API to work Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title Vivek Pandey assigned an issue to Cliff Meyers Jenkins / JENKINS-37831 Favoriting on Matrix style project broken Change By: Vivek Pandey Assignee: Vivek Pandey Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title Vivek Pandey commented on JENKINS-37831 Re: Favoriting on Matrix style project broken Cliff Meyers Assigning back to you Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title James Dumay commented on JENKINS-37831 Re: Favoriting on Matrix style project broken Vivek Pandey Cliff Meyers disabling favourites on matrix SGTM Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38016) Fresh install on 2.7.3 of blueocean requires a restart for API to work
Title: Message Title Vivek Pandey started work on JENKINS-38016 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title Vivek Pandey commented on JENKINS-37831 Re: Favoriting on Matrix style project broken Cliff Meyers Sorry for jumping, the legacy URL for matrix build is for a reason - that is if its matrix project then when user clicks on it, UI should redirect to classic UI for matrix project. See https://issues.jenkins-ci.org/browse/JENKINS-37427. Basically, if its matrix project (capability hudson.matrix.MatrixProject) then maybe favorite should be disabled. James Dumay what do you think? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful - when using Kyoto
Title: Message Title Vivek Pandey started work on JENKINS-38012 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38050) Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center
Title: Message Title Dan Di updated an issue Jenkins / JENKINS-38050 Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center Change By: Dan Di Summary: Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38050) Unable to successfully compare SHA-1 for all plugins using Web-GUI
Title: Message Title Dan Di updated an issue Jenkins / JENKINS-38050 Unable to successfully compare SHA-1 for all plugins using Web-GUI Change By: Dan Di On an Ubuntu 12.04.4 LTS box, we updated a config which then propegated changes from a bunch of plugins via Jenkins->Manage Jenkins->Configure System and when added some info for an Artifactory server . This caused unknown behavior that was causing all attempts to edit Job configs to cyclically request credentials, never-ending.To recover, we removed newly propegated XML files from /var/lib/jenkins and made backups of what was left, then viewed the old `good` configs with the jobHistory plugin, saved those as XML files, and then copied them into /var/lib/jenkinsThis reversed the issue of no longer being able to edit configs, but injected a new issue. We cannot successfully install any new plugins with the Web-GUI, nor can we `Check Now`Proxy info not set in Web-GUI but on the ubuntu box itself. No proxy info _should_ have been updated as we were just addressing plugins.Attachment shows example error for "java.io.IOException: Downloaded file /var/lib/jenkins/plugins/plugin_name.jpi.tmp does not match expected SHA-1, expected 'SomeSHA=', actual 'SomeOtherSha='"When trying Check Now with http://updates.jenkins-ci.org/update-center.json, getting this error also completely shown in other attachment: "javax.servlet.ServletException: java.lang.IllegalArgumentException: Could not find (numeric) updateCenterVersion in..."We then tried updating Jenkins from 2.x to 2.7 -- this did _not_ change the behavior, which surprised us to be frank.How can we fix the update center queries, even if it is a workaround? Right now all plugins have to be handled manually... Add Comment
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful - when using Kyoto
Title: Message Title Vivek Pandey commented on JENKINS-38012 Re: Pipeline has failed but its only stage is successful - when using Kyoto Confirmed failures are not propagated correctly with kyoto plugin 0.1. Part of it is due to the fact that there is regression in how kyoto propagates errors to FlowExecution. Opened a ticket https://issues.jenkins-ci.org/browse/JENKINS-38049. While it gets fixed, I have a workaround in blueocean branch bug/JENKINS-38012. With this workaround and with latest pipeline-model-definition (0.2-SNAPSHOT) failure propagation in all three types of scripts works well: legacy stage, blocked stage and kyoto style script. Andrew Bayer said 0.2 release is coming out tomorrow, after that we can proceed with integrating and test it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38051) Editor feedback round #2
Title: Message Title James Dumay created an issue Jenkins / JENKINS-38051 Editor feedback round #2 Issue Type: Task Assignee: Josh McDonald Attachments: empty.png, Jenkins Blue Ocean 2016-09-08 13-02-42.png, Sep.-08-2016 13-05-09.gif Components: blueocean-plugin Created: 2016/Sep/08 3:20 AM Priority: Minor Reporter: James Dumay Default state When you open the editor the first stage and step within that stage should be selectedCreating a new stage leaves the state of previous steps If I select the first stage and step then create a new stage it doesn't update the step listing correctly.I think an empty state like this would do the trick Add Comment
[JIRA] (JENKINS-38050) Unable to successfully compare SHA-1 for all plugins using Web-GUI
Title: Message Title Dan Di created an issue Jenkins / JENKINS-38050 Unable to successfully compare SHA-1 for all plugins using Web-GUI Issue Type: Bug Assignee: Unassigned Attachments: check_now_stack_trace.txt, example_plugin_failure.txt Components: core Created: 2016/Sep/08 3:20 AM Environment: Ubuntu 12.04.4 LTS Labels: plugin jenkins exception configuration plugins Priority: Critical Reporter: Dan Di On an Ubuntu 12.04.4 LTS box, we updated a config which then propegated changes from a bunch of plugins. This caused unknown behavior that was causing all attempts to edit Job configs to cyclically request credentials, never-ending. To recover, we removed newly propegated XML files from /var/lib/jenkins and made backups of what was left, then viewed the old `good` configs with the jobHistory plugin, saved those as XML files, and then copied them into /var/lib/jenkins This reversed the issue of no longer being able to edit configs, but injected a new issue. We cannot successfully install any new plugins with the Web-GUI, nor can we `Check Now` Proxy info not set in Web-GUI but on the ubuntu box itself. No proxy info should have been updated as we were just addressing plugins. Attachment shows example error for "java.io.IOException: Downloaded file /var/lib/jenkins/plugins/plugin_name.jpi.tmp does not match expected SHA-1, expected 'SomeSHA=', actual
Re: [JIRA] (JENKINS-38049) FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Interesting. I'll see what I can figure out. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38049) FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Title: Message Title
Vivek Pandey updated an issue
Jenkins / JENKINS-38049
FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Change By:
Vivek Pandey
Given pipeline script:{code:java}pipeline {agent label:''stages {stage ('Build') {sh 'echo1 "Building"'}}}{code}WorkflowRun.getExecution().getResult() reports Success also WorkflowRun.getExecution().getCauseOfFaulure() returns null. This is regression when compared with non-kyoto style pipeline. {code:java}node {stage ('Build') {sh 'echo1 "Building"'}}{code}Above script gives works correctly where WorkflowRun.getExecution().getResult() as FAILURE and WorkflowRun.getExecution().getCauseOfFaulure() as non null Throwable.What it does is that when we are dealing with FlowNodes and trying to determine if stage failed, does not work in this case and ends up reporting SUCCESS of overall run where its in fact was a failure. run.getResult() gives correct value as FAILURE.[~abayer] This is the issue I mentioned you over chat.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38049) FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Title: Message Title
Vivek Pandey updated an issue
Jenkins / JENKINS-38049
FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Change By:
Vivek Pandey
Given pipeline script:{code:java}pipeline {agent label:''stages {stage ('Build') {sh 'echo1 "Building"'}}}{code}WorkflowRun.getExecution().getResult() reports Success also WorkflowRun.getExecution().getCauseOfFaulure() returns null. This is regression when compared with non-kyoto style pipeline. {code:java}node {stage ('Build') {sh 'echo1 "Building"'}} {code} Above script gives WorkflowRun.getExecution().getResult() as FAILURE and WorkflowRun.getExecution().getCauseOfFaulure() as non null Throwable.What it does is that when we are dealing with FlowNodes and trying to determine if stage failed, does not work in this case and ends up reporting SUCCESS of overall run where its in fact was a failure. run.getResult() gives correct value as FAILURE.[~abayer] This is the issue I mentioned you over chat.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38049) FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Title: Message Title
Vivek Pandey created an issue
Jenkins / JENKINS-38049
FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Sep/08 3:00 AM
Priority:
Major
Reporter:
Vivek Pandey
Given pipeline script:
pipeline {
agent label:''
stages {
stage ('Build') {
sh 'echo1 "Building"'
}
}
}
WorkflowRun.getExecution().getResult() reports Success also WorkflowRun.getExecution().getCauseOfFaulure() returns null. This is regression when compared with non-kyoto style pipeline.
node { stage ('Build') { sh 'echo1 "Building"' } } Above script gives WorkflowRun.getExecution().getResult() as FAILURE and WorkflowRun.getExecution().getCauseOfFaulure() as non null Throwable. What it does is that when we are dealing with FlowNodes and trying to determine if stage failed, does not work in this case and ends up reporting SUCCESS of overall run where its in fact was a failure. run.getResult() gives correct value as FAILURE. Andrew Bayer This is the issue I mentioned you over chat.
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful - when using Kyoto
Title: Message Title Michael Neale commented on JENKINS-38012 Re: Pipeline has failed but its only stage is successful - when using Kyoto Vivek Pandey it likely is pulling down a docker image - so it will take time depending on the connection. Perhaps this is specific to when steps happen in docker... There is going to be a new pipeline model release in the next day, so perhaps we can try again then. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37166) Update the styling of the test result content
Title: Message Title James Dumay updated JENKINS-37166 Jenkins / JENKINS-37166 Update the styling of the test result content Change By: James Dumay Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay edited a comment on JENKINS-37878 Re: Implement a DisplayURLProvider for Blue Ocean Most plugins have been converted over to use this API:* Github branch source https://github.com/jenkinsci/github-branch-source-plugin/pull/75* Bitbucket branch source https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/17* Email https://github.com/jenkinsci/mailer-plugin/pull/29* HipChat https://github.com/jenkinsci/hipchat-plugin/pull/82* Slack https://github.com/jenkinsci/slack-plugin/pull/245* IM https://github.com/jenkinsci/instant-messaging-plugin/pull/15** IRC https://github.com/jenkinsci/ircbot-plugin/pull/17 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay edited a comment on JENKINS-37878 Re: Implement a DisplayURLProvider for Blue Ocean Most plugins have been converted over to use this API:* Github branch source https://github.com/jenkinsci/github-branch-source-plugin/pull/75* Email https://github.com/jenkinsci/mailer-plugin/pull/29* HipChat https://github.com/jenkinsci/hipchat-plugin/pull/82* Slack https://github.com/jenkinsci/slack-plugin/pull/245* IM https://github.com/jenkinsci/instant-messaging-plugin/pull/15** IRC https://github.com/jenkinsci/ircbot-plugin/pull/17 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-37878 Implement a DisplayURLProvider for Blue Ocean Change By: James Dumay Assignee: Vivek Pandey Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38047) Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc
Title: Message Title Andrew Bayer commented on JENKINS-38047 Re: Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/9... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38047) Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc
Title: Message Title Andrew Bayer updated JENKINS-38047 Jenkins / JENKINS-38047 Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38047) Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc
Title: Message Title Andrew Bayer started work on JENKINS-38047 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38013) Profile and minifi blue ocean loading
Title: Message Title James Dumay commented on JENKINS-38013 Re: Profile and minifi blue ocean loading Tom FENNELLY it looks like resources such as icons and fonts get reloaded often too. Could you investigate that as part of this? Ideally we would only bust the cache on these when the Blue Ocean version changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-38048 credentials id dropdown not populated Issue Type: Bug Assignee: Jesse Glick Attachments: image-2016-09-08-11-04-24-356.png Components: workflow-cps-global-lib-plugin Created: 2016/Sep/08 1:15 AM Environment: Clean docker env - jenkinsci/jenkin - 2.7.1 - recommended plugin loadout + workflow-cps-global-lib (2.3) + workflow-remote-loader (1.2) Priority: Minor Reporter: Ben Walding Adding a "Legacy SCM" git repository. The credentials ID drop down does not populate from existing items, nor do new items get added if I add them while editing the configuration. Console messages These may or may not be relevant (they seem relevant to me) hudson-behavior.js:417 Uncaught TypeError: Cannot read property 'firstChild' of undefinedregisterValidator @ hudson-behavior.js:417(anonymous function) @ behavior.js:111(anonymous function) @ behavior.js:107applySubtree @ behavior.js:93(anonymous function) @ select.js:251 hudson-behavior.js:472 Unable to find nearby scm/id
[JIRA] (JENKINS-38012) Pipeline has failed but its only stage is successful - when using Kyoto
Title: Message Title James Dumay commented on JENKINS-38012 Re: Pipeline has failed but its only stage is successful - when using Kyoto Good to know you're on it Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37425) Rework the behavior of Toasts for Run, Stop and Replay
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37425 Rework the behavior of Toasts for Run, Stop and Replay Change By: James Dumay Sprint: 1.0-pre-beta-1, 1.0-beta- 1 2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37425) Rework the behavior of Toasts for Run, Stop and Replay
Title: Message Title James Dumay commented on JENKINS-37425 Re: Rework the behavior of Toasts for Run, Stop and Replay Cliff Meyers lets punt this over to the next sprint then Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37667 Use ForkScanner to build DAG (ie adapt to bismuth api) Change By: James Dumay Sprint: 1.0-beta- 3 2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38047) Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-38047 Allow multiple positional (i.e., unnamed) parameters in Pipeline Model Definition steps etc Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/08 1:00 AM Environment: Pipeline Model 0.1 Priority: Critical Reporter: Andrew Bayer The declarative subset rule says that if you have multiple parameters to a step/function/whatever in the model, they have to be named parameters. That's causing problems - any pre-existing global library method with multiple parameters (and a closure body - not 100% sure this bombs out when you don't have a closure body, but this is bad enough as is!) will not work outside of a script block. That'd be bad enough on its own, but wait, it gets worse! The sandbox is somehow swallowing the MissingMethodException that's getting thrown when Groovy is looking for someMethod(Map, CpsClosure), resulting in the method never being executed without any error or explanation. That, my friends, is Bad. So...since I can't figure out how to deal with that swallowed exception for the life of me, I'm intending to remove the named parameters requirement. Yay.
[JIRA] (JENKINS-37603) Favourite icons do not have hover style
Title: Message Title Cliff Meyers updated JENKINS-37603 Jenkins / JENKINS-37603 Favourite icons do not have hover style Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title Cliff Meyers updated JENKINS-36895 Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37667 Use ForkScanner to build DAG (ie adapt to bismuth api) Change By: Michael Neale BlueOcean /nodes and /steps API use FlowGraphWalker to build it's DAG. This is not very efficient. It should be replaced with ForkScanner ( WIP, soon to be released AKA "bismuth api" ), it brings in optimizations (SAX style parser etc.). [~hrmpw] also says this needs more jargon in the title. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37667 Use ForkScanner to build DAG (ie adapt to bismuth api) Change By: James Dumay Sprint: 1.0-beta-3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37667 Use ForkScanner to build DAG (ie adapt to bismuth api) Change By: Michael Neale Summary: Use ForkScanner to build DAG (ie adapt to bismuth api) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Andrew Bayer commented on JENKINS-37932 Re: Error if no "agent" specified James Dumay Open a JIRA and give me a sense of what you mean? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG
Title: Message Title James Dumay commented on JENKINS-37667 Re: Use ForkScanner to build DAG Michael Neale gotcha Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38039) Developer wants to see the branch and PR list ordered by most recent
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38039 Developer wants to see the branch and PR list ordered by most recent Change By: James Dumay *In Scope*Order the collections returned in the rest API for Branches and PRs:* Favourited items appear at the top of the list, ordered by recently started* All other items appear after favourites, orders by recently started Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title James Dumay commented on JENKINS-37932 Re: Error if no "agent" specified We should also improve the error message for agent none Andrew Bayer tangentally, I think it would be pretty awesome if the error messages referred to our new docs on Jenkins.io WDYT? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG
Title: Message Title Michael Neale commented on JENKINS-37667 Re: Use ForkScanner to build DAG This is still relevant James Dumay as this is the new api for pipeline execution Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title James Dumay commented on JENKINS-37932 Re: Error if no "agent" specified Michael Neale though the literals are very nice from a UX perspective - they read like english +1 on any being the default. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37166) Update the styling of the test result content
Title: Message Title Keith Zantow updated JENKINS-37166 Jenkins / JENKINS-37166 Update the styling of the test result content Change By: Keith Zantow Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20959) f:descriptorRadioList does not render contents lazily
Title: Message Title Jesse Glick commented on JENKINS-20959 Re: f:descriptorRadioList does not render contents lazily See also /lib/hudson/project/config-scm.jelly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7192) Use multiple SCM sources
Title: Message Title Jesse Glick resolved as Won't Do Jenkins Pipeline addresses this as a core feature, so I think this can be closed—we do not plan to implement it in freestyle projects. Jenkins / JENKINS-7192 Use multiple SCM sources Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38037) Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14
Title: Message Title Jesse Glick updated JENKINS-38037 Jenkins / JENKINS-38037 Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14 Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38037) Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38037 Re: Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14 Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/plugins/workflow/cps/DSL.java http://jenkins-ci.org/commit/workflow-cps-plugin/a06779a2b831adc8042fa76be7f1f2747a8cb91b Log: [FIXED JENKINS-38037] Single-arg check for executable symbols fix Use the DescribableModel for symbols related to a meta-step when determining whether they should be parsed as having a single required argument. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38036) REGRESSION: read only access not working with github auth plugin and blue ocean
Title: Message Title Michael Neale commented on JENKINS-38036 Re: REGRESSION: read only access not working with github auth plugin and blue ocean I was able to reproduce it locally with github oauth plugin setup, and the following authorizatoin strategy: (same as dogfood): Should let anon read, but doesn't for /blue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38023) Favourite card label does not contain full path
Title: Message Title James Dumay commented on JENKINS-38023 Re: Favourite card label does not contain full path Cliff Meyers lets make the name wrap for now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Jesse Glick updated JENKINS-38045 Jenkins / JENKINS-38045 Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1 Change By: Jesse Glick Status: In Review Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36558) Sort the dashboard alphabetically
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36558 Sort the dashboard alphabetically Change By: James Dumay Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37917) Review permissions API for multi-branch pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37917 Review permissions API for multi-branch pipeline Change By: James Dumay Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38016) Fresh install on 2.7.3 of blueocean requires a restart for API to work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38016 Fresh install on 2.7.3 of blueocean requires a restart for API to work Change By: James Dumay Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38036) REGRESSION: read only access not working with github auth plugin and blue ocean
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38036 REGRESSION: read only access not working with github auth plugin and blue ocean Change By: Michael Neale Attachment: Screen Shot 2016-09-08 at 9.44.07 AM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37017) Github Org folder projects detail screen missing org name in path
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-37017 Github Org folder projects detail screen missing org name in path Change By: James Dumay Assignee: Thorsten Scherler Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35792) User needs to see better error pages
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35792 User needs to see better error pages Change By: James Dumay Sprint: 1.0-m10 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Developer can see a error message inline on a page
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Developer can see a error message inline on a page Change By: James Dumay Sprint: 1.0-m10 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35792) User needs to see better error pages
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35792 User needs to see better error pages Change By: James Dumay Sprint: 1.0-m10 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Developer can see a error message inline on a page
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Developer can see a error message inline on a page Change By: James Dumay Sprint: 1.0-m10 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title James Dumay commented on JENKINS-38044 Re: Following runs in Blue Ocean doesn't show console output Thorsten Scherler speaking further with Tyler about this on IRC, it appears that the Pipeline gets to this step and tries to expand it. No log is shown and the Pipeline does not continue. If he opens then closes the expander, he then sees the log scrolling and the Pipeline continues as per normal. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37427) Handle Matrix project in UI
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-37427 Handle Matrix project in UI Change By: James Dumay Assignee: Thorsten Scherler Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title Mike Kasberg created an issue Jenkins / JENKINS-38046 Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Sep/07 11:38 PM Environment: Jenkins 2.7.3, Gerrit Trigger Plugin 2.22.0 Labels: pipeline Priority: Major Reporter: Mike Kasberg I want to use the new Multibranch Pipeline features of Jenkins with Gerrit source control. I should be able to choose Gerrit as the source for a multibranch pipeline. I should be able to select one or more repositories from Gerrit that each have their own Jenkinsfile. The pipeline would run the Jenkinsfile from the patch set that was pushed to Gerrit. Add Comment
[JIRA] (JENKINS-36781) Display of SCM identifiers should be consistent
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-36781 Display of SCM identifiers should be consistent Change By: James Dumay Assignee: Thorsten Scherler Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38044 Following runs in Blue Ocean doesn't show console output Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-38044 Following runs in Blue Ocean doesn't show console output Change By: James Dumay Sprint: 1.0-beta-1 Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37335) github webhooks not working after changing repository URL with .ssh/config
Title: Message Title Mark Waite resolved as Won't Do No plan to fix this, since it relies on command line git's reference to ssh which then refers to the .ssh/config file for a hostname alias. That's too deep an indirection of information for the use cases handled by the git plugin, Jenkins / JENKINS-37335 github webhooks not working after changing repository URL with .ssh/config Change By: Mark Waite Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-38011) Result header modal does not include full path
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38011 Result header modal does not include full path Change By: James Dumay Summary: modal Result header is incorrect for multi-branch pipeline modal does not include full path Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37017) Github Org folder projects detail screen missing org name in path
Title: Message Title James Dumay commented on JENKINS-37017 Re: Github Org folder projects detail screen missing org name in path Thorsten Scherler this should have the full path to the Pipeline in the summary pages header. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay resolved as Duplicate Duplicates JENKINS-38011. Thanks for the report Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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-38011) modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38011 modal header is incorrect for multi-branch pipeline Change By: James Dumay Summary: REGRESSION: modal header is incorrect for multi-branch pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38011) REGRESSION: modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay commented on JENKINS-38011 Re: REGRESSION: modal header is incorrect for multi-branch pipeline Thorsten Scherler ahh OK perhaps not a regression. Can we please include the full name of the pipeline (Organization, Folders, Pipeline Name and Branch) in the header? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title R. Tyler Croy commented on JENKINS-38044 Re: Following runs in Blue Ocean doesn't show console output James Dumay, it's linked right there. Here's a NON HYPERLINKED VERSION https://github.com/reiseburo/verspaetung/blob/master/Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38011) REGRESSION: modal header is incorrect for multi-branch pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38011 REGRESSION: modal header is incorrect for multi-branch pipeline Change By: James Dumay At some point we broke the navigation and naming of the multi-branch PipelineThis Pipeline is called "Jenkins / App Store" !Jenkins Blue Ocean 2016-09-07 13-23-36.png|thumbnail! If I open a run the name is "Jenkins / master" but should be "Jenkins / App Store / master" ! Jenkins Blue Ocean Screenshot from 2016-09-07 13 18 - 23 28 - 36 48 .png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay reopened an issue Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38023) Favourite card label does not contain full path
Title: Message Title
Ben Walding edited a comment on JENKINS-38023
Re: Favourite card label does not contain full path
The folder layout that triggered this ticket is shown below [1]The problem is coming up with something sane without requiring twenty configuration options. In my case I need the last 2 items - others might be different. I don't think my example is too far off base though - given how multi-branch pipelines work and how you generally want to organise jobs in Jenkins.I also think the favourite cards should match the non-favourite cards (in a given size) - no matter the rules.(Off topic - the leading "Jenkins" is redundant in my current world-view)[1]{noformat}Applications (folder) www. cloudbees example .com (folder)build (multi-branch pipeline)deploy-staging (pipeline)deploy-production (pipeline) go login . cloudbees example .com (folder)build (multi-branch pipeline)deploy-staging (pipeline)deploy-production (pipeline) ... lots and lots more ...{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38023) Favourite card label does not contain full path
Title: Message Title Ben Walding commented on JENKINS-38023 Re: Favourite card label does not contain full path The folder layout that triggered this ticket is shown below [1] The problem is coming up with something sane without requiring twenty configuration options. In my case I need the last 2 items - others might be different. I don't think my example is too far off base though - given how multi-branch pipelines work and how you generally want to organise jobs in Jenkins. I also think the favourite cards should match the non-favourite cards (in a given size) - no matter the rules. (Off topic - the leading "Jenkins" is redundant in my current world-view) [1] Applications (folder) www.cloudbees.com (folder) build (multi-branch pipeline) deploy-staging (pipeline) deploy-production (pipeline) go.cloudbees.com (folder) build (multi-branch pipeline) deploy-staging (pipeline) deploy-production (pipeline) ... lots and lots more ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Andrew Bayer commented on JENKINS-38045 Re: Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1 Added to PR 53 (https://github.com/jenkinsci/workflow-cps-plugin/pull/53). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Andrew Bayer started work on JENKINS-38045 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Andrew Bayer updated JENKINS-38045 Jenkins / JENKINS-38045 Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1 Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Include the full path of the pipeline in the result header
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38043 Include the full path of the pipeline in the result header Change By: James Dumay Summary: Build detail view for job Include the full path of the pipeline in GitHub Organization Folder is incorrect the result header Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title James Dumay commented on JENKINS-38044 Re: Following runs in Blue Ocean doesn't show console output R. Tyler Croy can you please include a git repository or Jenkinsfile for us to use in reproduction? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Jesse Glick commented on JENKINS-38045 Re: Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1 Duplicate of a bug I already fixed, just need to update structs I think. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38045) Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-38045 Stack overflow in SymbolLookup.getValue() with non-existent function on core 2.7.1 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: structs-plugin Created: 2016/Sep/07 11:06 PM Environment: Core 2.7.1, structs 1.5, workflow-cps 2.15-SNAPSHOT Priority: Major Reporter: Andrew Bayer When running DSLTest.nonexistentFunctions() against core 2.7.1, I get a stack overflow: java.lang.StackOverflowError at jenkins.model.Jenkins.getExtensionList(Jenkins.java:2357) at jenkins.model.Jenkins.getDescriptor(Jenkins.java:1288) at org.jenkinsci.plugins.structs.SymbolLookup.getSymbolValue(SymbolLookup.java:189) at org.jenkinsci.plugins.structs.SymbolLookup.getSymbolValue(SymbolLookup.java:171) at org.jenkinsci.plugins.structs.SymbolLookup.getSymbolValue(SymbolLookup.java:190) at org.jenkinsci.plugins.structs.SymbolLookup.getSymbolValue(SymbolLookup.java:171) at org.jenkinsci.plugins.structs.SymbolLookup.getSymbolValue(SymbolLookup.java:190) (etc)
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title R. Tyler Croy commented on JENKINS-38044 Re: Following runs in Blue Ocean doesn't show console output I should note, that my Pipeline is this one and I think the fact that the first stage does not have a sh in it is part of the reproduction case. With another Pipeline, that starts with a sh right in the first stage, that seems to start (shows a little bit of console output), but doesn't "follow" the console output as the sh step continues to emit output (it puts out a lot) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38044) Following runs in Blue Ocean doesn't show console output
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-38044 Following runs in Blue Ocean doesn't show console output Issue Type: Bug Assignee: Unassigned Attachments: blue-ocean-shell-script.png, legacy-shell-script.png Components: blueocean-plugin Created: 2016/Sep/07 11:00 PM Environment: Jenkins 2.7.3. Blue Ocean Built at 7th September 2016 10:13 AM · (no branch) · ecb790d Priority: Minor Reporter: R. Tyler Croy I have noticed this weird anomaly with a Pipeline, when following along at home (karaoke mode I think you call it). When I hit a stage with a sh step, the step is rendered as if it is "open" (arrow pointing down), but there is no console output being emitted. The UI seems to be stuck there, and won't continue to the next stage's steps. Interestingly enough, clicking the step "closed" and then "re-opening" it, seems to unfreeze the interface
[JIRA] (JENKINS-38037) Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14
Title: Message Title Andrew Bayer commented on JENKINS-38037 Re: Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14 Figured it out - sigh. PR up at https://github.com/jenkinsci/workflow-cps-plugin/pull/53. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38037) Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14
Title: Message Title Andrew Bayer updated JENKINS-38037 Jenkins / JENKINS-38037 Single parameter metasteps don't work with named-parameter symbols as of workflow-cps 2.14 Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38043) Build detail view for job in GitHub Organization Folder is incorrect
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-38043 Build detail view for job in GitHub Organization Folder is incorrect Issue Type: Bug Assignee: Unassigned Attachments: gh-org-folder-wrong-name.png, master-branch-full.png Components: blueocean-plugin Created: 2016/Sep/07 10:55 PM Environment: Jenkins 2.7.3, Blue Ocean Built at 7th September 2016 10:13 AM · (no branch) · ecb790d Priority: Minor Reporter: R. Tyler Croy I have a GitHub Org Folder "Reiseburo" with a repository "verspaetung" inside of it. When navigating to any "detail" view, the title is incorrectly listed as "jenkins / reiseburo / master" which makes it unclear which repository in the org folder this is coming from. Add Comment
[JIRA] (JENKINS-38042) Blue Ocean does not render the GitHub Organization Folder "Display Name"
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38042 Blue Ocean does not render the GitHub Organization Folder "Display Name" Change By: James Dumay Sprint: 1.0-beta-3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
