Closed dNsl9r closed 3 years ago
This is DevOps internal caching that isn't that friendly with Business Central. Sometimes it even happens it takes files from a previous run.
to mitigate this, you could enable a better cleanup like this: Edit your pipeline, and go to triggers navigate to YAML and then Get Sources Set it up to clean all build directories
Thanks @waldo1001 - changed it. I'll be watching them - very well 🤖
btw: as far as I can see this can also be done in the YAML file, right?
Describe the bug We had a pipeline run, that failed with:
##[error]error AL1001: Source file 'c:\Run\DevOps\app.json' could not be found
The step did the following before:
Copy from [C:\Agent\_work\68\s] to [c:\Run\DevOps\]
So I checked the folder C:\Agent_work\68\s - it contains the app.json as expected.
After starting a new run for the pipeline the job completed without problems. And now the strange part:
Instead of generating a new "_work\NN" folder the pipeline run took the 68 one. This should not happen,right?
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior No error of course..