search

microsoft / powerplatform-build-tools

Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.
MIT License
200 stars 41 forks source link

ALM Release. Can see Managed and Unmanaged. Only allowed to select UnManaged #223

Closed rcatbp closed 2 years ago

rcatbp commented 2 years ago

Subsequent to #216 and the fix of CLI breaking as it generates _managed. Now fixed I tried CLI in a release but cannot select the managed solution.

(The build pipeline created the artifacts, running deprecated PowerShell, guessing it shouldn't matter) I also don't understand why I now get the t>,a>,s> folder structure either

ALM-release-with-new-cli ALM-cli-managed-no-ok-lit-up ALM-cli-UNmanaged-ok-lights-up

davidjenni commented 2 years ago

@rcatbp as long as the triggering build pipeline uploaded both the managed and unmanaged solution.zip to the artifact store, your release pipeline's file selection dialog should let you select. Also, after the fix we published, whatever file name should be hannded thru to the import solution task. Is that not what you observe? Can you share the log file for the import task?

re: the cryptic paths: this is the Azure DevOps' agent's way to keep paths short and avoid running into MAX_PATH issues

rcatbp commented 2 years ago

Hi David,

Thanks for looking, log attached, the run was okay.

As you saw on the screenshot, cannot select 'managed' odd.

Cheers, richard

From: David JENNI @.> Sent: 22 November 2022 17:11 To: microsoft/powerplatform-build-tools @.> Cc: Collins, Richard (TATA CONSULTANCY SERVICES (TCS)) @.>; Mention @.> Subject: Re: [microsoft/powerplatform-build-tools] ALM Release. Can see Managed and Unmanaged. Only allowed to select UnManaged (Issue #223)

@rcatbphttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frcatbp&data=05%7C01%7Crichard.collins%40bp.com%7Ce3ea3c865425440303e008daccaca509%7Cea80952ea47642d4aaf45457852b0f7e%7C0%7C0%7C638047339115142886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=t%2BXGcsaseVWNFhkQgJRZGHPS33E%2B%2BbbnILhlG97NJJ0%3D&reserved=0 as long as the triggering build pipeline uploaded both the managed and unmanaged solution.zip to the artifact store, your release pipeline's file selection dialog should let you select. Also, after the fix we published, whatever file name should be hannded thru to the import solution task. Is that not what you observe? Can you share the log file for the import task?

re: the cryptic paths: this is the Azure DevOps' agent's way to keep paths short and avoid running into MAX_PATH issues

— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowerplatform-build-tools%2Fissues%2F223%23issuecomment-1323998736&data=05%7C01%7Crichard.collins%40bp.com%7Ce3ea3c865425440303e008daccaca509%7Cea80952ea47642d4aaf45457852b0f7e%7C0%7C0%7C638047339115142886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Km2trY93V2g5meQPhVl67EV%2FzbluYrUWKHcnbca1o58%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXC243D5OMNZILJ5SGFJ2GLWJT5FLANCNFSM6AAAAAARPDNUR4&data=05%7C01%7Crichard.collins%40bp.com%7Ce3ea3c865425440303e008daccaca509%7Cea80952ea47642d4aaf45457852b0f7e%7C0%7C0%7C638047339115142886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J09xlyCPKYLHTYaBHmZa7dKcxcq91yIz3l0%2B%2BNVn28s%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>

davidjenni commented 2 years ago

@rcatbp not being able to select is indeed weird. This dialog and the capability that a selection is copied into the Location field, and thus into the "Solution Input file" text box is all done on the Azure DevOps side, our task extension has no ability to either make it succeed nor fail (none of our code is running in that experience). I don't know if this is a known issue w/ Azure DevOps' classical pipeline editor? Since we define the solution input file text box as editable, you can easily override and edit the name to fit.