This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Configure Travis CI for S3 compiled build deployment #213
Labels
Comments
Received S3 bucket information, need to determine what will be sent to the S3 bucket and if it will always have the exact same file name, or change with version increments. |
I've gotta setup a Gradle task to run specifically on Travis CI that will rename the APK that will be shipped to S3 to something like |
Currently prioritizing a few important bug fixes over this, hence time delays on this landing. Work has commenced however, and I feel good about the direction it's heading in. |
The bit.ly link |
emilva
added a commit
to emilva/Jisort
that referenced
this issue
Oct 11, 2016
ryanwarsaw
added a commit
that referenced
this issue
Dec 20, 2016
* Add temporarily file directory listing, for debugging purposes * Fix things * #213 added initial s3 config * Add latest build type and automatically strip version from file name * Add S3 credentials
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Travis CI has been setup and builds are passing, the next step is to request a S3 bucket to be used for storing the compiled build until a new Travis CI build has been triggered.
Tracking S3 bucket request here: MozillaFoundation/mofo-devops#412
The text was updated successfully, but these errors were encountered: