Stack Overflow Asked by Arthu Vinicius Demetrio Santia on November 29, 2020
1- Environment:
2- .gitlab-ci.yml file:
before_script:
- echo "--------- STARTING WORK ------------"
job_homologacao:
only:
- homologation
script:
- cd /home/ati/
- mkdir test
- echo "got here"
job_producao:
only:
- master
script:
- cd /home/ati/test/
- echo "got here"
3- Error presented when the runner is executed:
Running with gitlab-runner 13.2.1 (efa30e33) on runner with Akx_BvYF shell
Preparing the "shell" performer
Using Shell executor …
Preparing environment
Running on hermes …
ERROR: Job failed (system failure): prepare environment: exit status 1. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information
4- correction attempts:
I read and executed all the procedures contained in the codumentation:
I finded the error! o/ I was erroneously editing the file .bash_logout located inside my Home /home/ati/
Gitlab when installing gitlab-runner create a Home for him in /home/gitlab-runner/
I just had to comment on the contents of the /home/gitlab-runner/.bash_logout file for the job to work.
Correct answer by Arthu Vinicius Demetrio Santia on November 29, 2020
Did you check these?
Debian users should use APT pinning, because a native package called gitlab-ci-multi-runner is available in Debian Stretch and by default, when installing gitlab-runner, that package from the official repositories will have a higher priority.
Also, be sure to disable SKEL when installing GitLab Runner: set the environment variable GITLAB_RUNNER_DISABLE_SKEL to true before you install the package.
For details on both, see https://docs.gitlab.com/runner/install/linux-repository.html#apt-pinning
Answered by Iron Bishop on November 29, 2020
Get help from others!
Recent Answers
Recent Questions
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP