[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Discussed some thoughts on pre-release security verifications we might be able to enforce for plugins considered "essential" with Daniel Beck today. Including a minimum quality bar for essential plugins should definitely be a key criteria 23:54 @ we already have some automation for that -- InjectedTest takes care of XSS on recent baselines, configRoundTrip takes care of password fields used for plain text values. The problem is these are opt in (the latter) and often opted out (the former). 00:03 @ rtyler perhaps -- I got started with https://github.com/jenkins-infra/jenkins.io/blame/master/content/doc/developer/plugin-development/build-process.adoc#L29 but including it in content would have required too much yak shaving Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails f
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49806) Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49806 Describe criteria (JEP) for selecting plugins to include in Jenkins Essentials Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-02-28 19:55 Priority: Minor Reporter: R. Tyler Croy Some thoughts I have right now: Different plugins will be needed for different flavors, e.g. AWS flavor vs. Kubernetes (helm) package Current usage is not a sufficient metric. E.g. Blue Ocean is a better way for a lot of new developers to use Jenkins, but it's not yet hugely adopted. As a heavy user of Jenkins, rather than developer, I want to exercise some editorial control. Add Comment
