-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload latest master, beta and stable builds to AWS #1674
Conversation
Fixed CI-Tools/s3cmd-put so it only uploads if not a pull request. |
hmm the dynamically generated s3 directory index isn't quite right. |
In fact we do want artifacts for most builds so our testers can download straight from Travis and don't need the tool chain installed. |
I think I'm missing partially context here - the overall state / uploaded material looks good (I cleaned up a bit). I presume we can exchange the flow badge here soon too and call the job done? |
Sorry, that was not very clear. I was referring to the existing travis addon called artifacts which was already uploading Firmware.zip. https://github.com/PX4/Firmware/blob/master/.travis.yml#L81-L82 One last change to put things in project folders (so we can add px4flow alongside) and this should be good to go. As soon as this is in and working I'll add the few lines to px4flow travis.yml for upload and add the badge. |
Awesome, merging! |
Upload latest master, beta and stable builds to AWS
I removed the other s3 artifacts upload assuming you don't also want to keep every Firmware.zip on s3.
I uploaded some unnecessary files when attempting to use the travis builtin s3 upload. You could probably delete everything in the bucket at this point and travis will repopulate.