Restructure tripleo-ci to be Consumable Externally
This blueprint is aimed at allowing for external consumption of tripleo-ci. Currently, it is not possible to reproduce what is run in tripleo-ci outside of tripleo-ci. This makes it impossible for a developer to reproduce an issue with a patch locally. It also makes it impossible to have third-party CI systems which run the same jobs as tripleo-ci.
Blueprint information
- Status:
- Complete
- Approver:
- Emilien Macchi
- Priority:
- Low
- Drafter:
- John Trowbridge
- Direction:
- Approved
- Assignee:
- John Trowbridge
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
-
Implemented
- Milestone target:
-
queens-3
- Started by
- Emilien Macchi
- Completed by
- Emilien Macchi
Related branches
Related bugs
Sprints
Whiteboard
[2017-12-08] Moving to Queens-3 this is a developer facing tooling and should not impact operators.
Work Items
Work items:
Refactor tripleo-ci to clearly separate what environment a job runs in from what is actually run on top of that environment: TODO
Create developer documentation for reproducing tripleo-ci jobs: TODO
Create documentation for third-parties to create CI using tripleo-ci as the base: TODO
Dependency tree
* Blueprints in grey have been implemented.
