-
Notifications
You must be signed in to change notification settings - Fork 124
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
[Question]: Support for Preprocessor Symbols in AL-GO Workflows for NextMinor/NextMajor Builds #1358
Comments
Hi @freddydk, appreciate your insights on this. I was hoping that also
|
@mazhelez - can they use BuildModes for this? |
But artifacts are not output for the different build modes, but the default one. |
I guess the request here is:
Is this what you are looking for? |
@freddydk - Correct, that will work! |
Is this something we will be able to follow on the Roadmap? I interested in the timeline, if and when will this be available. |
I added an item to the roadmap this morning, merging this and a few other requests
Sendt fra Outlook til iOS<https://aka.ms/o0ukef>
…________________________________
Fra: Ivan Đorđević ***@***.***>
Sendt: Thursday, December 19, 2024 10:30:39 AM
Til: microsoft/AL-Go ***@***.***>
Cc: Freddy Kristiansen ***@***.***>; Mention ***@***.***>
Emne: Re: [microsoft/AL-Go] [Question]: Support for Preprocessor Symbols in AL-GO Workflows for NextMinor/NextMajor Builds (Issue #1358)
Is this something we will be able to follow on the Roadmap<https://aka.ms/ALGoRoadmap>?
I interested in the timeline, if and when will this be available.
—
Reply to this email directly, view it on GitHub<#1358 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSGUA2ASPUILLBATYENL3D2GKG37AVCNFSM6AAAAABTQBXCJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGE4DMMZTGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Can you share the card so we can follow? |
https://github.com/orgs/microsoft/projects/521/views/1?pane=issue&itemId=91449371 - a little strange heading, but this is because this workitem will solve some other issues as well (together with this problem) |
Question
Does the current AL-GO workflow support producing NextMinor and NextMajor artifacts built from the
main
branch with specific preprocessor symbols for each release? For instance, we’d like to trigger conditional code blocks specific to these builds only and publish those as separate artifacts.We aim to include conditional logic in the main branch that is only activated for NextMinor or NextMajor builds using preprocessor symbols like NEXTMAJOR, NEXTMINOR, CLEAN25, CLEAN26, etc.
The text was updated successfully, but these errors were encountered: