Skip to content

Unable to update gems without causing compile-test-assets as-if-jh to fail

I attempted to update Rugged in !73888 (closed), but this caused compile-test-assets as-if-jh to fail in https://gitlab.com/gitlab-org/gitlab/-/jobs/1755209981:

$ bundle install --jobs=$(nproc) --retry=3 --quiet  && bundle check
You have requested:
  rugged ~> 1.2
The bundle currently has rugged locked at 1.1.0.
Try running `bundle update rugged`
If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
Uploading artifacts for failed job

!70000 (merged) was updated on October 25. Since then, Gemfile was only touched once or twice. However, https://gitlab.com/gitlab-org/gitlab/-/jobs/1752507493 passed fine.

I'm not sure why this is failing. The dd-jh-fodler job extracts the archive into the jh directory, and it looks like the Gemfile is pointing to to jh/Gemfile.

add-jh-folder:
  extends: .setup:rules:add-jh-folder
  image: ${GITLAB_DEPENDENCY_PROXY}alpine:edge
  stage: prepare
  before_script:
    - apk add --no-cache --update curl bash
  script:
    - curl --location -o "jh-folder.tar.gz" "https://gitlab.com/gitlab-jh/gitlab/-/archive/main-jh/gitlab-main-jh.tar.gz?path=jh"
    - tar -xf "jh-folder.tar.gz"
    - mv gitlab-main-jh-jh/jh/ ./
    - ls -l jh/
  artifacts:
    expire_in: 2d
    paths:
      - jh/

/cc: @godfat, @rymai, @alberts-gitlab

Edited by Stan Hu