Deployment smoke test
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 2
Description
There have been several bugs that slip into fslabscli and ultimately take CI out of commission for fsl_libs and maybe andromeda too. The symptoms are often obvious if you just run the CI script against fsl_libs and inspect the output.
I would like us to enforce this kind of test somehow. Ideally the deployment of a new fslabscli would trigger a run of the new build against fsl_libs and link to the job so it can be inspected before actually deploying it.
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 locating the CI script used against fsl_libs and run it to observe the existing smoke-test output. Trace how a new fslabscli deployment is triggered and how fsl_libs, or possibly andromeda, is selected. Done means a new deployment runs this check before the actual deployment and provides an inspectable job link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100