<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hands-Free Releasing on CSIT-DOCS</title>
    <link>https://csit.fd.io/cdocs/overview/csit/hfr/</link>
    <description>Recent content in Hands-Free Releasing on CSIT-DOCS</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://csit.fd.io/cdocs/overview/csit/hfr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Core</title>
      <link>https://csit.fd.io/cdocs/overview/csit/hfr/the_core/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://csit.fd.io/cdocs/overview/csit/hfr/the_core/</guid>
      <description>Managing the testing jobs # Main principles # Start a run only if there is a testbed available for it. a. No (or minimal amount of) runs waiting for a testbed. b. No waste of executors. Periodically monitor the state of runs. a. Optimise the utilisation of testbeds. b. Minimise the overall testing time. Accept the runs not started by HFR. a. E.g. periodical runs can run independently on runs managed by HFR.</description>
    </item>
    
    <item>
      <title>The Configuration</title>
      <link>https://csit.fd.io/cdocs/overview/csit/hfr/the_configuration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://csit.fd.io/cdocs/overview/csit/hfr/the_configuration/</guid>
      <description>The Configuration # The configuration is divided into two parts:
configuration of HFR system itself, configuration of the testing process which includes (not only): testbeds, testing runs, priorities, parameters of the testing runs, … The configurations are:
structured, human and machine readable, both configurations are stored in GitHub repository in YAML format. HFR Configuration # The application configuration is read from two sources:
environment configuration file. All listed parameters are mandatory if it is not marked &amp;ldquo;optional&amp;rdquo;.</description>
    </item>
    
    <item>
      <title>Operational Data</title>
      <link>https://csit.fd.io/cdocs/overview/csit/hfr/operational_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://csit.fd.io/cdocs/overview/csit/hfr/operational_data/</guid>
      <description>Operational Data # The operational data reflect the current status of HFR, all runs and testbeds managed by it. It is stored on the HFR executor.
The Structure # The operational data is represented by a list of items. Each item represents a run managed by the HFR. The length of this list is the number of runs managed by HFR.
[ Run( node=str(), conf=RunConf( workflow=str(), # The item &amp;#39;inputs&amp;#39; depends on the GHA workflow specification, # example is for the report workflow.</description>
    </item>
    
    <item>
      <title>Interface</title>
      <link>https://csit.fd.io/cdocs/overview/csit/hfr/interface/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://csit.fd.io/cdocs/overview/csit/hfr/interface/</guid>
      <description>Interface # Interface to GHA # Interface to GitHub Actions uses GHA REST API and implements methods to:
start a run, get the status of a run, cancel a run (normal or force). Interface to Testbeds # The HFR uses existing set of testbeds and communicates with them via ssh channel using bash commands. It implements methods to:
get the status of testbed(s) find an available testbed, unreserve a testbed.</description>
    </item>
    
  </channel>
</rss>
