<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Core on</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/</link><description>Recent content in Core on</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 30 Jul 2026 17:52:44 +0200</lastBuildDate><atom:link href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuration</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/configuration/</link><pubDate>Tue, 13 Oct 2020 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/configuration/</guid><description>&lt;div class="paragraph"&gt;
&lt;p&gt;Updatecli requires a configuration file, or &amp;#34;manifest&amp;#34;, which describes the update pipeline.
A manifest describes the &amp;#34;what&amp;#34;, the &amp;#34;when&amp;#34;, and the &amp;#34;where&amp;#34; of the update pipeline.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Source</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/source/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/source/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;source&amp;#34; stage retrieves information from a third &amp;#34;resource&amp;#34; like a file, or an API and then uses that information in later stages.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Condition</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/condition/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/condition/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;A &amp;#34;condition&amp;#34; stage defines whether to run the &lt;a href="../target"&gt;&amp;#34;Target&amp;#34; stage&lt;/a&gt; stage of a pipeline.
It runs a check (depending on the resource kind) that returns a boolean indicating its success (&lt;code&gt;true&lt;/code&gt;) or failure (&lt;code&gt;false&lt;/code&gt;).&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Target</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/target/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/target/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;target&amp;#34; stage applies the value retrieved by a &lt;a href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/source/"&gt;source&lt;/a&gt; to a &amp;#34;resource&amp;#34;, such as a file in a Git repository.
It is the only stage allowed to modify something, and it runs only once every &lt;a href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/condition/"&gt;condition&lt;/a&gt; succeeded.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Action</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/action/</link><pubDate>Fri, 11 Apr 2025 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/action/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;An Updatecli action defines what happens after a change is detected and validated. While Updatecli’s sources find changes (like a new version), and targets define where to apply them (like a file), actions describe what to do next, such as creating a pull request.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Scm</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/scm/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/scm/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;An scm configuration provides the git repository information used by a source, a condition, a target,
an &lt;a href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/action/"&gt;action&lt;/a&gt;, or &lt;a href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/autodiscovery/"&gt;autodiscovery&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;When an updatecli pipeline is triggered, the first thing updatecli does, is clone all referenced git repositories into a temporary directory.
Resources referencing that scm through their &lt;code&gt;scmid&lt;/code&gt; key then operate on the clone rather than on the
current working directory, and a target that changes a file there gets its change committed and pushed
to a branch named after the pipeline &lt;code&gt;pipelineid&lt;/code&gt;.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Transformer</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/transformer/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/transformer/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;transformers&amp;#34; parameter can be used by any stage definition as a &amp;#34;source&amp;#34;, &amp;#34;condition&amp;#34;, or &amp;#34;target&amp;#34;.
A &amp;#34;transformers&amp;#34; object contains a list of transformers. Each kind of transformer rules applies a string manipulation like adding or removing characters.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Version Filter</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/versionfilter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/versionfilter/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Most &lt;a href="https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/source/"&gt;sources&lt;/a&gt; do not return a single value: a Docker registry returns every
tag of an image, a GitHub repository every release, a package registry every published version.
The &lt;code&gt;versionfilter&lt;/code&gt; key decides which one of them the source actually returns.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Manifest Order</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/order/</link><pubDate>Wed, 15 Apr 2026 07:21:01 +0200</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/order/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Updatecli orders execution at two different levels:&lt;/p&gt;
&lt;/div&gt;
&lt;div class="ulist"&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;between manifests&lt;/strong&gt;, with the root keys &lt;code&gt;id&lt;/code&gt; and &lt;code&gt;dependson&lt;/code&gt;, described on this page&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;between the resources of one manifest&lt;/strong&gt;, with the resource key &lt;code&gt;dependson&lt;/code&gt;, described in &lt;a href="#_resource_ordering"&gt;Resource ordering&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description></item><item><title>Labels</title><link>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/label/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-3597--amazing-golick-2d0138.netlify.app/docs/core/label/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_overview"&gt;Overview&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;Pipeline labels are arbitrary key/value pairs attached to a pipeline manifest that allow you to categorize, organize, and filter pipelines during execution and reporting.&lt;/p&gt;
&lt;/div&gt;</description></item></channel></rss>