Repository navigation
ci: PLTF-3461 run E2E after Replicated deploys - #1129
Merged
Merged
Conversation
aivong-openhands
changed the title
aivong-openhands
force-pushed
the
pltf-3461-e2e-replicated
branch
from
August 20, 2026 22:20
364eac4 to
52c3e57
Compare
aivong-openhands
changed the title
aivong-openhands
marked this pull request as ready for review
August 24, 2026 19:48
aivong-openhands
requested review from
dylan-openhands,
jlav and
mamoodi
as code owners
August 24, 2026 19:48
dylan-openhands
approved these changes
Aug 24, 2026
openhands-release-bot
Bot
added
the
released: openhands/0.50.1
Contributor
|
🚀 Released in openhands/0.50.1. |
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.
Why
A successful Replicated deployment should immediately exercise the instance that was updated. This adds a reusable E2E job that runs only after deployment succeeds and sends only
instanceto Argo, where the target URL, credential Secret, and pinned test revision remain controlled. The invocation token comes from thee2e-replicatedGitHub Environment, and the workflow has no manual trigger.The matching Argo event receiver and
ARGO_WORKFLOWS_E2E_TOKENenvironment secret must exist before this path can run.Validation
This PR was drafted by an AI agent on behalf of the user.