CI/Linux: Build/publish Docker images used to create DEB packages #695
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From now on, whenever we detect a modification to any of the 'ubuntu-*' Dockerfiles in the 'Dockerfiles' directory, a new image will be built first (with 'docker build'), and only then it will be used to actually build the app and generate DEB packages.
If no changes to these Dockerfiles are detected, we'll simply 'docker pull' the already-existing image from the GitHub Container Registry to build the app, which will give us a faster build time.
This new approach allows us to immediately test changes made to these Dockerfiles, without having to first build them locally, test them, push them to an OCI registry, and only then use them on GitHub Actions.
Please note that these images will only be pushed to the GitHub Container Registry if all three conditions below are met:
@nuttyartist If this gets merged, hopefully you don't have to do anything else and the images will automatically published to this page: https://github.com/nuttyartist/notes/pkgs/container/notes
If you guys like this idea, I can do the same for the RPM and AppImage build jobs next.