Teams often spend days manually setting up Jenkins, pipelines and implementing CI/CD effectively.
To allivate this CloudBees has been investing resources into the proposed Jenkins subproject Jenkins X: An opinionated continuous delivery solution for development and delivery of modern cloud applications on Kubernetes. Jenkins X has taken a Kubernetes-first approach, using best-of-breed solutions from the Kubernetes ecosystem, melded with DevOps best practices.
The Jenkins X project has focused on getting the plumbing right around the Kubernetes-based continuous delivery platform and includes an easy-to-use CLI to interact with it. CloudBees has been experimenting with a prototype concept that is currently known as CloudBees for Kubernetes. This UI-based application focuses on visualising the activities, resources and deployments that form part of a continuous delivery journey of Kubernetes-based applications into production.
Since we are in a cloud native world cloud is used to store artifacts or state rather than local.
This is where our partner need our help to support Azure also as a first class citizen and make Jenkins a cloud native part of it.
We see Jenkins in a lot of our customer environments. The goal helps us upskill and gain deep knowledge on Jenkins internals, and improving cloud storage support on this common platform. While Jenkins and k8s are both very common in our customer environments this also improves our visibility as partner in open source product support.
It a planned to use one day for internal upskilling and get to know the product code. Then spending 2 day on extending or fixing customer use cases like Detect security vulnerabilities in your Docker images
- Since we are on a mission to enable our customers we are still looking for customers with heavy Jenkins usage participating and coding with us.
- Who is willing to help or mentor with Jenkins and Java?