[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Liam Newman commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Joan Touzet This totally makes sense. An issue has been opened for it. https://issues.jenkins-ci.org/browse/JENKINS-61047 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.5294.1583343240833%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Joan Touzet commented on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
One enhancement that might be nice, if possible, is to have the values for an axis name be supported as non-literals. I don't seem to be able to make this work in the current version. Sorry if this isn't the right place, but you were asking for examples above... Example: pipeline { environment { LOW_ERLANG_VER = '19.3.6.8' MID_ERLANG_VER = '20.3.8.24' HIGH_ERLANG_VER = '22.2' {{ }}} stages { // ... // Other stages that need the values above // ... stage("Build") { matrix { axes { axis { name 'ERLANG_VERSION' values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}" {{ }}} } // axes // ... // do the build with ${ERLANG_VERSION} // ... } // matrix } // stage } // stages } // pipeline if that makes sense.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.9431.1576548360856%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Simon Larouche-Gagne commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline +1 on the exclude syntax, it's taking a lot of space. Also, can the values field of the axis block be dynamic instead of using a filter parameter? I have a use case with axes with a lot of values depending on a parameter, so if I can't act on the matrix values, my only option is to handle it in a when block? Also, in most cases, I would rather use a global variable to store my axes values as well, makes it easier to maintain and I could re-use it in another matrix block further down in the script. But overall I'm very happy to see a matrix block in declarative pipeline. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.2995.1575905820818%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Results of my humble review: It seems to be usable, it covers user cases Excludes syntax is quite huge, but I have no fast good idea for much compact one without imperative expressions from original matrix functionality, it could be very annoying to avoid all uninterested combinations with axis count >2, especially in cases where *most* of combinations are uninterested (e.g. at the start of a project) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3486.1574168401398%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Got it, thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3453.1574167860979%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline https://github.com/jenkinsci/pipeline-model-definition-plugin/tree/master/pipeline-model-definition/src/test/resources/matrix has a whole bunch of Jenkinsfile examples/test cases. =) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3396.1574167200820%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Hm. I've reviewed json file more detailed. It seems to be quite agile implementation, covering most of cases above. So what I need (and most users I believe) is a Jenkinsfile example, to review end-user syntax. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3363.1574165821332%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Denis Dudarev commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Thank you for great feature! I could only see 2 axis cases in tests and json files. Is this a limit for there? Anyway I need better instructions to check it out. For example - sample Jenkinsfile with 3axis build would be very useful. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3326.1574165581025%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Serhii Shepel commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Ah right! Thanks Steffen Seckler Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3278.1574165461474%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Steffen Seckler commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline from what I see, the files in the json test directory can give very good hints: https://github.com/jenkinsci/pipeline-model-definition-plugin/tree/master/pipeline-model-definition/src/test/resources/json/matrix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.3244.1574165281071%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Serhii Shepel commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Liam Newman could you please provide some info regarding usage and possibilities for the bindings... I can see a bunch of test cases here: (https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/335e44ff6d19cfd43f58be210d9af81e4491cdec/pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/MatrixTest.java), but a bit more details would be nice... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.2898.1574108884868%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Liam Newman commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline You can pull 1.5.0-beta1 from the experimental update site now to take a look at matrix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.2653.1574094962079%40Atlassian.JIRA.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev edited a comment on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. User case:{code:sh} * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User desired that combination '.*'-'linux|osx|android'-'cl' doesn't make sense * User desired that combination 'arm.*'-'win32|osx'-'.*' doesn't make sense * User desired that combination '.*'-'osx'-'gcc' is not supported yet{code} It could be regexp syntax, as I offered before, or more declarative imperative like in original "Matrix job". IMHO, only this approach could make sense in 90% user cases. Also, there should be a way to skip stage/step on given axises combination.User case:{code:sh}* User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8')* User has combination of platforms ('win32', 'linux', 'osx', 'android')* User has combination of compilers ('clang', 'gcc', 'cl', 'icc')* User has stage 'build'* User has stage 'build MSI package'* User desired that 'build' stage makes sense in any combination of axises* User desired that 'build MSI package' for '.*'-'linux|osx|android'-'.*' doesn't make sense{code}[~abayer], please let me know, if there is any design draft of upcoming API.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev edited a comment on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. User case:{code:sh} * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User desired that combination '.*'-'linux|osx|android'-'cl' doesn't make sense * User desired that combination 'arm.*'-'win32|osx'-'.*' doesn't make sense * User desired that combination '.*'-'osx'-'gcc' is not supported yet{code} It could be regexp syntax, as I offered before, or more declarative like in original "Matrix job". IMHO, only this approach could make sense in 90% user cases. Also, there should be a way to skip stage/step on given axises combination.User case:{code:sh}* User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8')* User has combination of platforms ('win32', 'linux', 'osx', 'android')* User has combination of compilers ('clang', 'gcc', 'cl', 'icc')* User has stage ' build ' * User has stage ' build MSI package ' * User desired that ' build ' stage makes sense in any combination of axises* User desired that ' build MSI package' for '.*'-'linux|osx|android'-'.*' doesn't make sense{code}[~abayer], please let me know, if there is any design draft of upcoming API.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev edited a comment on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. User case:{code:sh} * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User desired that combination '.*'-'linux|osx|android'-'cl' doesn't make sense * User desired that combination 'arm.*'-'win32|osx'-'.*' doesn't make sense * User desired that combination '.*'-'osx'-'gcc' is not supported yet{code} It could be regexp syntax, as I offered before, or more declarative like in original "Matrix job". IMHO, only this approach could make sense in 90% user cases. Also, there should be a way to skip stage/step on given axises combination.User case:{code:sh}* User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8')* User has combination of platforms ('win32', 'linux', 'osx', 'android')* User has combination of compilers ('clang', 'gcc', 'cl', 'icc')* User has stage build* User has stage build MSI package* User desired that build stage makes sense in any combination of axises* User desired that build MSI for '.*'-'linux|osx|android'-'.*' doesn't make sense{code} Please [~abayer], please let me know, if there is any design draft of upcoming API.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev edited a comment on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. Use User case: {code:sh} * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User desired that combination '.*' \ -'linux|osx|android' \ -'cl' doesn't makes make sense * User desired that combination 'arm.*' \ -'win32|osx' \ -'.*' doesn't makes make sense * User desired that combination '.*' \ -'osx' \ -'gcc' is not supported yet {code} It could be regexp syntax, as I offered before, or more declarative like in original "Matrix job". IMHO, only this approach could make sense in 90% usecases user cases . Also, there should be a way to skip stage/step on given axises combination. Use User case: {code:sh} * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User has stage build * User has stage build MSI package * User desired that build stage makes sense in any combination of axises * User desired that build MSI doesn for ' t make sense on ' .*' \ -'linux|osx|android' \ -'.*' doesn't make sense {code} Please let me know, if there is any design draft of upcoming API.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev edited a comment on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. Use case: * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User desired that combination '.*' \ -'linux|osx|android' \ -'cl' doesn't makes sense * User desired that combination 'arm.*' \ -'win32|osx' \ -'.*' doesn't makes sense * User desired that combination '.*' \ -'osx' \ -'gcc' is not supported yet It could be regexp syntax, as I offered before, or more declarative like in original "Matrix job". IMHO, only this approach could make sense in 90% usecases. Also, there should be a way to skip stage/step on given axises combination. Use case: * User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8') * User has combination of platforms ('win32', 'linux', 'osx', 'android') * User has combination of compilers ('clang', 'gcc', 'cl', 'icc') * User has stage build * User has stage build MSI package * User desired that build stage makes sense in any combination of axises * User desired that build MSI doesn't make sense on '.*' \ -'linux|osx|android' \ -'.*' Please let me know, if there is any design draft of upcoming API.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
Denis Dudarev commented on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
It would be great if not only 2d matrices would be supported(more than 2 axis should be supported). As well only sparsable matrices would be useful. Use case:
User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8')
User has combination of platforms ('win32', 'linux', 'osx', 'android')
User has combination of compilers ('clang', 'gcc', 'cl', 'icc')
User desired that combination '.*''linux|osx|android''cl' doesn't makes sense
User desired that combination 'arm.''win32|osx''.' doesn't makes sense
User desired that combination '.*''osx''gcc' is not supported yet
It could be regexp syntax, as I offered before, or more declarative like in original "Matrix job". IMHO, only this approach could make sense in 90% usecases. Also, there should be a way to skip stage/step on given axises combination. Use case:
User has combination of architectures ('x86', 'x86_64', 'armv7', 'armv8')
User has combination of platforms ('win32', 'linux', 'osx', 'android')
User has combination of compilers ('clang', 'gcc', 'cl', 'icc')
User has stage build
User has stage build MSI package
User desired that build stage makes sense in any combination of axises
User desired that build MSI doesn't make sense on '.''linux|osx|android''.'
Please let me know, if there is any design draft of upcoming API.
Add Comment
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-40986 Matrix structure for Declarative Pipeline Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.12742.1558993080672%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title
trejkaz commented on JENKINS-40986
Re: Matrix structure for Declarative Pipeline
I drafted up what I would hope this sort of thing would look like, and ended up with something like:
pipeline {
// ...
stages {
// ...
matrixBuild {
matrix [label: 'debian', prettyName: 'Debian'],
[label: 'ubuntu', prettyName: 'Ubuntu'],
[label: 'centos', prettyName: 'CentOS'],
[label: 'macos', prettyName: 'macOS'],
[label: 'windows', prettyName: 'Windows']
template {
stage("Test on ${prettyName}") {
agent {
label name
}
steps {
unstash 'compile-artifacts'
unstash 'dot-gradle'
gradle tasks: 'check', switches: '--stacktrace'
}
post {
always {
junit '*/build/test-results/**/*.xml'
}
}
}
}
}
// ...
}
}
The values in the maps for matrix would just become available in the context for template, and if you wanted to put whole closures in as the values, that's fine too. Practicality, though, no idea at all. I was going to try to do it as a pipeline library some day if free time ever came up.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Jan Sprinz updated an issue Jenkins / JENKINS-40986 Matrix structure for Declarative Pipeline Change By: Jan Sprinz Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Jan Sprinz commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Yes please! It's a must-have, really. The workaround of using loops in a scripted block for this is ugly and error-prone... All i really want for Christmas Easter is declarative Jenkins matrices. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Steffen Seckler commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline could we up the priority of this? seeing that most major other CI tools have this kind of feature, it should be implemented in jenkins rather soon... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-40986 Matrix structure for Declarative Pipeline Change By: Andrew Bayer Sprint: Declarative backlog Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Jan Sprinz commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Any news on this? Seems like most of the prerequisites are out of the way and this would be an absolute killer feature to have for declarative pipelines. I know it's way to early to think about visualization, but i'm not sure it's a good idea to include this in the normal blueocean pipeline view, since it would get really cluttered really fast. Maybe there could be a popup presenting something similar to the visualization of matrix builds in classic jenkins? I have a job with seven dimensions, i won't even try to imagine what it would look like to have all of those displayed in the normal pipeline view... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
