As a maintainer of uds-package-software-factory that is developing changes
I want my PRs to be tested before they are merged
so that I can have confidence that the changes that I make are working.
As a maintainer of uds-package-software-factory that is peer-reviewing others' changes
I want the automated testing pipeline to be definitive
so that I am not required to pull the changes down and test locally to ensure the change is working and hasn't broken something else
### Acceptance Criteria
- [ ] In order to merge a PR, it is required that a very simple E2E test passes that validates that GitLab has deployed successfully.
Notes:
We will need to decide as a team whether it is better to automatically trigger test runs or manually trigger them using the "Slash Command Dispatch" method (or some other equivalent method). It would be appropriate to create an ADR that describes the decision that was made and what its consequences are.
"Deployed successfully" means that all pods are reporting a "Ready" state and that an HTTP GET request to GitLab's login page returns a status code of 200.
An astute observer will notice that this issue looks identical to defenseunicorns/uds-capability-gitlab#5. That is the case now since our intention is that the first release of the UDS Software Factory Package contains just GitLab, with other capabilities being added incrementally. It will not be the case in the future as the intention of this testing suite will be to ensure that all of the various capabilities are being integrated successfully.
As a maintainer of uds-package-software-factory that is developing changes I want my PRs to be tested before they are merged so that I can have confidence that the changes that I make are working.
As a maintainer of uds-package-software-factory that is peer-reviewing others' changes I want the automated testing pipeline to be definitive so that I am not required to pull the changes down and test locally to ensure the change is working and hasn't broken something else
Notes: