Closed Miki-84 closed 3 years ago
Hi, it has probably something to do with the "February Update". It has been reported a couple of times: https://github.com/HodorNV/ALOps/issues?q=is%3Aissue+is%3Aclosed+Compile+OK
Can you try to set up your container with hyper-v isolation?
Here an example:
- task: ALOpsDockerStart@1
inputs:
docker_image: 'mcr.microsoft.com/businesscentral/sandbox'
docker_pull: true
docker_parameters: '--isolation=hyperv'
memory_gb: 8
Hi Waldo,
Thanks for the reply, I tried with the hyper-v isolation but the server was not ready for it. I will talk to my IT collegues and give it another try and i will let you know.
Thanks again and sorry for repeating the question.
Dear @Miki-84 ,
Please check this comment on another issue: https://github.com/HodorNV/ALOps/issues/119#issuecomment-621353208
This ALC issue seems to be related to the image, the same one as you are using. Could you check if changing the image resolves the problem?
Kind regards,
Hi AdminHodor,
I am having some troubles trying to compile in another image to test. It has to be pulled and the agent is giving me the 60 minutes timeout.... I can pull it previously manually but then ALOps does not reuse it and tries to pull it again and i've got the 60 minutes timeout again. Any idea how can I bypass this situation?
Hello @Miki-84 ,
It has to be pulled and the agent is giving me the 60 minutes timeout... 60 minutes is indeed the default timeout for Azure DevOps Jobs.
I can pull it previously manually but then ALOps does not reuse it This can not be correct, ALOps does not manipulate the image in any way. If you Pulled in manually, it should be picked up. Are you sure you pulled the correct image? ALOps does add the correct -ltsc2016 / 2019 tags when required.
When you look at the log for the DockerStart step, you should see the exact image name queried for pull. Use that exact image for your manual pull.
Kind regards,
@AdminHodor i finally was able to try to compile with another image (mcr.microsoft.com/businesscentral/sandbox:es) but it ended up crashing again.
I will try the hyperv solution as soon as i can and let you know how it went.
Thanks
Hi @Miki-84 , any input on this?
Hi Waldo,
Sorry for the delay. I never had the chance to try the hyperv solution because i was not in controll of the server and some bios modifications needed to be done. Sorry for that.
Hi @Miki-84 ,
we will have a new compiler-step this week (new release). This might solve your issue.
Hi @waldo1001 ,
I wil ltry again, because i don't know wwhy but my Azure devops pipelines have dissapeared, so i will give it a new try to see i f i can manage to generate the .app files from source code in devops. I'll keep you posted!
Hi @waldo1001 , Yesterday i could try the new version of ALOPS and it worked perfectly! A couple of questions though,
Thanks for everything!
Hi @Miki-84 ,
Yes, the ALOps license is activated, and is checking for trials. You will get warnings before it runs out (resulting in partially succeded pipeline runs) and eventually, when it runs out, the pipeline will simply fail. From the moment there is a license, it will just work again.
So I assume you used the "Compiler v2"? It's a preview feature (which is pretty stable - it's the only thing we use internally) that we are extending a bit as we speak .. so any feedback is always appreciated.
I misread the second question, so I changed my response above.
About the appname - it's basically because in our opinion it's interesting to also give details on which localization the app was built. At this point, it's not part of the setup. Why would you like to change it?
Hi @waldo1001, Actually there is no real reason that makes me want to change the name. It is probably my lack of expirience, but i always thought that the build would give me the final name of the extension and that i would not have to rename it in a release pipeline...or maybe MyExtension.1.0.XXX.0_onPrem_es.app should be the final name of the application? I don't see it...i think i am missing something here.
Thanks
Well, the release pipeline shouldn't care - it will just get a bunch of .app files, and install them, right?
You are right... i should start to realize that with this kind of automation there are some names that should not matter. Thanks!
Here's an example of why we went for thing naming template, the following yaml will build one app for multiple Types,Countries and Versions, all in one go.
azure-pipelines.yml
name: $(Build.BuildId)
# This compiler (v2) is not going to use a docker container, but it's going to use the artifacts that you specify in the parameters
# The compiler will "Batch Compile", meaning: it will compile everything in the workingfolder
jobs:
- job: MultiBuildSuperCompile
timeoutInMinutes: 0
pool: HOD-DOCKER
steps:
- template: 05_MultiVersion_template.yml
parameters:
artifacttypes: ['Sandbox','OnPrem']
artifactversions : ['16.3','16.4']
artifactcountries: ['w1','be']
05_MultiVersion_template.yml
parameters:
artifacttypes: []
artifactversions : []
artifactcountries: []
steps:
- ${{ each artifacttype in parameters.artifacttypes }}:
- ${{ each artifactversion in parameters.artifactversions }}:
- ${{ each artifactcountry in parameters.artifactcountries }}:
- task: ALOpsAppCompiler@2
displayName: 'ALOps Compile v2 - ${{ artifacttype }}-${{ artifactversion }}-${{ artifactcountry }}'
inputs:
artifacttype: '${{ artifacttype }}'
artifactversion: '${{ artifactversion }}'
artifactcountry: '${{ artifactcountry }}'
appversiontemplate: '1.0.*.0'
When run the pipeline explodes to all combinations:
Result of the pipeline are these artifacts, which explains the naming convention :-)
Hello,
I am trying to compile my AL project using the ALOpsAppCompiler step.
When compiling and executing alc.exe in the agent it fails with the following error:
If I try to execute the same alc.exe instruction locally in the machine then it works and generates the .app correctly:
My pipeline configuration is as follow:
And the complete log of the compilation step is:
I've been trying but I am stuck and i don't know how to continue. If you can give me any hint or idea about the solution it would be greate.