Visibility / accessibility of artifacts

[LorenzMeier]

We use build artifacts to store the binary for an autopilot firmware (http://px4.io) to an AWS bucket to allow flight-testers to grab the binary and fly it. The current setup is workable, however, the artifacts are buried deep-down in the console log. Would it be possible to add a listing of uploaded artifacts with a download link to the top of the page? For an example, please have a look at: https://travis-ci.org/PX4/Firmware/builds/44751661

[joshk]

Hi @LorenzMeier

We are working towards having this in the API, and a part of Travis CI without you needing to supply S3 credentials.

We don't have an ETA on this sorry, but we hope for sometime in Q1.

[davehunt]

Hey @joshk do you have an update on this - it would be a powerful feature!

[jmalonzo]

Ping! We'd love to have this one as well as perhaps having it visible in Github too? Perhaps a link to the artifact that was just uploaded? TIA

[backspace]

Until something like this is officially supported, you could use the GitHub Status API to implement it yourself. See this example in travis-web where pull requests are automatically deployed and have links added to the status display.