Open DanielGoehler opened 1 year ago
Freddy 's opinion that it should be solved in the pipeline doesn't make this is an ALOps-issue ;-).
As I understand it - Get-BcArtifactUrl returns nothing while it should return something. For me, that's clearly an issue in the Get-BcArtifactUrl function 🤷♂️.
Seems that Freddy still "needs to think that through" .. so let's see what he comes up with.
You know what I mean. I can't change the inner workings of the ALOpsAppCompiler v2 task. If you have a better idea to solve this problem, please let me know. This caused a lot of confusion for my collages yesterday.
Sorry - I didn't want to sound that we wanted to avoid this issue. We'll improve the error message.
What we will also do is implement a new parameter: "artifacturl", which will overrule any "Get-BCArtifact", and which makes you possible to even use local downloads, or implement your own logic in retrieving nextmajor.
@waldo1001 No problem. Most of the time it is not that important. A better error message would be a nice improvement. Even better if I can implement a fallback when Get-BCArtifact doesn't return anything.
Is your feature request related to a problem? Please describe. Twice a year, when a new BC version is released,
Get-BCArtifactUrl
fails to return an artifactUrl from 9:00 till 17:00, causing our NextMinor and NextMajor pipelines to fail.E.g.:
Describe the solution you'd like I suggested that BCContainerHelper could output the BC version before, so at least the pipelines will not fail. In a first answer Feddy thinks that this should be implemented in the pipeline (https://github.com/microsoft/navcontainerhelper/issues/2960#issuecomment-1495420602). This would mean in ALOps.
Describe alternatives you've considered At least a better error message would be nice like "Artifact download is currently not possible because the artifactUrl is empty".
Additional context Add any other context or screenshots about the feature request here.
the yaml
the output