# Bitrise deployment history **URL:** \ **Category:** Question & Answer\ **Created:** [September 4, 2018, 2:04pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100 "2018-09-04T14:04:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![tbarak](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tbarak](https://discuss.bitrise.io/u/tbarak)\ **Post date:** [September 4, 2018, 2:04pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/1 "2018-09-04T14:04:27Z")
Is there a way to see the consolidated builds artefacts, so users (testers) can easily revert to old versions? ---
**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\ **Post date:** [September 7, 2018, 8:11am UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/2 "2018-09-07T08:11:39Z")
Hi @tbarak! Thanks for the question! Are you referring to artifacts of older builds, or can you please clarify what do you mean by consolidated here? 🙂 ---
**Author:** ![tbarak](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tbarak](https://discuss.bitrise.io/u/tbarak)\ **Post date:** [September 7, 2018, 8:39am UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/3 "2018-09-07T08:39:45Z")
Hi @bitce We used to post debug versions for testers via Testfairy, and instead we are now posting the build results to slack (with QR), and the internal testers pick it from there. While we can still keep using Testfairy, the bitrise versions seems to be sufficient with one minor drawback: Testfairy had a versions options which users could use to easily install a previous version. If the deploy to bitrise step (or a similar step) could store the build urls in a fixed locations we could display to users (with some version tagging), it could be great. ---
**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\ **Post date:** [September 7, 2018, 2:28pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/4 "2018-09-07T14:28:14Z")
Thanks @tbarak! You do not have this option currently, but we do have two feature requests which are partially related, please see: > [@Static Public install page, so that QA can always download the apk of the latest build from the same location](http://discuss.bitrise.io/t/static-public-install-page-so-that-qa-can-always-download-the-apk-of-the-latest-build-from-the-same-location/715): > > 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](http://bitrise.uservoice.com/forums/235233-general/suggestions/11196141-static-public-install-page-so-that-qa-can-always) > [@Fix url to download apps](http://discuss.bitrise.io/t/fix-url-to-download-apps/5949): > > Description of the feature request Use case / for what or how I would use it on my previous company we had a build system based on jenkins that would give us a url with direct download link for the apk and ipa files like this: [http://jenkinsserver/[nameOfTheApp]/[branch]/latestSuccessfulBuild/[nameOfTheApp].apk](http://jenkinsserver/%5BnameOfTheApp%5D/%5Bbranch%5D/latestSuccessfulBuild/%5BnameOfTheApp%5D.apk) Right now on bitrise, the direct download link has a different id on every build and a token that expires. this would be very useful for our test automation system since we could dow… In case these wouldn’t match your use case completely (as I understand they don’t) feel free to add to the thread or create a new feature request about it! ---
**Author:** ![tbarak](https://avatars.discourse-cdn.com/v4/letter/t/d07c76/32.png) [@tbarak](https://discuss.bitrise.io/u/tbarak)\ **Post date:** [September 7, 2018, 2:40pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/5 "2018-09-07T14:40:26Z")
Looks good. where do we upvote? ---
**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\ **Post date:** [September 7, 2018, 2:46pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/6 "2018-09-07T14:46:44Z")
For the [feature request](http://discuss.bitrise.io/c/feature-request) board, you can find a rectangle with a number inside it as a prefix for the thread name. This counts the number of votes, you should see a blue Vote button below them 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\ **Post date:** [October 7, 2018, 2:48pm UTC](https://discuss.bitrise.io/t/bitrise-deployment-history/6100/7 "2018-10-07T14:48:20Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.