At 18:12 17.05.2023, you wrote:
>We resolved the dynamic matrix support by implementing a matrix step in a
>shared library,
>the matrix axis are arrays that can come from files if you want
>
>pipeline {
> agent any
>
> stages {
> stage('Matrix sample') {
> steps {
>
> matrix(
> agent: 'linux',
> axes:[
> axis('VAR_NAME_00', [ 1, 2 ]),
> axis('VAR_NAME_01', [ 'a', 'b', 'c', 'd', 'e' ])
> ],
> excludes: [
> axis('VAR_NAME_00', [ 1 ]),
> axis('VAR_NAME_01', [ 'd', 'e' ]),
> ]
> ) {
> echo "${VAR_NAME_00} - ${VAR_NAME_01}"
> }
>
> }
> }
> }
> }
>
>https://github.com/elastic/apm-pipeline-library/blob/main/vars/matrix.groovy
>https://github.com/elastic/apm-pipeline-library/blob/main/vars/matrix.txt
Thanks for your example, I'll take a look at it. Does it show up in the pipeline
stage view just like a regular job? I found that if the stage order is not each
time
the same then the stage view will reset with each build, so only the last one is
visible. Maybe the matrix can help me with that.
bye Fabi
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d9e0d167c9bfa81c963205694b503809%40indel.ch.
