/docs/08/Recent content in 8. Controlling Deployment Workflows on ArgoCD Basics TrainingHugoen-us/docs/08/tracking_deployment_strategies/Mon, 01 Jan 0001 00:00:00 +0000/docs/08/tracking_deployment_strategies/<p>If you are using ArgoCD with Git or Helm tools, ArgoCD gives you the availability to configure different tracking and deployment strategies.</p> <h2 id="helm">Helm</h2> <p>For Helm you can use Semver versions either to pin to a specific version or to track minor / patch changes.</p> <table> <thead> <tr> <th>Use Case</th> <th>How</th> <th>Examples</th> </tr> </thead> <tbody> <tr> <td>Pin to a version (e.g. in production)</td> <td>Use the version number</td> <td>1.2.0</td> </tr> <tr> <td>Track patches (e.g. in pre-production)</td> <td>Use a range</td> <td>1.2.* or &gt;=1.2.0 &lt;1.3.0</td> </tr> <tr> <td>Track minor releases (e.g. in QA)</td> <td>Use a range</td> <td>1.* or &gt;=1.0.0 &lt;2.0.0</td> </tr> <tr> <td>Use the latest (e.g. in local development)</td> <td>Use star range</td> <td>* or &gt;=0.0.0</td> </tr> </tbody> </table> <h2 id="git">Git</h2> <table> <thead> <tr> <th>Use Case</th> <th>How</th> <th>Notes</th> </tr> </thead> <tbody> <tr> <td>Pin to a version (e.g. in production)</td> <td>Either tag the commit with (e.g. v1.2.0) and use that tag, or using commit SHA.</td> <td>See commit and version pinning.</td> </tr> <tr> <td>Use the latest (e.g. in local development)</td> <td>Use HEAD or master (assuming master is your master branch).</td> <td>See HEAD / Branch Tracking</td> </tr> </tbody> </table> <h3 id="head--branch-tracking">Head / Branch Tracking</h3> <p>Either a branch name or a symbolic reference (like HEAD). For branches ArgoCD will take the latest commit of this branch. This method is often used in development environment where you want to apply the latest changes.</p>/docs/08/sync_windows/Mon, 01 Jan 0001 00:00:00 +0000/docs/08/sync_windows/<p>With Sync windows the user can define at which time applications can be synchronized automatically and manually by Argo CD. Allowed and forbidden time windows can be defined. Sync windows can be restricted to a subset of applications, clusters and namespaces and thus offer great flexibility.</p> <h2 id="task-821-create-application-and-project">Task 8.2.1: Create application and project</h2> <p>Now we want to create a new empty Argo CD project.</p> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>argocd proj create -s <span style="color:#4e9a06">&#34;*&#34;</span> -d <span style="color:#4e9a06">&#34;*,*&#34;</span> project-sync-windows-<span style="color:#000">$USER</span> </span></span><span style="display:flex;"><span>argocd app create sync-windows-<span style="color:#000">$USER</span> --repo https://github.com/acend/argocd-training-examples.git --path <span style="color:#4e9a06">&#39;example-app&#39;</span> --dest-server https://kubernetes.default.svc --dest-namespace <span style="color:#000">$USER</span> --project project-sync-windows-<span style="color:#000">$USER</span> </span></span><span style="display:flex;"><span>argocd app sync sync-windows-<span style="color:#000">$USER</span> </span></span></code></pre></div><p>You should see the following message after a successful sync</p>