ERROR: Build failed: exit status 1

Problem with build after last update. Wenn I run build from gitlab after last update, I get the following error message after 3s:

gitlab-ci-multi-runner 1.1.2 (78b3f82)
Using Shell executor...

ERROR: Build failed: exit status 1

I have tried to test the execution with --debug, and it is working fine. How can i check where the problem is?

I have exactly the same error when I upgrade to gitlab-ce 8.6.5

• gitlab-ci-multi-runner version 1.1.2 (78b3f82)
• OS debian 8.4

I have the same issue. Any way to solve it?

@Stanczak @dducatel I downgraded to 1.1.0 and it works.

@ayufan can you update CHANGELOG.md with changes for versions 1.1.1 and 1.1.2, please. It's not clear what could break our builds.

@tamtamchik The changes in 1.1.1 and 1.1.2 are trying to fix broken support for shell detection.

@tamtamchik What are you using: OS, Distrubution, what is default shell used by gitlab-runner user.

@ayufan
OS: Ubuntu 12.04.5 LTS
Shell for gitlab-runner: /bin/false

Strange, then how come 1.1.0 was working correctly without any settings for shell inconfig.toml file.

My config that actually works on 1.1.0

concurrent = 1

[[runners]]
  name = "..."
  url = "..."
  token = "..."
  tls-ca-file = ""
  executor = "shell"
  builds_dir = ""
  [runners.ssh]
  [runners.docker]
    image = ""
    privileged = false
  [runners.parallels]
    base_name = ""
  [runners.virtualbox]
    base_name = ""

I do know. I had to fix this two-or-three times, because of variety of configurations :(

https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/shells/bash.go#L201

This line misses --shell /bin/bash which was present in 1.1.0.

For now, you can use 1.1.2, but you have to usermod -s /bin/bash gitlab-runner.

@ayufan @Stanczak @dducatel usermod -s /bin/bash gitlab-runner did the job.

Thank you, @ayufan for a very fast response, and have a nice day!

usermod is working! Really thx!!

I'll release 1.1.3 that will solve that problem. The plan for release is tomorrow morning. For now you can try to grab Bleeding Edge! (it's building now). No longer the usermod fix will be required :)

Milestone changed to v1.1

Reassigned to @ayufan

cc @tmaczukin

Added waiting for feedback label

Did 1.1.3 or 1.1.4 resolved the problem?

Status changed to closed

We haven't received an update for more than 14 days so we will assume that the problem is fixed or is no longer valid. If you still experience the same problem try upgrading to the latest version. If the issue persists, reopen this issue or merge request with the relevant information.

@tmaczukin yes, it was fixed. Thanks!