Merge lp:~canonical-ci-engineering/ubuntu-ci-services-itself/pm into lp:ubuntu-ci-services-itself
Proposed by
Ursula Junque
Status: | Rejected |
---|---|
Rejected by: | Chris Johnston |
Proposed branch: | lp:~canonical-ci-engineering/ubuntu-ci-services-itself/pm |
Merge into: | lp:ubuntu-ci-services-itself |
Diff against target: |
447 lines (+362/-58) (has conflicts) 4 files modified
docs/components/planned.rst (+1/-1) docs/components/project-manager.rst (+0/-41) docs/components/test-database.rst (+0/-16) docs/components/ticket-system.rst (+361/-0) Conflict adding file docs/components/ticket-system.rst. Moved existing file to docs/components/ticket-system.rst.moved. |
To merge this branch: | bzr merge lp:~canonical-ci-engineering/ubuntu-ci-services-itself/pm |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Francis Ginther | Approve | ||
Vincent Ladeuil (community) | Approve | ||
Review via email: mp+198139@code.launchpad.net |
Commit message
Adding the design, modeling and beginning API calls for Houston.
Description of the change
Adding the design, modelling and part of the REST API calls for Houston (former project manager) phase 0.
Design section explains the approach to process source packages only.
NOTE: Nicely formatted page: http://
To post a comment you must log in.
Unmerged revisions
- 35. By Ursula Junque
-
Changing references from houston to ticket system
- 34. By Ursula Junque
-
Renaming houston to ticket system
- 33. By Chris Johnston
-
Fix build error
- 32. By Ursula Junque
-
Added set_subticket_
status - 31. By Ursula Junque
-
Added 'Not Started' status to workflow steps
- 30. By Ursula Junque
-
More formatting
- 29. By Ursula Junque
-
REST API in same title level as other to show in planned page
- 28. By Ursula Junque
-
API formatting
- 27. By Ursula Junque
-
removing ticket system as it's inside houston now
- 26. By Ursula Junque
-
s/project-
manager/ houston/
Overall: sounds great but already a bit complex, I wonder if we can simplify things a bit.
Some details:
24 +* Runs as a persistent service, when it goes down, the engine halts.
25 +* State needs to serialized whenever it is updated, so that status can be regenerated on a restart.
+1
57 +* PPA Assigner - Provides two PPAs to perform package builds, one for MPs themselves, another for MPs + trunk.
Isn't phase 0 using a single PPA only ?
60 +* Integration Test Runner - Runs the specified tests on up to 3 images.
61 +
Just 'Test Runner', the 'Integration' is silent ;)
80 + package: chris-foobar-pkg
81 + version: 1.1-0ubuntu2
82 + source: chris-foobar-src
Is there a strong reason to use ':' or can we use '=' instead ?
I don't want to bikeshed there so if you feel strongly about, go for
it. Otherwise, this is configuration data and I'd rather use '=' to make
sure we keep it simple and don't turn it into a full json that only experts
can decipher ;)
233 + WORKFLOW_STEPS = ( STEP_STATUSES = (
239 + WORKFLOW_
I don't get why those are split, aren't them all just states for the ticket ?
1 === added file 'docs/component s/houston. rst' s/project- manager. rst'
380 === removed file 'docs/component
O.M.G. !
This is a sin, please use 'bzr mv docs/components /project- manger. rst docs/components /houston. rst' !
A kitten dies everytime you do remove+add ;-)
More seriously, bzr supports renames, use that feature, it preserves
history, in this specific case it would have more clearly show what you did
change in this proposal.
....
Ha right, that was a rewrite on the side and the remove was revno 27.
Ok, the kitten survived after all ;)
Summary, no need to block on the questions asked above, the answers can come in a followup, this is significant progress, let's land it.