-
Notifications
You must be signed in to change notification settings - Fork 114
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
Error on deploy stage of CICD Run #1124
Comments
Is this a very large app? |
Or rather - it fails after 5 minutes and 8 seconds :-) 5 minutes = 300 seconds is a default timeout in many places. But in this case, it should use an infiniteTimeOut during publish to dev endpoint (https://github.com/microsoft/navcontainerhelper/blob/b2410696c2c9ce68b63f3ef1a65c0c09d0c58ed1/AppHandling/Publish-NavContainerApp.ps1#L211) If I can get the app and try this myself, I can troubleshoot and see where the timeout is - I haven't been able to repro this myself. |
Yes :) I just noticed that the app installed on the QA environment has scope of DEV. |
In the preview version of AL-Go, you can specify "scope": "PTE" in the deployment settings (released yesterday) If it works with PTE, then we know we have a bug when deploying to dev endpoint - I might not be able to fix it though. |
Ok... I'll see now if it works... on another note... Does the CICD always re-install all apps or will it only install apps that were modified? So if I do dev on another app in the repo that has a dependency on this large app, but I haven't modified the large app, will it re-install all apps in the repo, or just the app that I have modified? |
When doing PTE install - it should check the version numbers before installing. Hope that makes sense. |
Freddy, I want to do one more test but it will only be on monday... I'll get back to you during the day on monday. Thanks for the help. |
You can mail a download link to freddyk at microsoft dot com thanks |
Let me know here when you have sent something, thanks |
Any suggestions on where I can upload it or can I zip and attach to the mail? |
An attachment will probably be blocked. |
Ok thanks |
Ok... I have shared two apps.... the one we are struggling with is the "Base Application". The "CRM" application is dependent on the Base. The CICD should publish both. |
Thanks - what localization/country is your sandbox environment? |
Everything's W1. |
Your QA environment must be some kind of country right? you cannot install W1 in an online environment? |
We are an international company and our BC team is based in South Africa. Because we have people connecting from all over the world we installed our online environment in Ireland. Ireland has no localised version so we use W1. |
You can select IE |
Tried this - I am unable to reproduce this problem. |
@MUR-SDP - FYI, I will be out on vacation for the next 15 days and won't be as responsive on this topic - I was unable to repro the problem, but will continue to look for reasons why this fails when back. |
Thanks very much Freddy. I will check our internet speeds. We have a very fast connection but there has been many undersea cable issues between South Africa and the rest of the world lately that may still affect this. I will also try different connections and let you know. Our publish from VS Code to cloud sandbox also takes very long. We are able to upload manually so please enjoy your holiday and thanks once again. |
Hi Freddy, I don't expect replies until you are back but will post findings here in the meantime. I have run the CICD from an Azure VM which would take all internet speed issues out of the picture, but the time was still over 5 minutes. I then created a new QA Sandbox with Cronus data and it ran through instantly.... it seems using a copy of Production as a Sandbox contains too much data and lengthens the publishing process which then times out at 5 minutes. I suppose there's no way to increase the timeout so the only option is to scale down the database.... I'll have a look if I publish to a production environment if that changes things... anyway... I will close this one... Thanks again for your awesome support... |
@freddydk Just an update... it seems the issue was due to permissions on my App Registration. The permission sets assigned to the Entra App in BC was only for one company and this caused the pipelines to fail. All running fine now. Thanks |
Thanks for the info |
Good day...
As per Freddy, I am creating this as a new issue.
When running the CICD action on our AL-Go environment we get the following error:
Error: Deploying to QA failed. Exception calling "GetResult" with "0" argument(s): "An error occurred while sending the request."
Error: Process completed with exit code 1.
We have two apps in the repo of which one is quite big, about 1.5mb. The pipeline publishes this first (base) app but doesn't install it.
It errors before or while installing the app.
I am able to install the app from the Extension Management Page as well as publish and install the second app in the repo without issues.
The first run I did, this did work correctly....
Herewith a screenshot of the action:
Herewith the log:
Thanks very much...
The text was updated successfully, but these errors were encountered: