motivation

jenkins is a great CI system (continuous integration) with a plethora of plugins available. SUSE QA uses openQA extensively as it excels in distribution and product testing - not only image comparison (common misconception ;-) ). How about combining both in using jenkins with plugins to act as a UI for openQA?

potential goals

simpler feedback

jenkins can be used by test developers and maintainers to get simpler feedback on

what is the current "big picture" of jobs, e.g.

how many are failing

since when

how did the situation change

which failing tests are not claimed, where can I help

who is working on what

push notification

people who can fix failing tests, introduced a regression or the ones who want to keep tests running can be informed

by email

in IRC

other means as preferred by the user …

an alternative interface to control an openQA instance

Using the jenkins CI web interface to schedule jobs, control trigger, review maintenance of the openQA server itself

execution

My personal plan is to follow the following steps in this order and priority

interface openQA-->jenkins, i.e. one-way first from openQA to jenkins should be enough for first two goals, e.g. by polling in jenkins builds the status of openQA over its REST interface or maybe just the "client" script

Comments

Last hackweek I got distracted by other cool hackweek projects so not much time was invested in this project. I want to give it another try, maybe more focus on using jenkins as a "sophisticated cronjob UI" ;-)

select plugins as useful. Full list of plugins sed -n 's/Long-Name: //p' /var/lib/jenkins/plugins/*/META-INF/MANIFEST.MF, saved on /suse/okurz/local/jenkins_plugins.txt and sed -n 's/Short-Name: //p' /var/lib/jenkins/plugins/*/META-INF/MANIFEST.MF > ~/local/jenkins_plugins_short.txt. I did not follow on installing plugins automatically but this might help: https://gist.github.com/hgomez/2048146ddfb04ca42d91 based on a text list of plugins as saved in before. Restore from backup of /var/lib/jenkins makes sense, see https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Byhand. For this I enabled backup of my instance on lord.arch using unison to rsync everything from /var/lib/jenkins to ibrokeit.

Configured one job to trigger a build if either triggered manually or if URL content on OBS download repo changes, i.e. checking https://build.opensuse.org/package/binary/devel:openQA/openQA?arch=x86_64&filename=_buildenv&repository=SLE_12_SP1 checking the "last modification Date".
And another job taking on monitoring the execution by polling on the webapi response until the job finishes returning with the corresponding result of the openQA job.

Third job added which should trigger based on changes in github repo, in this case okurz/os-autoinst-distri-openQA on changes in master as well as new pull requests.

Similar Projects

This project is one of its kind!

Reply to :

Loading ...

# A First Level Header
## A Second Level Header
Use one asterisk to *emphasize*
Use two asterisks for **strong emphasis**
* Use asterisks
* for lists
This is an [example link](http://example.com/)
This is an ![example image](http://paste.opensuse.org/view/raw/68957446)
This is a user link @hans
This is a project link hw#some-cool-title