https://deploy-preview-2810--amazing-golick-2d0138.netlify.app/docs/automate/Recent content in Automate onHugo -- gohugo.ioen-USSat, 09 Jan 2021 08:48:45 +0000https://deploy-preview-2810--amazing-golick-2d0138.netlify.app/docs/automate/jenkins/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2810--amazing-golick-2d0138.netlify.app/docs/automate/jenkins/Description Updatecli is most effective when executed regularly and automatically. Example The current example is inspired by the repository jenkins-infra/charts. Requirement We assume using Jenkins with agent running from kubernetes using the kubernetes-plugin. We assume having access to credentials needed by your updatecli configurations which is "updatecli-github-token" in this case. The Jenkins agent uses the updatecli docker image to execute updatecli every 30 minutes. It applies the configurations found under the directory ".https://deploy-preview-2810--amazing-golick-2d0138.netlify.app/docs/automate/github_action/Sat, 09 Jan 2021 15:21:01 +0200https://deploy-preview-2810--amazing-golick-2d0138.netlify.app/docs/automate/github_action/Description Updatecli is most effective when executed regularly and automatically. So, lets see how to use updatecli in a GitHub Action. Credentials Updatecli requires a token to interact with the GitHub API. It can be done using different approaches. GITHUB_TOKEN The easiest one is the GITHUB_TOKEN which comes with two major limitations: For security reason, GitHub prevents to trigger GitHub action workflow from pullrequest created with a GITHUB_TOKEN, more information here.