diff options
| author | Patrick Steinhardt <psteinhardt@gitlab.com> | 2022-10-27 07:34:56 +0300 |
|---|---|---|
| committer | Patrick Steinhardt <psteinhardt@gitlab.com> | 2022-10-28 08:42:16 +0300 |
| commit | 31fcb2bfadc75e64e5c6730d233f753ca49f8997 (patch) | |
| tree | 82476035a62db65dc69747e7a103da2cea8c9f7a /doc | |
| parent | 19beefd248cd113b341470dca45bd8b57026251a (diff) | |
ruby: Move scripts that generate Proto sources into tools directory
We've got multiple scripts that are required to generate Ruby code from
our Protobuf definitions in the `_support` directory. This has multiple
smells:
- It's out-of-line with all the other tools, which nowadays are
located in the `tools` directory.
- It's hard to discover and find out which parts logically form a
unit.
- We are reusing the Gemfile of the Ruby sidecar to pin the
`grpc-tools` dependency to a specific version.
Move the tooling into its own `tools/protogem` directory that's got its
own Gemfile to fix these points. This also allows us to auto-update
dependencies via the Renovate bot like we do for our other tools.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/PROCESS.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/PROCESS.md b/doc/PROCESS.md index 2e55d85d0..cf80a59bc 100644 --- a/doc/PROCESS.md +++ b/doc/PROCESS.md @@ -473,12 +473,12 @@ tagging a RC is a good way to make sure the `gitlab` feature branch has the prop ## Publishing the Ruby gem -If an updated version of the Ruby proto gem is needed, it can be published to rubygems.org with the `_support/publish-gem` script. +If an updated version of the Ruby proto gem is needed, it can be published to rubygems.org with the `tools/protogen/publish-gem` script. If the changes needed are not yet released, [create a release candidate](#creating-a-release-candidate) first. - Checkout the tag to publish (vX.Y.Z) -- run `_support/publish-gem X.Y.Z` +- run `tools/protogen/publish-gem X.Y.Z` ## Publishing the go module |