<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci-Cd on Solo</title><link>https://solo.hiero.org/tags/ci-cd/</link><description>Recent content in Ci-Cd on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Solo CI Workflow</title><link>https://solo.hiero.org/docs/advanced-solo-setup/solo-ci-workflow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/solo-ci-workflow/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This guide walks you through integrating Solo into a GitHub Actions CI pipeline -
covering runner requirements, tool installation, and automated network deployment.
Each step installs dependencies directly in the workflow, since CI runners are
fresh environments with no pre-installed tools.&lt;/p&gt;
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;a class="td-heading-self-link" href="#prerequisites" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Before proceeding, ensure you have completed the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://solo.hiero.org/docs/simple-solo-setup/system-readiness/"&gt;&lt;strong&gt;System Readiness&lt;/strong&gt;&lt;/a&gt; — your local environment
meets all hardware and software requirements.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://solo.hiero.org/docs/simple-solo-setup/quickstart/"&gt;&lt;strong&gt;Quickstart&lt;/strong&gt;&lt;/a&gt; — you are familiar with the basic Solo
workflow and the &lt;code&gt;solo one-shot single deploy&lt;/code&gt; command.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This guide assumes you are integrating Solo into a GitHub Actions workflow
where each runner is a fresh environment. The steps below install all required
tools directly inside the workflow rather than relying on pre-installed
dependencies.&lt;/p&gt;</description></item></channel></rss>