ALOps Extension API task hangs #660
Labels
Comments
|
We are experiencing the same with around 40 apps, I was trying another approach described here, but the problem is the same that our pipeline also hangs (I have put a timeout to make it go to next task within 20 minutes. |
|
Few questions:
We're obviously dependent from the "dev endpoint" and how that reacts. We don't have anything under control from the moment we send the app to the dev endpoint .. so we need to figure out which it cancels first.. . @MortenRa , |
|
I was trying out other things due to this issue, which was to have the app uninstalled to install the new version of the app to see if that would solve my issue. (yes trying to use admincenterapi to uninstall a devscope app and no not sure if that can be solved) but if this issue reported here can be solved somehow, then I would not need the other approach in #634 -Not a big app and it does get installed, I merely thing it is the dependency it is waiting for(which also gets installed) -No Upgrade code -Yes -No |
My answers are basically the same as @MortenRa
This used to work, but as we increased the number of apps it started failing, so I agree it might be a limitation of the "dev endpoint". |
|
Hi, Any update on this? This is quite blocking for us. |
|
We have been trying to simulate, without success. Looking at the code, it's just a webservice-call, which obviously waits until it comes back with an answer. So at this point, how we see it, it's indeed a limitation of the dev endpoint :-/. Would you be able to help us setting up a repro? |
I'll ask around internally if this is a possiblity (company procedures etc... and I'm just a simple dev :-P) |
|
As mentioned in #668, we'll add more output on this task - hopefully it will be more clear what fails. |
Unfortunately at this point I was denied permission to assist in setting up a repro due to time constrains. However, I'll be happy to assist and provide feedback on the extended output. Thank you. |
|
We possible found the problem in this process, if the user used for calling the API is not in "English" the API will return a translated status that ALOps cannot match. Please try our latest release v1.459 Kind regards, |
|
We currently have disabled the AlExtensionAPI step cause of the issues. I'll give it a try next week. |
|
My apologies for the delay. This week I had some time to try this. ALOPS Info: The ALOps Extension API task unfortunately still hangs: During this step I kept track of what was happening:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We have 27 apps. 26 of these apps depend on our "Core" app. We use the ALOps Extension API task in a Release Pipeline to deploy to a Sandbox.
This pipeline hangs during publishing of the "Core" app. When you take a look at Extension Management in BC, you can see the task removes all other apps and installs the new "Core" app. After that the other apps are installed again. This process takes around 20 minutes. After completing the install of the "Core" app, the pipeline doesn't produce any output anymore and hangs. This prevents us from updating any other apps.
The output
Expected behavior
The process should continue after publishing/installing the Core App.
The text was updated successfully, but these errors were encountered: