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

Add Automatic suffix generation for DTFx.Core and DTFx.AzureStorage #1025

Merged
merged 9 commits into from
Mar 27, 2024

Conversation

davidmrdavid
Copy link
Collaborator

@davidmrdavid davidmrdavid commented Jan 9, 2024

As in title: automation to generate preview packages of DTFx.Core and DTFx.AzureStorage on ADO. This is the DTFX equivalent of: Azure/azure-functions-durable-extension#2709

This PR does two things:
(1) It makes the pipeline run automatically after every commit to the main branch
(2) On any automatic run, it appends a suffix to the generated package version.

In the long run, we can take this package version and automatically push it to our ADO feed so that it may be consumed by our pre-existing nightly DF Extension testing feed, so that we have nightly testing coverage across repos.

@davidmrdavid davidmrdavid changed the title [WIP] add manual suffix generation Add Automatic suffix generation for DTFx.Core and DTFx.AzureStorage Mar 22, 2024

<!-- This version is used as the nuget package version -->
<PropertyGroup Condition="$(VersionSuffix) == ''">
<Version>$(MajorVersion).$(MinorVersion).$(PatchVersion)</Version>
Copy link
Member

Choose a reason for hiding this comment

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

Should we continue to use $(VersionPrefix) like we were before, or did you have a reason to remove it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've re-added it. I can't recall exactly why I removed it (a local version of this PR has been sitting on my devbox for a while).

pr: none

pool:
name: '1ES-Hosted-DurableTaskFramework'
demands:
- ImageOverride -equals MMS2022TLS

variables:

- name: PackageSuffix
Copy link
Member

Choose a reason for hiding this comment

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

It seems PackageSuffix serves the same purpose as VersionSuffix. Was there a reason not to simply assign VersionSuffix directly as an alternative to creating a new build variable?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've unified them in VersionSuffix. I think I had made them differently because I wasn't sure to what extend I could just continue reading env variables in the .csproj. So far, it seems like I can do that with no restrictions, so I've removed the VersionSuffix xml variable I introduced and replaced it with this env var.

@davidmrdavid davidmrdavid requested a review from cgillum March 25, 2024 17:19
@davidmrdavid
Copy link
Collaborator Author

@cgillum: could you give this another pass?

@davidmrdavid davidmrdavid requested a review from cgillum March 27, 2024 18:51
@davidmrdavid davidmrdavid merged commit dbcabaf into main Mar 27, 2024
2 checks passed
@davidmrdavid davidmrdavid deleted the dajusto/automate-suffixes branch March 27, 2024 20:21
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.

2 participants