<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Pipeline Timing on Project Hummingbird</title>
		<link>https://hummingbird-project.io/docs/background/tools/pipeline-timing/</link>
		<description>Recent content in Pipeline Timing on Project Hummingbird</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://hummingbird-project.io/docs/background/tools/pipeline-timing/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>RPM pipeline timing design</title>
				<link>https://hummingbird-project.io/docs/background/tools/pipeline-timing/design/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://hummingbird-project.io/docs/background/tools/pipeline-timing/design/</guid>
				<description>&lt;h2 id=&#34;problem&#34;&gt;Problem&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#problem&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;We lack a clear way to see where time is spent in the RPM build pipeline.&lt;/p&gt;&#xA;&lt;h2 id=&#34;background&#34;&gt;Background&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#background&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;References:&#xA;&lt;a href=&#34;https://redhat.atlassian.net/browse/HUM-5819&#34; target=&#34;_blank&#34;&gt;HUM-5819&lt;/a&gt; - Create a diagram that describes all&#xA;phases and steps of various pipelines from start to finish. Then review with team.&#xA;&lt;a href=&#34;https://redhat.atlassian.net/browse/HUM-5820&#34; target=&#34;_blank&#34;&gt;HUM-5820&lt;/a&gt; - Time breakdown from MR creation to&#xA;completion of Release pipeline.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;During the F44 rebuild, RPM builds had problems whose causes were not immediately clear. The sprint&#xA;retrospective and a later F44-specific retrospective created HUM-5819 and HUM-5820 to improve&#xA;visibility into pipeline behavior and time spent in each phase.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Pipeline timing implementation plan</title>
				<link>https://hummingbird-project.io/docs/background/tools/pipeline-timing/implementation-plan/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://hummingbird-project.io/docs/background/tools/pipeline-timing/implementation-plan/</guid>
				<description>&lt;h2 id=&#34;purpose&#34;&gt;Purpose&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#purpose&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://hummingbird-project.io/docs/background/tools/pipeline-timing/design/&#34;&gt;original RPM pipeline timing design&lt;/a&gt; records&#xA;the HUM-5820 design and remains unchanged. This implementation plan records the&#xA;HUM-10942 revisions to retain execution timing and lineage for both RPM and&#xA;container pipelines, not a permanent notification catalogue or permanent S3&#xA;references on reporting rows. Its execution-only requirements supersede the&#xA;original design&amp;rsquo;s archive-reference and RPM-only scope decisions.&lt;/p&gt;&#xA;&lt;p&gt;The Status events database remains the storage location, but &lt;code&gt;pipeline-timing&lt;/code&gt; is a separate&#xA;project, image, and worker with its own deployment lifecycle and resource quotas. Hummingbird Status&#xA;continues legacy ingestion; the GitLab and Kubernetes event forwarders remain independent&#xA;publishers. This service split follows &lt;a href=&#34;https://gitlab.com/redhat/hummingbird/tools/-/merge_requests/1261&#34; target=&#34;_blank&#34;&gt;HUM-7529 MR&#xA;1261&lt;/a&gt; review without changing the&#xA;event contracts or lineage model.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
