Closed NAVFreak closed 1 year ago
Hard to see for us what causes this.
Can you check the build agent to see what is in your folder? Or check our repository for big files? Or a huge amount of files?
ALOps transfers all files in the repo to the container - that is slowed down for this project it seems, so it must be something in your repo...
@NAVFreak, any feedback on this?
@NAVFreak ?
Sorry. It seemed to disappear by itself. But... It maybe disappeared when we start using new agent servers and "tossed" the old ones with this problem 🤷
Den ons 8 mars 2023 11:19waldo @.***> skrev:
@NAVFreak https://github.com/NAVFreak ?
— Reply to this email directly, view it on GitHub https://github.com/HodorNV/ALOps/issues/584#issuecomment-1459940230, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIKZT4CC5TICFUEOGTVMCXDW3BMM7ANCNFSM6AAAAAARY3NWFE . You are receiving this because you were mentioned.Message ID: @.***>
In case searching folks come across this later:
We had a client with ALOps running a build agent with this problem. Very very slow on this step. I finally noticed that the "Transfer compressed Archive to session" line? That was the hold up. When I dug in, it was zipping, transferring, and unzipping 7gb into the docker for a 134mb app.
The "fix" for us ended up being to empty out the #\ folders in the agent Work path. Presumably, some clean up step hadn't run to flush old things out. Builds went from 1+ hour to a reasonable number of minutes again.
@waldo1001 - adding #672 PR so you don't have to figure out writing this up. 😄
We are running several pipelines but it is only pipelines in a certain project that we have problem with "Wait for container to start". For other pipelines it just takes a couple of minutes but in this project it takes around 10-40 minutes(!) and they are running on same machines. I saw #462 but in this case it has been turned off.
Is it the artifact that causes this? 🤔 I created a pipeline that was a copy with next minor and then it went fast, < 1:20 minutes two times
the used yaml The only difference that I can see between the pipelines is the artifact version because we create everything via a template.
the output Output of: ALOPS - Wait for Docker Container to start
Expected behavior That it shouldnt take that loong.
Screenshots
Additional context Images