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

Conditional Build Step for "Current build status" never triggers - or doesn't seem to

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • conditional-buildstep-plugin
    • None
    • CentOS
      Jenkins v1.533
      conditional-buildstep v1.31

      I have a multiconfiguration build with a conditional build step that is supposed to run when the build is marked as failed after an "invoke ant" step.

      In the build log for each [failed] configuration I don't even see that it's checking for this condition. In the system log I see nothing too.

      Sorry if I'm doing something stupid, I just have no idea where to look for the information.

      EDIT:
      It triggers for builds with SUCCESSFUL "Invoke Ant" steps before the conditional check. In the case where it is supposed to trigger, the build status AT BEST is set to "Unstable." Worst status is "FAILED".

          [JENKINS-19802] Conditional Build Step for "Current build status" never triggers - or doesn't seem to

          Kevin R. created issue -
          Kevin R. made changes -
          Summary Original: Conditional Build Step for "Current build status" never triggers - or doesn New: Conditional Build Step for "Current build status" never triggers - or doesn't seem to
          Kevin R. made changes -
          Description Original: I have a multiconfiguration build with a conditional build step that is supposed to run when the build is marked as failed after an "invoke ant" step.

          In the build log for each configuration I don't even see that it's checking for this condition. In the system log I see nothing too.

          Sorry if I'm doing something stupid, I just have no idea where to look for the information.           		New: I have a multiconfiguration build with a conditional build step that is supposed to run when the build is marked as failed after an "invoke ant" step.

          In the build log for each [failed] configuration I don't even see that it's checking for this condition. In the system log I see nothing too.

          Sorry if I'm doing something stupid, I just have no idea where to look for the information.

          EDIT:
          It triggers for builds with SUCCESSFUL "Invoke Ant" steps *before* the conditional check. In the case where it is supposed to trigger, the build status AT BEST is set to "Unstable." Worst status is "FAILED".
          Environment Original: CentOS
          Jenkins v1.532
          conditional-buildstep v1.31           		New: CentOS
          Jenkins v1.533
          conditional-buildstep v1.31

          Kevin R. added a comment -

          hello?

          Kevin R. added a comment - hello?

          Dominik Bartholdi added a comment -

          can you add a simple screenshot to show your config?

          Dominik Bartholdi added a comment - can you add a simple screenshot to show your config?

          Dominik Bartholdi added a comment -

          I don't realy know how you configured your job, but here are some examples: https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin

          Dominik Bartholdi added a comment - I don't realy know how you configured your job, but here are some examples: https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin

          Kevin R. added a comment -

          Sorry for the late response! Thanks for any info, please let me know if Im doing anything stupid.

          http://i.imgur.com/qL5n1Je.jpg

          Kevin R. added a comment - Sorry for the late response! Thanks for any info, please let me know if Im doing anything stupid. http://i.imgur.com/qL5n1Je.jpg

          Dominik Bartholdi added a comment -

          OK, I I can reproduce it - but to be honest, I think there is a conceptional problem with the idea of this "Condition".
          If a build step fails, the next steps do never have a chance to get a hand on the build again, so the conditional build step never gets called itself and therefore he can not make any decision on whether he should trigger anything or not (this in in the core of Jenkins).

          So for what I can see right now, the "Current build status" is not of much value.

          Dominik Bartholdi added a comment - OK, I I can reproduce it - but to be honest, I think there is a conceptional problem with the idea of this "Condition". If a build step fails, the next steps do never have a chance to get a hand on the build again, so the conditional build step never gets called itself and therefore he can not make any decision on whether he should trigger anything or not (this in in the core of Jenkins). So for what I can see right now, the "Current build status" is not of much value.

          Oleg Nenashev added a comment -

          Kevin,

          As a workaround, you can invoke post-failure build steps from "Flexible publish" post-build action.

          Oleg Nenashev added a comment - Kevin, As a workaround, you can invoke post-failure build steps from "Flexible publish" post-build action.

          Kevin R. added a comment -

          Hey Oleg!
          I just updated the build configuration. I'll let you know how it goes.

          Kevin R. added a comment - Hey Oleg! I just updated the build configuration. I'll let you know how it goes.

            domi Dominik Bartholdi
            chr0n1x Kevin R.
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: