-
Notifications
You must be signed in to change notification settings - Fork 20
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
Scripted build migration #157
base: master
Are you sure you want to change the base?
Conversation
condition: and(succeeded(), or(variables['Endjin.ForceDocPublish'], eq(variables['GitVersion.PreReleaseTag'], ''))) | ||
compileTasksServiceConnection: endjin-acr-reader |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to look at the customisations in this YAML file:
- Check whether they are still needed? (e.g. installing .NET 6)
- Check whether the extensibility points it uses are available in the scripted build version of the template (e.g.
postSpecs
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was one of the earliest projects to use .NET 6. (We did it to find out whether it gave a perf boost, which it did.)
I would expect we no longer need special handling for that.
We want to keep the benchmark run and the docfx build.
condition: and(succeeded(), or(variables['Endjin.ForceDocPublish'], eq(variables['GitVersion.PreReleaseTag'], ''))) | ||
compileTasksServiceConnection: endjin-acr-reader |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think moving line 69 earlier in the file, before the customisations, would make it easier to read
No description provided.