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

[PROF-6762] Migrate Ruby gem release step to use new api key #85

Merged
merged 2 commits into from
Jan 13, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion ruby/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,6 @@ Note: Publishing new releases to rubygems.org can only be done by Datadog employ
3. [ ] Update the <lib/libdatadog/version.rb> file with the `LIB_VERSION` and `VERSION` to use
4. [ ] Commit change, open PR, get it merged
5. [ ] Release by running `docker-compose run push_to_rubygems`.
(When asked for rubygems credentials, check your local friendly Datadog 1Password.)
6. [ ] Verify that release shows up correctly on: <https://rubygems.org/gems/libdatadog>

## Contributing
Expand Down
5 changes: 5 additions & 0 deletions ruby/Rakefile
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,11 @@ task push_to_rubygems: [
] do
system("gem signout") # make sure there are no existing credentials in use

puts "Please input 'libdatadog ruby release key' from 'Profiling - Falcon' Datadog 1Password:"
input = $stdin.gets.strip

ENV["GEM_HOST_API_KEY"] = input

system("gem push pkg/libdatadog-#{Libdatadog::VERSION}.gem")
system("gem push pkg/libdatadog-#{Libdatadog::VERSION}-x86_64-linux.gem")
system("gem push pkg/libdatadog-#{Libdatadog::VERSION}-aarch64-linux.gem")
Expand Down