[Oslc-Automation] Automation Execution scenario

[Vaibhav Srivastava]

Hi Mike, All

Thanks for the details of the scenario, I had a comment around
Job completes 
Job is updated to indicate it is complete 
Job is updated with a final verdict 
Job can possibly be updated with extra data (TBD, examples might be links 
to associated artifacts such as test results or approval records) 
Consumers can GET the final Job.

Bullet 3 : It may be possible for providers to update the extra data 
during the course of Job. I would imagine once the Job is initiated, the 
provider may want to keep the associated artifacts created and linked to 
the Job (even before Job completed).

Maybe with a scenario it will help and I will take the one mentioned here 
ie. test results.

Assume there is a Job to Run tests. 
The provider runs the Job (assume the Job is to run a Test suite which is 
a collection of testcases). Although the Job points to the actual 
completion of the collection object, there are incremental artifacts which 
the provider might want to create. If the association happens at the end, 
during the lifecycle of the Job, there may not be a mechanism to 
understand 'who' created the Test suite and lack of traceability.

Another one from a build scenario (not an expert of this area but will 
try):
A Job is to create a build for code base. 
A build contains multiple packages which get built separately and the last 
build step to create an offering. Although the Job points to the actual 
availability of the offering, during the course of the Job, there will be 
smaller packages built and the provider will keep creating them. The 
provider will want to create these packages but if we allow linkage of 
Offering to the Job at the Job completion time, there will not be 
traceability to the artifacts created and Job.

Approval records is one of the areas which I think surely falls in the 
'linking at the Job completion' scenario. I am sure there will be more in 
this area as well.

I think the job-artifact linkage could happen while the job is running or 
at the end of the job too. If this applies across we might want to keep 
that option open while formulating this scenario.

Thoughts?

Thanks
Vaibhav



From:   Michael F Fiedler <fiedler at us.ibm.com>
To:     oslc-automation at open-services.net
Date:   10/22/2011 12:27 AM
Subject:        [Oslc-Automation] Automation Execution scenario
Sent by:        oslc-automation-bounces at open-services.net




As a follow up to the workgroup discussion, I have tried to document the
execution scenario further [1].  Please take a look and provide comments 
on
the list or in the next workgroup meeting on 27 October.

There is still needed discussion on the parameter/environment passing
topic.

[1] - http://open-services.net/bin/view/Main/AutomationExecutionScenario

Regards,
Mike

Michael Fiedler
IBM Rational Software
fiedler at us.ibm.com
919-254-4170


_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20111024/bb61d4ae/attachment-0003.html>