vdk-heartbeat: pipelines-control-service-integration-tests image rebu…

…ild (#848) * vdk-heartbeat: pipelines-control-service-integration-tests image rebuild The vdk-heartbeat release documentation required a merge to master, for triggering the release process. However, the control-service CI/CD that depends on vdk-heartbeat, does not consider new vdk-heartbeat versions. Also, changing pipelines_control_service `version.txt` does not trigger release nor rebuild, for example #814 Added a comment to control-service `.gitlab-ci.yml` to trigger an IT image update. Documented a workaround in `README.md` until automated. Testing Done: will monitor the pipelines for image rebuild Signed-off-by: ikoleva <[email protected]>
vmware · May 30, 2022 · 21ab3a0 · 21ab3a0
1 parent 415f9a1
commit 21ab3a0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/projects/control-service/cicd/.gitlab-ci.yml b/projects/control-service/cicd/.gitlab-ci.yml
@@ -265,6 +265,7 @@ control_service_release:
       - main
     changes: *control_service_change_locations
 
+# TODO: automatically rebuild image on vdk-heartbeat change
 control_service_vdk_heartbeat_release:
   image: docker:19.03.8
   services:

diff --git a/projects/vdk-heartbeat/README.md b/projects/vdk-heartbeat/README.md
@@ -62,6 +62,7 @@ Releases are made to PyPI. <br>
 Versioning follows https://semver.org.
 
 * A release step in Gitlab CI is automatically triggered after merging changes if build/tests are successful.
+* To trigger a control-service integration tests image rebuild, commit any `control_service_change_locations`-defined change in [CONTRIBUTING.md](../control-service/cicd/.gitlab-ci.yml) except [version.txt](../control-service/projects/helm_charts/pipelines-control-service/version.txt)- until automated
 * Update major or minor version when necessary only.
 
 ## Tests