Build Linux and OS X packages on Travis - #1279

• Debian packages uploaded
• OS X packages uploaded

So, unfortunately, unlike AppVeyor, Travis CI doesn't provide a nice simple "here are the artifacts you uploaded" page. Meaning they have to be downloaded from the AWS bucket manually. Hm.

Awesome addition - Andy Jordan (@andschwa) How do I download the package non-interactively? Is the endpoint authenticated?

https://s3.amazonaws.com/powershell-travis-ci-artifacts/PowerShell/PowerShell/2774/2774.1/powershell_0.5.0-260-g970641e-1_amd64.deb

Raghu Shantha (@raghushantha) that's what I was wondering. Travis Plunk (@TravisEz13)?

Andy Jordan (@andschwa) Did you specify the region in the config? Looks like it is defaulting to something else

get this error when accessing the endpoint:

The region is set to us-west-2 per Travis's email.

Travis Plunk (@TravisEz13) dropped by. Here is an update:

1. Need to have the region in the url:
   https://s3-us-west-2.amazonaws.com/powershell-travis-ci-artifacts/PowerShell/PowerShell/2774/2774.1/powershell_0.5.0-260-g970641e-1_amd64.deb

Don't think travis-ci yml allows us to configure this.

2. Still get access denied with the new url. This is expected since we need to pass the secrets in the body of the request. This problem must go away once we make this system public.

So for now, we need to solve problem 1

Raghu Shantha (@raghushantha) I'm not sure what's wrong. The region is set correctly. The URL we're getting back is just from Travis's artifacts plugin. Travis Plunk (@TravisEz13) where the artifacts not uploaded to the end point?

When attempting to access the URL, I just get a permanent redirect:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>PermanentRedirect</Code>
<Message>
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
</Message>
<Bucket>powershell-travis-ci-artifacts</Bucket>
<Endpoint>powershell-travis-ci-artifacts.s3.amazonaws.com</Endpoint>
<RequestId>8ABFD83338C35113</RequestId>
<HostId>
tPkOrkKvXWNnt8sesI+Kmdpurr1QApgRmufDEu4QyKoDpbroPjtU6DrhG8bRfevdJFj344DUSmU=
</HostId>
</Error>

Which I think is fine, as you just follow the redirect to https://powershell-travis-ci-artifacts.s3.amazonaws.com/powershell-travis-ci-artifacts/PowerShell/PowerShell/2774/2774.2/powershell-0.5.0-260-g970641e.pkg, and then authenticate (somehow).

I just set up the awscli and synced the bucket down, it has what I expected. Can I merge now?

I believe what we would do when we go public is to make the bucket public, and then files would be available.

I think I see what you mean about the URL it publishes, looks like travis-ci/artifacts#69.

Ideally Travis-CI must emit the actual url (without redirection). I guess once travis-ci/artifacts#69 issue is resolved we get to see it.

For now these changes are good.

Yeah they could certainly do better on that. It's annoying. For now, I can get builds no problem, which means I can release packages from Travis 😄