jfrog / jfrog/setup-jfrog-cli

Add RB v2 Information to GitHub Actions Job Summary

Open
#217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
TypeScript
Stars
266
Forks
110
Avg merge
3d 15h
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.

N/A.

Describe the solution you'd like to see

I would like GitHub Actions using jfrog/setup-jfrog-cli@v4 to include a feature where Release Bundle v2 information is automatically summarized (similar to 'Published JFrog Build Info') and displayed in the job summary after a pipeline run. This summary would provide details about the Release Bundle, such as the bundle ID, included artifacts, and any relevant metadata. This would help developers and release managers have a clear understanding of what was included in a release without needing to manually track or review logs, making the process more efficient.

Describe alternatives you've considered

Currently, I manually track the Release Bundle v2 information by executing shell commands and writing the details to $GITHUB_STEP_SUMMARY. Integrating this feature natively would save a lot of time and reduce potential human errors. FYI: https://github.com/krishnamanchikalapudi/spring-petclinic/actions/runs/10968757709

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload names no source files or tests; start at the action entry point for setup-jfrog-cli@v4 and compare the existing “Published JFrog Build Info” job-summary behavior. Define which Release Bundle v2 fields must appear, then verify that a pipeline run writes the bundle ID, artifacts, and relevant metadata to $GITHUB_STEP_SUMMARY.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, devops, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.