Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bk artifacts list command #413

Merged
merged 4 commits into from
Dec 11, 2024
Merged

bk artifacts list command #413

merged 4 commits into from
Dec 11, 2024

Conversation

lizrabuya
Copy link
Contributor

@lizrabuya lizrabuya commented Dec 10, 2024

This PR implements bk artifacts list command

List artifacts for a build or a job in a build.

You can pass an optional build number. If omitted, the most recent build on the current branch will be resolved.

Usage:
  bk artifacts list [build number] [flags]

Examples:
# by default, artifacts of the most recent build for the current branch is shown
$ bk artifacts list
# to list artifacts of a specific build
$ bk artifacts list 429 
# to list artifacts of a specific job in a build
$ bk artifacts list 429 --job 0193903e-ecd9-4c51-9156-0738da987e87  
# if not inside a repository or to use a specific pipeline, pass -p
$ bk artifacts list 429 -p monolith 


Flags:
  -j, --job string        List artifacts for a specific job on the given build.
  -p, --pipeline string   The pipeline to view. This can be a {pipeline slug} or in the format {org slug}/{pipeline slug}. 
                          If omitted, it will be resolved using the current directory.
  -h, --help              help for list

I have also added the artifacts UUID when listing artifacts for a build or a job to provide user a reference when we implement the bk artifacts download <artifact uuid> command.

Screenshot 2024-12-11 at 11 47 31 AM

@lizrabuya lizrabuya marked this pull request as ready for review December 11, 2024 00:57
@lizrabuya lizrabuya merged commit deeafdb into main Dec 11, 2024
1 check passed
@lizrabuya lizrabuya deleted the SUP-27929-artifacts-list branch December 11, 2024 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants