mikefactorial
commented
1 year ago @bronsonacoutts apologies that this was never responded to. Will look into what's happening here, but may come back with questions.
Closed bronsonacoutts closed 1 year ago
mikefactorial
commented
1 year ago @bronsonacoutts apologies that this was never responded to. Will look into what's happening here, but may come back with questions.
bronsonacoutts
commented
1 year ago Know what? Thats quite alright, not really sure how you manage to respond to all of the posts you get on here period, let alone investigate them and provide solutions!
I have more info on this now.... After some resyncing and a variety of other things - I haven't seen specific error for a while now.
Instead, about the same time that this one stopped, I am now getting a fail on about 50% of my solutions when exporting to git .
It always fails at "updating deployment settings" here's a sample:
2022-11-17T07:23:19.3255802Z ##[section]Starting: Update Deployment Settings
2022-11-17T07:23:19.3415016Z ==============================================================================
2022-11-17T07:23:19.3415544Z Task : PowerShell
2022-11-17T07:23:19.3415997Z Description : Run a PowerShell script on Linux, macOS, or Windows
2022-11-17T07:23:19.3416408Z Version : 2.212.0
2022-11-17T07:23:19.3417450Z Author : Microsoft Corporation
2022-11-17T07:23:19.3418000Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2022-11-17T07:23:19.3418597Z ==============================================================================
2022-11-17T07:23:20.4448497Z Generating script.
2022-11-17T07:23:20.4938674Z ========================== Starting Command Output ===========================
2022-11-17T07:23:20.5220654Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\4729fa0c-12f4-4303-a225-d84980022553.ps1'"
2022-11-17T07:23:20.9429206Z {
2022-11-17T07:23:20.9429801Z "value": [
2022-11-17T07:23:20.9430166Z {
2022-11-17T07:23:20.9430658Z "BuildName": "deploy-validation-PowerBICommentary",
2022-11-17T07:23:20.9431262Z "BuildTemplate": null,
2022-11-17T07:23:20.9431782Z "DeploymentEnvironmentName": "Validation",
2022-11-17T07:23:20.9432370Z "DeploymentEnvironmentUrl": "https://<
2022-11-17T07:23:21.0110713Z ---- ------------- ------ ----
2022-11-17T07:23:21.0133075Z d----- 11/17/2022 7:23 AM config
2022-11-17T07:23:21.0378031Z Retrieved 3 deployment environments
2022-11-17T07:23:21.0396316Z https://dev.azure.com/<
2022-11-17T07:23:23.7695409Z ---- ------------- ------ ----
2022-11-17T07:23:23.7719805Z d----- 11/17/2022 7:23 AM Validation
2022-11-17T07:23:23.7842317Z Creating deployment settings
2022-11-17T07:23:23.8030131Z Creating custom deployment settings
2022-11-17T07:23:23.8191117Z https://dev.azure.com/<
2022-11-17T07:23:23.8586246Z Creating deployment settings
2022-11-17T07:23:23.8660413Z Creating custom deployment settings
2022-11-17T07:23:23.8701050Z https://dev.azure.com/<
2022-11-17T07:23:23.9090210Z Creating deployment settings
2022-11-17T07:23:23.9159864Z Creating custom deployment settings
2022-11-17T07:23:23.9277543Z
2022-11-17T07:23:23.9277924Z
2022-11-17T07:23:24.0161976Z ##[error]PowerShell exited with code '1'.
2022-11-17T07:23:24.0511750Z ##[section]Finishing: Update Deployment Setting
I have resynced pipelines (more than once) I have upgraded (more than once) I have checked all of the deployment profiles I have deleted deployment profiles and recreated them (more than once)
I thought at first that it was only affecting the solutions that I had changed the repo for alas; it seems to be occurring with any new solution that I create a profile for as well.
Similarly, I am getting a 404 when attempting to import a solution, like I say, I have resynced the repo, but perhaps I am doing something else wrong.
mikefactorial
commented
1 year ago @bronsonacoutts this appears to be related to another issue (https://github.com/microsoft/coe-starter-kit/issues/4077) specific to spaces in project names. There's a PR here that was merged 4 days ago with a 2 line change that will likely resolve your issue.
https://github.com/microsoft/coe-alm-accelerator-templates/pull/239
bronsonacoutts
commented
1 year ago @mikefactorial Thanks for that buddy! I just read this, it started working, so I guess your updates were successful!
Thanking you!
Still having issues with the import feature. I will do some more testing and check the other open issues to see if there is something related in the pipeline. Otherwise will raise a separate issue.
CoEStarterKitBot
commented
1 year ago @bronsonacoutts This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
bronsonacoutts
commented
1 year ago Awesome work! Thanks Mike. A real modern day Mother Theresa!
On Thu, 8 Dec 2022, 2:08 am CoE Bot, @.***> wrote:
@bronsonacoutts https://github.com/bronsonacoutts This has been fixed in the latest release. Please install the latest version of the toolkit https://aka.ms/CoEStarterKitDownload following the instructions for installing updates https://docs.microsoft.com/power-platform/guidance/coe/setup#installing-updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/coe-starter-kit/issues/4053#issuecomment-1341197766, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHETZPFWUR2QWBHEV2T3YLWMCY65ANCNFSM6AAAAAARPVXQRE . You are receiving this because you were mentioned.Message ID: @.***>
Describe the issue
Folks,
I have (what seems to be spontaneously) developed an error with the commit pipeline for some of my existing solutions (that have previously worked).
Some of the solutions that have previously run this pipeline several times successfully are now all failing at the same point. While other solutions from the same DEV environment continue to run BAU.
Starting: Saving Export Pipeline Parameters
Task : PowerShell Description : Run a PowerShell script on Linux, macOS, or Windows Version : 2.210.0 Author : Microsoft Corporation Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
Generating script. ========================== Starting Command Output =========================== "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\93087eee-abcc-418d-8a9a-cf9a10a281c6.ps1'" Write-Export-Pipeline-Parameters : A positional parameter cannot be found that accepts argument 'https://<>.crm6.dynamics.com/'.
At D:\a_temp\93087eee-abcc-418d-8a9a-cf9a10a281c6.ps1:5 char:1
[error]PowerShell exited with code '1'.
Finishing: Saving Export Pipeline Parameters
Expected Behavior
The pipeline successfully commits to Git.
What component are you experiencing the issue with?
ALM Accelerator Pipelines
What solution version are you using?
1.0.20221004.2 & CenterofExcellenceALMAccelerator-October2022-HF1
Steps To Reproduce
No response
Anything else?