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

[SDK] Add CI automation for release #23

Closed
bzz opened this issue Jul 18, 2018 · 4 comments
Closed

[SDK] Add CI automation for release #23

bzz opened this issue Jul 18, 2018 · 4 comments
Milestone

Comments

@bzz
Copy link
Contributor

bzz commented Jul 18, 2018

Add automation to produce a release on tag, that include next artefacts:

  • content of ./sdk dir
  • lookout binaries for linux/mac os

in a single archive, uploaded to GH release.

@bzz bzz added this to the Phase 0. SDK milestone Jul 18, 2018
@bzz bzz changed the title [SDK] Add CI for releasing binary [SDK] Add CI automation for release Jul 18, 2018
@carlosms
Copy link
Contributor

in a single archive

For other src-d projects we have separate files for _darwin_amd64.tar.gz, _linux_amd64.tar.gz. I think it makes sense to keep it that way for this project, or is there any reason to tar everything together?

@bzz
Copy link
Contributor Author

bzz commented Jul 20, 2018

Sorry for confusion - the suggestion was not to tar different architectures!

The suggestion is: for each architecture, have a separate archive that looks like

.
├── lookout
└── sdk
    ├── README.md
    ├── event.proto
    ├── github.com
    │   └── gogo
    │       └── protobuf
    │           └── gogoproto
    │               └── gogo.proto
    ├── gopkg.in
    │   └── bblfsh
    │       └── sdk.v1
    │           └── uast
    │               └── generated.proto
    ├── service_analyzer.proto
    └── service_data.proto

(or have one more parrent dir for convenience)

@carlosms
Copy link
Contributor

Reopening so we don't forget to setup GITHUB_TOKEN in Travis

@carlosms carlosms reopened this Jul 24, 2018
@carlosms carlosms removed their assignment Jul 24, 2018
@carlosms
Copy link
Contributor

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants