feat: Create a job artifact command
-
Please check this box if this contribution uses AI-generated content as outlined in the GitLab DCO & CLA
Description
Following the discussions on #7433 (closed), this is the first MR of a (long) series to create a specific job subgroup of commands.
I just moved the code from glab ci artifact to glab job artifact, and I keep the ci version to not introduce a breaking change without appropriate notice.
The purpose is to split the commands of glab ci into both glab job and glab pipeline (that's why I've also added the deprecation message on the pipe and pipeline aliases).
Instructed by this comment, I'll create one MR per command moved.
Related Issues
Part of #7433 (closed)
How has this been tested?
I added unit tests on this help message for the new job subgroup of commands, I keep the existing tests of the artifact command. I've also use the command on artifacts generated by this project.
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to change) -
Documentation -
Chore (Related to CI or Packaging to platforms) -
Test gap
Edited by Sylvain Nieuwlandt