Skip to content

Container image build validation successfull but build failed #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cybcon opened this issue Feb 6, 2024 · 1 comment
Closed

Container image build validation successfull but build failed #32

cybcon opened this issue Feb 6, 2024 · 1 comment
Assignees
Labels
chore updating grunt tasks etc; no production code change

Comments

@cybcon
Copy link
Owner

cybcon commented Feb 6, 2024

Summary

The pipeline run, triggered on PRs, for the workflow container-image-build-validation ends successfully if one of the jobs-chain ends successful.

grafik

grafik

Expected behaviour

The run fails if any of the jobs runs fails.

Example

#31
https://github.com/cybcon/modbus-server/actions/runs/7789913852?pr=31

@cybcon
Copy link
Owner Author

cybcon commented Feb 14, 2024

Another discussion on GitHub facing a similar issue: https://github.com/orgs/community/discussions/57724
The solution here is to set the parameter permissions: write-all inside the job definition.

This will be inside the .github/workflows/container-image-build-validation.yaml pipeline definition in job function-test-preparation:

grafik

@cybcon cybcon self-assigned this Feb 14, 2024
@cybcon cybcon added the chore updating grunt tasks etc; no production code change label Feb 14, 2024
@cybcon cybcon closed this as completed Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore updating grunt tasks etc; no production code change
Projects
None yet
Development

No branches or pull requests

1 participant