Pipeline status "unknown" when jobs use only "tags"?

We’re running our own GitlLab CE server and runners. When using CI that includes only “tags” like:

build_x86_64:
  stage: build
  only:
    -tags
  script:
    - npm run-script build-x86_64
  tags:
    - docker

The pipline and job runs fine (for tagged commits), but Gitlab doesn’t show the pipeline status icon on the tagged commit (details page), and the pipleline badge just shows unknown for me.

If I change the job to run based on our commit message (which are standardized for our release tags) but not run a second time due to the tag (which feels very hackish ;)) like:

build_x86_64:
  stage: build
  only:
    variables:
      - $CI_COMMIT_TITLE =~ /^Release v[0-9\.].*$/ 
  except:
    - tags
  script:
    - npm run-script build-x86_64
  tags:
    - docker

then the commit shows the pipe line status icon and the badge is correct.

I figure only “tags” is a pretty popular pattern, so am I alone in seeing this??

Thanks!

2 Likes

I have the same thing.
Will open up an issue in their tracker