Repair CI testing of actual publishing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
This repo is currently set up to only run certain tests (that require real AWS privileges) on the Appveyor and Travis CI systems.
They are enabled by making available the `AWS_ACCESS_KEY_ID` and `AWS_SECRETE_ACCESS_KEY` on the given CI system.
Currently both of these credentials have been removed since Mapbox has recently changed its internal policy on allowing AWS access via third party systems. This ticket services as a reminder that not all tests are currently running and will not be until this is restored.
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 reviewing the repository's Appveyor and Travis CI configuration to identify which publishing tests are gated on AWS credentials. Confirm the current credential policy and CI setup; done means the real-publishing tests run again with authorized credentials, or the issue is updated with a supported alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- ci-cd, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100