Expose build artifacts through the web UI
jspahrsummers opened this issue · comments
On the GitHub for Mac team, we're planning to use Jenkins to create our Release builds for us, and put them up as build artifacts. That's mostly working (using some settings in the config XML), but it's really inconvenient to have to go to Jenkins and find the correct job hash to access them.
It'd be awesome if Janky exposed the artifacts created by a given build.
I feel like #92 would be an ideal solution rather than building a
whole UI in Janky itself.
On Mon, Aug 20, 2012 at 7:00 PM, Justin Spahr-Summers
notifications@github.com wrote:
On the GitHub for Mac team, we're planning to use Jenkins to create our Release builds for us, and put them up as build artifacts. That's mostly working (using some settings in the config XML), but it's really inconvenient to have to go to Jenkins and find the correct job hash to access them.
It'd be awesome if Janky exposed the artifacts created by a given build.
—
Reply to this email directly or view it on GitHub.
Can we expose build artifacts the same way we expose console output? Most of our native/mobile apps could benefit from this.
Closing as stale...please re-open if someone has some codes for this.