| Summary: | extend builds model to support sub-builds | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | plcnkl |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 353355 | ||
|
Description
Steffen Pingel
(In reply to comment #0) > It is common for build server to support splitting a build plan into several > stages or sub-tasks: http://wiki.eclipse.org/Mylyn/Builds/Architecture. Based > on the discussion on bug 353355 the builds framework should support this. Mr. Pingel: Thank you very much for adding me to the cc list of this bug! After checking koji's web interface, I think your's and Mr. Kurtakov's suggestion about monitoring a koji package makes sense too. I also did an entity/api checking, I think we are able to travel to both builds and tasks with a given package ID (if the build is actually linked to a task in the database). So I will revise the data model and post it in bug #353355. Ken Leung Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |