approvals / approvals/ApprovalTests.LabVIEW
CI Improvements
Open
Nobody has claimed this yet.
- Dominant language
- LabVIEW
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
A couple issues with new Docker Setup
- make sure we are still building for 2020
- add back in testing both before and after building
- figure VIPM toml vs vipc
- figure out G-CLI - currently not using (using vipm instead) - do we still need it? I think yes for tests - could potentially use LabVIEW-CLI
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 reviewing the new Docker setup and the current CI configuration. Determine how the project targets 2020, where tests run before and after building, and how VIPM, VIPC, G-CLI, and LabVIEW-CLI are currently used; done means the CI workflow documents and implements the agreed build and test process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100