Re: Account Setup

> On 18. Aug 2017, at 19:28, Antonio Dorado wrote: > > was prompted to post my request on here Wrong mailing list. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Jelly server side methods

Hi, I know Jenkins provides some pre-defined buttons to call server side methods. I was wondering if there's a way to do this with other elements. My plan is to have clickable build badges that do server side things including kicking off a build. I know I can post to a URL to trigger a build

Re: Plugin idea: publish the analysis result (reading from the jxlint xml format)

You don’t need to create a new plugin. What you need is an XML parser for the warnings plugin (which uses analysis-core). In [1] you find some hints on how to create your own parser. You can also look at some other XML parsers in the parsers package to see what actually needs to be done. If

Account Setup

Hello, I was trying to setup my account at Jenkins.io (https://accounts.jenkins.io/), and was prompted to post my request on here. My name is Anthony Dorado. My email address I signed up with is: antonio@gmail.com I'm not sure if i'm supposed to post my complete email address here.

Re: Global Pipeline Libraries support for p4-plugin

On Fri, Aug 18, 2017 at 12:28 PM, Paul Allen wrote: > I can't find any 2.0 methods in the documentation link > you sent - is this out-of-date? Apparently. I do not know what process generated this Javadoc. You can file a JIRA ticket in the INFRA project. > The

Re: Global Pipeline Libraries support for p4-plugin

Thank you :-) I had implemented SCMSource for MultiBranch, but only the retrieve method for observer (2.0). I can't find any 2.0 methods in the documentation link you sent - is this out-of-date? Think I found the method in the source... /** * SPI: Looks up a specific revision based on some

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Hey Jesse, that's absolutely fantastic feedback :-) I believe we can close Phase #2 and #3 and have it finalised and announced officially at the Jenkins World Summit in SFO !! > On 18 Aug 2017, at 17:04, Jesse Glick wrote: > > On Fri, Aug 18, 2017 at 11:52 AM, Luca

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Hi Jesse, thanks for the feedback, that's what I needed as guidance for finalising the plugin. P.S. Would you have time at Jenkins World 2017 to pop up at the GerritForge booth and have a face-to-face chat on the plugins' evolutions? > On 18 Aug 2017, at 16:39, Jesse Glick

Re: Global Pipeline Libraries support for p4-plugin

On Fri, Aug 18, 2017 at 11:50 AM, pallen wrote: > Please can you point me to where I would need to implement support for > 'Global Pipeline Libraries' for the p4-plugin. Currently only 'Retrieval > method' of 'Legacy SCM' is available.

Global Pipeline Libraries support for p4-plugin

Hi Guys, Please can you point me to where I would need to implement support for 'Global Pipeline Libraries' for the p4-plugin. Currently only 'Retrieval method' of 'Legacy SCM' is available. If it was part of the scm-api implementation then I must have overlooked the extension point. Kind

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

On Fri, Aug 18, 2017 at 5:04 AM, Luca Milanesio wrote: > gerrit.withServer("http://gerrit:8080/;, "gerrit") { I would strongly advise you *not* to use the “DSL style” (`workflow-cps` dependency). Define `Step`s and leave it at that. >

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Sure, will do it now. Luca. On Friday, August 18, 2017 at 4:29:59 PM UTC+1, Jesse Glick wrote: > > Please comment on https://issues.jenkins-ci.org/browse/JENKINS-38046 > letting watchers know that this is finally available. > -- You received this message because you are subscribed to the

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Please comment on https://issues.jenkins-ci.org/browse/JENKINS-38046 letting watchers know that this is finally available. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it,

Re: Request for commit access

On 2017-08-16 9:15 PM, Oleg Nenashev wrote: > I am fine with that. There are several maintainers, who do not work in the > Jenkins project for sure. Not sure if it fits the current governance docs > and CoC. How do we proceed? -- You received this message because you are subscribed to the

Re: ec2 plugin maintenance

Alicia, I'm still around, but I have not been able to spend much time on this. I have (finally) reacted to your PR, and I think I can spend at least a little time reviewing PRs. If you would like commit rights to the plugin though, I would not have any problem with that. More people helping

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

> On 18 Aug 2017, at 14:10, Robert Sandell wrote: > > Cool, > So is this intended as a Branch API > > implementation? Something a la GitHub Branch Source Plugin >

Re: Plugin idea: publish the analysis result (reading from the jxlint xml format)

Unit test reports and static analysis reports are not the same thing. Analysis-core would be the way to go iiuc. /B 2017-08-18 14:18 GMT+02:00 Victor Martinez : > Maybe https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin could be > extended to support this use

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Cool, So is this intended as a Branch API implementation? Something a la GitHub Branch Source Plugin ? Which is what my mind goes to when reading things

Re: Plugin idea: publish the analysis result (reading from the jxlint xml format)

Maybe https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin could be extended to support this use case? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

> On 18 Aug 2017, at 12:19, Gustaf Lundh wrote: > > Cool stuff! Really looking forward to try it out! > > > - Stability: stream-events are based on SSH, which isn't scalable, reliable > > against downtime, etc. > > Please note: The Gerrit Trigger plugin does support

Plugin idea: publish the analysis result (reading from the jxlint xml format)

Dear Jenkins Developers, *In the “Before starting a new plugin” section of the documentation, you mention that we should contact you.* JXLint is a framework to create static analysis tool (linter) in java. See http://selesse.com/jxlint/ I am working on a tool based on this

[Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

Hi Gerrit and Jenkins Community, after over two years of iterations and improvements of the Gerrit CI workflow (https://gerrit-ci.gerritforge.com), I have decided that is about time to extract the logic of our workflow and make it available as a brand-new Jenkins plugin! Why? I wanted to use