<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Run Prow integration tests on Prow</title>
    <link>https://deploy-preview-674--k8s-prow.netlify.app/docs/test/integration/</link>
    <description>Recent content in Run Prow integration tests on Prow</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://deploy-preview-674--k8s-prow.netlify.app/docs/test/integration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fake Git Server (FGS)</title>
      <link>https://deploy-preview-674--k8s-prow.netlify.app/docs/test/integration/fakegitserver/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-674--k8s-prow.netlify.app/docs/test/integration/fakegitserver/</guid>
      <description>&lt;p&gt;FGS is actually not a fake at all. It is a real web server that serves real Git&#xA;repositories them over HTTP. FGS wraps around the vanilla &lt;code&gt;git http-backend&lt;/code&gt;&#xA;subcommand that comes with Git, calling it as a CGI executable. It supports both&#xA;read (e.g., &lt;code&gt;git clone&lt;/code&gt;, &lt;code&gt;git fetch&lt;/code&gt;) and write (e.g., &lt;code&gt;git push&lt;/code&gt;) operations&#xA;against it.&lt;/p&gt;&#xA;&lt;p&gt;FGS is used for integration tests. See &lt;code&gt;TestClonerefs&lt;/code&gt; for an example.&lt;/p&gt;&#xA;&lt;h2 id=&#34;usage-in-integration-testing&#34;&gt;Usage in Integration Testing&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;fakegitserver.go&lt;/code&gt; file is built automatically by &lt;code&gt;hack/prowimagebuilder&lt;/code&gt;,&#xA;and we deploy it to the KIND cluster. Inside the cluster, it accepts web traffic&#xA;at the endpoint &lt;code&gt;http://fakegitserver.default&lt;/code&gt; (&lt;code&gt;http://localhost/fakegitserver&lt;/code&gt;&#xA;from outside of the KIND cluster).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
