ci: reuse shared TCFS smoke secrets for Linux - #384
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
smoke_environmentworkflow_dispatch input to the Linux post-install smoke workflowtcfs-macos-smokeenvironment, which already owns the sharedTCFS_SMOKE_*storage secretstcfs-linux-smokeonce that environment has its own secretsWhy
The first real TIN-1422 dispatch against
v0.12.13-rc1failed before package install becausetcfs-linux-smokehas no secrets.tcfs-macos-smokehas the same five required secret names and is already used by the production macOS smoke lane.Failed run: https://github.com/Jesssullivan/tummycrypt/actions/runs/26071828210
Validation
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/linux-postinstall-smoke.yml"); puts "yaml ok"'git diff --checkRefs TIN-1422.