Written by Jamie Tanna
on 
CC-BY-NC-SA-4.0 Apache-2.0
1 mins

GitLab CI Shell Executor failing builds with ERROR: Job failed: exit status 1

Featured image for sharing metadata for article

Tonight I've been playing around with GitLab CI's shell executor, and my builds have been failing with this error:

Running with gitlab-runner 13.0.1 (21cb397c)
  on gitlab-runner 9vpTPhFS
Preparing the "shell" executor
00:00
Using Shell executor...
Preparing environment
00:01
Running on gitlab-runner...
Uploading artifacts for failed job
00:00
ERROR: Job failed: exit status 1

After some searching online, it appeared that similar to when receiving No Such Directory, this comment noted that it's an issue with SKEL - the solution was to delete .bash_logout from the gitlab-runner user's home, but I also removed .bashrc and .profile.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #gitlab-ci.

This post was filed under articles.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.