-
Notifications
You must be signed in to change notification settings - Fork 1
Research GitLab test environment options #51
Copy link
Copy link
Open
Labels
medium priorityThis should be addressed soonThis should be addressed soonresearchIndicate that this is a research/exploratory taskIndicate that this is a research/exploratory tasktaskTask/chore unrelated to a bug or feature requestTask/chore unrelated to a bug or feature request
Description
Activity
Metadata
Metadata
Assignees
Labels
medium priorityThis should be addressed soonThis should be addressed soonresearchIndicate that this is a research/exploratory taskIndicate that this is a research/exploratory tasktaskTask/chore unrelated to a bug or feature requestTask/chore unrelated to a bug or feature request
Description
The GitLab CI integration was created and released without a corresponding test environment to use to make sure it all works in an automated fashion. Manual testing was performed for the initial release, but extensive manual testing is not a good option for the long term. This is a spike/research ticket that is meant to explore options for the best path forward. Time box this ticket to no more than one (1) working day.
Additional Details
There is already a
phylum-dev/TestGitLabWorkflowprivate repository that was used for this purpose in the past, but it has not been updated to match the new integration. It may also be replaced with something different. Ideally, the method for testing integrations would be extensible such that each new integration would bring an incremental change and not a completely new set of repositories and testing methods. It is also a goal to devise a solution that is able to run in an automated fashion...in either this repository, the CLI repository, or both.Acceptance Criteria