Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Execute commands hierarchically in a commit #238

Merged
merged 2 commits into from Apr 15, 2014
Merged

Execute commands hierarchically in a commit #238

merged 2 commits into from Apr 15, 2014

Conversation

makyo
Copy link
Contributor

@makyo makyo commented Apr 14, 2014

This introduces a means to execute commands after commands on which they depend
have already been executed. There will be two follow-up branches:

  • Wait until each level of the hierarchy has fully executed (i.e.: RPC
    callbacks received) executed before moving on to the next
  • Remove commands from the changeset after they have executed.

Fixed test that was doing a deep-equal on an object that had changed.

This introduces a means to execute commands after commands on which they depend
have already been executed.  There will be two follow-up branches:

* Wait until each level of the hierarchy has fully executed (i.e.: RPC
  callbacks received) executed before moving on to the next
* Remove commands from the changeset after they have executed.

Fixed test that was doing a deep-equal on an object that had changed.
@makyo
Copy link
Contributor Author

makyo commented Apr 14, 2014

To QA:

Use /:flags:/ecs/mv and deploy some services, then run app.ecs.commit() from the console. Everything else should work unchanged.

}
}

function placeIfNeeded(value, key) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if all of these nested function calls were methods on ECS with the data passed into them on each call.

@hatched
Copy link
Contributor

hatched commented Apr 14, 2014

👍 Thanks for this branch it looks good!
The function to method thing is the only thing I feel strongly about, the rest is up to you.

@jujugui
Copy link
Contributor

jujugui commented Apr 14, 2014

Test PASSed.
Refer to this link for build results: http://ci.jujugui.org:8080/job/juju-gui/725/

@jujugui
Copy link
Contributor

jujugui commented Apr 15, 2014

Test PASSed.
Refer to this link for build results: http://ci.jujugui.org:8080/job/juju-gui/726/

@makyo
Copy link
Contributor Author

makyo commented Apr 15, 2014

:shipit:

@jujugui
Copy link
Contributor

jujugui commented Apr 15, 2014

Status: merge request accepted. Url: http://ci.jujugui.org:8080/job/juju-gui-merge

jujugui added a commit that referenced this pull request Apr 15, 2014
This introduces a means to execute commands after commands on which they depend
have already been executed.  There will be two follow-up branches:

* Wait until each level of the hierarchy has fully executed (i.e.: RPC
  callbacks received) executed before moving on to the next
* Remove commands from the changeset after they have executed.

Fixed test that was doing a deep-equal on an object that had changed.
@jujugui jujugui merged commit b320e08 into juju:develop Apr 15, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants