rename `automation` dir to be oriented with the std-ci system

Description

Hey,

please support the `.ovirtci` directory as a fallback to the `automation` directory.

In cases where multiple CI systems are used, it is heplful to have each's CI tool's configuration in a directory containing the vendor or so string.

See also the discussion here https://ovirt-jira.atlassian.net/browse/OVIRT-1047?focusedCommentId=27061&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-27061

Activity

Show:
Eyal Edri
August 29, 2017, 1:33 PM

Slightly changed from the original request, its not mandatory we'll call it '.ovirtci', but just something that wont be too generic as 'automation', but rather named after the std-ci framework.

So we'll need to find a name for it.

Barak Korren
September 28, 2017, 9:13 AM

Adding as a blocker for this because it tracks our current efforts to make a new STDCI configuration format where the use of the 'automation' dir can be avoided.

Daniel Belenky
February 4, 2018, 9:18 AM
Edited

As is done, [1] Adds support for different configurations to be used.
Currently supported names:

[1] https://gerrit.ovirt.org/c/87108/

Eyal Edri
June 10, 2018, 3:44 PM

this can probably be closed now that V2 supports multiple naming options

Barak Korren
June 10, 2018, 4:57 PM

STDCI V2 now allows full customization of where scripts and configuration files reside.

Assignee

Daniel Belenky

Reporter

Fabian Deutsch

Blocked By

None

Components

Priority

High
Configure