Bug 253285 - Define workflows around consumption and promotion
Summary: Define workflows around consumption and promotion
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Dash Athena (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Common Build Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2008-11-03 15:12 EST by Andrew Overholt CLA
Modified: 2012-01-30 11:32 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2008-11-03 15:12:51 EST 
When are builds promoted and made available for others to consume as dependencies?  How do we define whether or not we want the latest build of our dependencies or some stable stream/build?
Comment 1 Nick Boldt CLA 2009-07-29 02:55:51 EDT 
http://wiki.eclipse.org/Common_Build_Infrastructure/Publishing

Re: referencing "latest successful" or "latest stable" builds, see:

http://divby0.blogspot.com/2009/07/tracking-build-status-with-hudson-data.html

In other words, Hudson permits all this already.

Deciding what deps to use by a downstream build shall be left as an exercise for that downstream consumer. They can point at an upstream Hudson URL, an update site, an update site zip, etc.

Fixed.