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

Expose analysis-collector results to pipeline env variables

    Details

    • Similar Issues:

      Description

      Use case: Every build should be unstable if it has any issues found.
      Email should be sent to committers only in case there are new issues in the current build.

      Right now if team wants emails on new issues it is only possible to make build unstable only if new issues found. So build with some issues, but no new issues will succeed.

      The solution might be to expose analysis results to the pipeline env variables.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          I don't follow what exactly is required? The build results are already exposed as API or tokens (token.makro plug-in). Are these information not enough?

          Show
          drulli Ulli Hafner added a comment - I don't follow what exactly is required? The build results are already exposed as API or tokens (token.makro plug-in). Are these information not enough?
          Hide
          vorobievalex Alexander Vorobiev added a comment -

          I wish I new this before But need to move to pipeline (workflow-plugin) now.
          Token-macro plugin might be logical mediator, but it does not yet expose variables to pipeline groovy code. So the solution might be to consume token-macro output in workflow-plugin.

          Show
          vorobievalex Alexander Vorobiev added a comment - I wish I new this before But need to move to pipeline (workflow-plugin) now. Token-macro plugin might be logical mediator, but it does not yet expose variables to pipeline groovy code. So the solution might be to consume token-macro output in workflow-plugin.
          Hide
          jglick Jesse Glick added a comment -

          Not clear to me what is being requested here, so suggested solutions are premature.

          Show
          jglick Jesse Glick added a comment - Not clear to me what is being requested here, so suggested solutions are premature.
          Hide
          vorobievalex Alexander Vorobiev added a comment -

          So, current behavior of the warnings plugin (as well as JUnit - JENKINS-26276):
          Analyses output that can be handled in Jenkisfile is the build result - SUCCESS or UNSTABLE if there are warnings found.

          Expected behavior:
          It should be also possible to get how many new warnings appeared.

          This will be used to send notification about new warning once to authors of the causing commits only, not to authors of every subsequent commit until the warning is fixed.

          Show
          vorobievalex Alexander Vorobiev added a comment - So, current behavior of the warnings plugin (as well as JUnit - JENKINS-26276 ): Analyses output that can be handled in Jenkisfile is the build result - SUCCESS or UNSTABLE if there are warnings found. Expected behavior: It should be also possible to get how many new warnings appeared. This will be used to send notification about new warning once to authors of the causing commits only, not to authors of every subsequent commit until the warning is fixed.
          Hide
          drulli Ulli Hafner added a comment -

          Actually I still don't get it what needs to be done. I think all information is already available: either as token, API or action attached to the job. You can get this action from the job and get all interesting properties.

          Show
          drulli Ulli Hafner added a comment - Actually I still don't get it what needs to be done. I think all information is already available: either as token, API or action attached to the job. You can get this action from the job and get all interesting properties.

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              vorobievalex Alexander Vorobiev
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: