-
Notifications
You must be signed in to change notification settings - Fork 305
Feature/travis ci #119
base: master
Are you sure you want to change the base?
Feature/travis ci #119
Changes from all commits
aa245ba
97a90cd
e05ec89
cbe5679
bd215f1
1de71c5
00366e5
2c088e2
ff7d5eb
ddd9ca5
9adda27
7bb5450
1929a3c
2a057a0
a374a3a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
sudo: required | ||
services: | ||
- docker | ||
language: node_js | ||
node_js: | ||
- "4.1" | ||
- "4.0" | ||
- "0.12" | ||
- "0.11" | ||
- "0.10" | ||
- "0.8" | ||
- "0.6" | ||
- "iojs" | ||
before_install: | ||
- docker pull 66pix/s3ninja:latest | ||
before_script: | ||
- docker run -p "9444:9444" 66pix/s3ninja:latest & | ||
- sleep 10 | ||
addons: | ||
hosts: | ||
- node-s3-test.localhost | ||
- s3-bucket.localhost |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,6 +37,7 @@ function createClient() { | |
accessKeyId: process.env.S3_KEY, | ||
secretAccessKey: process.env.S3_SECRET, | ||
endpoint: process.env.S3_ENDPOINT, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @pennycoder here is where the S3_ENDPOINT var is used. Had to disable ssl for the mock - this should be converted to an env var as well, so current s3 behaviour is preserved as you mentioned. |
||
sslEnabled: false | ||
}, | ||
}); | ||
} | ||
|
@@ -97,8 +98,7 @@ describe("s3", function () { | |
Prefix: remoteRoot, | ||
Bucket: s3Bucket, | ||
}; | ||
var deleter = client.deleteDir(s3Params); | ||
deleter.on('end', function() { | ||
client.createBucket(s3Bucket, function() { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would be nice if the current s3 behavior could also be preserved. Perhaps make this option a different environment variable or add a variable that changes the mode of the tests to be either local or against S3 - depending on the variable would change the behavior? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is the S3_ENDPOINT env var that one can use to determine what ... endpoint to use. I'm not sure of the spec for createBucket - does it fail catastrophically if one attempts to create a bucket that already exists? |
||
done(); | ||
}); | ||
}); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this new function also be documented in the readme?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, will do that if and when we actually manage to get CI working with S3Ninja. Which I am still not 100% convinced will be a thing.
Also I hacked this in and have no idea if it matches the expected format for a new API function.