Ci/cd jobs failing today at "created fresh repository"

GitLab CI/CD
1

Today I’m finding that my ci/cd jobs are failing. The job starts out like this, but hangs after “created fresh repository” and sits there for an hour or so before dying:

Running with gitlab-runner 13.5.0 (ece86343) on docker-auto-scale z3WU8uu- Preparing the "docker+machine" executor 00:34 Using Docker executor with image ruby:2.5 ... Pulling docker image ruby:2.5 ... Using docker image sha256:b7280b81558d31d64ac82aa66a9540e04baf9d15abb8fff1cb6ccf770533ba61 for ruby:2.5 with digest ruby@sha256:c790a101d80a26e058c5ebe20bdb8843cbed62cd60e4fb5bf4132943d6fa2688 ... Preparing environment 00:02 Running on runner-z3wu8uu--project-19170435-concurrent-0 via runner-z3wu8uu--srm-1604957489-3bf2c155... Getting source from Git repository $ eval "$CI_PRE_CLONE_SCRIPT" Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/catselbow/practical-computing-for-science-and-engineering/.git/ Created fresh repository.

The job is simple: it just copies some files into public:

pages:
script:

  • mkdir public
  • sh gitlab-pages-deploy.sh
  • cp -r book-web-site/* public/
    artifacts:
    paths:
    • public
      only:
  • master
2

Hi,
did you have any news on this?
I struggle with an Group-Runner and this error see: Group Runner stuck with 'Created fresh repository.'

Regards…

3

Have you successfully run any jobs on this runner, or is this the only job you have attempted to run?

Where is your runner provisioned?(AWS, GCP, etc.)

How much memory/CPU/disk space do the executors have? I think there is a chance that the executor is running out of resources and hanging because of that.

4

Hi,
I run an shell runner on an Windows10 LTSC VM as Service.

The runner is not able to run ANY job at all.
Resources:

  • RAM (in total): 8GB (not exceeding 4GB during running 2 jobs)
  • Disk: 128 GB

We do have a shared runner which is working perfectly :frowning:

Thanks for your imput

5

I think it might have to do with how your runner is configured then. I think this because in the output

 Preparing the "docker+machine" executor 00:34

shows that the runner is using the docker+machine executor, which is not the same as the shell executor.

Do you mind sharing the config.toml that is on the runner and any flags you used when registering the runner? (with any sensitive information redacted)

6

I can’t find the ouptut in my original post:

Preparing the “docker+machine” executor 00:34

Is it possible, that you quoted an different post?

The thing is, that I don’t have privileged access to the machine (that’s why we use it as service)

I wrote this config.toml (below) and orderd an admin to registration of the runner with

.\gitlab-runner.exe register

concurrent = 2
check_interval = 0
log_level = "debug"
log_format = "text"

[session_server]
  session_timeout = 1800

[[runners]]
  name = "Computername"
  url = "https://git.company.com/"
  token = "TOKEN"
  executor = "shell"
  shell = "powershell"
  environment = ["PATH=PATH;C:/git/bin;C:/cmake/bin;C:/MinGW/bin"]
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
    [runners.cache.azure]
7

I apologize, I quoted the post at the top of this thread by the user catselbow, I didn’t notice that you are a different user.

In that case, I’m sorry but I don’t know how to help you. Hopefully someone will come through here who has more experience with shell executors who can help you.

1 Like