Re: Jenkins Flyer 2014

1500 Jenkins flyers arrived today. They are just waiting to be handed out. :) Regards, Fred On Wednesday, January 1, 2014 4:51:25 PM UTC+1, FredG wrote: > > Hi, > > I wish everyone a *Happy New Year 2014*! > > FOSDEM 2014 is coming up soon. Therefore I'd like to get the discussion > started abou

Re: auto-installer for a plugin - where should the backend crawler go?

Thank you Larry for your help. Writing a tool installer should be simple, but I can't find some basic guidance. This link - https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer - has many holes in how to develop, run and test an installer locally. Is there an reliable source

Re: auto-installer for a plugin - where should the backend crawler go?

That I don't know, but I think the crawler will produce a json file you can look at, and maybe inject into your Jenkins instance. On Tue, Jan 21, 2014 at 2:48 PM, Vicki Kozel wrote: > So how do i test the crawler locally? I test my plugin through running mvn > hpi:run. > > > On Tuesday, January

Re: auto-installer for a plugin - where should the backend crawler go?

So how do i test the crawler locally? I test my plugin through running mvn hpi:run. On Tuesday, January 21, 2014 1:17:17 PM UTC-8, Larry Shatzer, Jr. wrote: > > You don't add it to your plugin. It belongs inside the backend crawler > codebase. > > > On Tue, Jan 21, 2014 at 1:12 PM, Vicki Kozel

Re: auto-installer for a plugin - where should the backend crawler go?

You don't add it to your plugin. It belongs inside the backend crawler codebase. On Tue, Jan 21, 2014 at 1:12 PM, Vicki Kozel wrote: > My question is: where should the crawler file go under my plugin > directory structure? > > On Tuesday, January 21, 2014 11:43:21 AM UTC-8, Larry Shatzer, Jr.

Re: auto-installer for a plugin - where should the backend crawler go?

My question is: where should the crawler file go under my plugin directory structure? On Tuesday, January 21, 2014 11:43:21 AM UTC-8, Larry Shatzer, Jr. wrote: > > They are found in the backend crawler project... > > https://github.com/jenkinsci/backend-crawler > > -- Larry > > > On Tue, Jan 21,

Re: auto-installer for a plugin - where should the backend crawler go?

My question is: where should the crawler file go under my plugin directory structure? On Tuesday, January 21, 2014 10:34:27 AM UTC-8, Vicki Kozel wrote: > > Hello, > I need to write an auto-installer for a plugin - where should the crawler > go? I looked at the gradle plugin on GIT, but the c

Best way to load a file into a Jenkins plugin

Hi, I'm writing a jenkins build plugin and the build needs to make some HTTPS calls but the server requires auth with a certificate and private key. What would be the best way (from the user's point of view) to allow him to load a custom keystore from the project configuration page, under my pl

Re: auto-installer for a plugin - where should the backend crawler go?

On 21.01.2014, at 19:34, Vicki Kozel wrote: > I need to write an auto-installer for a plugin - where should the crawler go? > I looked at the gradle plugin on GIT, but the crawler is not there in the > plugin repo. Help is appreciated! Everything you need should be here: https://wiki.jenkins

Re: auto-installer for a plugin - where should the backend crawler go?

They are found in the backend crawler project... https://github.com/jenkinsci/backend-crawler -- Larry On Tue, Jan 21, 2014 at 11:34 AM, Vicki Kozel wrote: > Hello, > I need to write an auto-installer for a plugin - where should the crawler > go? I looked at the gradle plugin on GIT, but the

Re: Where are Jenkins users?

I am looking at JUC Europe in June 2014. On Mon, Jan 20, 2014 at 12:07 PM, FredG wrote: > Judging by the increasing interest for JUCs I guess it's reasonable. It > will probably depend on the date and the remaining time to spread the word. > Is there a rough time frame when a European JUC could

auto-installer for a plugin - where should the backend crawler go?

Hello, I need to write an auto-installer for a plugin - where should the crawler go? I looked at the gradle plugin on GIT, but the crawler is not there in the plugin repo. Help is appreciated! Vicki -- You received this message because you are subscribed to the Google Groups "Jenkins Developer

Publishing cucumber test results

(Moving this topic to a new thread so that the main issue I'm having with the other one doesn't get overlooked!) Hi Peter, Interestingly enough we are planning on pushing results back from the cucumber plugin to another system – so I wonder if there is some commonality that the plugin shoul

RE: Probable class loading issue / conflict between plugins

Hi Peter, Interestingly enough we are planning on pushing results back from the cucumber plugin to another system – so I wonder if there is some commonality that the plugin should expose rather than requiring many plugins parsing the same files. /James From: jenkinsci-dev@googlegroups.com [m

Re: PR to add matrix build support to Cobertura plug-in

I have a new pull request that I think solves this in a better way: https://github.com/jenkinsci/cobertura-plugin/pull/26 This works by creating a [`MatrixAggregator`](http://javadoc.jenkins-ci.org/hudson/matrix/MatrixAggregator.html) that on [`endRun`](http://javadoc.jenkins-ci.org/hudson/ma

Probable class loading issue / conflict between plugins

Hi, I am writing a custom plugin to publish cucumber test results to a quality center database for internal reporting needs. To do so, I am using the cucumber-jvm gherkin library to process the test result file as was done in the cucumber-testresult-plugin. My code is working fine and process

Performance-plugin release?

Hi, We would like to use a csv file with the plugin but the bugfix for JENKINS-20160 isn't released yet, which hinders us. Is there a release of the Performance plugin coming in the near future, and if so, when? Br Tomas Westling, Sony Mobile Communications -- You received this message becaus

Re: License for existing plugins without license notices.

https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin States that: "If nothing is defined, your code will be assumed to fall under the MIT license terms", so it should be no problem adding the MIT license there. To be on the safe side t

License for existing plugins without license notices.

Hello. JENKINS-21270 points plugins without license information: https://issues.jenkins-ci.org/browse/JENKINS-21270 Parameterized-trigger-plugin is also pointed. As I was just planning to make its new release merging some pull requests, I'm going to add a license notice to that if I can. Please