Basic CI task for the TripleO UI
Since the UI is installed by default as part of the undercloud install, it would be good to have a basic check on CI to make sure new patches don't break it. The basic check should be a simple call to make sure the URL is accessible and checking that an element on the page is present.
Blueprint information
- Status:
- Complete
- Approver:
- Emilien Macchi
- Priority:
- Medium
- Drafter:
- Julie Pichon
- Direction:
- Approved
- Assignee:
- Julie Pichon
- Definition:
- Approved
- Series goal:
- Accepted for ocata
- Implementation:
-
Implemented
- Milestone target:
-
ocata-1
- Started by
- Julie Pichon
- Completed by
- Steven Hardy
Related branches
Related bugs
Sprints
Whiteboard
[jpichon]
1. Ensure all the patches needed for the UI to be installed by default on the undercloud are merged ( with https:/
2. Ensure the UI currently works when installed like this [DONE]
- Error 400 bad request (bug 1628484) (fixed)
- Module react-portal not found: resolved once DLRN picked up the new tripleo-ui-deps package ( https:/
- Keystone URL not set correctly (bug 1630546) (fixed)
3. Find where in CI that check should live and write it. [DONE]
Where -> The undercloud job, and undercloud_
https:/
Patch at https:/
4. Add undercloud job to tripleo-ui gate and puppet-tripleo gate, as it is a common source of breakage for the UI configuration. [DONE]
Patch at https:/
- - - - -
[akrivoka]
question brought up at summit: does it make sense to have this check implemented as a validation? we want to make it consumable outside the ci.
[jpichon]
Seems like it'd be something nice to have as well, in addition to this! The CI check is to make sure other changes don't completely break us, the goal is different.
