Re: Jenkins CIA program

[Waribam Bhalindra]

Hi,

>
> I have been using Jenkins for 2 years now and planning to promote Jenkins
> to a larger audience out of the workspace where I am working right now. We
> are expecting around 25 - 30 comprising of people with no knowledge of
> Jenkins and people with some knowledge.
>
> Found about the Jenkins CIA Program (
> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CIA+Program) and
> really like the idea.
>
> How to we start the Jenkins CIA program?
>
>- We are planning the event around end of November, 2012.
>- Planning for 2 agents.
>
> Any further details to start the program will be highly appreciated.
>
> Thanks and Regards,
> Bhalindra Waribam
>

Re: Backports to LTS 1.480.1

[Kohsuke Kawaguchi]

I'm flying back to home today, and planning to take a sweep Tuesday afternoon.

2012/10/22 Vojtech Juranek :
> Hi,
> as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
> I identified and backported following bug fixes:
>
> JENKINS-13336 Invalid JSON is produced during remote api operations [2]
> JENKINS-14667 java.io.InvalidClassException [3]
> JENKINS-15277 Check view permissions before showing config page [4]
> JENKINS-15493 Excessive memory usage with large number of request threads [5]
>
> Please let me know by Tuesday if there are any other critical or blocker
> issues need to be backported to 1.480.1. As also agree on the meeting, RC
> should be available by Wednesday.
>
> Thanks
> Vojta
>
> [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html
> [2] https://issues.jenkins-ci.org/browse/JENKINS-13336
> [3] https://issues.jenkins-ci.org/browse/JENKINS-14667
> [4] https://issues.jenkins-ci.org/browse/JENKINS-15277
> [5] https://issues.jenkins-ci.org/browse/JENKINS-15493



-- 
Kohsuke Kawaguchi

Re: Unable to test Jenkins plugin

[Bruno P. Kinoshita]

Hi Dimitri, 

I created a plug-in last week I think, and run mvn hpi:run and it worked fine 
(it was using 1.466 too).

But my Maven is 3.0.4. There are some special settings for Maven 2.x in the 
plug-in tutorial, but could you consider updating your Maven to 3.0.4, maybe 
installing both, and giving it a try? 

If you are not able to run the plug-in with Maven 3.0.4, then we can further 
investigate this issue. What do you think? 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


>
> From: Dimitri CHARLES 
>To: jenkinsci-dev@googlegroups.com 
>Sent: Monday, 22 October 2012 9:45 PM
>Subject: Re: Unable to test Jenkins plugin
> 
>
>I forgot to say that I am using 
>Maven 2.2.1
>Jenkins 1.466
>
>Le mardi 23 octobre 2012 01:32:58 UTC+2, Dimitri CHARLES a écrit :
>I am actually trying to develop a Jenkins plugin using maven but I am unable 
>to test it.
>>I created my project with the command mvn -cpu hpi:create. I called 
>>the project jenkins-plugin-tutorial. I packaged it with mvn package or mvn 
>>install and run the Jenkins server with mvn hpi:run.
>>By default, there is a HelloWorlBuilder for testing purpose that should 
>>appear at the Jenkins configuration page (Jenkins Menu -> Manage Jenkins -> 
>>Configure System) or under the Build section, but it does not display.
>>I followed these two tutorials (here and here) step by step many times by 
>>making sure that I do not make a mistake but it still dont work.
>>Maybe I have made something wrong. Can somebody gives me some hint how to 
>>correct my errors.
>
> 

Re: Unable to test Jenkins plugin

[Dimitri CHARLES]

I forgot to say that I am using 
Maven 2.2.1
Jenkins 1.466

Le mardi 23 octobre 2012 01:32:58 UTC+2, Dimitri CHARLES a écrit :
>
> I am actually trying to develop a Jenkins plugin using maven but I am 
> unable to test it.
>
> I created my project with the command mvn -cpu hpi:create. I called the 
> project 
> jenkins-plugin-tutorial. I packaged it with mvn package or mvn install and 
> run the Jenkins server with mvn hpi:run.
>
> By default, there is a HelloWorlBuilder for testing purpose that should 
> appear at the Jenkins configuration page (Jenkins Menu -> Manage Jenkins -> 
> Configure System) or under the Build section, but it does not display.
>
> I followed these two tutorials 
> (here
>  and here ) 
> step by step many times by making sure that I do not make a mistake but it 
> still dont work.
>
> Maybe I have made something wrong. Can somebody gives me some hint how to 
> correct my errors.
>

Unable to test Jenkins plugin

[Dimitri CHARLES]

I am actually trying to develop a Jenkins plugin using maven but I am 
unable to test it.

I created my project with the command mvn -cpu hpi:create. I called the project 
jenkins-plugin-tutorial. I packaged it with mvn package or mvn install and 
run the Jenkins server with mvn hpi:run.

By default, there is a HelloWorlBuilder for testing purpose that should 
appear at the Jenkins configuration page (Jenkins Menu -> Manage Jenkins -> 
Configure System) or under the Build section, but it does not display.

I followed these two tutorials 
(here
 and here ) 
step by step many times by making sure that I do not make a mistake but it 
still dont work.

Maybe I have made something wrong. Can somebody gives me some hint how to 
correct my errors.

Re: RE: Backports to LTS 1.480.1

[Vojtech Juranek]

Done

On Monday 22 October 2012 09:19:45 Nord, James wrote:
> I would like to nominate JENKINS-15382 [1]
> 
> Not a critical or blocker, but it caused me some intermittent grief. (and
> I've been running this in production backported to 1.466.2 thanks to
> Cloudbees)
> 
> /James
> 
> [1] https://issues.jenkins-ci.org/browse/JENKINS-15382.
> 
> > -Original Message-
> > From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
> > d...@googlegroups.com] On Behalf Of Vojtech Juranek
> > Sent: 21 October 2012 21:55
> > To: jenkinsci-dev@googlegroups.com
> > Subject: Backports to LTS 1.480.1
> > 
> > Hi,
> > as agreed on the last Jenkins meeting [1], next LTS will be based on
> > 1.480.
> > I identified and backported following bug fixes:
> > 
> > JENKINS-13336 Invalid JSON is produced during remote api operations [2]
> > JENKINS-14667 java.io.InvalidClassException [3]
> > JENKINS-15277 Check view permissions before showing config page [4]
> > JENKINS-15493 Excessive memory usage with large number of request threads
> > [5]
> > 
> > Please let me know by Tuesday if there are any other critical or blocker
> > issues need to be backported to 1.480.1. As also agree on the meeting, RC
> > should be available by Wednesday.
> > 
> > Thanks
> > Vojta
> > 
> > [1]
> > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html
> > [2] https://issues.jenkins-ci.org/browse/JENKINS-13336
> > [3] https://issues.jenkins-ci.org/browse/JENKINS-14667
> > [4] https://issues.jenkins-ci.org/browse/JENKINS-15277
> > [5] https://issues.jenkins-ci.org/browse/JENKINS-15493
> 
> 
> 
> 
> 
> ** This message is confidential and intended only for the addressee.
> If you have received this message in error, please immediately notify the
> postmas...@nds.com and delete it from your system as well as any copies.
> The content of e-mails as well as traffic data may be monitored by NDS for
> employment and security purposes. To protect the environment please do not
> print this e-mail unless necessary.
> 
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales. Registered
> no. 3080780. VAT no. GB 603 8808 40-00
> ***
> ***

Re: Request for hosting plugin vboxwrapper

[nicolas de loof]

this should be fixed now

2012/10/22 theirix 

>
>
> On Monday, October 15, 2012 8:09:50 PM UTC+4, R Tyler Croy wrote:
>>
>>
>> On Sun, 14 Oct 2012, Eugene Seliverstov wrote:
>>
>> >
>> > Plugin is hosted at my github account: https://github.com/theirix/**
>> vboxwrapper-plugin 
>> > Could you please review an idea and provide an access to host the
>> plugin at jenkinsci.
>>
>>
>> Should be set up under 
>> https://github.com/jenkinsci/**vboxwrapper-plugin
>>
>
> Hello,
>
> It seems that a forked git repository is read only for me. Could you
> provide write permissions for the repository?
> Thank you!
>
>
>>
>> - R. Tyler Croy
>> --**
>> Code: https://github.com/rtyler
>>  Chatter: https://twitter.com/agentdero
>>
>

Re: Request for hosting plugin vboxwrapper

[theirix]

On Monday, October 15, 2012 8:09:50 PM UTC+4, R Tyler Croy wrote:
>
>
> On Sun, 14 Oct 2012, Eugene Seliverstov wrote: 
>
> > 
> > Plugin is hosted at my github account: 
> https://github.com/theirix/vboxwrapper-plugin 
> > Could you please review an idea and provide an access to host the plugin 
> at jenkinsci. 
>
>
> Should be set up under https://github.com/jenkinsci/vboxwrapper-plugin 
>

Hello,

It seems that a forked git repository is read only for me. Could you 
provide write permissions for the repository?
Thank you!
 

>
> - R. Tyler Croy 
> -- 
> Code: https://github.com/rtyler 
>  Chatter: https://twitter.com/agentdero 
>

Lazy job loading might be affecting CopyArtifacts plugin.

[Jason Swager]

I just submitted JENKINS-15594 (
https://issues.jenkins-ci.org/browse/JENKINS-15594).  Ever since we've 
upgraded Jenkins to 1.486, we've had intermittent and sporadic failures in 
our jobs that use the CopyArtifacts plugin.  I've confirmed that the job 
supplying the artifact files DOES exist, but the plugin can't seem to copy 
them.  The intermittent nature of the bug is also odd - 20 jobs start 
together that all reference the same job and build to copy artifacts from. 
 5 will succeed, the other 15 will fail because no files are copied.  So I 
know that the source build/job of the artifacts exist - but isn't always 
accessible.

I'm not sure if this problem is in the CopyArtifact plugin, or is it in the 
core.  Maybe a locking/race problem in the core?
Can anyone help with this issue?
Thanks,
Jason Swager

Re: hpi:run classpath hell

[domi]

I have updated the documentation:
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Structure#PluginStructure-Classloader
/Domi

On 21.10.2012, at 10:28, Edo Shor  wrote:

> Hi,
> 
> My plugin uses velocity engine v 1.7 for creating reports. Can't change that.
> HPI plugin has a transitive dependency on v1.4 of this library causing 
> classpath hell erros.
> I've tried to get rid of it somehow with maven excludes with no avail.
> 
> Is there any chance to change the way the plugin launches jenkins ? 
> Maybe some standalone jvm ? or a fresh classloader ?
> 

Re: Request hosting - GitHub ID (JerryCai) , jenkins-ci.org account ID jerrycai

[domi]

Just send us the repo location and your github ID so we can for it and add 
grant you all the required permissions
/Domi


On 20.10.2012, at 08:13, Jerry Cai  wrote:

> Dear all Jenkins-Devs ,
> 
> Jenkins CI is my favorite CI system , and I am very interested in it's 
> opening framework , and I has already developed a cloud-based server 
> managements plugin -GSSH , It is very convenient and largely used by my team 
> , I want to join and contribute it to our public jenkins-plugins repository 
> too , 
> 
> Best Regards!
> -Jerry Cai

Re: Maven Projects with dependencies is too eager since 1.481

[domi]

I think this should get fixed or reverted and back ported into the new LTS 
release.
/Domi

On 18.10.2012, at 21:43, Jeff Maxwell  wrote:

> We have the same requirement.
> 
> On Thursday, September 27, 2012 11:02:00 AM UTC-5, liam.j.bennett wrote:
> While this is clearly a bug that needs fixing it would be useful to have the 
> functionality to resolve downstream/upstream jobs with a fixed version 
> (configurable of-course). 
> 
> We no longer use SNAPSHOTS but use release versions with 
> BUILD_ID-BUILD_NUMBER and dynamically update dependencies using the 
> maven-versions-plugin at build time. At the moment we are having to manually 
> configure downstream/upstream relationships so having Jenkins auto-resolve 
> them for fixed versions would be very useful to us.
> 
> On Wednesday, September 19, 2012 4:04:37 PM UTC+1, Larry Shatzer, Jr. wrote:
> I've noticed something weird with Maven projects that are set to build 
> downstream jobs if there is a SNAPSHOT dependency. It now lists jobs as 
> dependencies (and builds them) even if it is not a SNAPSHOT dependency but a 
> regular dependency.
> 
> It looks like the code for JENKINS-12735 to allow version ranges is causing 
> this. If you use version of 1.0.0, that should not trigger 
> it, but the other uses like [1.0.0,2.0.0), etc. should. This is causing lots 
> of extra unnecessary builds when you have a lot of projects that are 
> dependent on each other, but set to a release of the other and not a SNAPSHOT.
> 
> -- Larry

New plugin - builds-chain-fingerprinter

[AdvanTiSS]

Hello, let me contribute to jenkins with this plugin please.
https://github.com/advantiss/builds-chain-fingerprinter

RE: Backports to LTS 1.480.1

[Nord, James]

I would like to nominate JENKINS-15382 [1]

Not a critical or blocker, but it caused me some intermittent grief. (and I've 
been running this in production backported to 1.466.2 thanks to Cloudbees)

/James

[1] https://issues.jenkins-ci.org/browse/JENKINS-15382.

> -Original Message-
> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
> d...@googlegroups.com] On Behalf Of Vojtech Juranek
> Sent: 21 October 2012 21:55
> To: jenkinsci-dev@googlegroups.com
> Subject: Backports to LTS 1.480.1
>
> Hi,
> as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
> I identified and backported following bug fixes:
>
> JENKINS-13336 Invalid JSON is produced during remote api operations [2]
> JENKINS-14667 java.io.InvalidClassException [3]
> JENKINS-15277 Check view permissions before showing config page [4]
> JENKINS-15493 Excessive memory usage with large number of request threads
> [5]
>
> Please let me know by Tuesday if there are any other critical or blocker 
> issues
> need to be backported to 1.480.1. As also agree on the meeting, RC should be
> available by Wednesday.
>
> Thanks
> Vojta
>
> [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html
> [2] https://issues.jenkins-ci.org/browse/JENKINS-13336
> [3] https://issues.jenkins-ci.org/browse/JENKINS-14667
> [4] https://issues.jenkins-ci.org/browse/JENKINS-15277
> [5] https://issues.jenkins-ci.org/browse/JENKINS-15493




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

Re: Re: Backports to LTS 1.480.1

[Vojtech Juranek]

I guess this marker is that the issue is either "blocker" or "critical" (+ the 
fix has to be in Jenkins for at least cca 2 weeks).

I'm asking because someone could forget to bump the issue to critical (default 
is "major") or I can miss something (both happened in the past). 


On Monday 22 October 2012 07:55:18 nicolas de loof wrote:
> Makes me wonder : can we have some way on Jira to tag issues as "*request
> backport to LTS*", so that LTS management would not require you to do such
> a reminder ?
> 
> 2012/10/21 Vojtech Juranek 
> 
> > Hi,
> > as agreed on the last Jenkins meeting [1], next LTS will be based on
> > 1.480.
> > I identified and backported following bug fixes:
> > 
> > JENKINS-13336 Invalid JSON is produced during remote api operations [2]
> > JENKINS-14667 java.io.InvalidClassException [3]
> > JENKINS-15277 Check view permissions before showing config page [4]
> > JENKINS-15493 Excessive memory usage with large number of request threads
> > [5]
> > 
> > Please let me know by Tuesday if there are any other critical or blocker
> > issues need to be backported to 1.480.1. As also agree on the meeting, RC
> > should be available by Wednesday.
> > 
> > Thanks
> > Vojta
> > 
> > [1]
> > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html
> > [2] https://issues.jenkins-ci.org/browse/JENKINS-13336
> > [3] https://issues.jenkins-ci.org/browse/JENKINS-14667
> > [4] https://issues.jenkins-ci.org/browse/JENKINS-15277
> > [5] https://issues.jenkins-ci.org/browse/JENKINS-15493

Re: New plugin - debian package builder

[nicolas de loof]

granted you access, but you just can push commits to github

2012/10/22 Ivan Kalinin 

> Great! What do i do next? How do I grigger the job?
>
>
> On Monday, October 22, 2012 12:32:04 PM UTC+4, nicolas de loof wrote:
>
>> forked as 
>> https://github.com/jenkinsci/**debian-package-builder-plugin
>> CI job on https://jenkins.ci.**cloudbees.com/job/plugins/job/**
>> debian-package-builder-plugin/
>>
>> 2012/10/22 Ivan Kalinin 
>>
>> Hello! I would like to contribute a plugin to the community – a debian
>>> package builder tool. It's created to analyze, build and publish debian
>>> packages.
>>>
>>> My github id is *pupssman*, the plugin is at
>>> https://github.com/pupssman/**debian-package-builder
>>>
>>> Best,
>>> Ivan Kalinin.
>>>
>>>
>>>
>>

Re: New plugin - debian package builder

[Ivan Kalinin]

Great! What do i do next? How do I grigger the job?

On Monday, October 22, 2012 12:32:04 PM UTC+4, nicolas de loof wrote:
>
> forked as https://github.com/jenkinsci/debian-package-builder-plugin
> CI job on 
> https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/
>
> 2012/10/22 Ivan Kalinin >
>
>> Hello! I would like to contribute a plugin to the community – a debian 
>> package builder tool. It's created to analyze, build and publish debian 
>> packages.
>>
>> My github id is *pupssman*, the plugin is at 
>> https://github.com/pupssman/debian-package-builder
>>
>> Best,
>> Ivan Kalinin.
>>
>>
>>
>

Re: New plugin - debian package builder

[nicolas de loof]

forked as https://github.com/jenkinsci/debian-package-builder-plugin
CI job on
https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/

2012/10/22 Ivan Kalinin 

> Hello! I would like to contribute a plugin to the community – a debian
> package builder tool. It's created to analyze, build and publish debian
> packages.
>
> My github id is *pupssman*, the plugin is at
> https://github.com/pupssman/debian-package-builder
>
> Best,
> Ivan Kalinin.
>
>
>

Re: New Plugin

[nicolas de loof]

This should be ok now

2012/10/22 Phil Rumble 

> Bump... is there anyone who can help?
>
>
>
> On Tue, Jul 17, 2012 at 9:19 PM, Phil Rumble wrote:
>
>> I don't how to do that, is there anything that I need to do?
>>
>>
>> On Tue, Jul 17, 2012 at 5:07 PM, Ullrich Hafner > > wrote:
>>
>>>  Seems that the lotus-connections-plugin is not part of jenkins-ci.
>>>
>>> I don't know how to fix that with the bot (or in github)... Does anybody
>>> know how to assign a project to jenkins-ci?
>>>
>>> Ulli
>>>
>>>
>>> On 07/17/2012 08:40 AM, Phil Rumble wrote:
>>>
>>>
>>> I don't seem to have commit rights. Can you assist please?
>>>
>>> On Thu, Jul 12, 2012 at 3:00 PM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
 + CI job
 https://jenkins.ci.cloudbees.com/job/plugins/job/lotus-connections/


 2012/7/12 Vojtech Juranek 

> Hi,
> forked as lotus-connections-plugin [1]. I got some error when setting
> up
> teams, so please verify that you have the commit rights.
> Welcome aboard!
> Vojta
>
> [1] https://github.com/jenkinsci/lotus-connections-plugin
>
> On Thursday 12 July 2012 10:32:20 Phil Rumble wrote:
> > Done. the repo is called LotusConnectionsPlugin
> >
> > On Wed, Jul 11, 2012 at 1:11 PM, Vojtech Juranek <
> vjura...@redhat.com>wrote:
> > > Hi,
> > > could you push your plugin into github (under your account), so
> that we
> > > can
> > > fork it under jenkinsci?
> > > Thanks
> > > Vojta
> > >
> > > On Tuesday 10 July 2012 22:03:43 Rumble wrote:
> > > > Hi,
> > > > I'd like to add a new plugin "LotusConnections" which will post
> a build
> > > > status message to Lotus Connections.
> > > > My github id is 'philrumble'
> > > >
> > > > Thanks
>


>>>
>>>
>>>
>>
>

New plugin - debian package builder

[Ivan Kalinin]

Hello! I would like to contribute a plugin to the community – a debian 
package builder tool. It's created to analyze, build and publish debian 
packages.

My github id is *pupssman*, the plugin is at 
https://github.com/pupssman/debian-package-builder

Best,
Ivan Kalinin.