Closed
Bug 1266094
Opened 9 years ago
Closed 9 years ago
Set up Travis for AWS Provisioner
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1261006
People
(Reporter: dustin, Unassigned)
Details
I got complacent in
https://github.com/taskcluster/aws-provisioner/pull/70
assuming that Travis would barf if the very small patch was ill-formed. We're not even running Travis, so that didn't work :(
Travis should both run the tests, and run the linter.
This can use the fake entities support to avoid colliding in Azure, but will need "real" AWS access.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: AWS-Provisioner → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•