Static Public install page, so that QA can always download the apk of the latest build from the same location

[viktorbenei]

From Scott LaHay on 2015/12/24 17:22:41 +0000

Currently Bitrise creates a unique URL, on each build, for the public install page. I would prefer to have a URL that gets updated with each build. This way, My testers will always download the latest app without me having to resend the email

Copied from original feature request: http://bitrise.uservoice.com/forums/235233-general/suggestions/11196141-static-public-install-page-so-that-qa-can-always

[viktorbenei]

From Anonymous on 2017/01/09 09:55:15 +0000

the only thing that holds people at hockey currently

[viktorbenei]

From Anonymous on 2016/03/11 16:24:44 +0000

That would be very interesting. We can currently do it manually (using our own server, a custom webpage and the cURL Bitrise step) but having a static install page for a desired file would definitly do the trick.

[viktorbenei]

Related feature request:

Create client install page with a list of preselected builds

From Marko Tadic on 2016/07/08 11:50:47 +0000 Currently, each build can have its public install page, so when we reach a point that we’re ready for client test we manually send them link to public install page of some particular build. As time goes by, these links get lost somewhere inside Slack, Mail etc, so clients ask from us to send them again link for some particular version they want to test or compare with. Now, we could (as an alternative) develop some simple backend API and webpage w…

[jpita]

We implemented this on our side with an ftp server running on our jenkins machine and sending the builds there. Shouldn’t be much harder to do it on your side with a similar structure to this https://chromedriver.storage.googleapis.com/index.html

[apersian]

Would love to see this feature implemented. Ideally including the ability to password protect the install page.