[JIRA] (JENKINS-41741) wrong parameters order with Jenkins Parameterized Trigger plugin
Title: Message Title Vincent Bricard-Vieu created an issue Jenkins / JENKINS-41741 wrong parameters order with Jenkins Parameterized Trigger plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2017/Feb/06 7:57 AM Environment: job-dsl-plugin 1.57 parameterized trigger plugin 2.32 jenkins 2.19.4 Labels: plugins Priority: Blocker Reporter: Vincent Bricard-Vieu when generating a parameterized trigger build, I want to run the current project with the same parameters except a boolean I want to switch In my DSL groovy script, I tried the options: same node current build boolean parameter but I got boolean parameter same node current build This above order is always the same, whatever the order of commands I specified in script The boolean parameter I want is overriden by current build whereas it should be the contrary. I prefer that the order of generated components matches the order of commands in groovy DSL. I tried automatically
[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Marten Lootsma commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Hi Marco Steffan, I'd like to give your plugin modifications a try as well. I tried to create the plugin by cloning the repository and building it with maven, but then I ran in some (noob?) problems. git clone g...@github.com:jenkinsci/cppcheck-plugin.git cd cppcheck-plugin/ git checkout jenkins-35096_cppcheck_plugin_pipeline_support mvn packge Then I got the following error below. Did I do something wrong? [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.jenkins-ci.plugins:cppcheck:1.22-SNAPSHOT: Failure to find org.jenkins-ci.plugins:plugin:pom:2.16 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 4, column 13 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jenkins-ci.plugins:cppcheck:1.22-SNAPSHOT (/home/marten/Projects/cppcheck-plugin/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.jenkins-ci.plugins:cppcheck:1.22-SNAPSHOT: Failure to find org.jenkins-ci.plugins:plugin:pom:2.16 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 4, column 13 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Add Comment
[JIRA] (JENKINS-41582) Change official docker image to not use alpine
Title: Message Title R. Tyler Croy commented on JENKINS-41582 Re: Change official docker image to not use alpine I'm not sure I'm understanding what you're asking Michael Neale. I believe there is a fundamental misunderstanding of how our docker images are working here. Regardless of whether something is alpine or Debian-based, they both provide plenty of developer tools through their respective package managers. HOWEVER, the Jenkins Docker image drops the root permission, a standard best practice for distributed images such as ours (USER jenkins in the Dockerfile), which means that the jenkins user does not have root permissions. That means regardless of what base image we start with, the jenkins user would not be able to install additional packages unless it was run in a non-standard way as root. Perhaps a better solution would be to fix up this pull request and suggest that people mount their /var/run/docker.sock so the blueocean'd Jenkins master would have access to a functional Docker daemon? 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-41668) No way to specify directory for dockerfile
Title: Message Title James Dumay commented on JENKINS-41668 Re: No way to specify directory for dockerfile This pain point showed up on the user list https://groups.google.com/forum/m/#!topic/jenkinsci-users/NnX_PviNY2A 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-40439) Move parsers into external library
Title: Message Title Tuukka Mustonen commented on JENKINS-40439 Re: Move parsers into external library Well... unfortunately I think this didn't fly. Should probably be closed? 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-41717) Blue Ocean - Steps section should show full log for given step.
Title: Message Title mishal shah commented on JENKINS-41717 Re: Blue Ocean - Steps section should show full log for given step. Thanks James Dumay! 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-41664) Blue Ocean fails to load in MS Edge (Eventsource)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41664 Blue Ocean fails to load in MS Edge (Eventsource) Change By: Michael Neale Summary: Blue Ocean fails to load in MS Edge ( Even source Eventsource ) 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-41664) Blue Ocean fails to load in MS Edge
Title: Message Title Michael Neale commented on JENKINS-41664 Re: Blue Ocean fails to load in MS Edge Added this one to current sprint just in case. I think Keith picked this one up too. I am slightly confused as I thought the polyfill was loaded in any case and would kick in if there was no event source? (at least last I spoke to Tom, this was the theory). 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-41664) Blue Ocean fails to load in MS Edge (Even source)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41664 Blue Ocean fails to load in MS Edge (Even source) Change By: Michael Neale Summary: Blue Ocean fails to load in MS Edge (Even source) 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-41664) Blue Ocean fails to load in MS Edge
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41664 Blue Ocean fails to load in MS Edge Change By: Michael Neale Sprint: iapetus 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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Hi Sorry for the noise, I got this working now. I re-read the documentation at https://jenkins.io/doc/book/pipeline/shared-libraries/ and found this piece of text which I think it was not there the first time I read it??For Shared Libraries which only define Global Variables (vars/), or a Jenkinsfile which only needs a Global Variable, the annotation pattern @Library('my-shared-library') _ may be useful for keeping code concise. In essence, instead of annotating an unnecessary import statement, the symbol _ is annotated.??Anyway, basically now (without using the [permissive plugin script|https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin] ) this is working using the notation by switching*@Library('library@BranchName') \_ * instead of: * @Library('library@BranchName')** import foo*where {{foo}} is a file in */var/foo.groovy* with the following notation: *@Library('library@BranchName') \_* I bit anti-intuitive for me, but hey.. I'm happy that this is working
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Hi Sorry for the noise, I got this working now. I re-read the documentation at https://jenkins.io/doc/book/pipeline/shared-libraries/ and found this piece of text which I think it was not there the first time I read it??For Shared Libraries which only define Global Variables (vars/), or a Jenkinsfile which only needs a Global Variable, the annotation pattern @Library('my-shared-library') _ may be useful for keeping code concise. In essence, instead of annotating an unnecessary import statement, the symbol _ is annotated.??Anyway, basically now (without using the [permissive plugin script|https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin] ) this is working using the notation*@Library('library@BranchName') \_*instead of:*@Library('library@BranchName')**import foo*where {{foo}} is a file in {{ * /var/foo.groovy }} *
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum commented on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Hi Sorry for the noise, I got this working now. I re-read the documentation at https://jenkins.io/doc/book/pipeline/shared-libraries/ and found this piece of text which I think it was not there the first time I read it For Shared Libraries which only define Global Variables (vars/), or a Jenkinsfile which only needs a Global Variable, the annotation pattern @Library('my-shared-library') _ may be useful for keeping code concise. In essence, instead of annotating an unnecessary import statement, the symbol _ is annotated. Anyway, basically now (without using the permissive plugin script ) this is working using the notation @Library('library@BranchName') _ instead of: @Library('library@BranchName') import foo where foo is a file in {{ /var/foo.groovy}}
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Just checking if the issue I'm seeing is the same as this one.I have a [global shared library|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin] setup that works fine, but when I try to run something from a branch using the _Library ('library @ BranchName_ BranchName')_ notation I get the {{hudson.remoting.ProxyException: groovy.lang.MissingMethodException:}} exception The thing is that I'm running the job with the admin user which has full permissions. Also, the exception is not logged in under *In-process Script Approval* so I can not whitelist it.Is this another bug or is it the same? Do you need logs or something?Since we do trust all the authenticated users and since we are using github enterprise as the backend for the global shared library, we have every branch created and every commit logged, so I gave the [permissive plugin script|https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin] a try, but did not work. If the configuration toggle is not going to be implemented, I think my next step is to recompile this plugin with the sandbox disable?
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-41740) Show empty state on the Activity, Branch and PR tab when there are no branches
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41740 Show empty state on the Activity, Branch and PR tab when there are no branches Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 4:33 AM Priority: Minor Reporter: James Dumay In Scope Show a message on the activity, branch and pr tab when there are no branches "Learn more" should link to the documentation at http://jenkins.io/doc/ should only show for multibranch pipelines Zeplin https://zpl.io/15eMCT Add Comment
[JIRA] (JENKINS-41739) Update empty state on the Branch and PR tab when job is not multibranch pipeline
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41739 Update empty state on the Branch and PR tab when job is not multibranch pipeline Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 4:31 AM Priority: Minor Reporter: James Dumay In Scope Style update for the existing non-multibranch pipeline messaging on the branch and PR tabs to match https://zpl.io/mYebh Check to make sure that it never shows for multibranch pipeline but shows for pipeline, freestyle, maven, etc Add Comment
[JIRA] (JENKINS-41738) Empty state for when there are no pipelines in the organization folder
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41738 Empty state for when there are no pipelines in the organization folder Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 4:29 AM Priority: Minor Reporter: James Dumay Requires that we group pipelines on the dashboard by organization JENKINS-40209. In Scope Show an empty state when there are no pipelines in the org folder "Check again" button rescans the organization Zeplin: https://zpl.io/dGvgd Add Comment
[JIRA] (JENKINS-41737) Dashboard screen when there are no pipelines
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41737 Dashboard screen when there are no pipelines Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 3:55 AM Priority: Minor Reporter: James Dumay In Scope Empty state for the dashboard when there are no pipelines create pipeline should link to the creation flow zeplin https://zpl.io/Z22SNPa Add Comment
[JIRA] (JENKINS-41150) Allow flyway to be installed automatically
Title: Message Title Suresh Kumar closed an issue as Fixed Fixed and released in version 1.7 Jenkins / JENKINS-41150 Allow flyway to be installed automatically Change By: Suresh Kumar Status: Open Closed Assignee: Suresh Kumar Keith Collison 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
[JIRA] (JENKINS-41520) Build description is not rendered properly
Title: Message Title Suresh Kumar commented on JENKINS-41520 Re: Build description is not rendered properly Michal Gauza Let me know which version browser you are using. and if possible provide further information to replicate this issue it helps me to fix and release patch. 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-41619) NPE in Pipeline Step after update
Title: Message Title Suresh Kumar commented on JENKINS-41619 Re: NPE in Pipeline Step after update Andreas Steffens Let me know from which version you have upgraded plugin to latest version and the configuration of previous version. So that I can verify the bug and if possible will release a patch once we were able to replicate the issue. 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean *In Scope** Form elements should come with a way of providing a description** Update to match the zeplin links brody has provided in the comments* Description should appear between the element label and value.* Update the job parameter dialog and input step so that it uses the form element description* The primary button should be first* Checkbox group (even if only 1) needs a title, as per the design.* Checkbox on left with label on the right* Radio group title at top, not bottom.That means a form input should be displayed in this order:* Label* Description* Value (radios, checkbox, etc) Zeplin - https://zpl.io/Z20esxf !Pasted_Image_6_2_17__12_21_pm.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
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title James Dumay commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch Oleg Korsak just to clarify, we won't be providing a view where you can see all the pipeline visualizations for multiple runs in one case. At this time we unable to make the design scale well to work with our visualization. Pipeline Stage View. However, you will be able to use the filter to see all the active runs for a particular branch with the completion of this ticket. We will have other links that can jump you to the activity tab filtered to a specific branch. 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean edited a comment on JENKINS-41341 Re: Standardize form descriptions https://zpl.io/Z20esxf ! Modal Form Pasted_Image_6_2_17__12_21_pm .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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean *In Scope** Form elements should come with a way of providing a description** Update to match the zeplin links brody has provided in the comments* Description should appear between the element label and value.* Update the job parameter dialog and input step so that it uses the form element description* The primary button should be first* See "Modal Form.png" top mockup, addressing issues with bottom design* Checkbox group (even if only 1) needs a title, as per the design.* Checkbox on left with label on the right* Radio group title at top, not bottom.That means a form input should be displayed in this order:* Label* Description* Value (radios, checkbox, etc) 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
[JIRA] (JENKINS-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean Attachment: Modal Form.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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Michael Neale commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch Oleg Korsak yes, I believe there is another ticket covering that specifically (needs this one first though). 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean Attachment: Pasted_Image_6_2_17__12_21_pm.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-41341) Standardize form descriptions
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: James Dumay Attachment: Parametrized example 2017-01-24 08-09-17.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-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41736
Better descriptions for jenkins.branch.BranchEventCause
Change By:
James Dumay
We want to display the hudson.model.CauseAction "short description" on the UI in Blue Ocean. However, the {{BranchEventCause}} has a pretty generic description that isn't meaningful to the user.Could we have a better cause description for the branch events?"Pull Request opened by i386" etc ?*Example of current cause action as reported to Blue Ocean *{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
[JIRA] (JENKINS-41365) Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab
Title: Message Title James Dumay commented on JENKINS-41365 Re: Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab Michael Neale I'd have to go through testing this again. Not too worried at the moment as we are not officially targeting Bitbucket for 1.0. 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-41365) Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab
Title: Message Title Michael Neale commented on JENKINS-41365 Re: Pipeline with Bitbucket sources do not show Pull Requests on the Pull Requests tab James Dumay - beta with the latest SCM any better with this? Could this be the same as we saw with github where a restart made it show up? Did it show up in the classic PR view but not blue ocean? 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40979
Developer would like to see why the Pipeline has been triggered
Change By:
James Dumay
*Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message cell should be the trigger reason. !message.png|thumbnail! *Notes*Would be good to do in conjunction with JENKINS-39860. *Technical details*There should be an action on each run like:{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}You want to pick the first "cause" from that array. Every cause has a {{shortDescription}}.EDIT: I realise in this example that the cause is pretty meaningless to users and have asked for this particular description to be fixed in JENKINS-41736.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40979
Developer would like to see why the Pipeline has been triggered
Change By:
James Dumay
Comment:
There should be an action on each run like:{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}You want to pick the first "cause" from that array. Every cause has a {{shortDescription}}.EDIT: I realise in this example that the cause is pretty meaningless to users and have asked for this particular description to be fixed in JENKINS-41736.
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Just checking if the issue I'm seeing is the same as this one.I have a [ global shared library| http://example.com]( https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin] setup that works fine, but when I try to run something from a branch using the _Library@BranchName_ notation I get the {{ hudson.remoting.ProxyException: groovy.lang.MissingMethodException:}} exception The thing is that I'm running the job with the admin user which has full permissions. Also, the exception is not logged in under *In-process Script Approval* so I can not whitelist it.Is this another bug or is it the same? Do you need logs or something?Since we do trust all the authenticated users and since we are using github enterprise as the backend for the global shared library, we have every branch created and every commit logged, so I gave the [permissive plugin script|https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin] a try, but did not work. If the configuration toggle is not going to be implemented, I think my next step is to recompile this plugin with the sandbox disable?
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Just checking if the issue I'm seeing is the same as this one.I have a _ [ global shared library_ library|http://example.com] (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin ) ] setup that works fine, but when I try to run something from a branch using the _Library@BranchName_ notation I get the {{ hudson.remoting.ProxyException: groovy.lang.MissingMethodException:}} exception The thing is that I'm running the job with the admin user which has full permissions. Also, the exception is not logged in under *In-process Script Approval* so I can not whitelist it.Is this another bug or is it the same? Do you need logs or something?Since we do trust all the authenticated users and since we are using github enterprise as the backend for the global shared library, we have every branch created and every commit logged, so I gave the [permissive plugin script| https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin ] a try, but did not work. If the configuration toggle is not going to be implemented, I think my next step is to recompile this plugin with the sandbox disable?
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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay edited a comment on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
There should be an action on each run like:{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}You want to pick the first "cause" from that array. Every cause has a {{shortDescription}}.EDIT: I realise in this example that the cause is pretty meaningless to users and have asked for this particular cause description to be fixed in JENKINS-41736.
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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay edited a comment on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
There should be an action on each run like:{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}You want to pick the first "cause" from that array. Every cause has a {{shortDescription}}. EDIT: I realise in this example that the cause is pretty meaningless to users and have asked for this particular cause to be fixed in JENKINS-41736.
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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Federico Naum commented on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Just checking if the issue I'm seeing is the same as this one. I have a _ global shared library_ (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin) setup that works fine, but when I try to run something from a branch using the Library@BranchName notation I get the {{ hudson.remoting.ProxyException: groovy.lang.MissingMethodException:}} exception The thing is that I'm running the job with the admin user which has full permissions. Also, the exception is not logged in under In-process Script Approval so I can not whitelist it. Is this another bug or is it the same? Do you need logs or something? Since we do trust all the authenticated users and since we are using github enterprise as the backend for the global shared library, we have every branch created and every commit logged, so I gave the https://wiki.jenkins-ci.org/display/JENKINS/Permissive+Script+SecuIrity+Plugin a try, but did not work. If the configuration toggle is not going to be implemented, I think my next step is to recompile this plugin with the sandbox disable?
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-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41736
Better descriptions for jenkins.branch.BranchEventCause
Change By:
James Dumay
We want to display the hudson.model.CauseAction "short description" on the UI in Blue Ocean. However, the {{BranchEventCause}} has a pretty generic description that isn't meaningful to the user .Could we have a better cause description for the branch events?"Pull Request opened by i386" etc ?*Example of current cause*{code}{ "_class": "hudson.model.CauseAction", "_links": {"self": { "_class": "io.jenkins.blueocean.rest.hal.Link", "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"} }, "causes": [{ "_class": "jenkins.branch.BranchEventCause", "shortDescription": "Branch event"} ], "urlName": "cause"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay commented on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
There should be an action on each run like:
{
{
"_class": "hudson.model.CauseAction",
"_links": {
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"
}
},
"causes": [
{
"_class": "jenkins.branch.BranchEventCause",
"shortDescription": "Branch event"
}
],
"urlName": "cause"
}
You want to pick the first "cause" from that array. Every cause has a shortDescription.
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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean *In Scope** Form elements should come with a way of providing a description** Update to match the zeplin links brody has provided in the comments* Description should appear between the element label and value.* Update the job parameter dialog and input step so that it uses the form element description* The primary button should be first*See "Modal Form.png" top mockup, addressing issues with bottom design * That means a form input should be displayed in this order:* Label* Description* Value (radios, checkbox, etc) 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-41735) Investigate acceptability of overall performance
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41735 Investigate acceptability of overall performance Issue Type: Story Assignee: Keith Zantow Components: blueocean-plugin Created: 2017/Feb/06 12:46 AM Priority: Minor Reporter: Michael Neale As chatted about on various forums - an overview of the performance (web, resource loading, end to end) is needed to see if we have any blockers for a release candidate. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-41735) Investigate acceptability of overall performance
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41735 Investigate acceptability of overall performance Change By: Michael Neale Sprint: panthalassa iapetus 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
Michael Neale commented on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
Josh McDonald there should be enough data to show what the trigger was already in the row data. The text can be "Triggered by {reason} " type of thing
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-41734) User Education
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41734 User Education Issue Type: Epic Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 12:36 AM Priority: Minor Reporter: James Dumay 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
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title Federico Naum assigned an issue to Federico Naum Jenkins / JENKINS-28178 Option to disable sandbox in CpsScmFlowDefinition Change By: Federico Naum Assignee: Jesse Glick Federico Naum 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-41731) Allow the access to the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo updated an issue Jenkins / JENKINS-41731 Allow the access to the current user's role(s) in the Jenkins 2 pipeline Change By: Jose A. Iñigo It would be great to be able to access the current user's assigned role(s) in the Jenkins 2 pipelines.This would come in handy to determine wether whether the current user is allowed to execute some steps/stages. 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-41731) Allow the access to the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo updated an issue Jenkins / JENKINS-41731 Allow the access to the current user's role(s) in the Jenkins 2 pipeline Change By: Jose A. Iñigo Summary: Allow the access of to the current user's role(s) in the Jenkins 2 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-41642) Handle when favouriting a pipeline fails
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41642 Handle when favouriting a pipeline fails Change By: James Dumay Issue Type: Improvement Bug 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-38460) Move toasts from bottom left to bottom right
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38460 Move toasts from bottom left to bottom right Change By: James Dumay Sprint: post- release candidate 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-41008) Display elapsed time on hover of running job icon
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-41008 Display elapsed time on hover of running job icon 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-40887) Update ChangeSet API for a span of failing runs to be inclusive
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40887 Update ChangeSet API for a span of failing runs to be inclusive Change By: James Dumay Sprint: post- release candidate 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-41200) Developer can see ANSI color in log file
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41200 Developer can see ANSI color in log file Change By: James Dumay Sprint: post- release candidate 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-41293) Testing and upgrading of SCM changes
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41293 Testing and upgrading of SCM changes Change By: James Dumay Sprint: pannonian , iapetus 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-41293) Testing and upgrading of SCM changes
Title: Message Title James Dumay updated JENKINS-41293 Jenkins / JENKINS-41293 Testing and upgrading of SCM changes 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41638 "Open Blue Ocean" button doesn't work unless the server URL is set correctly 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-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38751 Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job 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-41280) Hide organization prefix from UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41280
Hide organization prefix from UI
Change By:
James Dumay
It is confusing to have these prefixes in the UI.*In Scope** Hide the organization prefix the Dashboard, Summary and Result screens + anywhere else we display the organization name * * May need to go through all the screens to find them* Use {{blueocean.organizations.enabled}} system property to enable/disable them
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-41540) Need to show the "cause of blockage" message for a Pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41540 Need to show the "cause of blockage" message for a Pipeline Change By: James Dumay Sprint: panthalassa release candidate 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-41579) API for Pipeline level for causeOfBlockage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41579 API for Pipeline level for causeOfBlockage Change By: James Dumay Sprint: pannonian release candidate , panthalassa pannonian 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-41579) API for Pipeline level for causeOfBlockage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41579 API for Pipeline level for causeOfBlockage Change By: James Dumay Sprint: pannonian , panthalassa 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-41579) API for Pipeline level for causeOfBlockage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41579 API for Pipeline level for causeOfBlockage Change By: James Dumay Sprint: pannonian , iapetus 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-41540) Need to show the "cause of blockage" message for a Pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41540 Need to show the "cause of blockage" message for a Pipeline Change By: James Dumay Sprint: iapetus 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-41540) Need to show the "cause of blockage" message for a Pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41540 Need to show the "cause of blockage" message for a Pipeline Change By: James Dumay Sprint: panthalassa 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-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay Sprint: panthalassa 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-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay Sprint: iapetus 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-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay 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-40978) Preview release of editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40978 Preview release of editor Change By: James Dumay Priority: Major Blocker 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-41586) Acceptance tests for Pipeline Editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41586 Acceptance tests for Pipeline Editor 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-41611) Pipeline Editor Node Designs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41611 Pipeline Editor Node Designs Change By: James Dumay Sprint: pannonian , panthalassa 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-41611) Pipeline Editor Node Designs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41611 Pipeline Editor Node Designs Change By: James Dumay Sprint: pannonian , iapetus 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-41611) Pipeline Editor Node Designs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41611 Pipeline Editor Node Designs Change By: James Dumay Attachment: Pipeline Editor 2017-02-06 10-26-24.png *Scope** UI & interaction design for nodes * We want this variant !Pipeline Editor 2017-02-06 10-26-24.png|thumbnail! http://codepen.io/brody/pen/JEMGWz 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-41361) Copy icon on the Load/save screen
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41361 Copy icon on the Load/save screen Change By: James Dumay Sprint: panthalassa 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-40638) Undo not capturing values within steps properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40638 Undo not capturing values within steps properly Change By: James Dumay Sprint: tethys, christmas, pannonian , panthalassa 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-41548) Unable to use double quotes and round trip with them
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41548 Unable to use double quotes and round trip with them Change By: James Dumay Sprint: iapetus 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-41548) Unable to use double quotes and round trip with them
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41548 Unable to use double quotes and round trip with them Change By: James Dumay Sprint: panthalassa 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-40638) Undo not capturing values within steps properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40638 Undo not capturing values within steps properly Change By: James Dumay Sprint: tethys, christmas, pannonian , iapetus 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-41361) Copy icon on the Load/save screen
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41361 Copy icon on the Load/save screen Change By: James Dumay Sprint: iapetus 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message cell should be the trigger reason. !message.png|thumbnail!*Notes*Would be good to do in conjunction with JENKINS-39860. 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-39860) messages column in blue ocean should display if there are more commits
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39860 messages column in blue ocean should display if there are more commits Change By: James Dumay Sprint: tasman, release candidate panthalassa 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-38540) Add REST API redirects for /runs and /queue
Title: Message Title James Dumay resolved as Duplicate Merge into JENKINS-40924 Jenkins / JENKINS-38540 Add REST API redirects for /runs and /queue 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Michael Neale Josh McDonald 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-39860) messages column in blue ocean should display if there are more commits
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-39860 messages column in blue ocean should display if there are more commits Change By: James Dumay Assignee: Ivan Meredith Josh McDonald 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: panthalassa 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: iapetus 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-41662) Proceed button fails
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41662 Proceed button fails Change By: James Dumay Sprint: iapetus 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-39860) messages column in blue ocean should display if there are more commits
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39860 messages column in blue ocean should display if there are more commits Change By: James Dumay Sprint: tasman, post- release candidate 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-41541) Support Agent and environment config at a stage level (currently is only global)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41541 Support Agent and environment config at a stage level (currently is only global) Change By: James Dumay Sprint: panthalassa 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-41237) Error result for when creation fails
Title: Message Title James Dumay stopped work on JENKINS-41237 Change By: James Dumay Status: In Progress Open 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-41541) Support Agent and environment config at a stage level (currently is only global)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41541 Support Agent and environment config at a stage level (currently is only global) Change By: James Dumay Sprint: iapetus 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-41237) Error result for when creation fails
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-41237 Error result for when creation fails Change By: James Dumay Assignee: Brody Maclean James Dumay 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Michael Neale Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Brody Maclean Michael Neale 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-41582) Change official docker image to not use alpine
Title: Message Title Michael Neale commented on JENKINS-41582 Re: Change official docker image to not use alpine R. Tyler Croy So you mean that people use docker pipeline (or declarative) always instead of building direct? Would this work with a bind mount like that? 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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message column cell should be the trigger reason. !message.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-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message column should be the trigger reason. !message.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-41733) Review all the table columns and their responsive rules
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41733 Review all the table columns and their responsive rules Issue Type: Task Assignee: Brody Maclean Attachments: C35bRzFWcAAx5bZ.jpg Components: blueocean-plugin Created: 2017/Feb/05 10:55 PM Priority: Minor Reporter: James Dumay https://twitter.com/kohsukekawa/status/828199752470769665 Add Comment
[JIRA] (JENKINS-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40660 Parallel Test Stage in Blue Ocean marks build as successful before completing Change By: Michael Neale Sprint: tethys, iapetus post-release 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-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-40660 Parallel Test Stage in Blue Ocean marks build as successful before completing Change By: Michael Neale Assignee: Michael Neale 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41205 Stage graph unsuitable for large, complex pipelines Change By: James Dumay Sprint: post- release candidate 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.
