Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-3976

Release pipeline: Setup `continue` step

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 1.1.0.Final
    • None
    • Build and release
    • None
    • False
    • False
    • Undefined
    • ---
    • ---
    • 2020 Week 49-51 (from Nov 30)

      `skip` was used until now to just skip a job. but skipping a deploy job would anyway launch the promote part, even if the deploy was totally failing and we just ignored it.

      `skip` should in that case avoid the promote job to be executed.

      a new `continue` choice should be set. For example in the case of testing failing due to instability but artifacts are still ok.

              tradisso@redhat.com Tristan Radisson
              tradisso@redhat.com Tristan Radisson
              Dominik Hanak Dominik Hanak
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: