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

Separate backend deployment status and frontend tab status #30

Open
dsavchenko opened this issue Sep 8, 2023 · 3 comments
Open

Separate backend deployment status and frontend tab status #30

dsavchenko opened this issue Sep 8, 2023 · 3 comments
Assignees

Comments

@dsavchenko
Copy link
Member

No description provided.

@dsavchenko dsavchenko self-assigned this Sep 8, 2023
@dsavchenko
Copy link
Member Author

stage_failed added to status by #31
TODO: add logic to only try to regenerate the frontend tab without rebuilding the backend

@volodymyrss
Copy link
Member

what's the status of this, @dsavchenko ?

@dsavchenko
Copy link
Member Author

The idea of this is to record the stage of deployment, which was failed (this is done) and start from it the next time (to avoid e.g. unnecessary rebuilds of container). This logic is not implemented, but the priority is rather low, because problems mostly occur when building the container, later stages fail rarely.

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

No branches or pull requests

2 participants