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

[enhancement] Gitlab ci update: run plan job directly after its validate job without wating for all other validate job #48

Open
arongate opened this issue Dec 26, 2023 · 0 comments

Comments

@arongate
Copy link
Contributor

arongate commented Dec 26, 2023

For really large project, with long validate task, wait for all validate task to finish cause the context to expire which leads to force run init perform again for plan command.

Solution: perform plan job directly after its validate job before without wating for all other validate job to run.

@arongate arongate changed the title Gitlab ci update: perform plan job directly after its validate job before without wating for all other validate job to run as we do now Gitlab ci update: run plan job directly after its validate job without wating for all other validate job Feb 6, 2024
@arongate arongate changed the title Gitlab ci update: run plan job directly after its validate job without wating for all other validate job [enhancement] Gitlab ci update: run plan job directly after its validate job without wating for all other validate job Feb 6, 2024
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

1 participant