• Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Minor Minor
    • multijob-plugin
    • None
    • Jenkins 2.38
      Multijob plugin 1.26

      Hi.

      We have Jenkins jobs which use multijob plugin and we start some downstream jobs conditionally.
      It means that some jobs configured in MultiJob will never start, some may finish successfully or be unstable.
      So once there is a downstream job which is disabled via condition ('enableCondition' and 'condition' XML options) the MultiJob build is always reported as failed no matter what are the results of builds which were actually executed.

          [JENKINS-47033] MultiJob treats not started builds as failure

          I believe this is due to MultiJobRunnerImpl.evaluateResult() checks only for "isWorseThan()", but does not check if a build was conditionally disabled.
          Or conditionally disabled builds should not be populated with addSubBuild()..

          Pavel Malyshev added a comment - I believe this is due to MultiJobRunnerImpl.evaluateResult() checks only for "isWorseThan()", but does not check if a build was conditionally disabled. Or conditionally disabled builds should not be populated with addSubBuild()..

          Closing issue as part of tikal-multijob-plugin issues cleanup.
          If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

          Yoram Michaeli added a comment - Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

            Unassigned Unassigned
            afunix Pavel Malyshev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: