sort out jobs which didn't move to std ci

Description

http://pastebin.test.redhat.com/386625

The filtered list which doesn't include projects who doesn't need to move, which are using a 'rel-eng' kind of building..

http://pastebin.test.redhat.com/386628

Activity

Show:

Eyal Edri September 18, 2016 at 2:07 PM

no action for now,
the projects which are NOT part of standard CI are:

ebay-cors-filter_master
jasperreports-server
nsis-simple-service-plugin
ovirt-engine-extension-aaa-jdbc
ovirt-engine-extension-aaa-ldap
ovirt-engine-extension-aaa-misc
ovirt-engine-extension-logger-log4j
ovirt-engine-nodejs
ovirt-engine-nodejs-modules
ovirt-engine-wildfly-overlay10
ovirt-engine-wildfly10
ovirt-wgt
py2exe-py2.7
python-windows
pywin32-py2.7
qemu
slf4j
unboundid-ldapsdk
vcredist-x86

Each maintainer might decide to move it to standard CI in the future, for now it doesn't block any CI flow or job.

Former user August 24, 2016 at 10:54 AM
Edited

The following projects are still not in yaml:

  • mom

  • ovirt-engine-extension-aaa-ldap

  • ovirt-engine-extension-aaa-misc

  • ovirt-engine-extension-logger-log4j

  • ovirt-vmconsole

  • ovirt-reports (abandoned - no need to move to std-ci)

I've contacted the maintainers and sent them a link to the doc that explains how to add the projects to std-ci.

There are also other projects which are still using the old create-rpms jobs.

Eyal Edri August 21, 2016 at 2:50 PM

this might be duplicate, feel free to close.

Eyal Edri July 28, 2016 at 6:59 AM

we need updated list of projects which are not in STD CI, so we'll encourage maintainers to move.

Fixed

Details

Assignee

Reporter

Priority

Created June 23, 2016 at 8:09 AM
Updated September 29, 2016 at 8:48 AM
Resolved September 18, 2016 at 2:07 PM