S3 deployment #207
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#207
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "s3-deployment"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After talking with @nikooo777 about our expired GitHub credentials and the desire to include the branch builds, we have changed it to push to our S3 account (available at http://build.lbry.io/lbrycrd/ ). Since we release rarely, it seemed easy enough for me to just copy builds from there to GitHub. As it stands here, there is only one build per branch/tag stored.
Untested, but looks good to me.