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

Add Release Script #358

Merged
merged 6 commits into from
May 3, 2019
Merged

Add Release Script #358

merged 6 commits into from
May 3, 2019

Conversation

jonny-improbable
Copy link
Contributor

@jonny-improbable jonny-improbable commented Feb 20, 2019

  • Triggered by travis when a new tag matching vX.y.z is pushed.
  • Generates grpcwebproxy binaries for win, mac, and linux
  • Uses github-release binary to do what it says on the tin and attach the grpcwebproxy binaries to the release
  • Uses lerna publish to publish the client packages to npm

TODO

  • Verify that this works locally by publishing v0.9.0 to NPM and github
  • Inject credentials into travis for creating github releases

- Generates grpcwebproxy binaries for win, mac, and linux
- Uses `github-release` binary to do what it says on the tin and attach the grpcwebproxy binaries to the release
- Uses `lerna publish` to publish the client packages to npm
Copy link
Contributor

@johanbrandhorst johanbrandhorst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this, it's been way overdue!

go/generate-grpcwebproxy-binaries.sh Outdated Show resolved Hide resolved
@johanbrandhorst
Copy link
Contributor

As an alternative to this, have you looked at configuring some GitHub actions? We can use actions for both of these steps I think.

- Remove quotes from around bash glob as the github-release script will not expand globs.
echo "Publishing $TAG"

# Create github release and attach server binaries
./node_modules/.bin/github-release upload \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we rely on this being installed automatically by Travis?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you referring to github-release? I've added it to the project's list of npm dependencies.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I just don't understand how travis works, I don't think we're checking in ./node_modules/, does travis guarantee that it will run npm install before any script or something?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe so, however given our current flakey tests I am concerned that the publish step will never be reached as the test test that proceeds it will likely fail.

You mentioned using Github Actions as an alternative - these are new to me, let me take a look.

- Fix hard-coded version strings in binary filenames
- Rename "build" folder to "dist"
@johanbrandhorst
Copy link
Contributor

To add to my previous comment about github actions: https://sosedoff.com/2019/02/12/go-github-actions.html.

publish-release.sh Outdated Show resolved Hide resolved
@johanbrandhorst
Copy link
Contributor

Would be nice to have 0.9.1 for #359 btw.

@johanbrandhorst
Copy link
Contributor

bump

@jonny-improbable
Copy link
Contributor Author

Thanks for the bump @johanbrandhorst; just checked in with our eng-velocity team who are happy for me to go ahead and investigate github actions. I've taken the first step and signed up for the beta.

We're going to try out github actions instead!
@jonny-improbable jonny-improbable merged commit da05487 into master May 3, 2019
@jonny-improbable jonny-improbable deleted the feature/release-script branch May 3, 2019 11:09
@jonny-improbable
Copy link
Contributor Author

Took the executive decision to merge this as-is.

Github never got back to me with with regards to adding us to the Github Hooks Beta, but seeing as I need to cut a release today, I'm going to invoke this script on my machine to at-least automate most of the process.

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

Successfully merging this pull request may close these issues.

2 participants