summaryrefslogtreecommitdiffstats
path: root/roles/check-compose
Commit message (Collapse)AuthorAgeFilesLines
* Drop 'remove old manual install' steps that served their purposeAdam Williamson2017-03-061-5/+0
|
* Switch from git checkout to packaged install of openqa_clientAdam Williamson2017-03-061-26/+13
| | | | In check-compose and openqa/dispatcher roles, now it's packaged.
* openQA roles: use python2-fedfind not fedfindAdam Williamson2017-02-181-2/+2
| | | | I split the package, we don't need the CLI, only the lib.
* check-compose: use appropriate fedmsg consumerAdam Williamson2017-02-143-4/+10
| | | | Don't use prod consumer on staging...
* In ansible 2.2 always_run is depreciated. Switch to check_mode.Kevin Fenzi2016-11-011-1/+1
|
* check-compose: don't need this nowAdam Williamson2016-10-281-3/+0
|
* check-compose: update git repo locationAdam Williamson2016-10-281-6/+9
| | | | I moved it to Pagure.
* check-compose: handle new two-week Atomic composesAdam Williamson2016-06-281-0/+7
| | | | | | | | Update the check-compose config file to use the variant config for the 'Atomic' milestone as well as the 'Postrelease' milestone - this should DTRT for the new Pungi 4 two-week Atomic composes, which have 'Atomic' as their milestone, sending the report to the correct addresses.
* openqa/check-compose: tweak package installs and sourcesAdam Williamson2016-03-081-1/+8
| | | | | we need some from updates-testing for now. also, we need openqa-httpd for the server.
* check-compose: restart fedmsg-hub on check-compose changesAdam Williamson2016-03-071-0/+2
|
* openqa_dispatcher: revise for fedmsg hub consumerAdam Williamson2016-03-071-0/+1
| | | | | ditch the old systemd consumer service, install the fedmsg consumer config file, add some fedmsg-hub reload notifications.
* check-compose: we don't have a service any moreAdam Williamson2016-03-041-3/+0
|
* trim check-compose package requirementsAdam Williamson2016-03-041-2/+1
|
* check-compose: switch to fedmsg-hub based fedmsg consumerAdam Williamson2016-03-042-16/+10
| | | | | | | | | I'm switching the misc. QA fedmsg consumers over to using fedmsg- hub, due to https://github.com/fedora-infra/fedmsg/issues/365 . So we need to adjust how we install check-compose, install a config file to enable the consumer, and also set up the fedmsg base and hub roles on the openqa server boxes (which do the check-compose job ATM).
* check-compose: 'make clean' before 'make'Adam Williamson2016-03-031-0/+6
| | | | | or else it doesn't do the make step, even if it would change something. irritating.
* drop some old cleanup bits now they've runAdam Williamson2016-03-031-8/+0
|
* check-compose: requires python-m2ext for message signature checkAdam Williamson2016-03-031-0/+1
|
* this goddamn timeAdam Williamson2016-03-031-1/+1
|
* check-compose: python2-fedmsg not python-fedmsgAdam Williamson2016-03-031-1/+1
| | | | godfuckingdamnit
* openqa_dispatcher and check-compose: package dep fixesAdam Williamson2016-03-031-0/+1
|
* check-compose: update to new fedmsg daemon-y check-composeAdam Williamson2016-03-031-6/+10
|
* check-compose: only send Postrelease report on errorAdam Williamson2016-01-191-0/+3
| | | | | | Cloud folks want this email sent only if there's some kind of problem (missing image or openQA failure), I've just added an option to check-compose to allow for that, enable it here.
* check-compose: enable the postrelease timerAdam Williamson2016-01-191-0/+1
|
* check-compose: send Postrelease emails to appropriate folksAdam Williamson2016-01-191-0/+4
| | | | | | | | | | This is for https://phab.qadevel.cloud.fedoraproject.org/T690 , it goes along with some changes to check-compose itself to allow reports for different milestones to have different config settings, which (if I didn't mess anything up) should result in those reports going to Mike McGrath and the cloud@ list, as requested, while Rawhide and Branched reports continue to go to test@ and devel@.
* check-compose: drop always_run from git stepsAdam Williamson2016-01-131-2/+0
| | | | | | as per the similar recent commit to openqa roles, this is not needed and breaks stuff (as the checkout is run during 'check' but the install step isn't, the updated code is never installed)
* Add some more always_run magic pixie dustKevin Fenzi2015-12-151-0/+3
|
* check-compose: set base URL for compose check reportsAdam Williamson2015-12-052-0/+13
|
* check-compose: damnit, more dashesAdam Williamson2015-12-041-6/+6
|
* check-compose: do a systemd daemon reload after installing unitsAdam Williamson2015-12-041-0/+4
|
* check-compose: apparently no dashes in variable names? WHATEVSAdam Williamson2015-12-042-14/+14
|
* check-compose: d'oh, template missing endifsAdam Williamson2015-12-041-0/+6
|
* check-compose: build before install and set prefixAdam Williamson2015-12-041-1/+7
|
* add a check-compose role and activate it on openqa serversAdam Williamson2015-12-042-0/+83
I just killed the old BOS openqa deployment, which sends out those 'compose check' emails, so I'm gonna go ahead and have this new openqa deployment start sending out those emails a little earlier than planned. This should result in both prod and staging openqa running a compose check each day, but only prod should actually send out an email report.