Skip to content

Job log adds new lines (a carriage return) after moving gitlab-runner to kubernetes helm chart

Summary

When job dynamically append text line, the job log adds a new line each time. It appeared after we moved gitlab-runner to kubernetes executor (helm deploy on gke)

What is the current bug behavior?

Currently it adds new lines at each sequence

What is the expected correct behavior?

No new lines appear

Relevant logs and/or screenshots

How it was before moving gitlab-runner to kubernetes:

image

[0KRunning with gitlab-runner 13.3.1 (738bbe5a)
[0;m[0K  on **-staging1-*** Ly93dBZh
[0;msection_start:1599656946:prepare_executor
[0K[0K[36;1mPreparing the "docker+machine" executor[0;m
[0;m[0KUsing Docker executor with image eu.gcr.io/****:latest ...
[0;m[0KPulling docker image gitlab/gitlab-runner-helper:x86_64-738bbe5a ...
[0;m[0KUsing docker image sha256:db017d20d60cb6ba8eab810c598967322dc31ac5510638e208dfe1baaec4442f for gitlab/gitlab-runner-helper:x86_64-738bbe5a ...
[0;m[0KStarting service docker:dind ...
[0;m[0KPulling docker image docker:dind ...
[0;m[0KUsing docker image sha256:66dc2d45749a48592f4348fb3d567bdd65c9dbd5402a413b6d169619e32f6bd2 for docker:dind ...
[0;m[0KWaiting for services to be up and running...
[0;m

How it works now:

image

[0KRunning with gitlab-runner 13.3.1 (738bbe5a)
[0;m[0K  on gitlab-build-gitlab-runner-58594464fd-bstwd rBdrzY6Q
[0;msection_start:1602403446:prepare_executor
[0K[0K[36;1mPreparing the "kubernetes" executor[0;m
[0;m[0KUsing Kubernetes namespace: gitlab
[0;m[0KUsing Kubernetes executor with image ${DOCKER_REGISTRY_URL}/****:latest ...
[0;m[0KUsing attach strategy to execute scripts...
[0;msection_end:1602403446:prepare_executor
[0Ksection_start:1602403446:prepare_script
[0K[0K[36;1mPreparing environment[0;m

On github runners it displaying correctly also.

Edited by Maxim Vorontsov