F25 Self Contained Change: Release Engineering Automation Workflow Engine

[Jan Kurik]

= Proposed Self Contained Change: Release Engineering Automation
Workflow Engine =
https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkfl...

Change owner(s):
* Adam Miller <maxamillion AT fedoraproject DOT org>


Centralized entry point, logging, and dash board for pre-defined
Automated Workflow tasks used by the Release Engineering team with
delegation and self-service tasks for members of various teams who
normally depend on Release Engineering for various tasks.


== Detailed Description ==
Currently Fedora Release Engineering Automation tasks are performed by
various scripts run on various machines within the Fedora
Infrastructure with no real centralized logging. Some of these are
automated by chron jobs and some run by hand by request of various
members within the Fedora Community, normally around Fedora Test Days.
Finding information about old tasks is not always the easiest of
things to do and the delegation of tasks is currently not available.
The goal here is to provide a solution that removes those barriers.

Workflows will be executed and potentially orchestrate actions between
multiple other systems or tools such as bodhi, pungi, and koji.
Fedmsgs will be emitted with information about the start and
completion of workflows along with metadata about them.

In the event of a compose, certain fedmsg output will be picked up by
taskotron and autocloud to perform various levels of testing.

(Change Wrangler note: as the section is quite complex, please check
the Change page to get more details)

== Scope ==
* Proposal owners shall have to:
- Determine what the "Engine" will be after evaluation and working
with the Fedora RelEng and Infrastructure teams for advisement.
- Deploy RelEng Automation Workflow Engine
--  Fully automated deployment in Fedora Infrastructure Ansible
- Document Workflow Automation
--  How workflows are created
--  How to run workflows
--  How new contributors can get started

* Release engineering
- Deploy the "Engine"

* Policies and guidelines
- Need to determine who can create/run workflows
- Define guidelines for writing workflows

(Change Wrangler note: as the Scope section is quite complex, please
check the Change page to get more details)
-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

[Adam Williamson]

On Fri, 2016-06-03 at 17:59 +0200, Jan Kurik wrote:
>  = Proposed Self Contained Change: Release Engineering Automation
>  Workflow Engine =
>  https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkfl... 

YAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Germano Massullo]

Il 03 giu 2016 18:48, "Adam Williamson" >
YAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY

LOL