Gitlab CI/CD Artifact to Asset

GitLab CI/CD
1

Describe your question in as much detail as possible:
Hi all! I’m using GitLab CI/CD to create releases after building various parts of a program in several different stages. Ultimately, I’d like the artifacts of these stages to be promoted to assets for my releases. Currently, it appears that my release job downloads the artifacts as expected, but I’m not sure how or if is possible to promote these artifacts to assets.

  • What are you seeing, and how does that differ from what you expect to see?
    My artifacts are downloaded into my release job - using the assets: option I expect to be able to promote the artifacts into assets but that does not appear to work as the link that I create during asset creation is a dead link that goes nowhere.
  • Consider including screenshots, error messages, and/or other helpful visuals
release:
    tag_name: ${MAJOR}.${MINOR}.${REVISION}
    description: 'CHANGELOG.md'
    assets:
      links:
      - name: 'pycZip'
        filepath: 'pyc.zip'
        url: 'http://gitlab.gitlab01.com/gui/projectone/-/releases/pyc${MAJOR}.${MINOR}.${REVISION}'
      - name: 'resourcesZip'
        filepath: 'resources.zip'
        url: 'http://gitlab.gitlab01.com/gui/projectone/-/releases/resources${MAJOR}.${MINOR}.${REVISION}'

  • What version are you on? Are you using self-managed or GitLab.com?

    • GitLab (Hint: /help): Self managed, 13.12.1-ee
    • Runner (Hint: /admin/runners): Docker, registry.gitlab.com/gitlab-org/release-cli:latest

  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
    I’ve attempted to make simpler examples but I might be fundamentally misunderstanding how release assets are created. My attempted examples are long since deleted, but think using a .txt as the release asset.

I think I’ve read just about all the documentation regarding release assets - I think I’m still quite lost.

Any help is appreciated!