Add integration-test creds to the publish job - #114
Merged
Conversation
The publish job runs sonatypeCentralUpload, which re-runs :test, but its env only injected the filestorage creds. The ats/chat/crm/hris/ knowledgebase/ticketing integration tests then threw on missing MERGE_API_KEY_SECONDARY / account tokens and failed the release. Inject the same per-category secrets the test job uses so the publish build's test run has creds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
stephanieyao72
approved these changes
Jul 16, 2026
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
2 participants
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
The publish job (
sonatypeCentralUpload) re-runs:testduring its build, but itsenv:only injectedMERGE_API_KEY_FILESTORAGE/MERGE_ACCOUNT_TOKEN_FILESTORAGE. The ats/chat/crm/hris/knowledgebase/ticketing integration tests throw on missingMERGE_API_KEY_SECONDARYand their account tokens, so the release build failed — even though the same tests pass in thetestjob, which has all the secrets.This injects the same per-category secrets into the publish job so its test run matches the test job.
Requires
These repo/org secrets must be set (already referenced by the
testjob):MERGE_API_KEY_SECONDARY,MERGE_ACCOUNT_TOKEN_ATS,MERGE_ACCOUNT_TOKEN_CHAT,MERGE_ACCOUNT_TOKEN_CRM,MERGE_ACCOUNT_TOKEN_HRIS,MERGE_ACCOUNT_TOKEN_KNOWLEDGEBASE,MERGE_ACCOUNT_TOKEN_TICKETING.🤖 Generated with Claude Code