action #10516

[functional][u] Use jenkins as extension for openQA

Added by okurz about 4 years ago. Updated about 1 month ago.

Status:ResolvedStart date:01/02/2016
Priority:LowDue date:
Assignee:okurz% Done:

0%

Category:-
Target version:QA - future
Duration:


Related issues

Related to openQA Tests - action #34102: [functional][y][epic] improve openqa/scripts Rejected 02/05/2018 31/12/2020
Related to openQA Tests - action #36778: [functional][u][y][epic] improve openqa triggering mechan... Blocked 05/06/2018
Copied to openQA Infrastructure - action #42233: [functional][u] Production-grade jenkins.qa.suse.de for Q... Feedback 01/02/2016

History

#1 Updated by AdamWill about 4 years ago

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.

#2 Updated by dmaiocchi about 4 years ago

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 :) )

#3 Updated by okurz over 3 years ago

  • 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

#4 Updated by okurz over 3 years ago

  • Description updated (diff)

#6 Updated by okurz about 3 years ago

  • Category set to Feature requests

#7 Updated by coolo over 2 years ago

  • Project changed from openQA Project to openQA Tests
  • Category changed from Feature requests to Infrastructure

#8 Updated by okurz about 2 years ago

  • 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

#9 Updated by okurz almost 2 years ago

  • Target version changed from future to future

#10 Updated by okurz almost 2 years ago

  • Related to action #34102: [functional][y][epic] improve openqa/scripts added

#11 Updated by okurz almost 2 years ago

  • Related to action #36778: [functional][u][y][epic] improve openqa triggering mechanisms, standardize OBS/IBS deliverables structure, trigger jobs using other means added

#13 Updated by okurz over 1 year ago

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

#14 Updated by okurz over 1 year ago

  • Copied to action #42233: [functional][u] Production-grade jenkins.qa.suse.de for QA SLE (EMEA) added

#15 Updated by okurz over 1 year ago

  • Subject changed from [functional]Use jenkins as extension for openQA to [functional][u] Use jenkins as extension for openQA

#16 Updated by okurz over 1 year ago

  • Status changed from In Progress to Workable

#17 Updated by szarate about 1 year ago

  • Project changed from openQA Tests to openQA Infrastructure
  • Category deleted (Infrastructure)

#18 Updated by okurz about 1 year ago

  • 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" :)

#19 Updated by okurz about 1 month ago

  • 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