Skip to content

馃尡 fix(ci): sanitize env for asciinema upload #1925

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmshort merged 1 commit into from
Apr 18, 2025
Merged

馃尡 fix(ci): sanitize env for asciinema upload #1925

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 7 additions & 1 deletion .github/workflows/catalogd-demo.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,11 @@ jobs:
with:
go-version-file: "go.mod"
- name: Run Demo Update
run: make demo-update
run: |
env -i \
HOME="$HOME" \
PATH="$PATH" \
TERM="xterm-256color" \
SHELL="/bin/bash" \
make demo-update

@camilamacedo86 camilamacedo86 Apr 17, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hi @tmshort

(Yes, I know env -i starts with an empty environment. Do you know what's in the existing CI's environment that's causing a problem?)

The fix keeps only the required ENV VARs, so future GitHub changes won鈥檛 break anything. For example, I couldn鈥檛 reproduce the issue locally (macOS) with the current code.

I didn鈥檛 dive deep into the exact ENV differences**鈥擝ecause today it鈥檚 ENV A, tomorrow ENV B.** The goal was just to unblock us and avoid this from happening again. If we want to rethink the approach, we can always do that in a future PR. Personally, I don鈥檛 think it鈥檚 worth spending more time here on this one.

Let me know if anything seems off!

@tmshort tmshort Apr 18, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It works locally for me on linux... but the question is, why is the CI environment "off"?