Original author is PramodChandoria
This set of scenarios centers around the interactions of the automation execution tools (or worker systems) that are typically/frequently used to perform the work on behalf of the OSLC Service Provider and the actual OSLC Server Provider itself.
This outlines the high level scenario of the interaction between Automation server and Automation Tool.
The term “automation tool” can also be thought of as agent or worker.
- Automation Tool registers with Automation Server with the type of Automation Tool. Automation Server responds back with a URL to look for further work
- Automation Server User (manual or scheduling facility) initiates Execution of a Automation plan.
(Either user can choose one of the registered tool for execution or Automation Server can decides itselt to dynamically
allocate Execution to one of the Registered Automation tool.)
- An Automation Task is created to track this request.
- Automation Tool polls periodically to Automation Server on provided URL for any work assigned
- Automation Tool, upon finding an Automation Task, follows the link to get more information about the request
- Automation Tool picks up the work and updates the Automation Server about the work it has taken
- Automation tool continues to work and keeps on updating Automation Server with progress and any other status messages.
- Optionally an user can Cancel the Automation task. Automation tool upon receiving such instruction cancel further execution and update Automation Task
- Automation Tool upon completion of the work, Creates Automation Result back to Automation Server.
- Automation tool updates Automation task to link with the result created and and mark Automation task as complete with 100% progress.
- Automation tool repeats from step #4