Skip to content
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.

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

Already on GitHub? Sign in to your account

chore: make sure that the webapp is available for the engine in the engine publish step #1807

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

Dartoxian
Copy link
Contributor

Description

This PR makes the enclave manager web ui available during the engine build step - this should fix the issue seen here https://app.circleci.com/pipelines/github/kurtosis-tech/kurtosis/9327/workflows/48587b79-2de3-4f3f-9b2f-3d0a6bf184b2/jobs/129862

Is this change user facing?

YES/NO
No

References (if applicable):

@Dartoxian Dartoxian changed the title Make sure that the webapp is available for the engine in the engine publish step fix: make sure that the webapp is available for the engine in the engine publish step Nov 16, 2023
@Dartoxian Dartoxian changed the title fix: make sure that the webapp is available for the engine in the engine publish step chore: make sure that the webapp is available for the engine in the engine publish step Nov 16, 2023
@adschwartz adschwartz added this pull request to the merge queue Nov 16, 2023
Merged via the queue into main with commit 7c34582 Nov 16, 2023
41 of 42 checks passed
@adschwartz adschwartz deleted the bgazzard/fix-engine-publish branch November 16, 2023 18:15
Dartoxian added a commit that referenced this pull request Nov 16, 2023
…in the engine publish step (#1807)"

This reverts commit 7c34582.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants