You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "brian wickman (JIRA)" <ji...@apache.org> on 2014/02/04 00:25:05 UTC

[jira] [Created] (AURORA-167) Add on_success and on_failure Constraints to Thermos

brian wickman created AURORA-167:
------------------------------------

             Summary: Add on_success and on_failure Constraints to Thermos
                 Key: AURORA-167
                 URL: https://issues.apache.org/jira/browse/AURORA-167
             Project: Aurora
          Issue Type: Task
          Components: Thermos
            Reporter: brian wickman
            Priority: Trivial


Currently there is one supported constraint in Thermos: 'order' or if you think of it another way, "on_finish".

Constraint(order = ['A', 'B']) means that 'B' should run after 'A' has completed, regardless of its terminal state.  In a way, this could be translated to Constraint(on_success = ['A', 'B'], on_failure = ['A', 'B'])

But there shouldn't be anything preventing somebody from doing Constraint(on_success = ['A', 'B'], on_failure = ['A', 'C']).  E.g. maybe process 'B' sends an e-mail that a deploy was successful, and process 'C' starts a rollback process.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)