/docs/contribution_guidelines/Recent content in Contribution Guidelines on JobsetHugoen/docs/contribution_guidelines/development/Mon, 01 Jan 0001 00:00:00 +0000/docs/contribution_guidelines/development/<h2 id="dependencies">Dependencies</h2> <ul> <li><code>go&gt;=1.24.0</code></li> <li><code>make</code></li> <li><code>kubectl</code></li> <li><code>git</code></li> <li><code>docker</code></li> <li>Kubernetes cluster running one of the last 3 Kubernetes minor versions <ul> <li><a href="https://kind.sigs.k8s.io/">kind</a> allows you to run a local Kubernetes cluster using Docker containers</li> </ul> </li> </ul> <h2 id="building-and-deploying-jobset-from-source">Building and deploying JobSet from source</h2> <h3 id="building-the-image">Building the image</h3> <p>See <a href="https://github.com/kubernetes-sigs/jobset/blob/main/Makefile"><code>Makefile</code></a> targets for more information. In particular:</p> <ul> <li><code>make image-build</code>: Builds a JobSet image locally</li> <li><code>make image-push</code>: Builds a JobSet image locally AND pushes it to the registry</li> </ul> <p>The <code>make image-push</code> hook will attempt to push the built image to the public <code>us-central1-docker.pkg.dev/k8s-staging-images/jobset</code> registry with an image tag determined by <code>git describe</code>. It is recommended to set your own <code>GIT_TAG</code> and <code>IMAGE_REGISTRY</code> environment variables to ensure that your latest changes are pushed to an image registry your cluster can access.</p>