[Oslc-Automation] Alternate teardown scenario

[Michael F Fiedler]

In last week's workgroup meeting I mentioned it might be helpful (to me,
anyway) to have an alternate to the primary teardown scenario.   We have
been discussing teardown in terms of deployed configurations or
environments, but it would be useful to see if the concepts still stand for
a non-deployment scenario.   While it might not be as compelling, I've
tried to apply some of the concepts to the build domain and summarize it in
the following bullets:

- Build plan for Product A is executed via an Automation Request

- Build result contains contributions for a) logfile locaions,  b) location
of binary build artifacts such has jar files, plugins, war files, etc c)
location of binary install image produced by the build

- The test team wants to ensure that this build is kept for as long they
are using it for integration testing with Product B

- The test team registers "interest" in this build (mechanism still TBD)
and the Product B build

- Optionally, the Product A build result is linked/related to the Product B
build result being used (mechanism still TBD)

- When testing is complete, interest in Product A and B is deregistered and
the builds are eligible for teardown (deletion) if no other parties are
interested.

Comments?   Holds water or too contrived?

Regards,
Mike

Michael Fiedler
IBM Rational Software
fiedler at us.ibm.com
919-254-4170
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130501/7a6c25af/attachment-0003.html>