- Nov 26, 2021
-
-
nimrod authored
The image fails to build with the latest stable release (Bullseye) and since I'm using it anymore, I'm not going to invest time in figuring this out (it's either going back a version and seeing if that works or removing the image altogether).
-
- Nov 06, 2021
-
-
nimrod authored
-
nimrod authored
Those jobs are not always in the workflow and that makes the workflow invalid in those cases. Since the build and push already happens before those jobs will use the newer base images anyway.
-
nimrod authored
-
nimrod authored
-
nimrod authored
Some images are base images for other images. There's a need to build the base images first.
-
nimrod authored
-
nimrod authored
-
nimrod authored
- Use the environment variables (like APACHE_RUN_USER or APACHE_LOG_DIR) during the build, so now they're set earlier. - Add the APACHE_LOCK_DIR.
-
- Nov 05, 2021
- Oct 23, 2021
-
-
nimrod authored
- Use the containerfiles templates. - The repo was renamed as part of a refactor.
-
- Sep 20, 2021
- Sep 17, 2021
-
-
nimrod authored
- New, updated or migrated pre-commit hooks. - Fix found issues.
-
- Jul 24, 2021
-
-
nimrod authored
-
- Jul 23, 2021
- Jun 04, 2021
-
-
nimrod authored
I'm getting 401 or 403 with the project set.
-
nimrod authored
Without the CONTEXT variable, the rules for push jobs was broken and always triggered. This also pulled in the dependency jobs. I don't see a way to avoid defining the CONTEXT variable in both build and push jobs.
-
nimrod authored
Same as the buster image, but bullseye.
-
nimrod authored
Both latest and buster tags.
-
- May 29, 2021
-
-
nimrod authored
- Notify on scheduled pipeline failures. - Seperate the IMAGE and CONTEXT variables. Allow building where the 2 don't match (planning for httpd/buster and httpd/bullseye).
-
- May 21, 2021
- May 16, 2021