spinframework / spinframework/spin-docs
CI/CD: simplify artifact step
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 23
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Ref https://github.com/spinframework/spin-docs/pull/36#discussion_r2017650758
With https://github.com/spinframework/spin-docs/pull/36 we persist relevant artifacts so that the subsequent deploy step can use them to deploy the website. However, the current approach of listing all of the file paths that are referenced in the app's spin.toml is fragile and a maintenance burden. Look into another approach while still maintaining the overall flow of "build artifacts, deploy artifacts" in the pipeline.
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 with the artifact persistence and deploy flow introduced in PR #36, including the file-path list derived from the app's spin.toml. Review the linked discussion, then investigate an alternative that removes this fragile listing while preserving the pipeline's existing "build artifacts, deploy artifacts" flow; done means both steps still work without that maintenance burden.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100