docs: update Jenkins integration guide with Kubernetes and VM examples#533
Open
caiomede-tk wants to merge 4 commits intomainfrom
Open
docs: update Jenkins integration guide with Kubernetes and VM examples#533caiomede-tk wants to merge 4 commits intomainfrom
caiomede-tk wants to merge 4 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
|
thanks @caiomede-tk - should https://docs.testkube.io/articles/jenkins-ui be updated also/accordingly? Perhaps add tip at the top pointing to the non-ui approach as preferred? |
olensmar
reviewed
Apr 17, 2026
|
|
||
| :::warning | ||
|
|
||
| Testkube CLI Jenkins Plugin is only compatible with Testkube Control Plane SaaS or Cloud, because there is no property or environment variable to override Control Plane API URI, please use the Groovy scripts as it's recommended above. |
Member
There was a problem hiding this comment.
wordsmithing:
- change "..is only compatible with Testkube Control Plane SaaS or Cloud.." -> "only works with the Cloud-hosted Testkube Control Plane"
- change ".. Control Plane API URI,.." -> ".. Control Plane API URI. If you are hosting the Control Plane yourself, please use.."
Collaborator
Author
There was a problem hiding this comment.
Improvements applied, please check
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restructures the Jenkins integration documentation to cover multiple deployment scenarios and prioritize the Docker image approach over the Jenkins plugin.
Changes
kubeshop/testkube-cliDocker image directly in a Kubernetes pod template, with examples for both Cloud and Self-Hosted Testkube. Includes important notes aboutsecurityContext.runAsUserandHOMEenv var requirements.curl -sSLf https://get.testkube.io | shdirectly on Jenkins agents, with examples for Cloud, EKS, and GKE.setupTestkube()examples.Why
The previous docs only covered the Jenkins plugin approach (
setupTestkube()). Users running Jenkins on Kubernetes can avoid binary download issues entirely by using thekubeshop/testkube-cliimage, and VM users benefit from a straightforward CLI install script.