Allow to use commands output as CI cache key

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

As a developer, I want to use commands as cache:key for GitLab CI, so I can use ruby:latest image and ruby -v cache key, and/or cat Gemfile, echo $SOME_VARIABLE, etc.

Intended users

Software Developer, maybe Engineers.

User experience goal

(does it duplicate "Problem to solve" section?)

The user should be able to use .gitlab-ci.yml with GitLab to cache dependencies flexible, avoid two-files one-variable-prefix limits.

Proposal

cache:
  key:
    commands:
      - ruby -v
      - echo $IMAGE
      - cat *.gemspec

Further details

Cirrus CI has similar approach: https://cirrus-ci.org/guide/writing-tasks/#cache-instruction

Honestly, it can replace files, prefix and other instructions.

Permissions and Security

• Add expected impact to members with no access (0)
• Add expected impact to Guest (10) members
• Add expected impact to Reporter (20) members
• Add expected impact to Developer (30) members
• Add expected impact to Maintainer (40) members
• Add expected impact to Owner (50) members

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references