Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting name for matrix pipelines #2819

Open
4 tasks done
JakobDev opened this issue Nov 14, 2023 · 1 comment
Open
4 tasks done

Allow setting name for matrix pipelines #2819

JakobDev opened this issue Nov 14, 2023 · 1 comment
Labels
enhancement improve existing features server

Comments

@JakobDev
Copy link

JakobDev commented Nov 14, 2023

Clear and concise description of the problem

Since #2695 the build status of matrix pipelines gets correctly reported, what is awesome. However, there is still room for improvement. Currently it gets reported as {name}/{number}. It would be better if a name would be used instead of a number.

Suggested solution

Add a new filed matrixname which allows setting the name for a matrix pipeline. With the example from the documentation it could look like this:

matrix:
  GO_VERSION:
    - 1.4
    - 1.3
  DATABASE:
    - mysql:5.5
    - mysql:6.5
    - mariadb:10.1

steps:
  build:
    image: golang:${GO_VERSION}
    commands:
      - go get
      - go build
      - go test

services:
  database:
    image: ${DATABASE}

matrixname: ${GO_VERSION}-${DATABASE}

This would be reported as e.g. {name}/1.4-mysql:5.5.

Alternative

If only one variable is used, we can also use the variable instead of the number.

Additional context

No response

Validations

  • Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
  • Read the Contributing Guidelines.
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@JakobDev JakobDev added the feature add new functionality label Nov 14, 2023
@qwerty287 qwerty287 added enhancement improve existing features server and removed feature add new functionality labels Nov 14, 2023
@aozomaro
Copy link

On this I have another use case:
We run a rather large suite of automated ui tests. To do this, we use a matrix workflow that essentially 1 dimensional (Machine-1 - Machine-n) … what would be nice is to be able to roll up all runs into a single status report in GitHub .. currently it reports a large number of jobs and that is causing developers confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement improve existing features server
Projects
None yet
Development

No branches or pull requests

3 participants