mapbox / mapbox/mapnik-omnivore
Fix appveyor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Appveyor is busted, let's fix it! (or get rid of it)
It looks like we are installing our own versions of node from the mapbox CDN. Curious if we could move over to testing out with Appveyor's built-in versions so we can be a bit more flexible with updating to v4/v6.
I assume we are building on Visual Studio 2015 so @BergWerkGIS is able to test locally. Some insight from you would be great here!
cc @springmeyer @GretaCB @flippmoke @artemp
Contributor guide
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 inspecting the repository's AppVeyor configuration and the Node installation steps that fetch versions from the Mapbox CDN; compare them with AppVeyor's built-in Node versions and the Visual Studio 2015 environment mentioned here. Done means CI works with the chosen Node setup, or AppVeyor is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100