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

Allow more build steps to run in parallel #8273

Merged
merged 1 commit into from
Sep 12, 2022
Merged

Allow more build steps to run in parallel #8273

merged 1 commit into from
Sep 12, 2022

Conversation

anthony-c-martin
Copy link
Member

@anthony-c-martin anthony-c-martin commented Sep 6, 2022

Changes to build.yml so that more steps are able to run in parallel. The main change is to split Bicep build step into steps to build and publish the various components, and a step to run the tests. This ensures that the VSCode extension jobs can run immediately after the language server has been published and doesn't have to wait for the C# tests to finish.

I wanted to be able to split the VSCode extension build & test into separate stages, so that the VSIX would be published even if a test/linting fails, but couldn't find an easy way to do this.

See example workflow run here: https://github.com/anthony-c-martin/bicep/actions/runs/3000590478

Microsoft Reviewers: Open in CodeFlow

Copy link
Contributor

@shenglol shenglol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@majastrz
Copy link
Member

majastrz commented Sep 9, 2022

@anthony-c-martin You'll need to force this in because the job names have changed and don't match the required checks anymore.

@anthony-c-martin anthony-c-martin enabled auto-merge (squash) September 12, 2022 17:41
@anthony-c-martin anthony-c-martin merged commit c3cd047 into Azure:main Sep 12, 2022
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.

3 participants