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

Update CI pipeline to support installing build-tools from npm #11670

Merged
merged 12 commits into from Aug 26, 2022
Merged

Conversation

tylerbutler
Copy link
Member

@tylerbutler tylerbutler commented Aug 25, 2022

We use our homegrown build-tools to do some tasks in our CI pipelines. It's helpful to be able to install the local in-repo version of the tools in most cases, but sometimes we want to install from npm instead. This change enables us to control the version of the build tools that are installed via a pipeline variable that's set when the pipeline is run.

@github-actions github-actions bot added area: build Build related issues base: main PRs targeted against main branch labels Aug 25, 2022
@tylerbutler tylerbutler marked this pull request as ready for review August 26, 2022 00:35
@tylerbutler tylerbutler requested review from a team as code owners August 26, 2022 00:35
@@ -21,6 +21,10 @@ parameters:
- default
- skip
- force
- name: buildToolsVersionToInstall
displayName: Fluid build tools version (default = installs version in repo)
Copy link
Member

Choose a reason for hiding this comment

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

should it default to not repo? the repo version does add non-trivial time to the pipeline.

Copy link
Member Author

Choose a reason for hiding this comment

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

Once the build tools are baked, I'll update the default for main. In lts it'll default to npm, but main for now will use the in-repo version.

@tylerbutler tylerbutler merged commit b51bc25 into main Aug 26, 2022
@tylerbutler tylerbutler deleted the pipeline branch August 26, 2022 23:58
@github-actions
Copy link
Contributor

This commit is queued for merging with the next branch! Please ignore this PR for now. Contact @microsoft/fluid-cr-infra for help.

tylerbutler added a commit that referenced this pull request Aug 27, 2022
This is the same as #11670 with some minor adjustments for the lts branch. Most notably, it defaults to the latest npm version of the build tools instead of the in-repo version.
npm ci
popd

- ${{ if ne(parameters.buildToolsVersionToInstall, 'repo') }}:
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious if we use an if-equal above and an independent if-not-equal here over an else for some reason?

WayneFerrao pushed a commit to WayneFerrao/FluidFramework that referenced this pull request Aug 31, 2022
tylerbutler added a commit that referenced this pull request Aug 31, 2022
This is the same as #11670 with some minor adjustments for the lts branch. Most notably, it defaults to the latest npm version of the build tools instead of the in-repo version.
tylerbutler added a commit that referenced this pull request Sep 28, 2022
…2160)

This is the same as #11670 with some minor adjustments for the 0.59.4000
release branch. Most notably, it defaults to the latest npm version of
the build tools instead of the in-repo version.
tylerbutler added a commit that referenced this pull request Oct 14, 2022
The previous change in #11670 was incomplete. It did not properly pass
through the build tools location from the ADO UI all the way to the
right places. This change corrects that.

I tested by manually running a build with the "next" value for the build
tools source, and verified that the prerelease (tagged `@next`) version
was installed.
sharptrip pushed a commit to sharptrip/FluidFramework that referenced this pull request Oct 17, 2022
The previous change in microsoft#11670 was incomplete. It did not properly pass
through the build tools location from the ADO UI all the way to the
right places. This change corrects that.

I tested by manually running a build with the "next" value for the build
tools source, and verified that the prerelease (tagged `@next`) version
was installed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build Build related issues base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants