CI currently builds all docker images each time it is run in a Push cycle. We should use Nx Affected to determine which projects need to be rebuilt, and update all other tags of unaffected ones to the latest.
Acceptance Criteria:
I want to run CI builds utilizing Nx affected tooling
because this will improve the speed of CI
and this will help me to speed up and increase reliability of PRs and deployments, while reducing redundant work.
Development Checklist:
In the CI for PUSH:
[ ] Use Nx Affected to determine which apps need to be rebuilt.
[ ] Build and dockerize any apps that are affected.
[ ] Generate a tag -- TODO: Determine tagging scheme. Possibly "branch-SHA-pipeline#" e.g. main_4a50a62_92919.
Description:
CI currently builds all docker images each time it is run in a Push cycle. We should use Nx Affected to determine which projects need to be rebuilt, and update all other tags of unaffected ones to the latest.
Acceptance Criteria:
I want to run CI builds utilizing Nx affected tooling because this will improve the speed of CI and this will help me to speed up and increase reliability of PRs and deployments, while reducing redundant work.
Development Checklist:
In the CI for PUSH:
main_4a50a62_92919.Resources
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
User story is includedUser role and type are identifiedWireframes are included (if required)·Definition of Done (Note: If any of these points are not applicable, mark N/A)