Repository navigation
Set -x flag for release script to show commands being run - #2639
Conversation
eregon
commented
Sep 15, 2026
- This makes it much easier to rerun a command if it failed and to know where the script stopped.
* This makes it much easier to rerun a command if it failed and to know where the script stopped.
mislav
left a comment
There was a problem hiding this comment.
Good idea! I never needed this since I made the script and I would know by heart which part of it failed based on the output, but I can imagine this would be useful to everyone else.
| # - [automated] a GitHub Action will create a Homebrew PR for the new release | ||
|
|
||
| set -e | ||
| set -ex |
There was a problem hiding this comment.
Thoughts on using something like:
[ -n "${DEBUG-}" ] && set -x
So that the extra debug/tracing output is opt-in rather than always on?
There was a problem hiding this comment.
Is there a use case for wanting to not see the extra output?
I think the extra output doesn't matter if it works, but it's important to be there if it fails.
Having it only after setting DEBUG is too late.
|
What failed in my case is the It actually happened multiple times to me already. There used to be an early |
ruby-build 20260916 Created-by: HarmonybrewBot Commit-by: HarmonybrewBot Merged-by: HarmonybrewBot Description: Created by `brew bump` --- Created with `brew bump-formula-pr`.<details> <summary>release notes</summary> <pre>## What's Changed * Set -x flag for release script to show commands being run by @eregon in rbenv/ruby-build#2639 * Hide dup3() and pipe2() from configure on macOS older than 27 by @hsbt in rbenv/ruby-build#2641 **Full Changelog**: https://github.com/rbenv/ruby-build/compare/v20260915...v20260916</pre> <p>View the full release notes at <a href="https://github.com/rbenv/ruby-build/releases/tag/v20260916">https://github.com/rbenv/ruby-build/releases/tag/v20260916</a>.</p> </details> <hr> See merge request: Harmonybrew/homebrew-core!20421