Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62487

Detail each stage of the pipeline in the pull request checks

      Hello

      It would be really nice if we could have the detail of each stage of the Jenkinsfile inside the Gitea checks report, instead of just the summary through the Jenkins' task name.

      This would allow PR makers to quickly see which step of the checks failed (is it unit tests? is it code style? is it build?), and also allow blocking PR automatically for specific checks (ie. allow merging if unit tests and build checks pass, but ignore if code style didn't pass) - without having to duplicate the root task on Jenkins.

      Thanks!

          [JENKINS-62487] Detail each stage of the pipeline in the pull request checks

          Guillaume L created issue -
          Guillaume L made changes -
          Summary Original: Detail each stage of the pipeline in the pull request New: Detail each stage of the pipeline in the pull request checks
          Guillaume L made changes -
          Description Original: Hello

          It would be really nice if we could have the detail of each stage of the Jenkinsfile inside the Gitea checks report, instead of just the summary through the Jenkins' task name.

          This would allow PR makers to quickly see which step of the checks failed (is it unit tests? is it code style? is it build?), and also allow blocking PR automatically for specific checks (ie. allow merging if unit tests and build checks pass, but ignore if code style didn't pass).

          Thanks!
          New: Hello

          It would be really nice if we could have the detail of each stage of the Jenkinsfile inside the Gitea checks report, instead of just the summary through the Jenkins' task name.

          This would allow PR makers to quickly see which step of the checks failed (is it unit tests? is it code style? is it build?), and also allow blocking PR automatically for specific checks (ie. allow merging if unit tests and build checks pass, but ignore if code style didn't pass) - without having to duplicate the root task on Jenkins.

          Thanks!
          Steven made changes -
          Steven made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            xplodwild Guillaume L
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: