- Apr 24, 2022
-
-
Vincent Stchu authored
-
Vincent Stchu authored
-
Vincent Stchu authored
-
Vincent Stchu authored
-
Vincent Stchu authored
-
Vincent Stchu authored
-
JiHu Release Tools Bot authored
-
- Apr 23, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
- Apr 22, 2022
-
-
DJ Mountney authored
CI: improve image cache handling See merge request gitlab-org/build/CNG!988
-
Jason Plum authored
-
Jason Plum authored
Bump container registry to v3.39.2 See merge request gitlab-org/build/CNG!987
-
João Pereira authored
-
- Apr 21, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
- Apr 20, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
Jason Plum authored
fix(gitlab-pages): graceful termination See merge request gitlab-org/build/CNG!979
-
Jason Plum authored
Update CI certification job for latest gitlab-omnibus-builder image See merge request gitlab-org/build/CNG!873
-
Gerard Hickey authored
-
Jason Plum authored
Bump container registry to v3.39.1 See merge request gitlab-org/build/CNG!982
-
João Pereira authored
-
- Apr 19, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
Jason Plum authored
fix: gitlab-workhorse graceful termination See merge request gitlab-org/build/CNG!972
-
Steve Azzopardi authored
What --- Move the gitlab-pages process to be PID 1 inside of the container by using `exec` in start up script and CMD in exec form as well. Why --- In https://gitlab.com/gitlab-org/charts/gitlab/-/issues/3249 we found out that most image we build their main process doesn't run as PID 1. This can lead to issues where we assume `SIGTERM` is being sent to the process but it isn't, it's sent to the bash script that starts the process which doesn't redirect the signal to the gitlab-pages process. Signed-off-by:
Steve Azzopardi <sazzopardi@gitlab.com> Reference: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/3249
-
Steve Azzopardi authored
What --- - Move `gitlab-workhorse` process to PID 1 - Add feature flag to set `gitlab-workhorse` in PID 1. Off by default, and will be removed after successful rollout in GitLab.com Why --- GitLab-workhorse supports [graceful termination](https://gitlab.com/gitlab-org/gitlab/-/issues/325114), however, we are not [using it](https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/15497#note_911366252), this causes the `gitlab-workhorse` pod to run for `30s` on shutdown responding with `502` and then receiving `SIGKILL`. By default Kubernetes sends `SIGTERM` to PID `1` in the container, and workhorse [listens for this signal](https://gitlab.com/gitlab-org/gitlab/-/blob/dbeafad46dda53092c0eb46eceb2337a83f3ee9c/workhorse/main.go#L242) however workhorse is not `PID` 1 as seen in the process tree below, this is because of 2 reasons: 1. `CMD` isn't passed as an array. https://docs.docker.com/engine/reference/builder/#cmd in it specifies: `CMD command param...
-
- Apr 15, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
Balasankar 'Balu' C authored
toolbox: Add redis-tools for Redis client See merge request gitlab-org/build/CNG!968
-
Stan Hu authored
Changelog: added
-
- Apr 14, 2022
-
-
JH_CNG_SYNC_TOKEN authored
-
Jason Plum authored
Include ruby version in gitlab-go container version See merge request gitlab-org/build/CNG!971
-
DJ Mountney authored
-
JH_CNG_SYNC_TOKEN authored
-
Balasankar 'Balu' C authored
Update Node from 14 to 16.14.2 and Yarn to 1.22.5 to 1.22.18 See merge request gitlab-org/build/CNG!965
-
Miguel Rincon authored
-
Balasankar 'Balu' C authored
Install missing transient dependencies Closes gitlab-org/gitlab#358890 See merge request gitlab-org/build/CNG!974
-
Wenbin Shu (Vincent Stchu) authored
Adopt new tcr registry See merge request gitlab-cn/build/cng-images!21
-
Vincent Stchu authored
-
Hossein Pursultani authored
-
JH_CNG_SYNC_TOKEN authored
-
- Apr 13, 2022
-
-
DJ Mountney authored
Bump container registry to v3.39.0 See merge request gitlab-org/build/CNG!973
-
João Pereira authored
-
JH_CNG_SYNC_TOKEN authored
-