[JIRA] (JENKINS-38251) Fetching favorited items for a user is very slow
Title: Message Title Tom FENNELLY commented on JENKINS-38251 Re: Fetching favorited items for a user is very slow This should no longer be the case. The user object is now attached as preloaded data. 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Andrew Melo commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Sorry, James Durmay – I'm not super familiar with JIRA quoting. I can rewrite/edit if it makes it clearer. 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
James Dumay commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Andrew Melo BTW you can wrap code in JIRA in {code} some code {code} to preserve formatting
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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Andrew Melo commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I think the visualization is a second-order optimization, but at least firing off the subordinate nodes would speed things up a lot. And ,as a script writer, if I could hint to you who goes where visually, that would simplify your job 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
Andrew Melo commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
I like it! My only hitch would be trying to describe the dependency that wasn't a series of stages (forgive my pseudo-code) where things would block unnecessarily: stage("checkout") { git checkout XXX } node("linux-ubuntu") { stage("compile") { XXX} } node("linux-centos") { stage ("compile") { XXX } ; stage ("test") { YYY } } It's a contrived example, but I currently do something like: state("checkout") { git checkout XXX } stage("compile") { parallel { node ("linux-ubuntu") { XXX } node ("linux-centos") { XXX } } stage ("test") { node ("linux-centos") { YYY } } which means every part of "compile" has to finish before the "test" phase happens, even if there are available executors. If there's a rewrite in a declarative language, I'd hope that the "test" parts could at least start before all the "compile" stages start. I know it's not what's exposed in the current or blue ocean implementations, but it would be nice to fire off additional nodes/stages without waiting on unnecessary parallel branches.
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-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title Vivek Pandey commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed James Dumay Ah, I see. You are referring to these 'not build' stage/parallels as skipped where I was referring to skipped stage support thats coming up using TagAction (its still in PR stage, https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/47). declarative plugin has new stage status 'SKIPPED_FOR_CONDITIONAL', its represented as SKIPPED run state in corresponding blueocean PR - https://github.com/jenkinsci/blueocean-plugin/pull/608. 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Roman Pickl commented on JENKINS-39887 Re: redmine plugin crashes blue ocean show more link Thanks for the fast response! I'm very sorry to say that actually the error was on my side. the field I introduced in https://github.com/jenkinsci/redmine-plugin/pull/16 and then updated to the newest version of the plugin, I did not save the jobs again. the redmine project was defined as part of the checkout step: checkout([$class: 'SubversionSCM', additionalCredentials: [], browser: [$class: 'RedmineRepositoryBrowser', repositoryId: 'example_project', *repositoryOffset: '/trunk'*], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[credentialsId: '123', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: SVN_URL]], workspaceUpdater: [$class: 'UpdateUpdater']]) sorry :| 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Matthew Douglass commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed I too just ran into this bug. We deleted a job to clear out old history, recreated it and all of our builds now fail because of milestones on an old version. I highly disagree with the milestone data surviving deletion of the entire job. Given the current architecture, if I ever delete a job that uses milestones than that job name is forever unusable on that server. That seems highly undesirable to me. 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Matthew Douglass reopened an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Matthew Douglass Resolution: Not A Defect Status: Closed 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Matthew Douglass updated an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Matthew Douglass Priority: Minor 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-39905) Wrong Path for BitbucketWeb Source Files
Title: Message Title
Christoph Forster edited a comment on JENKINS-39905
Re: Wrong Path for BitbucketWeb Source Files
I have the following Setup:* Jenkins 2.32* Git Plugin 3.0.0* Pipeline Plugin 2.4 (Pipeline SCM Plugin 2.3)* Atlassian Bitbucket v4.9.1MyPipeline Source looks like {code}checkout([$class: 'GitSCM', branches: [[name: '*/develop']], userRemoteConfigs: [[url: 'ssh://git@myBitbucket/myProject/myRepository.git']], browser: [$class: 'BitbucketWeb', repoUrl: 'https://myBitbucket/projects/myProject/repos/myRepository']]){code}I highlighted the Link and the Result !bitbucket_history.png|thumbnail!I also tried to create a new Job and a new Repository with the same effect (even if I only have a master)
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-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed Vivek Pandey though I am confused - where is the work for tag actions being tracked? You made this comment yesterday https://issues.jenkins-ci.org/browse/JENKINS-39463?focusedCommentId=278010=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-278010 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-39871) Skipped stages should show up as unbuilt
Title: Message Title James Dumay resolved as Fixed The backend does the right thing now Jenkins / JENKINS-39871 Skipped stages should show up as unbuilt Change By: James Dumay Status: Open 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-39871) Skipped stages should show up as unbuilt
Title: Message Title James Dumay edited a comment on JENKINS-39871 Re: Skipped stages should show up as unbuilt The backend does the right thing now making this ticket obsolete 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-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay updated JENKINS-38330 Jenkins / JENKINS-38330 Use the declarative model to show all stages and parallels to be executed 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-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed Vivek Pandey yes absolutely - Ive seen this in action and its amazingly good 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
James Dumay edited a comment on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
[~perilousapricot] being able to deliver a consistent visualization is one of the drivers of the new [Declarative Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/] syntax. Declarative Pipeline is more structured. For example, you can only [nest a single parellel block within a stage|https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Parallelism#split-up-a-test-suite]. There is no nesting of stages but parallel branches can have names that do what a lot of people on the comments of this ticket have done by defining a stage within a parellel.To use [~elgalu]'s example, in Pipeline Script:{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } parallel ( "chrome" : { stage('chrome') { println 'running tests in chrome' } }, "firefox" : { stage('firefox') { println 'running tests in firefox' } }, "edge" : { stage('edge') { println 'running tests in edge' } } )}{code}Would be the following in Declarative:{code}pipeline { agent label:''" // same as node { ... } stages {stage('build') { steps {println 'I prepare the build for the parallel steps' }}stage('browser testing') { parallel ('chrome': { println 'running tests in chrome'},'firefox': { println 'running tests in firefox'},'edge': { println 'running tests in edge'} )} }}{code}Now the more awesome part is that we can figure out how the Pipeline is displayed by reading the model vs executing it. That allows us to describe all the stages, steps and parallel branches before execution (making [a linter|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/58] feasible), build your own tooling to modify or construct Jenkinsfiles and even provides a foundation for the Jenkins project to build a [Pipeline Editor|https://jenkins.io/images/post-images/blueocean/pipeline-editor.png].It may not be as flexible as the scripting variant that you've come to know but it will give much more consistent results across many of the pain points discussed here (however, you can use Script from a shared library in Declarative as an escape hatch). All this does not mean that Blue Ocean won't be trying to visualize your Jenkinsfiles written in Pipeline Script. It's important to us that it works for the majority case. However, we recognise that due to the nature of the beast there are going to be some things that just won't be possible to visualize when using Script.
Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
James Dumay edited a comment on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
[~perilousapricot] being able to deliver a consistent visualization is one of the drivers of the new [Declarative Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/] syntax. Declarative Pipeline is more structured. For example, you can only [nest a single parellel block within a stage|https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Parallelism#split-up-a-test-suite]. There is no nesting of stages but parallel branches can have names that do what a lot of people on the comments of this ticket have done by defining a stage within a parellel.To use [~elgalu]'s example, in Pipeline Script:{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } parallel ( "chrome" : { stage('chrome') { println 'running tests in chrome' } }, "firefox" : { stage('firefox') { println 'running tests in firefox' } }, "edge" : { stage('edge') { println 'running tests in edge' } } )}{code}Would be the following in Declarative:{code}pipeline { agent label:''" // same as node { ... } stages {stage('build') { steps {println 'I prepare the build for the parallel steps' }}stage('browser testing') { parallel ('chrome': { println 'running tests in chrome'},'firefox': { println 'running tests in firefox'},'edge': { println 'running tests in edge'} )} }}{code}Now the more awesome part is that we can figure out how the Pipeline is displayed by reading the model vs executing it. That allows us to describe all the stages, steps and parallel branches before execution (making [a linter|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/58] feasible), build your own tooling to modify or construct Jenkinsfiles and even provides a foundation for the Jenkins project to build a [Pipeline Editor|https://jenkins.io/images/post-images/blueocean/pipeline-editor.png].It may not be as flexible as the scripting variant that you've come to know but it will give much more consistent results across many of the pain points discussed here (however, you can use Script from a shared library in Declarative as an escape hatch) .All this does not mean that Blue Ocean won't be trying to visualize your Jenkinsfiles written in Pipeline Script. It's important to us that it works for the majority case. However, we recognise that due to the nature of the beast there are going to be some things that just won't be possible to visualize when using Script.
Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
James Dumay edited a comment on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
[~perilousapricot] being able to deliver a consistent visualization is one of the drivers of the new [Declarative Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/] syntax. Declarative Pipeline is more structured. For example, you can only [nest a single parellel block within a stage|https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Parallelism#split-up-a-test-suite]. There is no nesting of stages but parallel branches can have names that do what a lot of people on the comments of this ticket have done by defining a stage within a parellel.To use [~elgalu]'s example, in Pipeline Script:{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } parallel ( "chrome" : { stage('chrome') { println 'running tests in chrome' } }, "firefox" : { stage('firefox') { println 'running tests in firefox' } }, "edge" : { stage('edge') { println 'running tests in edge' } } )}{code}Would be the following in Declarative:{code}pipeline { agent label:''" // same as node { ... } stages {stage('build') { steps {println 'I prepare the build for the parallel steps' }}stage('browser testing') { parallel ('chrome': { println 'running tests in chrome'},'firefox': { println 'running tests in firefox'},'edge': { println 'running tests in edge'} )} }}{code}Now the more awesome part is that we can figure out how the Pipeline is displayed by reading the model vs executing it. That allows us to describe all the stages, steps and parallel branches before execution (making [a linter|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/58] feasible), build your own tooling to modify or construct Jenkinsfiles and even provides a foundation for the Jenkins project to build a [Pipeline Editor|https://jenkins.io/images/post-images/blueocean/pipeline-editor.png].It may not be as flexible as the scripting variant that you've come to know but it will give much more consistent results across many of the pain points discussed here. All this does not mean that Blue Ocean won't be trying to visualize your Jenkinsfiles written in Pipeline Script. However, we recognise that due to the nature of the beast there are going to be some things that just won't be possible to visualize when using Script.
Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
James Dumay commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Andrew Melo being able to deliver a consistent visualization is one of the drivers of the new Declarative Pipeline syntax. Declarative Pipeline is more structured. For example, you can only nest a single parellel within a stage. There is no nesting of stages but parallel branches can have names that do what a lot of people on the comments of this ticket have done by defining a stage within a parellel. To use Leo Gallucci's example, in Pipeline Script:
node() {
stage('Build') {
println 'I prepare the build for the parallel steps'
}
parallel (
"chrome" : { stage('chrome') { println 'running tests in chrome' } },
"firefox" : { stage('firefox') { println 'running tests in firefox' } },
"edge" : { stage('edge') { println 'running tests in edge' } }
)
}
Would be the following in Declarative:
pipeline {
agent label:''" // same as node { ... }
stages {
stage('build') {
steps {
println 'I prepare the build for the parallel steps'
}
}
stage('browser testing') {
parallel (
'chrome': {
println 'running tests in chrome'
},
'firefox': {
println 'running tests in firefox'
},
'edge': {
println 'running tests in edge'
}
)
}
}
}
Now the more awesome part is that we can figure out how the Pipeline is displayed by reading the model vs executing it. That allows us to describe all the stages, steps and parallel branches before execution (making a linter feasible), build your own tooling to modify or construct Jenkinsfiles and even provides a foundation for the Jenkins project to build a Pipeline Editor. It may not be as flexible as the scripting variant that you've come to know but it will give much more consistent results across many of the pain points discussed here. All this does not mean that Blue Ocean won't be trying to visualize your Jenkinsfiles written in Pipeline Script. However, we recognise that due to the nature of the beast there are going to be some things that just won't be possible to visualize when using Script.
Add Comment
[JIRA] (JENKINS-39905) Wrong Path for BitbucketWeb Source Files
Title: Message Title Christoph Forster commented on JENKINS-39905 Re: Wrong Path for BitbucketWeb Source Files I have the following Setup: Jenkins 2.32 Git Plugin 3.0.0 Pipeline Plugin 2.4 (Pipeline SCM Plugin 2.3) Atlassian Bitbucket v4.9.1 MyPipeline Source looks like checkout([$class: 'GitSCM', branches: [[name: '*/develop']], userRemoteConfigs: [[url: 'ssh://git@myBitbucket/myProject/myRepository.git']], browser: [$class: 'BitbucketWeb', repoUrl: 'https://myBitbucket/projects/myProject/repos/myRepository']] ) I highlighted the Link and the Result 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-39905) Wrong Path for BitbucketWeb Source Files
Title: Message Title Christoph Forster updated an issue Jenkins / JENKINS-39905 Wrong Path for BitbucketWeb Source Files Change By: Christoph Forster Attachment: bitbucket_history.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-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title Vivek Pandey commented on JENKINS-38330 Re: Use the declarative model to show all stages and parallels to be executed James Dumay With https://issues.jenkins-ci.org/browse/JENKINS-39463, complete pipeline graph is going to be presented even if its partially executed. Maybe we should close this. 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-39929) Shelve Project causes jobs to be updated twice
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-39929 Shelve Project causes jobs to be updated twice Issue Type: Improvement Assignee: ashlux Components: shelve-project-plugin Created: 2016/Nov/22 6:46 AM Environment: Jenkins 2.7.3 shelve-project-plugin:1.5 Priority: Major Reporter: Allan BURDAJEWICZ The Shelve project plugin enforce a property whenever an item is Updated as well as when all items have been Loaded This is inefficient. It also impacts other functionalities/plugins. For example the Job Config History plugin - which implements SaveableListener - will add 2 entries when you save a job because every time a job is saved, the Shelve Plugin update it to enforce the ShelveProjectProperty. Add Comment
[JIRA] (JENKINS-29358) job-level promotion status shows incorrect information
Title: Message Title Orlin Jechev commented on JENKINS-29358 Re: job-level promotion status shows incorrect information Works fine. Thank you, Oleg Nenashev! 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-39928) Integration with Jenkinsfile
Title: Message Title Johan Steyn updated an issue Jenkins / JENKINS-39928 Integration with Jenkinsfile Change By: Johan Steyn Not sure if this was raised before, but its not clear how one can integrate the quality gate plugin into the Jenkinsfile. Is there a way to achieve this already? There is no documentation support for 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-39928) Integration with Jenkinsfile
Title: Message Title Johan Steyn created an issue Jenkins / JENKINS-39928 Integration with Jenkinsfile Issue Type: Improvement Assignee: Ivana Sh Components: quality-gates-plugin Created: 2016/Nov/22 6:28 AM Priority: Minor Reporter: Johan Steyn 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"
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
Andrew Melo commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
I understand completely it's hard to try and arrange a display for the results of a turing-complete programming language, but perhaps the compromise is allowing the programmer define where things should go, instead of having the language try to divine out the positioning post-facto. For instance (pseudo code, please be gentle) stage("checkout",0,0) { git checkout } stage("build",1,0) { build windows} stage("build",1,1) { build linux} stage("deploy",2,0) { deploy windows} stage("deploy",2,1) { deploy linux} Since the person writing the code knows (ostensibly) where things should go, you could just trust them to make the right grid-like display of each node/step
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-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Michael Neale updated JENKINS-39854 Jenkins / JENKINS-39854 REGRESSION: activity/branch run status is not updated after closing karaoke mode Change By: Michael Neale 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Michael Neale commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage malcolm crum Malcolm - could you sketch out what you would hope that the test stage above would look like? could be on a metaphorical back of a napkin (or literal napkin, although they can be hard to draw on). My guess is something like: 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: Michael Neale Attachment: stages.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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title tilak raj updated an issue Jenkins / JENKINS-34562 Parameterized Build option not providing advanced button in build page Change By: tilak raj Labels: jenkins new parameterized parameterized-trigger parameters plugin 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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title tilak raj commented on JENKINS-34562 Re: Parameterized Build option not providing advanced button in build page Hi, I have updated the component, i don't see any plugin for my requirement, it seems to the new process. please let me know, if you have any questions, we are eagerly waiting for your reply... 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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title tilak raj edited a comment on JENKINS-34562 Re: Parameterized Build option not providing advanced button in build page Hi,I have updated the component, i don't see any plugin for my requirement, it seems to the new process.please let me know, if you have any questions, we are eagerly waiting for your reply... Thanks,Tilak., 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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title tilak raj updated an issue Jenkins / JENKINS-34562 Parameterized Build option not providing advanced button in build page Change By: tilak raj Labels: jenkins new plugin 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-39927) REGRESSION: left most table column contents are out of alignment
Title: Message Title James Dumay commented on JENKINS-39927 Re: REGRESSION: left most table column contents are out of alignment Assuming all the table refactoring will cover this so I am assigning to you 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-39927) REGRESSION: left most table column contents are out of alignment
Title: Message Title James Dumay started work on JENKINS-39927 Change By: James Dumay 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-39927) REGRESSION: left most table column contents are out of alignment
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-39927 REGRESSION: left most table column contents are out of alignment Change By: James Dumay Assignee: 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-39927) REGRESSION: left most table column contents are out of alignment
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39927 REGRESSION: left most table column contents are out of alignment Issue Type: Task Assignee: Unassigned Attachments: upload (1).png, upload (2).png Components: blueocean-plugin Created: 2016/Nov/22 4:44 AM Priority: Minor Reporter: James Dumay Left most table columns on Activity, Branches are off. likely Pull Requests too but I haven't verified. Add Comment
[JIRA] (JENKINS-39463) Integrate pipeline-model-definition 0.6
Title: Message Title Vivek Pandey updated JENKINS-39463 Jenkins / JENKINS-39463 Integrate pipeline-model-definition 0.6 Change By: Vivek Pandey 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-38323) Developer can drag and drop to reorder steps within a stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38323 Developer can drag and drop to reorder steps within a stage Change By: Michael Neale In Scope* Developer can drag and drop to reorder steps within a stage using the drag handles * Investigate how much effort this is before fully implementing 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-38587) User can add and edit a block scoped step
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38587 User can add and edit a block scoped step Change By: Michael Neale Sprint: tasman 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-38587) User can add and edit a block scoped step
Title: Message Title Michael Neale started work on JENKINS-38587 Change By: Michael Neale 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-37991) jenkins-dsl-plugin gradle test fails when using new slackNotifier syntax
Title: Message Title Pedro Coelho commented on JENKINS-37991 Re: jenkins-dsl-plugin gradle test fails when using new slackNotifier syntax I have the exact same problem with both slackNotifier (plugin version 2.1) and ghprbTrigger (plugin version 1.33.1). Jenkins version is 2.33. I have been using the build script at https://github.com/sheehan/job-dsl-gradle-example which is an augmented version of the one you mention. Tests pass locally and it fail when running in Jenkins, in a seed job that executes the gradle steps as it does locally. Everything works in Jenkins when ignoring the tests. This did not happen two weeks earlier. I am unsure at this point what I've upgraded, but if you wish to revisit this bug I'll be happy to investigate. 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-39853) REGRESSION: alignment all wonky on branches listing
Title: Message Title Josh McDonald closed an issue as Fixed Jenkins / JENKINS-39853 REGRESSION: alignment all wonky on branches listing Change By: Josh McDonald Status: Resolved 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-39853) REGRESSION: alignment all wonky on branches listing
Title: Message Title Josh McDonald updated JENKINS-39853 This particular regression is fixed, but the underlying issue with tables + links needs more attention. Jenkins / JENKINS-39853 REGRESSION: alignment all wonky on branches listing Change By: Josh McDonald 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
[JIRA] (JENKINS-39853) REGRESSION: alignment all wonky on branches listing
Title: Message Title Josh McDonald updated JENKINS-39853 Jenkins / JENKINS-39853 REGRESSION: alignment all wonky on branches listing Change By: Josh McDonald 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-26522) Annotated block/stage status
Title: Message Title Sam Van Oort commented on JENKINS-26522 Re: Annotated block/stage status James Dumay Not quite in review – part of this is, but there's a bit more to be done before we can consider it complete. 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-26522) Annotated block/stage status
Title: Message Title Sam Van Oort updated JENKINS-26522 Jenkins / JENKINS-26522 Annotated block/stage status Change By: Sam Van Oort Status: In Review 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-26522) Annotated block/stage status
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-26522 Annotated block/stage status Change By: Sam Van Oort Assignee: Jesse Glick Sam Van Oort 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-38251) Fetching favorited items for a user is very slow
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-38251 Fetching favorited items for a user is very slow Change By: Michael Neale Assignee: 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-39893) Enable findbugs
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-39893 Enable findbugs Change By: Michael Neale Assignee: 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-39647) Failed to write defaultParameterValue
Title: Message Title Vivek Pandey commented on JENKINS-39647 Re: Failed to write defaultParameterValue Michael Neale That will be great! 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-39647) Failed to write defaultParameterValue
Title: Message Title Michael Neale commented on JENKINS-39647 Re: Failed to write defaultParameterValue Vivek Pandey perhaps Tom might be able to take a look at this after other things? 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-26522) Annotated block/stage status
Title: Message Title James Dumay started work on JENKINS-26522 Change By: James Dumay 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-26522) Annotated block/stage status
Title: Message Title James Dumay updated JENKINS-26522 Jenkins / JENKINS-26522 Annotated block/stage status Change By: James Dumay 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-39888) REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location
Title: Message Title Michael Neale commented on JENKINS-39888 Re: REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location hrm.. I think Ivan Meredith pointed this out yesterday - events weren't being stopped at the right point... 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-38848) API to enumerate available credentials
Title: Message Title Michael Neale updated JENKINS-38848 Jenkins / JENKINS-38848 API to enumerate available credentials Change By: Michael Neale Status: In Review 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder edited a comment on JENKINS-39887 Re: redmine plugin crashes blue ocean show more link Hi [~romanp], thanks for the report.Could you check if the job has assigned Redmine instance - is the "Assign Redmine project" is *checked on*?Redmine(SVN)RepositoryBrowser searches for this information.[~coervivek] there is already a PR - https://github.com/jenkinsci/redmine-plugin/pull/20 , which should fix the issue, but it still needs more thorough review. But indeed this isn't related to blueocean plugin, so I've removed it from issue Component box. 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder updated an issue Jenkins / JENKINS-39887 redmine plugin crashes blue ocean show more link Change By: Łukasz Jąder Component/s: blueocean-plugin 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder assigned an issue to Łukasz Jąder Jenkins / JENKINS-39887 redmine plugin crashes blue ocean show more link Change By: Łukasz Jąder Assignee: Vivek Pandey Łukasz Jąder 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder updated an issue Jenkins / JENKINS-39887 redmine plugin crashes blue ocean show more link Change By: Łukasz Jąder Priority: Critical 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-39887) redmine plugin crashes blue ocean show more link
Title: Message Title Łukasz Jąder commented on JENKINS-39887 Re: redmine plugin crashes blue ocean show more link Hi Roman Pickl, thanks for the report. Could you check if the job has assigned Redmine instance - is the "Assign Redmine project" is checked on? Redmine(SVN)RepositoryBrowser searches for this information. Vivek Panday there is already a PR - https://github.com/jenkinsci/redmine-plugin/pull/20 , which should fix the issue, but it still needs more thorough 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-39926) No Gitlab configuration in Build Triggers
Title: Message Title Y Z created an issue Jenkins / JENKINS-39926 No Gitlab configuration in Build Triggers Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Nov/21 11:36 PM Priority: Major Reporter: Y Z 1. The plugin https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin is installed, but invisible or not available to be configured at "Build Triggers" when the multi-branch job is configured. If we go to the created job for a particular branch the option is available and could be configured. 2. On each reindexing on multi-branch job, the previously configured Gitlab settings for the branch jobs are reset and Gitlab build trigger is disabled. Add Comment
[JIRA] (JENKINS-39888) REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location
Title: Message Title Cliff Meyers commented on JENKINS-39888 Re: REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location For posterity: when the A elements were added in the TD's, the outer TR still had a click handler on it. This caused the router.push to be called twice, so Run Detail's "opener" link was pointing to itself. Clicking "close" destroyed the modal but did not actually navigate backwards (it navigated to itself). The broken scrolbar is because that DOM is actually part of the "snapshot" that Keith added to prevent the "flash" when navigating to Run Details. 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-39925) CulpritsRecipientProvider does not populate with all users who committed since the last non-broken build when the current build is successful i.e. emailing on a fixed build
Title: Message Title Dylan Underwood created an issue Jenkins / JENKINS-39925 CulpritsRecipientProvider does not populate with all users who committed since the last non-broken build when the current build is successful i.e. emailing on a fixed build Issue Type: Bug Assignee: Unassigned Components: email-ext-recipients-column-plugin Created: 2016/Nov/21 11:27 PM Environment: Jenkins ver. 2.19.1, Email Extension Plugin version 2.52, Red Hat Enterprise Linux Server release 6.7, Java 1.8, running Jenkins directly, rpm install, launched via service, Priority: Major Reporter: Dylan Underwood Using Jenkins Pipeline I need to email all users who made changes while the build was broken as well as when the build is fixed. The CulpritsRecipientProvider provider seems to claim to have this functionality. But when the build result is successful this list is not populated. It is only populated when the build result is not successful. $class: 'CulpritsRecipientProvider' - Sends email to the list of users who committed a change since the last non-broken build till now. This list at least always include people who made changes in this build, but if the previous build was a failure it also includes the culprit list from there. In my previous version of Jenkins, 1.658, and Email-Ext version 2.52 in a Freestyle project I was able to set the Triggers to send on Fixed and add the correct recipient list. Is this functionality available in a pipeline job?
[JIRA] (JENKINS-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Michael Neale commented on JENKINS-39852 Re: REGRESSION: Loading worm never finishes on dashboard Yes Tom FENNELLY didn't see that - I will close that one and put the content here (less clicking) - I assume you would like Thor to take it on? 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-39852) REGRESSION: Loading worm never finishes on dashboard
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39852 REGRESSION: Loading worm never finishes on dashboard Change By: Michael Neale In a recent beta a regression was introduced that means the dashboard in most cases never finishes showing the loading worm. You can see this as the little white strip at the top. The app works, and you can navigate, but it looks very very bad and may be symtomatic of other problems. I know as of commit 7b7d2858e58caccd3b8e3d9f787bfb4f0c9ba103 this was not a problem. It seems to be introduce in this commit: 1ba6c8edb0f3f5e1912bd6a0b1f842dd8e7690b0ie: https://github.com/jenkinsci/blueocean-plugin/commit/1ba6c8edb0f3f5e1912bd6a0b1f842dd8e7690b0 Some explanation by [~tfennelly]: "The does not seem to be clicking into action on the pipelines page, with the result that the loading indicator just stays in a loading state forever, which looks a bit weird. I had a quick look at it but can't make any sense of it. Maybe someone else can.Seems like PageLoading is not activated on the page at all and so the LoadingIndicator show and hide functions are never called. That's just from a quick scan though, so not really sure." Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39671) PageLoading indicator not working on pipelines page
Title: Message Title Michael Neale closed an issue as Duplicate Jenkins / JENKINS-39671 PageLoading indicator not working on pipelines page Change By: Michael Neale Status: Open Closed 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-39924) Implement git repository browser for redmine hosted git repos
Title: Message Title Łukasz Jąder created an issue Jenkins / JENKINS-39924 Implement git repository browser for redmine hosted git repos Issue Type: New Feature Assignee: Unassigned Components: redmine-plugin Created: 2016/Nov/21 11:12 PM Priority: Minor Reporter: Łukasz Jąder This plugin already supports SVN Repository browser for SVN repos hosted on redmine instance. The idea is to add dependency (maybe optional) on git-plugin and extend GitRepositoryBrowser and create RedmineGitRepositoryBrowser - which will create links to git commits viewable in Redmine repositories tab. Add Comment
[JIRA] (JENKINS-38150) Handle declarative pipeline preparatory steps and postBuild stage
Title: Message Title Vivek Pandey updated JENKINS-38150 Jenkins / JENKINS-38150 Handle declarative pipeline preparatory steps and postBuild stage 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-38587) User can add and edit a block scoped step
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-38587 User can add and edit a block scoped step Change By: Keith Zantow Assignee: 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-39888) REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location
Title: Message Title Michael Neale started work on JENKINS-39888 Change By: Michael Neale 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-39888) REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location
Title: Message Title Michael Neale assigned an issue to Cliff Meyers Thor - looks like Cliff has found the cause and has a fix WIP Jenkins / JENKINS-39888 REGRESSION: opening/closing run dialog breaks scrolling of activity list and does not update window location Change By: Michael Neale Assignee: Thorsten Scherler 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-39854) REGRESSION: activity/branch run status is not updated after closing karaoke mode
Title: Message Title Michael Neale started work on JENKINS-39854 Change By: Michael Neale 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-39592) Unable to use global function defined within library project
Title: Message Title Jesse Glick resolved as Not A Defect As discussed in the plugin documentation, for this case you should pass in this, not steps, as execEcho is a global variable not a step. Jenkins / JENKINS-39592 Unable to use global function defined within library project Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Jesse Glick commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs Probably same as JENKINS-38679; needs investigation and a minimal test case. 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-39622) Triggering a parametrized job from shared library sometimes deletes all parameters
Title: Message Title Jesse Glick resolved as Cannot Reproduce No idea what could cause such a problem, unless the downstream build is using the properties step to define its parameters and it sometimes omits that job property. Obviously if you find a way to reproduce, reopen with details. Jenkins / JENKINS-39622 Triggering a parametrized job from shared library sometimes deletes all parameters Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39899 workflow-lib : declaring several Libraries causes them to overlap Change By: Jesse Glick 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-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39899 workflow-lib : declaring several Libraries causes them to overlap Change By: Jesse Glick Component/s: 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-39847) Improved visualization for multiple "parallel"s within the same stage block
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Improved visualization for multiple "parallel"s within the same stage block
Change By:
James Dumay
{panel:title=Improved visualization for multiple "parallel"s within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.The current behaviour in Blue Ocean is to show all the parallels belonging to a stage under the same stage. However, this is currently not working due to by a bug in pipeline - see JENKINS-39839.{panel}The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39847) Improved visualization for multiple "parallel"s within the same stage block
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Improved visualization for multiple "parallel"s within the same stage block
Change By:
James Dumay
{panel:title=Improved visualization for multiple "parallel"s within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.The current behaviour in Blue Ocean is to show all the parallels belonging to a stage under the same stage by . However, this is currently not working due to by a bug in pipeline - see JENKINS-39839.{panel}The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39847) Improved visualization for multiple "parallel"s within the same stage block
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Improved visualization for multiple "parallel"s within the same stage block
Change By:
James Dumay
{panel:title=Improved visualization for multiple "parallel"s within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.The current behaviour in Blue Ocean is to show all the parallels belonging to a stage under the same stage by this is currently not working due to by a bug in pipeline - see JENKINS-39839 .{panel}The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39923) CLI command for Declarative linter
Title: Message Title Andrew Bayer commented on JENKINS-39923 Re: CLI command for Declarative linter Still debating also adding a shell script that you can download and run without needing to have CLI SSH port access to the master. Haven't decided yet. 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-39847) Improved visualization for multiple "parallel"s within the same stage block
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Improved visualization for multiple "parallel"s within the same stage block
Change By:
James Dumay
{panel:title=Improved visualization for multiple "parallel"s within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations. The current behaviour in Blue Ocean is to show all the parallels belonging to a stage under the same stage. {panel}The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39145) add support to pass actions list besides the parameters list to the build step
Title: Message Title Jesse Glick resolved as Incomplete Jenkins / JENKINS-39145 add support to pass actions list besides the parameters list to the build step Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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-39847) Improved visualization for multiple "parallel"s within the same stage block
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39847 Improved visualization for multiple "parallel"s within the same stage block Change By: James Dumay Summary: Misrepresentation of Improved visualization for multiple parallels "parallel"s within the same stage block 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-39847) Misrepresentation of multiple parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Misrepresentation of multiple parallels
Change By:
James Dumay
{panel:title= Support Improved visualization for multiple "parallel" s within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.{panel}The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39847) Misrepresentation of multiple parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39847
Misrepresentation of multiple parallels
Change By:
James Dumay
{panel:title=Support for multiple "parallel" within the same stage block isn't planned at this time |titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.{panel} The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Giacomo Boccardo the only ticket you have quoted that is unscheduled is JENKINS-39847. Aside, I think we do support parellel very well - Blue Ocean is the only place where parellel visualisation is supported so far As you can see, its a hard problem to solve visually when there are so many variations in the way that parallel can be used within Pipeline Script. The challenge with creating a visualization for Pipeline is to create a visualisation for turing complete programming language. That isn't practically possible under all circumstances. 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-39827) Pipeline error step message is not displayed in flowGraphTable
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39827 Pipeline error step message is not displayed in flowGraphTable Change By: Jesse Glick Component/s: workflow-basic-steps-plugin Component/s: pipeline-build-step-plugin 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-39827) Pipeline error step message is not displayed in flowGraphTable
Title: Message Title Jesse Glick resolved as Not A Defect By design. The error is an exception message, which may or may not be printed by whoever catches the exception. Jenkins / JENKINS-39827 Pipeline error step message is not displayed in flowGraphTable Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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-39921) Pipeline job type unable to run in specified docker image
Title: Message Title Jesse Glick resolved as Not A Defect I think you are looking for the Docker Pipeline plugin. Jenkins / JENKINS-39921 Pipeline job type unable to run in specified docker image Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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-39800) Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException
Title: Message Title Kevin Logan commented on JENKINS-39800 Re: Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException If it helps any we upgraded Jenkins from 1.653 and Java from 6b38-1.13.10-1~deb7u1 when this problem 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-39923) CLI command for Declarative linter
Title: Message Title Andrew Bayer updated JENKINS-39923 Jenkins / JENKINS-39923 CLI command for Declarative linter 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-39923) CLI command for Declarative linter
Title: Message Title Andrew Bayer commented on JENKINS-39923 Re: CLI command for Declarative linter Initial PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/58 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-38442) Support nested stages in the Pipeline Graph
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38442
Support nested stages in the Pipeline Graph
Change By:
James Dumay
{panel:title=Support for nested stages is currently unplanned|titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Its possible to have infinitely nested stages that would be impossible for the visualization to display correctly.It's also impossible for us to correctly decide if a inner stage should be used as a "label" for a set of steps or if it is an actual stage. Labelling using {{stage}} needs to be revisited in Pipeline Script .The Blue Ocean team needs to refine the design for the pipeline graph for this to be supported.{panel}*Original ticket*I've tried using nested stages in order to group each shell script alone to have a meaningful data, however this broken the UI of blueocean and it stopped it from showing showing the variant steps.*Example 1*{code:java}def test = [:]test["a"] = {stage ("a") {stage ("ab") {sh "echo stage abc"}stage ("xyz") {sh "echo stage xyz"}}}test["b"] = {stage ("b") {stage ("bb") {sh "echo stage bb"}stage ("bxz") {sh "echo stagebxyz"}}}node { //stage 'start' parallel test stage ('middle') { sh "echo middle" } }{code}*Example 2*{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } stage('Test') { parallel ( "win7-vs2012" : { stage("checkout") { }; stage("build") { }; stage("test") { } }, "win10-vs2015" : { stage("checkout") { }; stage("build") { }; stage("test") { }}, "linux-gcc5" : { stage("checkout") { }; stage("build") { }; stage("test") { } }) }}{code}
Add Comment
[JIRA] (JENKINS-39923) CLI command for Declarative linter
Title: Message Title Andrew Bayer started work on JENKINS-39923 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-38442) Support nested stages in the Pipeline Graph
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38442
Support nested stages in the Pipeline Graph
Change By:
James Dumay
{panel:title=Support for nested stages is currently unplanned|titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Its possible to have infinitely nested stages that would be impossible for the visualization to display correctly.It's also impossible for us to correctly decide if a inner stage should be used as a "label" for a set of steps or if it is an actual stage. Labelling using { { stage} } needs to be revisited.The Blue Ocean team needs to refine the design for the pipeline graph for this to be supported.{panel}*Original ticket*I've tried using nested stages in order to group each shell script alone to have a meaningful data, however this broken the UI of blueocean and it stopped it from showing showing the variant steps.*Example 1*{code:java}def test = [:]test["a"] = {stage ("a") {stage ("ab") {sh "echo stage abc"}stage ("xyz") {sh "echo stage xyz"}}}test["b"] = {stage ("b") {stage ("bb") {sh "echo stage bb"}stage ("bxz") {sh "echo stagebxyz"}}}node { //stage 'start' parallel test stage ('middle') { sh "echo middle" } }{code}*Example 2*{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } stage('Test') { parallel ( "win7-vs2012" : { stage("checkout") { }; stage("build") { }; stage("test") { } }, "win10-vs2015" : { stage("checkout") { }; stage("build") { }; stage("test") { }}, "linux-gcc5" : { stage("checkout") { }; stage("build") { }; stage("test") { } }) }}{code}
Add Comment
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38442
Support nested stages in the Pipeline Graph
Change By:
James Dumay
{panel:title=Support for nested stages is currently unplanned|titleBGColor=lightgrey}There is some debate on how this concept can be visualised in Blue Ocean. Its possible to have infinitely nested stages that would be impossible for the visualization to display correctly. It's also impossible for us to correctly decide if a inner stage should be used as a "label" for a set of steps or if it is an actual stage. Labelling using {stage} needs to be revisited. The Blue Ocean team needs to refine the design for the pipeline graph for this to be supported.{panel}*Original ticket*I've tried using nested stages in order to group each shell script alone to have a meaningful data, however this broken the UI of blueocean and it stopped it from showing showing the variant steps.*Example 1*{code:java}def test = [:]test["a"] = {stage ("a") {stage ("ab") {sh "echo stage abc"}stage ("xyz") {sh "echo stage xyz"}}}test["b"] = {stage ("b") {stage ("bb") {sh "echo stage bb"}stage ("bxz") {sh "echo stagebxyz"}}}node { //stage 'start' parallel test stage ('middle') { sh "echo middle" } }{code}*Example 2*{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } stage('Test') { parallel ( "win7-vs2012" : { stage("checkout") { }; stage("build") { }; stage("test") { } }, "win10-vs2015" : { stage("checkout") { }; stage("build") { }; stage("test") { }}, "linux-gcc5" : { stage("checkout") { }; stage("build") { }; stage("test") { } }) }}{code}
Add Comment
