Running automated tests with containerized agents on IBM® Cloud Private
To adopt IBM® Cloud Private fully and manage the entire development to deployment workflow on cloud, you would want to start and stop capabilities with a few clicks. By providing the agents in containers, you can dynamically provision capability as required without procuring the machines and installing the agents.
Before you begin
You must have configured IBM® Cloud Private as per the instructions in Configuring IBM Cloud Private.
About this task
You must use only floating licenses to play back the tests.
To automate deployment and playback of the tests, you can choose to create bash scripts for the
Kubernetes commands and integrate with Jenkins.
Note: The version number of the container images and
the desktop products must match. If you have previous version of the container image, uninstall it
and install the current version. To uninstall the image, use these commands:
- Stop the container by running
.docker stop "CONTAINER ID"
- Uninstall the image by running
.docker rmi -f "image ID"
Procedure
-
Log in to the IBM® Cloud Private
management console and complete the following steps:
- Verify that you have two deployments of the agent by clicking .
-
On your workbench, use the Agent Status button to verify the two
container agents are polling the workbench.
Note: The agent host names should match the IDs of the containers running in IBM® Cloud Private. Make a note of the IP address of each agent because they will be used when creating the agent locations.
- Create a new location asset for each container agent and associate it with a user group. For more information, see Running a user group at a remote location.
-
Run the schedule and verify the test results in the workbench.
Note: The deployment step could result in the schedule launch remaining in the
Launching
state for several minutes.