-
Notifications
You must be signed in to change notification settings - Fork 6
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
Improve CI process #721
Labels
Comments
matiasgarciaisaia
added a commit
that referenced
this issue
Mar 12, 2024
Since the development image was basically a subset of the production one, we now unify them in a multi-stage image. See #721
matiasgarciaisaia
added a commit
that referenced
this issue
Mar 12, 2024
Instead of sharing a repository, make each of them have its own. See #721
Merged
matiasgarciaisaia
added a commit
that referenced
this issue
Mar 19, 2024
* Unify Dockerfiles for app's prod & development Since the development image was basically a subset of the production one, we now unify them in a multi-stage image. See #721 * Stop retrying apt packages installation in Docker The old retries were probably set up to workaround network issues in the old CI process. We don't need them now. See 500369f See #721 * Split mapcache & mapserver Docker repos Instead of sharing a repository, make each of them have its own. See #721
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some issues with the new Github Actions based CI process that we should tackle:
Dockerfile-dev
is exactly the same as the first few steps of thebuild
stage for the actual image (we should reuse thebuild
stage, or a subset of it, for development and tests)The text was updated successfully, but these errors were encountered: