e2e tests: use quickstart workflow from forked repo #520
+22
−116
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
sreuland
force-pushed
the
use_quickstart_pipe
branch
from
3cc39fe to
e3530f2
Compare
… will just reference local docker repo for image when forked pr
sreuland
changed the title
sreuland
changed the title
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.
What
Changed e2e test to use new quickstart build pipeline and quickstart runtime action which runs quickstart container as an action.This is using an updated system-test(system-test/146) which no longer builds or references quickstart. Instead tests configured to run against remote target rpc url pointing at the quickstart run by gha step.
Why
Reduce duplicate image build times, lower test build/setup times.
Known limitations