-
Hi, I was wondering if anyone can shed some light on the following: We are running Cypress in Azure Devops Pipelines and to speed up the build we run multiple cloud agents in parallel. We get these agents from Microsoft and then run This machine is sending different environment parameters than the first machine that started this parallel run. The existing run is: xxx In order to run in parallel mode each machine must send identical environment parameters such as:
This is the third time it is happening so we are now looking at a perm solution which will prevent this in the future. We tried looking at the documentation but it's not clear how Chrome is installed by Cypress and if we can control the versions (so that we can switch to the newer version when we are sure it's rolled out everywhere). Can anyone shed some light on this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Never mind, found out that it uses the installed Chrome version and Cypress doesn't install it itself. As information: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md the agent uses this image which probably isn't updated yet on all agents Microsoft supplies. |
Beta Was this translation helpful? Give feedback.
-
@Rutix If you are able, please provide a Azure Pipelines YAML, but it sounds like a custom container is not being used in your configuration. Most likely passing a container parameter with one of our Cypress Docker Images will ensure that all of the workers have the same version of Node along with browsers. |
Beta Was this translation helpful? Give feedback.
-
@kevinold That sounds like a good plan! We are gonna try to see if we can use a Cypress Docker image and will report back! Thanks for the tip. |
Beta Was this translation helpful? Give feedback.
Never mind, found out that it uses the installed Chrome version and Cypress doesn't install it itself. As information: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md the agent uses this image which probably isn't updated yet on all agents Microsoft supplies.