Skip to content
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

WIP: fix: try to fix docker job #1062

Merged
merged 3 commits into from
Aug 4, 2023
Merged

Conversation

JellyBellyDev
Copy link
Member

No description provided.

@JellyBellyDev JellyBellyDev changed the title fix: try to fix docker job WIP: fix: try to fix docker job Aug 4, 2023
@JellyBellyDev JellyBellyDev merged commit 2ea5c1b into master Aug 4, 2023
2 of 4 checks passed
@JellyBellyDev JellyBellyDev deleted the fix/try-to-fix-docker-job branch August 4, 2023 18:18
@@ -94,7 +94,7 @@ jobs:

docker:

runs-on: ubuntu-20.04
runs-on: ubuntu-latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ubuntu-22.04 would be better. The latest is not predictable, is just like using dev-master in composer...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would use latest on pipelines to ensure it goes automatically on newer versions. For building tools, I believe it could be ok. If we are strict on pinning versions then we need to change elsewhere to ping the apt packages otherwise we can't ensure reproducibility (at the moment we are not pinning any package in the dockerfile nor in the pipelines).
I'm happy to give it another round to pin everything, the only downside is that it'll require more maintenance to keep it up to date.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok pin please! ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants