action #10516
closed
[functional][u] Use jenkins as extension for openQA
Added by okurz over 8 years ago.
Updated about 4 years ago.
Description
user story¶
As an openQA instance administrator I want to trigger tests on new product builds, monitor working status, provide push notification to users with jenkins not to reinvent the wheel on this
acceptance criteria¶
- "rsync.pl" can be replaced by jenkins
further notes¶
This is an extension on https://hackweek.suse.com/13/projects/1208
For the record, Fedora will soon switch to using [https://taskotron.fedoraproject.org/ Taskotron] for this purpose. I'm not sure if SUSE is at all interested in using it, but thought I'd mention it. It's basically a task scheduler and test result storage database with a focus on QA automation.
ok thx Adam for your post and advice with taskotron.
I would like to know, what is the difference between Tasktron and Jenkins, in better words, why you are going to make Tasktron when there is Jenkins that's mature and is really adapt for testing. I want to know, it's not a provocation. ( i already read your docs, so just don't paste and copy :) )
- Status changed from New to In Progress
Some steps have been done already. http://lord.arch.suse.de:8080 is a jenkins instance in use, e.g. openSUSE Krypton on o3 is triggered by this jenkins instance. If anyone is interested, you are welcome to ask me. Next steps could be
- extract jenkins build step code snippets into a repo and call them from there
- provide a jenkins appliance
- document it, blog about it, provide a video
- replace
rsync.pl
- …
- world domination
- Description updated (diff)
- Category set to Feature requests
- Project changed from openQA Project to openQA Tests
- Category changed from Feature requests to Infrastructure
- Subject changed from Use jenkins as extension for openQA to [functional]Use jenkins as extension for openQA
- Priority changed from Normal to Low
- Target version set to future
- Target version changed from future to future
- Related to coordination #36778: [functional][u][y][epic] improve openqa triggering mechanisms, standardize OBS/IBS deliverables structure, trigger jobs using other means added
I moved the jenkins instance from lord.arch.suse.de:8080 to jenkins.qa.suse.de . Moved /var/lib/jenkins/ to jenkins.qa.suse.de, followed https://devopscube.com/access-run-jenkins-port-80/ for nginx reverse proxy to forward traffic over port 80 to internal 8080 and replaced references to lord.arch with jenkins.qa in /var/lib/jenkins/*.xml
- Copied to action #42233: Production-grade jenkins.qa.suse.de for QA SLE (EMEA) added
- Subject changed from [functional]Use jenkins as extension for openQA to [functional][u] Use jenkins as extension for openQA
- Status changed from In Progress to Workable
- Project changed from openQA Tests to openQA Infrastructure
- Category deleted (
Infrastructure)
- Status changed from Workable to New
@szarate does not want to see it in the Workable list, which is fine for now. It's in "future" :)
- Status changed from New to Resolved
- Assignee set to okurz
jenkins.qa.suse.de is running fine but nothing is moving forward. I doubt this ticket provides more help staying open.
Also available in: Atom
PDF