Closed petertijsma closed 1 year ago
petertijsma
commented
1 year ago UPDATE: Tried removing one level "CurrentApp" from the directory structure and now it worked. Seems that compile fails if there is only one directory with sources (in this case only "s/CurrentApp/App") Normally i have more subdirectories like "s/ThirdPartyApps/xxxxx" etc.
Still, I think this should not influence the compiler
waldo1001
commented
1 year ago Could it be that your initial setting was wrong?
I see in your output that the targetproject-param is:
F:\ADOAgents\Agent2\_work\21\s\CurrentApp\CurrentApp\App\app.json
Twice "CurrentApp" seems a mistake?
waldo1001
commented
1 year ago Another tip to investigate:
Perform a Get-ChildItem -Path "c:\Run\DevOps\" -Recurse in a docker exec after the Docker Wait.. .
petertijsma
commented
1 year ago Found the culprit:
Yaml of a build with MULTIPLE resources:
steps:
- checkout: self
path: s\CurrentApp
clean: true
persistCredentials: true # allow git auth token be used
- checkout: ThirdPartyApps
path: s\ThirdPartyApps
clean: true
persistCredentials: true # allow git auth token be used
Output of "ALOpsDockerWait"
*** Copy Working folder to Docker Container: 8fdd30267a436b879b6e15946ce53f50dc4d5cd469e2b8bd0b4c13ffd1d5a4e1
*** Docker Working Folder: c:\Run\DevOps\
*** Copy from [F:\ADOAgents\Agent1\_work\1\s] to [c:\Run\DevOps\]
*** Compression Enabled Transfer (Dotnet)
Yaml of a build with a SINGLE resource:
steps:
- checkout: self
path: s\CurrentApp
clean: true
persistCredentials: true # allow git auth token be used
Output of "ALOpsDockerWait"
*** Copy Working folder to Docker Container: c341676886ef4447c9ef17016b68098b78ce233377778bb4f6528bfed0c14380
*** Docker Working Folder: c:\Run\DevOps\
*** Copy from [F:\ADOAgents\Agent1\_work\24\s\CurrentApp] to [c:\Run\DevOps\]
*** Compression Enabled Transfer (Dotnet)
See the difference in the copy action?
Somehow ALOps tries to be smart and limit the number of directory levels if there's only one directory, but this is confusing further down the road :-)
At least good to know now. Will be able to work with it.
(PS, your tip to list the contents of C:\Run\Devops did the trick to find this :-) )
waldo1001
commented
1 year ago We're working with workingdirectory, which gets messed up when working with multiple checkouts. So if working with multiple checkouts, you'll have to manage it like above.
Hi,
I'm trying to create a new build pipeline (based on an older existing one), but for some reason it doesn't want to compile/create the app because it can't find te project folder
The Compile Step output:
It states:
error AL1018: Directory 'c:\Run\DevOps\CurrentApp\App' could not be found error AL1001: Source file 'c:\Run\DevOps\CurrentApp\App\app.json' could not be foundBut when I check the agent itself (and thus the folder that needs to be transferred to the Docker, all seems good:
No clue what's wrong.
Just a sidenote: The idea here is to generate a separate small translation app, containing only the xlf file needed for our main app. This way, translations can be added to the production environment (On Premise) easily without disturbing everybody else. Since there is only the xlf file present, no schema updates are necessary, making it very quick and easy to publish.