Skip to content
Open
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
2 changes: 1 addition & 1 deletion docs/execute/binaries.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ There are three ways to run system-tests with a custom node tracer.
- Create a file `nodejs-load-from-npm` in `binaries/`
- In the file, add the path to the branch of the custom tracer. The content will be installed by npm install.
- Content Examples:
- `DataDog/dd-trace-js#master`
- `DataDog/dd-trace-js#main`
- `DataDog/dd-trace-js#<commit-hash>`
- Run any scenario normally with `./build.sh nodejs` and `./run.sh` and your remote changes will be in effect
2. Using a custom tracer existing in a local branch.
Expand Down
4 changes: 2 additions & 2 deletions utils/scripts/load-binary.sh
Original file line number Diff line number Diff line change
Expand Up @@ -312,8 +312,8 @@ elif [ "$TARGET" = "agent" ]; then
elif [ "$TARGET" = "nodejs" ]; then
assert_version_is_dev

LIBRARY_TARGET_BRANCH="${LIBRARY_TARGET_BRANCH:-master}"
# NPM builds the package, so we put a trigger file that tells install script to get package from github#master
LIBRARY_TARGET_BRANCH="${LIBRARY_TARGET_BRANCH:-main}"
# NPM builds the package, so we put a trigger file that tells install script to get package from github#main
echo "DataDog/dd-trace-js#$LIBRARY_TARGET_BRANCH" > nodejs-load-from-npm
echo "Using $(cat nodejs-load-from-npm)"

Expand Down
Loading