<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>What is a Spinnaker Artifact? on Spinnaker</title>
		<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/</link>
		<description>Recent content in What is a Spinnaker Artifact? on Spinnaker</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Artifacts from Build Triggers</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/from-build-triggers/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/from-build-triggers/</guid>
				<description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;When an external CI system triggers a pipeline, Spinnaker can use the CI build information to&#xA;inject relevant artifacts into the pipeline. The instructions here assume that you have&#xA;&#xA;&lt;a href=&#34;https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/ci/&#34;&gt;set up a CI system&lt;/a&gt;&#xA; and are familiar with using&#xA;&#xA;&lt;a href=&#34;https://deploy-preview-637--spinnaker-io.netlify.app/docs/guides/user/pipeline/expressions/#property-files&#34;&gt;property files&lt;/a&gt;&#xA; to pass variables from&#xA;CI builds to Spinnaker pipelines.&lt;/p&gt;&#xA;&lt;p&gt;The extraction of artifacts from the build information is done via a Jinja template; the&#xA;template uses the trigger as context and outputs a list of artifacts to inject into the&#xA;pipeline. Spinnaker provides a set of &#xA;&lt;a href=&#34;#supplied-templates&#34;&gt;standard templates&lt;/a&gt;&#xA; to use for&#xA;artifact extraction, which users can augment with custom templates.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Artifacts In App Engine</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-appengine/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-appengine/</guid>
				<description>&lt;p&gt;Artifacts can be used for the following in the Google App Engine provider:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;They can be used to reference a GCS bucket that contains source code to be deployed on Google App Engine.&lt;/li&gt;&#xA;&lt;li&gt;They can be used to reference a docker image stored in Google Container Registry to be deployed on App Engine Flex.&lt;/li&gt;&#xA;&lt;li&gt;They can be used to reference config files (such as app.yaml) to be used during deployment to App Engine.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h2 id=&#34;artifacts-referencing-source-code-from-gcs&#34;&gt;Artifacts referencing source code from GCS&lt;/h2&gt;&#xA;&lt;p&gt;To use an artifact to reference source code that is stored in a GCS bucket, use the &amp;ldquo;GCS&amp;rdquo; Source Type&#xA;when configuring a Server Group.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Artifacts In Cloud Foundry</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-cloud-foundry/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-cloud-foundry/</guid>
				<description>&lt;h2 id=&#34;artifacts-referencing-app-manifest&#34;&gt;Artifacts referencing app manifest&lt;/h2&gt;&#xA;&lt;p&gt;To use an artifact to reference a manifest file (such as a manifest stored in a GitHub repository), choose &amp;ldquo;Artifact from execution context&amp;rdquo; in the Application section of the &amp;ldquo;Configure Deployment Cluster&amp;rdquo; screen, and configure the artifact details.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-cloud-foundry/cf-manifest-artifact-github.png&#34;&#xA;&#x9;&#x9;&#x9;alt=&#34;In a Deploy stage, choose a GitHub file artifact as the manifest source for a server group.&#34;&gt;&lt;figcaption&gt;&#xA;&#x9;&#x9;&#x9;&lt;p&gt;In a Deploy stage, choose a GitHub file artifact as the manifest source for a server group.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Artifacts In Kubernetes</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-kubernetes/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-kubernetes/</guid>
				<description>&lt;h2 id=&#34;manifests-as-artifacts&#34;&gt;Manifests as artifacts&lt;/h2&gt;&#xA;&lt;p&gt;There are two ways to deploy a manifest:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The manifest is supplied statically to a pipeline as text&lt;/li&gt;&#xA;&lt;li&gt;The manifest is supplied as an artifact&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The image below shows a deploy stage that deploys a manifest stored in a GCS bucket:&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://deploy-preview-637--spinnaker-io.netlify.app/docs/reference/artifacts/in-kubernetes/manifest-artifact.png&#34;&#xA;&#x9;&#x9;&#x9;alt=&#34;Depending on how this pipeline is configured, it will only run when the referenced file in GCS is modified.&#34;&gt;&lt;figcaption&gt;&#xA;&#x9;&#x9;&#x9;&lt;p&gt;Depending on how this pipeline is configured, it will only run when the referenced file in GCS is modified.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
