<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog Posts on Pipelines as Code</title>
    <link>https://docs.pipelinesascode.com/v0.36.0/docs/blog/</link>
    <description>Recent content in Blog Posts on Pipelines as Code</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://docs.pipelinesascode.com/v0.36.0/docs/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenShift Pipelines 1.15 PAC release</title>
      <link>https://docs.pipelinesascode.com/v0.36.0/docs/blog/release-osp-1.15/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.pipelinesascode.com/v0.36.0/docs/blog/release-osp-1.15/</guid>
      <description>&lt;p&gt;OpenShift Pipelines 1.15 presents several new enhancements to Pipelines-as-Code. Below are the key updates.&lt;/p&gt;&#xA;&lt;h2 id=&#34;much-improved-gitops-commands&#34;&gt;&#xA;  Much improved GitOps Commands&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#much-improved-gitops-commands&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;These commands allow you to make quick comments on a pull request to restart a&#xA;PipelineRun through Pipelines-as-Code.&lt;/p&gt;&#xA;&lt;p&gt;Commonly used commands include &lt;code&gt;/test&lt;/code&gt; pipelinerun to rerun a specific&#xA;pipelinerun, or &lt;code&gt;/retest&lt;/code&gt; to rerun all PipelineRuns.&lt;/p&gt;&#xA;&lt;h3 id=&#34;trigger-pipelineruns-irrespective-of-annotations&#34;&gt;&#xA;  Trigger PipelineRuns Irrespective of Annotations&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#trigger-pipelineruns-irrespective-of-annotations&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;p&gt;Previously, to re-trigger PipelineRuns, they had to match specific annotations&#xA;such as &lt;code&gt;pipelinesascode.tekton.dev/on-event&lt;/code&gt; set to pull_request. Now, this&#xA;constraint is removed, allowing you to trigger any PipelineRuns with &lt;code&gt;/test&lt;/code&gt;&#xA;regardless of their annotation status. This is particularly useful if you need&#xA;to run a pipelinerun selectively before merging a PR, without it automatically&#xA;consuming resources with each update.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
