Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push 'dev' releases to public storage #416

Closed
Waldz opened this issue Sep 28, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@Waldz
Copy link
Member

commented Sep 28, 2018

Currently we are pushing dev version to https://github.com/mysteriumnetwork/build-artifacts/tree/mysterium-node

Problem1. This is private
Problem2. Using Git branch as storage solution

Acceptance Criteria:

  • Implement storage solution, which is public (S3 probably)

@Waldz Waldz added this to the Paid identity POC milestone Sep 28, 2018

@soffokl

This comment has been minimized.

Copy link
Member

commented Oct 1, 2018

We are pushing dev versions in the containers to the docker hub: https://hub.docker.com/r/mysteriumnetwork/myst/tags/

I think that these docker images covers 100% of needs for the prepared binaries for devs.
In any special case, it's easy to build a new binary.

I think it's not worth it to keep and maintain another one services for that.

@Waldz

This comment has been minimized.

Copy link
Member Author

commented Oct 1, 2018

No, we need standalone (just executable) version pushed somethere.

@soffokl soffokl self-assigned this Oct 2, 2018

@Waldz

This comment has been minimized.

Copy link
Member Author

commented Oct 2, 2018

We had a script before to push Github releases wo Travis plugin 1f15b2e

We had idea with @tadovas , that later we will remake releases with bash script,
because it makes possible to test releases from developer’s machine, not only Travis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.