Continuous Delivery Foundation

Mentors: Student: Harshit Chopra

<p>This project idea proposes to implement two new credential bindings i.e. gitSshPrivateKey and gitUsernamePassword, that will contribute files and environment variables to sh, bat, and powershell steps so that they can use command line git to perform authenticated operations. Thus allowing Jenkins Pipeline and FreeStyle users to run authenticated git commands in sh, bat, and powershell in a pipeline job/freestyle project.</p>

Mentors: Student: Daniel Ko

<p>One of the best ways to learn Spinnaker is to use Spinnaker. This project is focused on generating (and destroying) temporary sandbox environments for new users to play around with, hosted by spinnaker.io.</p>

Mentors: Student: Akihiro Kiuchi

<p>In Jenkins, we have a Remoting module, which implements a communication layer in the Jenkins automation server. It’s being primarily used for controller ⇔ agent interaction. The purpose of this project is to develop software to support the monitoring and troubleshooting of the Remoting system. To achieve this purpose, we will collect telemetry data (metrics, traces, logs) of the Remoting module with OpenTelemetry and send the data to the OpenTelemetry Protocol endpoint. Which OpenTelemetry endpoint to use and how to visualize the data are up to users.</p>

Mentors: Student: Shruti Chaturvedi

<p>Enhance interoperability in the current Jenkins architecture by designing a plugin for Jenkins which emits and consumes CloudEvents. CloudEvents is an industry-adopted standard specification for describing event and event data (also referred to as Payload). This project enables Jenkins to produce CloudEvents (as a source) for common Jenkins events like a project build success/failure, which other tools (example Azure Event Grid) can consume. This project also enables Jenkins to be configured as a sink where external tools (example Amazon Kinesis) can send CloudEvents, and Jenkins can consume those events to perform a Jenkins action. Implementing this plugin in a workflow will give Jenkins users the ability to use and extend an event-driven Jenkins workflow to systems which use CloudEvents for defining their events.</p>

Mentors: Student: Aditya Srivastava

<p>The main idea behind the project is to build a plugin to <strong>automatically determine the next semantic version</strong> for a repository using the Conventional Commits (C.C) system. As the CI/CD world is moving more towards <strong>complete automation</strong> and <strong>minimal human interaction</strong>, the ability to fully automate a release, including the determination of the "next" release version becomes desirable. The proposed plugin does exactly that. Taking in various sources of input and git commit and tag history of the repository, it outputs the next semantic version or the next release version.</p>