Switch from Circle artifacts to Github releases
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
We currently use CircleCI's artifacts feature. It allows us to store our API data and website for 30 days. This retention period has been a hassle for the productive env since we need to always have these two archives built and stored on CircleCI every month, if we don't the build fails because the archives aren't present anymore.
We could instead use Github APIs and create new releases attaching our archives, then pulling those ones here in the deploy.sh script.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the deploy.sh script and identify how the two archives are currently retrieved from CircleCI artifacts. Review the GitHub APIs needed to create releases and attach archives, then define the retrieval flow in deploy.sh. Done means productive deployments no longer depend on 30-day CircleCI artifacts and can pull both archives from GitHub releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100