you don’t fit it in the command. the git part you have to set it at the source control part. that will be executed before the build task. no matter if is executed on master or slave. once the project is pulled,you have to refer to it in the script by jenkins variables, not by full path. it will be relative to the $WORKSPACE
hint: just make a simple job, set the git part, add a task to run a script where you just list the current directory content
everytime a jenkins build is started,the workspace is created on the fly,so the root path will always change. this is why in the execution script you have to use the environment variables provided by jenkins
[quote=“Russ_Thomas, post:5, topic:32128”]
What’s it going to take for me to get you to write a series of integrations TIPS?
from your side nothing…from my side … time. and more time
le: now seriously, digging into jenkins is easy. just hit the ‘show environment variables’ link displayed here and there. with bambooo, oook. here is a different story, but same philosophy
As my job is running in a slave machine, this is what I did:
In the general tab of the Jenkins job, check the GitHub option, then give the git url https://myGitHubUrl./myGitHubRepository.git
In the slave, disable checking the certificates, so I wouldn’t get error for unkown certificates. This I did it by opening a git bash and executing the commands:
a. git init
b. git config --global http.sslVerify false
in the execute Windows batch build step, in the Jenkins job,
//go to the git folder where the katalon project is located
cd “C:\DEV\git\myRepository”
//pull the project, so you have the last version of the source
git pull
//go to the folder where the katalon studio is stored
cd “C:\Katalon_Studio_Windows_64-6.2.1”
//execute the test suite
katalon -noSplash -runMode=console -projectPath=“C:\git\myRepository\MyProject.prj” -retry=0 -testSuitePath=“Test Suites/create_client” -executionProfile=“default” -browserType=“IE”
this is a bit redundant. since you already configured the git repo … it is already pulled i wil try to find some time tomorrow to post my aproach by using only already configured git and jenkins variables. may not be accurate since mostly i used linux slaves but you may figure it out