Add a CI job that runs the merged paket executable against a simple dependencies file
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
In order to prevent issues like #4062 there should be some sort of simple smoke check of the IL-merged paket.exe in the CI pipleine.
It would seemingly only need to happen on windows (mono never reproduced the failures seen in that issue for me), and it would be a failing step for the windows build if errors occur.
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 Windows CI build configuration and the step that produces or runs the IL-merged paket.exe. Add a smoke check using a simple dependencies file, with the Windows job failing when the executable errors; done means this check runs reliably in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100