Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

Hello Abhishek, I forgot to mention that we have office hours and all students are invited to participate and ask questions. See https://jenkins.io/projects/gsoc/#office-hours for specific times. Martin On Friday, March 16, 2018 at 8:55:52 PM UTC-4, martinda wrote: > > On Friday, March 16,

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

I forgot to mention that we have office hours and all students are invited to participate and ask questions about GSoC. See https://jenkins.io/projects/gsoc/#office-hours for the times. Martin On Friday, March 16, 2018 at 9:50:28 PM UTC-4, martinda wrote: > > Hello Vineeth, > > Thank you for

Re: [GSOC 2018] EDA Plugin : Developing a Jenkins Plugin for one of the EDA tools viz FuseSOC

Hi Lakhan, Thank you for your interest in the GSoC project on EDA plugin for Jenkins. There are many things a Jenkins EDA plugin can do. It can run the EDA tool, but that is rather trivial as anyone can shell out and call the tool from the command line. But what get more interesting is

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

Hello Vineeth, Thank you for your interest. We have some student information, but it looks like you have already read it: https://jenkins.io/projects/gsoc/students/ If you find something is missing please let us know. If you have already studied the external workspace manager code base and

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

On Friday, March 16, 2018 at 11:17:02 AM UTC-4, Jesse Glick wrote: > > you are proposing some YAML > format—easily handled by an existing pair of extension points in > `workflow-multibranch`. I have discussed this is another thread. > Hi Jesse, I could be wrong but I have the impression that

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

On Friday, March 16, 2018 at 5:39:09 PM UTC-4, Abhishek Gautam wrote: > > > *@martinda * > While my research I came across something called EnvironmentContributor in > Jenkins. Do you think that we can use this to pass required variables to > the build processes? > Hi Abhishek, I have never

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

It’s a normal step - what I’m talking about is counting Pipelines containing one or more script blocks, I.e., what percentage of total Declarative Pipelines use script blocks, which I think is a more useful metric than just how many script block invocations there are. A. On Fri, Mar 16, 2018 at

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

Hello Everyone, Thank you for the clarifications. Oleg Nenashev and James Nord thank you for the recommendation of *"Snake YAML".* *@martinda * While my research I came across something called EnvironmentContributor in Jenkins. Do you think that we can use this to pass required variables to

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

(replies inline) On Fri, 16 Mar 2018, Andrew Bayer wrote: > If we???re going to be tracking step invocations anyway, it???d be interesting > to count the number of Declarative Pipelines with a script block, maybe? I kind of assumed that if we were incrementing a counter on step invocations that

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

(replies inline) On Fri, 16 Mar 2018, Daniel Beck wrote: > > > On 16. Mar 2018, at 21:28, R. Tyler Croy wrote: > > > > * What are other metrics which would positively impact the development of > > Jenkins? > > Assuming the Essentials setup allows for whitelisting

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

I think it would be interesting to record some metrics around the complexity of Pipelines, such as cyclomatic complexity and number of lines in the Jenkinsfile. If shared libraries are used record the complexity and size of those. Also the size of the strings passed to external scripting steps

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

On Fri, Mar 16, 2018 at 4:28 PM, R. Tyler Croy wrote: >* distinct built-in step invocations (i.e. not counting Global Variable > invocations) Careful with metasteps: `step` and `wrap` should count their `delegate`s, so we count individual plugins contributing

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

On Fri, Mar 16, 2018 at 4:20 PM, Baptiste Mathus wrote: > yes, users should still backup, JENKINS-49406 is *not* a backup system True, though users will try to treat it as one. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

> On 16. Mar 2018, at 21:28, R. Tyler Croy wrote: > > * What are other metrics which would positively impact the development of > Jenkins? Assuming the Essentials setup allows for whitelisting pipeline methods, knowing which methods are whitelisted (or got rejected on

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

If we’re going to be tracking step invocations anyway, it’d be interesting to count the number of Declarative Pipelines with a script block, maybe? A. On Fri, Mar 16, 2018 at 4:28 PM R. Tyler Croy wrote: > The successful adoption and iterative improvement of Jenkins

[Essentials] Collecting usage telemetry from Jenkins Pipeline

The successful adoption and iterative improvement of Jenkins Essentials [0] is heavily contingent on a spectrum of automated feedback which I've been referring to as "telemetry" in many of the design documents. I wanted to start discussing the prospect of collecting anonymized Pipeline usage

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

@Jesse The alternative I had considered too was to just have multiple volumes. But I agree having only one is also more inlined with Essentials philosophy, having only one volume to actually backup (because yes, users should still backup, JENKINS-49406 is *not* a backup system) is simpler. @James

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

I am a newbie in open source community but i feel i am capable enough to understand and give back to community my best. I am interested in working with "CLOUD FEATURES FOR EXTERNAL WORKSPACE MANAGER PLUGIN. " I spent decent time on understanding project and would like to look into it more

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

On Thu, Mar 15, 2018 at 12:27 PM, R. Tyler Croy wrote: > I > assume that it "just works" and there's no quality concerns we should have > from > a non-standard placement of data on disk? Any obvious problems would have been reported long ago. (I remember some fixes

Re: Multibranch event listener for Github PR labels

On Fri, Mar 16, 2018 at 11:21 AM, Steven F wrote: > GHBS's > PullRequest event returns a null revision in case of a PR merge I suppose you are referring to

Re: Multibranch event listener for Github PR labels

On Friday, March 16, 2018 at 3:05:30 PM UTC, Jesse Glick wrote: > > It is important. When a PR branch project is built, `checkout scm` and > related features will select a particular commit from the PR (not > always the most recent), and may additionally merge it against a > particular commit

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

On Thu, Mar 15, 2018 at 10:22 PM, martinda wrote: > there there is another model which is to have a job that handles all the pull > requests of a git repo to a given branch. For example say there is a git > repository called jupiter/juno.git (jupiter is the name of

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

On Wed, Mar 14, 2018 at 1:55 PM, R. Tyler Croy wrote: > core and plugin upgrades can result in > modification of config.xml and other object-serialized-files on disk when an > upgrade occurs. Does happen, but rarely. In most cases, format changes take effect on disk only

Re: Multibranch event listener for Github PR labels

On Thu, Mar 15, 2018 at 4:44 AM, Steven F wrote: > I was unable to return a PullRequestSCMRevision for > the PR head because its constructor is package private. Then, I couldn't > tell if that was important because I couldn't trace where these returned > heads are used in

Re: first draft of a new JEP: Jenkins X: Jenkins for Kubernetes CD

sounds like a great idea! What kind of times would suit folks? On 15 March 2018 at 22:35, Michael Neale wrote: > Nice description! > > Given the disparate timezones of everyone involved, would it make sense to > have a few office hour type things? (not sure if there is

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

On Friday, March 16, 2018 at 10:12:33 AM UTC, Oleg Nenashev wrote: > > > We just need to get input from YAML file and do things according to that. >> >> There is a java lib available to parse YAML file: >> https://github.com/FasterXML/jackson-dataformats-text/tree/master/yaml >> > > According to

Re: Valgrind plugin maintainer out of action

Thanks for the update! If you are interested in co-maintaining the plugin, feel free to reach out to the maintainer. Usually the plugins need much more love than a particular person can dedicate, and having multiple maintainers/contributors could improve the plugin's health a lot. BR, Oleg On

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

Hi Abhishek, +1 to what you say. Any comments about the project proposal will be appreciated. Actually we expect students to make their own proposals, so do not consider the project idea description as a specification. We just need to get input from YAML file and do things according to that. >