Re-evalute CI templates
Needed pipelines
-
Create jars + images of the main/release branch
- Trigger: Create a tag in the "main" branch
- Expected output:
- Build jars based on the internal version of each component, found in the project's pom.xml (actual version is found in main project's pom.xml)
- Build docker images tagging them as :{triggering_tag_name}
-
Create jars + images of the develop branch
- Trigger: Commit to the "develop" branch
- Expected output:
- Build jars based on the internal version of each component, found in the project's pom.xml (actual version is found in main project's pom.xml)
- Build docker images tagging them as :develop
-
Create jars + images of a protected branch (other than develop/main)
- Trigger: Commit to a protected branch (other than develop/main)
- Expected output:
- Build jars based on the internal version of each component, found in the project's pom.xml (actual version is found in main project's pom.xml)
- Build docker images tagging them as :{protected_branch_name}
-
Dry-run creation of jars + images of an unprotected
- Trigger: Commit to an unprotected branch (side development branch)
- Expected output:
- Dry-run building of jars based on the internal version of each component, found in the project's pom.xml (actual version is found in main project's pom.xml)
- Dry-run building (no-push) docker images tagging them as :{unprotected_branch_name}
Issues found: