Netflix/atlas

automatically publish release assets

Open

#1256 opened on Feb 10, 2021

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Scala (3,553 stars) (341 forks)batch import
enhancementhelp wanted

Description

When running the release build we should automatically update the release assets so that the standalone jar is consistently available. Right now that is a manual process and is often forgotten.

Contributor guide

Tech stack
scala
Domain
releaseci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with SBT build toolunderstanding of GitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the current release process by examining the repository's build configuration, likely in `build.sbt` and any GitHub Actions workflows under `.github/workflows/`. Look for existing release scripts or steps that manually handle assets. Automate the attachment of the standalone JAR to the release using GitHub Actions' `softprops/action gh release` or similar, ensuring the JAR is built during the release workflow.