Hey there,
in this post, we would like to introduce you to a selection of our GitOps resources. The following list is ever evolving, so don’t miss out on coming back occasionally. For every resource we provide a dedicated topic which we will link here.
GitOps-Playground:
The GitOps-Playground is, as the name suggests, a playground with which you can try and test different GitOps solutions. Feel free to comment on our implementation, tell us more about yours or your ideas in implementing the GitOps workflow.
You can find the GitOps-Playground here:
GitOps-Build-Lib:
In our environment we try to re-use code as much as possible and so the GitOps-Build-Lib was born. It is being used in our GitOps-Playground which
leads to a strong reduction of code in the Jenkins-Pipelines. What do you think? Do you have suggestions on improving it? Let us know!
You can find the GitOps-Build-Lib here:
What is ”GitOps”?
An introductory piece to give you a broad understanding of this new technology. Feel free to give us feedback, be it good or bad ;). Constructive criticism is always welcome.
Read it here:
Automation assistants: GitOps tools in comparison
Even though the world of GitOps is pretty young, the landscape of current solutions might be overwhelming at first glance. This post gives you a brief summary of the most common solutions. Do you have any further questions?
Read it here:
Coding continuous delivery: CIOps VS. GitOps with Jenkins
Are you asking yourself if you want to switch from CIOps to GitOps?
Are you building new pipelines and want to know which of these are the right choice? Then don’t look further, we have the right literature for you. Any questions? Feel free to ask them here.
Read it here:
4 Likes