From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
|setup= | |setup= | ||
# | # ensure that the Jenkins is up and running | ||
# you should complete [https://fedoraproject.org/wiki/Msrb:TestDay/Test_2 freestyle project] test case first | |||
|actions= | |actions= | ||
# try to run: <code>jenkins-cli -s http://localhost:8080/ help</code> | # try to run: <code>jenkins-cli -s http://localhost:8080/ help</code> |
Revision as of 05:01, 30 September 2014
Description
Try to interact with Jenkins from command-line.
Setup
- ensure that the Jenkins is up and running
- you should complete freestyle project test case first
How to test
- try to run:
jenkins-cli -s http://localhost:8080/ help
- you should see list of all available commands
- try to run:
jenkins-cli -s http://localhost:8080/ list-jobs
- you should see a list of all projects:
project1
- try to run:
jenkins-cli -s http://localhost:8080/ build project1 -s -v
- this should fire a new build of "project1":
Started project1 #2 Started by command line by anonymous Building in workspace /var/lib/jenkins/jobs/project1/workspace [workspace] $ /bin/sh -xe /tmp/hudson7729477737891392405.sh + echo 'Build Successful!' Build Successful! Finished: SUCCESS Completed project1 #2 : SUCCESS
- try to run
jenkins-cli -s http://localhost:8080/ groovysh
- you should see a Groovy shell prompt:
Groovy Shell (1.8.9, JVM: 1.8.0_11) Type 'help' or '\h' for help. ------------------------------------------------------------------------------- groovy:000>
- try to run some Groovy code, for example:
uname -a".execute().text
- type "quit" to quit the Groovy shell
Expected Results
- there should be no failures or stacktraces printed on stdout/stderr