Your Privacy
We use cookies to give you a better experience in Alchemy Help Center
You can learn more about what kind of cookies we use, why, and how from our Privacy Policy. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings in our cookie banner to change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer. For more details, check out our Privacy Policy link below.
View Privacy Policy
Strictly Necessary Cookies
These cookies are necessary for the website to function and cannot be switched off in our systems, but do not store any person information. They are usually set in response to your actions that triggers a request for services, such as setting your privacy preferences, logging in or filling forms. You can change your browser settings to alert you about these cookies, but some parts of the Website may not work.
View Cookies
Since the grids are being automatically deleted, I want to execute the suites on the Grid I manually created. Is this possible in Alchemy?
0 Votes
David posted about 1 month ago Admin Best Answer
If you configure the Alchemy Gridworks integration to execute on a specific grid, then when the test completes, the grid is not destroyed. To do this get the gridId from the Gridworks UI. The gridID is in the red box below. To get straight to the GridWorks UI, login at: https://ui.alchemytesting.cloud/dashboard
Now in the Alchemy client add the gridID to your Alchemy Gridowrks configuration.
Now when you execute using the Gridorks router configured in this manner, the existing grid will be used, and not destroyed at the end of the suite execution. The nodes will stop according to the timeouts set in the configuration. However, the Recordings of executed tests on nodes spun up during the test will be available in the Recordings.
Hope this helps, I will also add that you can alter the target grid at runtime by manipulating the command line to run with -CLD_gridId <<gridID>>. Where <<gridID>> is the gridID of the existing grid in Alchemy Gridworks where you want to run the suite. So, it doesn't matter if the existing gridID was different or even missing from the original executable when it was built.
0 Votes
1 Comments
David posted about 1 month ago Admin Answer
If you configure the Alchemy Gridworks integration to execute on a specific grid, then when the test completes, the grid is not destroyed. To do this get the gridId from the Gridworks UI. The gridID is in the red box below. To get straight to the GridWorks UI, login at: https://ui.alchemytesting.cloud/dashboard
Now in the Alchemy client add the gridID to your Alchemy Gridowrks configuration.
Now when you execute using the Gridorks router configured in this manner, the existing grid will be used, and not destroyed at the end of the suite execution. The nodes will stop according to the timeouts set in the configuration. However, the Recordings of executed tests on nodes spun up during the test will be available in the Recordings.
Hope this helps, I will also add that you can alter the target grid at runtime by manipulating the command line to run with -CLD_gridId <<gridID>>. Where <<gridID>> is the gridID of the existing grid in Alchemy Gridworks where you want to run the suite. So, it doesn't matter if the existing gridID was different or even missing from the original executable when it was built.
0 Votes
Login or Sign up to post a comment