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

More information on conditions in the output

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • conditional-buildstep-plugin, run-condition-plugin
    • None
    • Jenkins 1.467 (on Windows 7), Run Condition Plugin 0.10, conditional-buildstep plugin 1.1, Any Build Step Plugin 0.1, Flexible Publish Plugin 0.10

      I have a project with a build step with an AND condition. The first is a BOOLEAN condition on an environment variable "TriggerGame". The second is a STRING condition on another environment variable "CONFIGURATION".

      In the same project, I also have a post-build step (using Flexible Publish Plugin) with a STRING condition on the environment variable "CONFIGURATION".

      The output of the build step (using conditional-buildstep) is not sufficient to follow the result of the evaluation:
      >> Run condition [And] enabling prebuild for step [BuilderChain]
      >> Run condition [Strings match] enabling prebuild for step [Archive the artifacts]

      In the output of the post-build step (Flexible Publish) is easier to follow:
      >> Strings match run condition: string 1=[Release], string 2=[Release]
      >> Run condition [Strings match] enabling perform for step [Archive the artifacts]

      Can you modify your output for STRING condition to be like Flexible Publish ?
      Can you add an output for BOOLEAN condition ? Like "Boolean condition: ${ENV,var="TriggerGame"} evaluate to false"

        1. build-step.png
          build-step.png
          34 kB
        2. output.png
          output.png
          20 kB
        3. post-build-step.png
          post-build-step.png
          20 kB

          [JENKINS-14584] More information on conditions in the output

          Dominik Bartholdi added a comment -

          Logging of each run condition is currently done in each condition implementation, we might have to think about how to do this in a more generic way.

          Dominik Bartholdi added a comment - Logging of each run condition is currently done in each condition implementation, we might have to think about how to do this in a more generic way.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: imod
          Path:
          src/main/java/org/jenkins_ci/plugins/run_condition/core/BooleanCondition.java
          src/main/java/org/jenkins_ci/plugins/run_condition/core/CauseCondition.java
          src/main/java/org/jenkins_ci/plugins/run_condition/core/FileExistsCondition.java
          src/main/java/org/jenkins_ci/plugins/run_condition/core/StatusCondition.java
          src/main/resources/org/jenkins_ci/plugins/run_condition/Messages.properties
          http://jenkins-ci.org/commit/run-condition-plugin/1125b04ae091387daad4523367114565e2b2ca36
          Log:
          [FIXED JENKINS-14584] add more output at evaluation of conditions

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: imod Path: src/main/java/org/jenkins_ci/plugins/run_condition/core/BooleanCondition.java src/main/java/org/jenkins_ci/plugins/run_condition/core/CauseCondition.java src/main/java/org/jenkins_ci/plugins/run_condition/core/FileExistsCondition.java src/main/java/org/jenkins_ci/plugins/run_condition/core/StatusCondition.java src/main/resources/org/jenkins_ci/plugins/run_condition/Messages.properties http://jenkins-ci.org/commit/run-condition-plugin/1125b04ae091387daad4523367114565e2b2ca36 Log: [FIXED JENKINS-14584] add more output at evaluation of conditions

            bap bap
            thoudayer T. Houdayer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: