Closed TrevorNodeJS closed 7 months ago
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team
to your comment.
Issue got stale and no further activity happened. It has automatically been closed. Please re-open in case you still consider it relevant.
There are Three stages enabled in my pipeline:
Acceptance
Docker image tonghe-hello-world:1.0.3-20240118093828_8acb8cc6525a0934d22b447865818278994b41f0 is deployed into target cluster successfully.
Promote
docker image is push into docker registry: tonghe-hello-world-release:1.0.3
Release
kubernetesDeploy alwayse deploy tonghe-hello-world:1.0.3-20240118093828_8acb8cc6525a0934d22b447865818278994b41f0, instead of promoted docker image tonghe-hello-world-release:1.0.3
for your information, kubernetes can deploy promoted docker image tonghe-hello-world-release:1.0.3 via below input:
expectation:
kubernetes can deploy promoted docker image tonghe-hello-world-release:1.0.3 via below input: