Skip to content

fix: use destination definition name in place of string for custom object #236

fix: use destination definition name in place of string for custom object

fix: use destination definition name in place of string for custom object #236

Triggered via pull request September 20, 2024 07:53
Status Skipped
Total duration 4s
Artifacts
Generate Tag Names
0s
Generate Tag Names
Report Code Coverage  /  get_workflow_url
Report Code Coverage / get_workflow_url
Build User Transformer Docker Image - Prod  /  Get Changed files
Build User Transformer Docker Image - Prod / Get Changed files
Build User Transformer Docker Image - Prod  /  Get SHA information
Build User Transformer Docker Image - Prod / Get SHA information
Report Code Coverage  /  Code Coverage
Report Code Coverage / Code Coverage
Build User Transformer Docker Image - Prod  /  Build Transformer Docker Image AMD64
Build User Transformer Docker Image - Prod / Build Transformer Docker Image AMD64
Build User Transformer Docker Image - Prod  /  Build Transformer Docker Image ARM64
Build User Transformer Docker Image - Prod / Build Transformer Docker Image ARM64
Report Code Coverage  /  ...  /  notify
Report Code Coverage / slack notification on failure / notify
Build User Transformer Docker Image - Prod  /  Create multi-arch manifest
Build User Transformer Docker Image - Prod / Create multi-arch manifest
Update Helm Charts For Production and Create Pull Request
0s
Update Helm Charts For Production and Create Pull Request
Fit to window
Zoom out
Zoom in