Jenkins / Cloud Native SIG

Jenkins Open Telemetry plugins for Jenkins controllers and agents were a great start. Let’s discuss what we can do next to provide a great observability experience for Jenkins users in the CI/CD space, including tracing, metrics and logging parts.

Meeting notes: https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.9zkqotza30hg

Tekton Client Plugin has been a great start for Jenkins and Tekton integration. But Tekton is just a Pipeline step at the moment. What if we make the Jenkins Pipeline orchestrator part (Multibranch, Jenkins UI/reporting, ) universal and allow plugging in multiple Pipeline engines, including [Jenkins Pipeline with and without Sandbox, Tekton, Jenkinsfile Runner, and more]?

Meeting notes: https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.rbvy02o8js5h

Let’s review the current Jenkinsfile Runner status. How is the project doing? What are the obstacles and missing features? What is the roadmap towards the 1.0 release?

Jenkinsfile Runner: https://github.com/jenkinsci/jenkinsfile-runner

Meeting notes: https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.ywqy0v70eb25

No description provided.

We focused this Cloud Native SIG meeting on the CloudEvents plugin for Jenkins and Shruti Chaturvedi's GSoC work.

Mauricio Salantino spoke about his work on the CDF SIG Events Protocol Proof of Concept, https://github.com/cdfoundation/sig-events/blob/main/poc/README.md, with further discussion on the CloudEvents plugin.

Discussion on architectural choices for the plugin and a decision to start attending the CDF Event SIG 😊

Discussion on architecture, including consideration of Knative eventing architecture, especially its use of brokers. Lots of discussion on the CDF SIG Events Protocol Proof of Concept: https://github.com/cdfoundation/sig-events/blob/main/poc/README.md

Super interesting work! ☀️

We start by discussing IBM's docs on Configuring Jenkins as an event source: https://www.ibm.com/docs/en/cem?topic=integrations-jenkins

Then Shruti demos her latest work. And we discuss questions on using Jenkins as a sink and the scope of Jenkins actions.

The First Coding Phase has completed! This week will be an evaluation week. CDF GSoC participants are invited to present their work next week.

Shruti demos her latest work with discussion and feedback. ☀️

Shruti raised questions on ordering and/or locking of event order when have a larger system of events. One example would be if a build has started, but an event is received which means the build should stop, how is this handled?
Vibhav: these questions are great and part of a larger discussion on how to handle events in event based systems -- next week the Events SIG is meeting and it would be fantastic to raise these questions there and discuss further.

Shruti Chaturvedi demos her latest work, discussion follows and we wrap with next steps for the week ahead.

Second week of GSoC coding phase!
Shruti Chaturvedi has pushed her implementation of a CloudEvents plugin for Jenkins here: https://github.com/jenkinsci/cloudevents-plugin

During this session we reviewed her work, especially from the point of view of a user -- what features do they need? how should this be configured in the Jenkins UI?

At today's third community bonding meeting for GSoC CloudEvents plugin, we discussed various plugins that are listening to and capturing events in Jenkins pipelines.

First week of GSoC coding phase! Shruti demoed an initial implementation of CloudEvents plugin for Jenkins.

Awesome work already! 👑

This is the second community bonding meeting for GSoC CloudEvents plugin and already Shruti is doing impressive exploratory work!

Note: the decision to record the meeting was taken about 10 minutes in. Thus, the recording starts just as Shruti shows her week's exploratory work and we map out next steps.

GSoC CloudEvents plugin meeting notes: https://docs.google.com/document/d/11uMgE29StGLZEeOTteRXWIOpohBFk9ztwj1JeiUv9-U/edit#

Wise people say that “running Jenkins in a cloud environment is not a trivial task”. Find out how we aim to simplify that, using the Jenkins Operator for Kubernetes.

The trend to move infrastructure to cloud is undeniable. Jenkins has been of great help with building applications for countless developers for over a decade now, but it does have its limitations. Running it in a cloud environment is nothing but a trivial task. See how we can leverage the new and exciting technologies such as Kubernetes and Operator SDK to overcome the shortcomings. As a result achieve truly scalable and robust Jenkins in the cloud using the Jenkins Operator.

References:

- Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/278322004/
- GitHub repository: https://github.com/jenkinsci/kubernetes-operator
- Website: https://jenkinsci.github.io/kubernetes-operator/
- Roadmap: https://github.com/jenkinsci/kubernetes-operator/blob/master/ROADMAP.md

Speakers:

Mateusz Korus - a DevOps Engineer at VirtusLab with experience working with high-traffic cloud infrastructure. Enthusiastic about reactive technologies and the observer pattern. Tea enjoyer.

Piotr Ryba - a DevOps Engineer at VirtusLab, working on the Jenkins Operator project. During his professional work, he wore many hats ranging from Software Development to IT Operations. Experienced in programming mobile apps and microservice applications.

Presentation of Tekton Client Plugin here:
This SIG meeting took place 2 hours after and was a natural follow on discussion, including:
Future use of Tekton Client plugin with CloudEvents plugin
Improving debugging of Tekton Client plugin

Recording of the online Meetup on May 14, 2021. Presenters: Vibhav Bobade, James Strachan, Gareth Evans.

Kubernetes has become the staple for cloud native infrastructure today. With the rise of the microservice architecture and focus on container based serverless solutions, CI/CD solutions also have to adhere to what works best on Kubernetes.

Tekton is a Pipeline engine which checks all the boxes for a performant Cloud Native CI/CD solution. It provides users the ability to create composable pipelines which run on serverless workloads in Kubernetes. And now it is possible to use Tekton itself via Jenkins. With the Tekton Client Plugin, the user would be able to manage Tekton resources from their Jenkins instance and run Tekton Pipelines in the cloud. In this meetup we will discuss and demo how one can configure the Tekton Client Plugin and use it to deploy to Kubernetes in an efficient and Cloud Native fashion.

References:
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/278067201/
* Slides: https://docs.google.com/presentation/d/1voA1RR2U74GG0rzd4BGruslWgUmIZWR69n8mDqo2POk/edit?usp=sharing
* Plugin repo: https://github.com/jenkinsci/tekton-client-plugin
* Tekton: https://tekton.dev/
* Blogpost by James Strachan: https://cd.foundation/blog/2020/11/05/bridging-the-gap-with-tekton-client-plugin-for-jenkins/

Join the Cloud Native SIG channels to meet presenters and to ask any questions! https://www.jenkins.io/sigs/cloud-native/

No description provided.

No description provided.

Excellent discussion on CloudEvents! And the proposed Jenkins GSoC project idea of CloudEvents plugin. :)

No description provided.

No description provided.

GSoC 2021 CloudEvents plugin proposal by Vibhav Bobade https://github.com/jenkins-infra/jenkins.io/pull/4079.

No description provided.

Jenkins Cloud-Native SIG Meeting for 20201030

Presentation by Sumit Sarin, a GSoC 2020 student in the Jenkins project. File fingerprinting is a way to track which version of a file is being used by a job/build, making dependency tracking easy. The fingerprint engine of Jenkins can track usages of artifacts, credentials, files, etc. within the system. It does this by maintaining a local XML-based database. This leads to dependence on the physical disk of the Jenkins master. This project involved extending Jenkins core to support storing of fingerprints in an external storage, along with two reference implementations, backed by Redis and PostgreSQL respectively. Various functionalities like migration and cleanup were developed and released. Users can now use these plugins to externalize the storage of their fingerprints. This project was one step forward in developing a cloud native Jenkins.

Talk abstract: This presentation will start with a brief introduction about the fingerprinting engine in Jenkins and its use case. Then we will discuss the motivation behind externalizing these fingerprints. We will discuss the external fingerprint storage API built during the course of the project, and what features it allows the plugin developers to use. Then we will talk about the two reference implementations built by us during the project, backed by Redis and PostgreSQL. We will discuss fingerprint cleanup and migration strategies. A demo will be presented which will show the working of the plugins and their functionality in action. We will conclude the presentation with what potential future areas of improvement can be for this project where the community is more than welcome to contribute. And lastly a short Q&A with the developers behind this project.

References:

* Project page: https://www.jenkins.io/projects/gsoc/2020/projects/external-fingerprint-storage/
* Redis Fingerprint Storage Plugin: https://github.com/jenkinsci/redis-fingerprint-storage-plugin/
* PostgreSQL Fingerprint Storage Plugin: https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin
* JEP: https://github.com/jenkinsci/jep/tree/master/jep/226

Openshift has been making Jenkins available to it’s users as a primary CI/CD tool for a few years. Our users and customers are happy with it because it seamlessly integrates with the Openshift ecosystem. This talk will showcase the Jenkins Operator on Openshift. The Operator allows users to manage and use their Openshift supported Jenkins instances. We are excited to share new features that have been added to the Operator since our last Jenkins Online Meetup on the Openshift Operator for Jenkins.

References:
* Slides: https://docs.google.com/presentation/d/1As3eMYEiyBsEILfpvEMjpP1s-pJ0OeyVAuPZtXrjAGA/edit?usp=sharing
* https://github.com/jenkinsci/kubernetes-operator
* Jenkins Operator for RedHat - https://github.com/redhat-developer/jenkins-operator
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/271690719/

About the speaker: I work at Red Hat as a Software Engineer in the Jenkins Team. I maintain Openshift specific Jenkins plugins with my team and contribute to Tekton and Helm on the side. In my free time, I play guitar, do programmatic art using processing or go for a run.

Presentation of the External Fingerprint storage by Sumit Sarin, a GSoC 2020 student in the Jenkins organization. Sumit will itroduce the project and demo the current prototype of the external fingerprint storage, powered by Redis. Then we will discuss the architecture and potential use-cases for the Jenkins users.

References:

* Slides: https://docs.google.com/presentation/d/1hrdOYKXBWyQG-k53KUe6zFXJ3KWEK4t7smdtpNtp1Wo/edit?usp=sharing
* Project page: https://www.jenkins.io/projects/gsoc/2020/projects/external-fingerprint-storage/
* Plugin prototype: https://github.com/jenkinsci/redis-fingerprint-storage-plugin
* Jenkins Core patch: https://github.com/jenkinsci/jenkins/pull/4731
* Jenkins Enhancement Proposal draft: https://github.com/jenkinsci/jep/pull/289

We are restarting the Cloud Native special interest group in the Jenkins project. At this meeting we discussed the framework for Cloud Native SIG 2.0: topics of interest, founding projects and next steps. We also had a discussion about Jenkins Operator for Kubernetes and External Fingerprint Storage.

* Full agenda and meeting notes: https://docs.google.com/document/d/13zeaKgtud5jZ5RqZEh1lrwjDXJRm7j31scPymlrMpfo/edit#heading=h.o039rac74cyu
* Discussion in the mailing list: https://groups.google.com/forum/#!topic/jenkinsci-dev/nuOedyIwfyw
* Chat for discussion: https://gitter.im/jenkinsci/cloud-native-sig