Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task groups #2

Open
synhershko opened this issue Sep 23, 2010 · 1 comment
Open

Task groups #2

synhershko opened this issue Sep 23, 2010 · 1 comment

Comments

@synhershko
Copy link
Owner

Currently, all IUpdateTask objects are applied in one go, or rollbacked at once if something goes wrong. NAppUpdate should support grouping of tasks, so a feed (NauXml or any other) can specify what tasks are related to each other. This way, even if one task fails another unrelated one can still be completed.

Presenting a new "BatchTask" object will probably do the job, but some thought needs to be put into this, so functionality such as update descriptions, reporting, rolling back etc will all be compatible and done correctly.

@jamielennox
Copy link

have a look at my branch taskgroups for my ideas.

If you keep a group simply as a task that performs other tasks then the flow of the library changes very little. That branch also works without breaking the NAppXML format.

It is a little unclean and not ready to be brought across but it should show my thoughts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants