Re: Suggestion: versioning the schema for Configuration as Code

2018-05-15 0:20 GMT+02:00 Liam Newman : > Nicolas, > > Moving things to a separate JEP makes sense is some cases but it doesn't > sound like the works here. The design choices that need to be made in > relation to credentials CasC will effect the design of the JEP-201.

Compatiblity problem between gradle-jpi-plugin:0.26.0 (latest) and gradle:<4.4

It report an exception `Unable to load class 'org.gradle.api.file.DirectoryProperty'` when I update the gradle plugin [gradle-jpi-plugin](https://github.com/jenkinsci/gradle-jpi-plugin) to version 0.26.0, which is the [latest

[GSoC] Code Coverage API Plugin project introduction

Hi, all My name is Shenyu Zheng, this year I am participating in Jenkins GSoC as a student. I will be working on the Code Coverage API Plugin. I am very excited that I can work with the Jenkins community on such an interesting project. For Code Coverage API Plugin, there are a lot of

Request Jenkins security team membership for Jeff Thompson

I’d like to request to join the Jenkins security team to help review and fix security changes and issues. I’m a software engineer at CloudBees and have begun contributing to Jenkins projects and plugins. In the past, I’ve worked on security issues for a variety of other projects or companies.

Re: Suggestion: versioning the schema for Configuration as Code

Nicolas, Moving things to a separate JEP makes sense is some cases but it doesn't sound like the works here. The design choices that need to be made in relation to credentials CasC will effect the design of the JEP-201. Many plugins could be done in later JEPs, but for concepts as key as

Re: Request to join security team

+1 —— Jeff Thompson Senior Software Engineer CloudBees.com Fort Collins, Colorado E: jeff.thomp...@cloudbees.com > On May 14, 2018, at 9:55 AM, Matt Sicker wrote: > > Hi, I'm interested in joining the security team. I'm a software engineer at > CloudBees who is

Re: Request to join security team

+1 > On May 14, 2018, at 11:55, Matt Sicker wrote: > > Hi, I'm interested in joining the security team. I'm a software engineer at > CloudBees who is working on some security-related epics. I've got 2FA enabled > on GitHub (username: jvz), signed the CLA, and am

Request to join security team

Hi, I'm interested in joining the security team. I'm a software engineer at CloudBees who is working on some security-related epics. I've got 2FA enabled on GitHub (username: jvz), signed the CLA, and am registered on Freenode (nick: musigma). My Jenkins community username is also jvz. As for

Re: Deprecating ruby-runtime

On Mon, May 14, 2018 at 10:04 AM, Daniel Beck wrote: > ruby-runtime has caused quite some work for core maintainers I have personally spent a fair amount of time trying to deal with it; for example, writing what seems to have been the first acceptance test exercising any

Re: Suggestion: versioning the schema for Configuration as Code

On Fri, May 11, 2018 at 5:44 PM, nicolas de loof wrote: > Secret is already supported based on jenkins-core registered stapler > converters. Yes; my point was only that due to the nature of secrets, JCasC needs to support keeping the actual values separate from the main

Deprecating ruby-runtime

ruby-runtime is a plugin that allows Jenkins plugins to be implemented in Ruby. It has quite a number of problems: * The source code situation is a mess, with two separate repositories. https://github.com/jenkinsci/ruby-runtime-plugin/pull/6#issuecomment-383842017