We have a few scenarios where updating the build result after the build has completed is helpful.
- A build is used to kick off child builds and for purposes of viewing the results/downloads/links/logs in one place, the child builds update the original build with their contributions. - If a build has failed or there is some other useful information about that build, having the ability to update the build result with notes about the build keeps information from getting lost. - Perhaps, a build has been declared the final build for the release and the ability to mark the build as locked and not available for deletion insures that all of the results and downloads are kept. Best regards, Brent Ulbricht Rational Build 512-286-2502 From: Richard Rakich/Lexington/IBM@IBMUS To: [email protected] Date: 10/24/2011 05:10 PM Subject: Re: [Oslc-Automation] Automation Execution scenario Sent by: [email protected] The only time I can think of where one would want to modify results after a job is complete is if there was a problem in the build and it was fixed manually. I have seen this a number of times when something was broken in a build job and a fix was delivered. Instead of starting a whole new job, the portion of the build that failed was rebuilt manually, status updated and the rest of the original job is continued on. I'm not sure if that would count as still being an active job or not, but it is a somewhat typical use case. - Rich Richard Rakich Build Architect - IBM Rational Software IBM E-mail: [email protected] Find me on: LinkedIn: http://www.linkedin.com/in/rrakich 550 King St "The only reason a problem is a problem is because I am Littleton, MA using an old solution to solve a new problem. To solve a 01460-1250 new problem requires imagination, intuition, faith and a United States love for adventure" - Robert Kiyosaki [email protected] wrote on 10/24/2011 05:59:05 PM: > From: Charles Rankin/Austin/IBM@IBMUS > To: [email protected], > Date: 10/24/2011 06:00 PM > Subject: Re: [Oslc-Automation] Automation Execution scenario > Sent by: [email protected] > > [email protected] wrote on 10/24/2011 02:24:57 AM: > > > Vaibhav Srivastava <[email protected]> > > > > 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. > > I agree with you Vaibhav. My assumption is that most of the updates > would happen while the job is still running. In fact, while I find > utility in being able to update the job after it is in a "final" > state (i.e., after it has completed execution), I don't believe that > all (most?) tools support that capability. We'll probably have to > call that out in the spec as a SHOULD or MAY. > > Charles Rankin > Rational CTO Team -- Mobile Development Strategy > 101/4L-002 T/L 966-2386_______________________________________________ > Oslc-Automation mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
