Closed cmoulliard closed 3 years ago
Yes, I agree with that!
I will push the change and we will see if job will not be called for next PR push
If condition
is wrong as only one job was executed and no container image was build : https://github.com/snowdrop/release-manager/actions/runs/785457835
To be checked: @aureamunoz @jacobdotcosta
Look at this: https://github.com/snowdrop/release-manager/actions/runs/785517134 https://github.com/snowdrop/release-manager/commit/e33299d6f7378b189a0aeb10a5baa2a68588a06f However, the image built failed @cmoulliard
There is still an issue as the files resulting of the application built (= jar, lib, ...) are uploaded here
/home/runner/work/release-manager/release-manager
while docker buildx
is looking to find them here
#5 [3/4] COPY target/lib/* /deployments/lib/
#5 sha256:cb1baa6abc82dff111ea8381b0a3b0752ef545ebaaf20cd856308f4d567a0e54
#5 ERROR: lstat /var/lib/docker/tmp/buildkit-mount250359445/target/lib: no such file or directory
------
> [3/4] COPY target/lib/* /deployments/lib/:
------
error: failed to solve: rpc error: code = Unknown desc = lstat /var/lib/docker/tmp/buildkit-mount250359445/target/lib: no such file or directory
Problem reported within the previous commit has been fixed: https://github.com/snowdrop/release-manager/actions/runs/785782147
Suggestion
Refactor the github workflow to only build an image on main branch commits and not not for PR.
Example of code
WDYT: @jacobdotcosta @aureamunoz