inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: inedo-buildmaster-plugin
    • None
    • Environment:
      BuildMaster 6.0.10
      Jenkins 2.121.3
      inedo-buildmaster plugin 2.0.1

      After called Deploy BuildMaster Package to Stage, it will end up reporting that the BuildMaster job was aborted even though the job wasn't aborted.

      The job does have warnings but it completes without errors.

      This causes Jenkins to see the build job as a failure.

      If a job does not have warning then it completes fine.

            Assignee:
            Andrew Sumner
            Reporter:
            Jon Starbird
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: