https://docs.pipelinesascode.com/v0.38.0/docs/dev/ Recent content in Contributor Resources on Pipelines as Code Hugo en-us https://docs.pipelinesascode.com/v0.38.0/docs/dev/release-process/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.pipelinesascode.com/v0.38.0/docs/dev/release-process/ <h1 id="release-process-for-pipelines-as-code"> Release process for Pipelines-as-Code <a class="anchor" href="#release-process-for-pipelines-as-code">#</a> </h1> <ul> <li> <p>Clear out the PR needed to be merged.</p> </li> <li> <p>Wait that CI is connected.</p> </li> <li> <p>Verify PAC CI cluster is up.</p> </li> <li> <p>Verify that you have gpg signing <a href="https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification">setup</a> for your commits.</p> </li> <li> <p>Prepare to tag the release with a version, you need to choose between a major release/minor or patch release.</p> </li> <li> <p>If for example you choose to do the release 1.2.3 you tag it locally :</p> </li> </ul> <div class="highlight"><pre tabindex="0" style="color:#272822;background-color:#fafafa;-moz-tab-size:2;-o-tab-size:2;tab-size:2;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>git tag v1.2.3 </span></span></code></pre></div><ul> <li>And pushing it directly to the repo (you need access) :</li> </ul> <div class="highlight"><pre tabindex="0" style="color:#272822;background-color:#fafafa;-moz-tab-size:2;-o-tab-size:2;tab-size:2;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>% <span style="color:#111">NOTESTS</span><span style="color:#f92672">=</span>ci git push git@github.com:openshift-pipelines/pipelines-as-code refs/tags/1.2.3 </span></span></code></pre></div><ul> <li>When it started you can follow it on the pac cluster :</li> </ul> <p><code>tkn pr logs -n pipelines-as-code-ci -Lf</code></p>