Details
-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
13
-
False
-
False
-
No
-
No
-
No
-
Pending
-
None
-
MODH Sprint 37
Description
The pipeline configuration has been discussed in the Building & Testing WG:
- Raise a Pull Request.
- Author of the PR will add /build or /test as a comment in the PR
/build command:
- Syntax: /build
- Generate a new livebuild image with the code changes in PR (IMP: PR should always be rebased with the main branch so that all the merged PRs are taken for creating the livebuild image).
- Output: quay.io/modh/rhods-operator-live-catalog:{repo-name}-{jira-issue}
/test command:
- Syntax: /test
- If the /build command has not been executed, trigger the build pipeline.
- Once the jenkins pipeline for creating the livebuild is successful, automatically smoke test jenkins pipeline will get triggered using the livebuild image.
- After smoke job completion, status of the smoke test is added (PASS/FAIL) in the PR.
- If passed, The Jira issue corresponding to the PR will be updated from "Coding In Progress" to "Pull request Sent" once the step 3 adds comment as "PASS" in the PR.
- In case of failure, author of the PR debugs and analyses the failure and reruns /test.
- When reviewers approve the change and it is finally merged into the main branch the Jira issue will be updated from “Pull request Sent” to “Verified for RC”.