Adding scripts for publishing to S3 RPM repo #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
echeipesh
commented
Oct 18, 2018
| @@ -0,0 +1,16 @@ | |||
| # Container for publishing GeoDocker RPMs to RPM repo on hosted S3 | |||
| FROM centos:7 | |||
There was a problem hiding this comment.
This probably should be the same Docker image that is used for building RPMs, why not?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we dump RPMs to S3 bucket with their SHA, this is serviceable.
As we move to make these artifacts the reference distribution for GeoTrellis/GeoPySpark testing and deployment we need to have a better way to version and install them. Publishing them to an RPM repo where they can be RPM installed from is part of the solution.