Re: Building on 8 Operating Systems with 2 Systems

[Sami Tikka]

My Jenkins runs in VMware virtual machine and slaves in libvirt/KVM vms. No 
problems so far.

-- Sami

Raghavendra Achar  kirjoitti 8.2.2013 kello 7.37:

> Thanks a lot Andrew for the quick reply, Will Jenkins work on the virtual 
> configurations??Has it been tested by many??
> Can i make First system as Jenkins master and other 7 OS configurations as 
> virtual Jenkins Slaves in other system.
> Will this be the best approach??Please suggest
> 
> regards
> Raghavendra
> 
> On Friday, February 8, 2013 10:31:28 AM UTC+5:30, Andrew Melo wrote:
>> 
>> I would just roll 8 virtual machines
>> 
>> 
>> Andrew Melo
>> Sent from my secret fortress.
>> 
>> On Feb 7, 2013, at 22:57, Raghavendra Achar  wrote:
>> 
>>> Hello, 
>>>   I need to build my visual studio applications on 8 OS 
>>> configurations using Jenkins.But i have a constraint on the System 
>>> resource. 
>>> I have only 2 systems to use. Is this possible easily?What is the best 
>>> approach to do this.
>>> PC1 (32 bit): 
>>> - partition0: Windows XP – 32bit – English 
>>> - partition1: Windows XP – 32bit – Korean 
>>> - partition2: Windows7 – 32bit – English 
>>> - partition3: Windows7 – 32bit – Korean 
>>> PC2 (64 bit): 
>>> - partition0: Windows XP – 64bit – English 
>>> - partition1: Windows XP – 64bit – Korean 
>>> - partition2: Windows7 – 64bit – English 
>>> - partition3: Windows7 – 64bit – Korean 
>>> 
>>> Regards 
>>> raghavendra
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkinsci-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Sami Tikka]

Kamal Ahmed  kirjoitti 8.2.2013 kello 20.40:

> i increased the PermGen, like you suggested and for the last few minutes its 
> working ok, i even have a build going.
> Crossing Fingers.
> It would be nice to have RELEASE NOTES with every new build,

http://jenkins-ci.org/changelog, but it might not always be obvious the Jenkins 
memory requirements have changed. 

I guess the developers themselves might not always keep good track of that. 
Java is notorious for being a bit liberal with your RAM.

> or at least have a place where we can share our experiences about a 
> particular release.
> 

Click on the "Community ratings" on the changelog page. 

Another place for sharing experiences is this mailing list.

- Sami

> Thanks,
> -Kamal.
> 
> 
> From: Kamal Ahmed 
> To: "jenkinsci-users@googlegroups.com"  
> Sent: Friday, February 8, 2013 10:37 AM
> Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
> resolved for now, by downgrading jenkins to 1.494
> 
> But all the slaves are now off line, how do i bring the slaves back on ?
> Thanks,
> -Kamal.
> 
> 
> From: Kamal Ahmed 
> To: "jenkinsci-users@googlegroups.com"  
> Sent: Friday, February 8, 2013 8:53 AM
> Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
> This was working with the same amount of PermGen Space yesterday BEFORE the 
> upgrade.
> 
> jenkins JVM options:
> 
> 
> /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins 
> --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid 
> -- /usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
> --webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
> 
> /usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
> --webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
> 
> Thiis is what i see when i do ps -ef | grep java
> 
> 
> Java version:
> 
> java version "1.6.0_35"
> Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
> Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
> 
> 
> after i let the Jenkins stay initially at the main , i get the following 
> error in by browser ( this is in addition to the CPU being pegged 100% ) 
> 
> Content Encoding Error
> 
>   The page you are trying to view cannot be shown because it uses an 
> invalid or unsupported form of compression.
>   Please contact the website owners to inform them of this problem.
> 
> Some build's ago in 2009, i saw someone complain about the exact coding 
> error, and it was a plugin issue that Kohsuke fixed in the release plugin.
> 
> Thanks,
> -Kamal.
> From: "Mandeville, Rob" 
> To: "jenkinsci-users@googlegroups.com"  
> Sent: Friday, February 8, 2013 8:02 AM
> Subject: RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
> If you’re running out of PermGen space, your problem is with your JVM.  Your 
> CPU may be getting pegged because your JVM is desperately garbage collecting 
> to get every last byte of storage left, but I could be wrong.  Basically, 
> you’re going to have to tell the JVM running your Jenkins instance to give 
> you more PermGen space.
>  
> Find out (if you don’t already know) which application server you’re running 
> Jenkins with (if you’re launching it like “java –jar Jenkins.war”, you’re 
> using the onboard WinStone app server), and which JVM you’re running that 
> server in.  You’ll have to determine how much PermGen space you’re allocating 
> (likely the default that your JVM gives) and how to tell the JVM running your 
> App server to give it more.  Again, if you’re launching Jenkins as a plain 
> Java app and using WinStone, you can add the PermGen space arguments right to 
> the Java command line.
>  
> --Rob
>  
>  
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
> Sent: Friday, February 08, 2013 7:47 AM
> To: jenkinsci-users@googlegroups.com
> Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>  
> Hi,
> After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting 
> java.lang.OutOfMemoryError: PermGen space
> After i click any link on Jenkins page, the CPU gets pegged 100%
>  
>  
> This also happens when i let the page stay there and not click on anything.
>  
> Anyone found a resolution for this?
> Thanks,
> -Kamal.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
> The information in this message is for the intended recipient(s) only and may 
> be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
> protected from disclosure. If you are not the intended recipient(s), or an 
> employee or agent responsible for delivering this mes

Re: Detect command failure?

[Sami Tikka]

I'm guessing you are using ant to execute phpunit. 

Maybe you could tell ant to fail on error. Currently you have told ant to 
ignore the phpunit exit code.

-- Sami

Adam Tong  kirjoitti 9.2.2013 kello 0.17:

> Hi,
> 
> Here is the section of build.xml that configures the way phpunit is
> run by jenkins:
> 
> ---
>  description="Run unit tests using PHPUnit and generates
> junit.xml and clover.xml">
>
>
>
>
> 
> --
> 
> It works perfectly, I can see the failures if any and everything.One
> day, we had a problem with phpunit that was blocking at some level,
> and I wondered if I can catch that at jenkins level.
> 
> As you see in the description of the configuration, phpunit generates
> the files junit.xml and clover.xml.
> 
> When phpunit crashes I could make a test if one of those files was
> correctly generated, but I do not know where to insert that test.
> 
> 
> Thank you
> 
> On Wed, Feb 6, 2013 at 4:12 PM, Sami Tikka  wrote:
>> We need more details to help you.
>> 
>> What type of job have you created?
>> 
>> How exactly are you executing phpunit? What is the build step you use? 
>> Shell, CMD, something else?
>> 
>> Can you show us the exact command or configuration?
>> 
>> More information is better than less.
>> 
>> -- Sami
>> 
>> Adam Tong  kirjoitti 5.2.2013 kello 21.13:
>> 
>>> Hi,
>>> 
>>> Where should I do this check exactly?
>>> 
>>> Is there a way to do that in build.xml?
>>> 
>>> Thank you
>>> 
>>> On Tue, Feb 5, 2013 at 12:03 PM, Mark Waite  wrote:
 If your call to phpunit is expected to create a file, you could check that
 file is created and then use "exit 1" to cause the build script to exit 
 with
 the failure.
 
 Mark Waite
 
 
 
 From: Adam Tong 
 To: jenkinsci-users@googlegroups.com
 Sent: Tuesday, February 5, 2013 9:17 AM
 Subject: Detect command failure?
 
 Hi,
 
 I am running jenkins on Linux.
 
 Yesterday, because of a memory issue, phpunit was not able to run the
 hole tests suite. However the build was still successful.
 
 I understand that if phpunit fails it does not return any errors or
 failures.
 
 Now I am wondering if there is a way to make Jenkins detect this kind of
 issues.
 
 Thank you
 
 --
 You received this message because you are subscribed to the Google Groups
 "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
 
 
 
 
 --
 You received this message because you are subscribed to the Google Groups
 "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: clearcase.jpi

[Vincent Latombe]

Hi

you can find it there http://mirrors.jenkins-ci.org/plugins/clearcase/

Vincent


2013/2/8 David Dey 

> Where can I manually download the latest Clearcase plugin for Jenkins?  Is
> it still an hpi file or has its extension changed to jpi yet?
>
> Thanks
>
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Detect command failure?

[Adam Tong]

Hi,

Here is the section of build.xml that configures the way phpunit is
run by jenkins:

---
 




 
--

It works perfectly, I can see the failures if any and everything.One
day, we had a problem with phpunit that was blocking at some level,
and I wondered if I can catch that at jenkins level.

As you see in the description of the configuration, phpunit generates
the files junit.xml and clover.xml.

When phpunit crashes I could make a test if one of those files was
correctly generated, but I do not know where to insert that test.


Thank you

On Wed, Feb 6, 2013 at 4:12 PM, Sami Tikka  wrote:
> We need more details to help you.
>
> What type of job have you created?
>
> How exactly are you executing phpunit? What is the build step you use? Shell, 
> CMD, something else?
>
> Can you show us the exact command or configuration?
>
> More information is better than less.
>
> -- Sami
>
> Adam Tong  kirjoitti 5.2.2013 kello 21.13:
>
>> Hi,
>>
>> Where should I do this check exactly?
>>
>> Is there a way to do that in build.xml?
>>
>> Thank you
>>
>> On Tue, Feb 5, 2013 at 12:03 PM, Mark Waite  wrote:
>>> If your call to phpunit is expected to create a file, you could check that
>>> file is created and then use "exit 1" to cause the build script to exit with
>>> the failure.
>>>
>>> Mark Waite
>>>
>>>
>>> 
>>> From: Adam Tong 
>>> To: jenkinsci-users@googlegroups.com
>>> Sent: Tuesday, February 5, 2013 9:17 AM
>>> Subject: Detect command failure?
>>>
>>> Hi,
>>>
>>> I am running jenkins on Linux.
>>>
>>> Yesterday, because of a memory issue, phpunit was not able to run the
>>> hole tests suite. However the build was still successful.
>>>
>>> I understand that if phpunit fails it does not return any errors or
>>> failures.
>>>
>>> Now I am wondering if there is a way to make Jenkins detect this kind of
>>> issues.
>>>
>>> Thank you
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Hardware resource plugin

[Justin Ryan]

Ah-hah! That's exactly what I was looking for, thanks.

I started playing with it, and it's relatively straight-forward to setup.
(I happy to take this email thread of the mailing list to another one if
that's better.)

Just so you know my use case, I want to create a bunch of pretty generic
resources on a Node, representing the block devices on it, e.g. /dev/sdc,
/dev/sdd, etc. So I go to the Node and create a single External Resource
TreeNode, called BLOCK_DEVICE. Then under that I create a few "External
Resource" nodes. Each has a name like SBC, SBD, etc. I was hoping to leave
it at this and just say on the Job that I need a BLOCK_DEVICE, but that
seems to not be the case. I believe I have to add some property, so I added
a "available" property as true. And then make that the Resource Selection
Criteria be available == true. This feels hacky, so if you have a better
scheme for this, I'd be happy to hear. Otherwise it's working great!




On Fri, Feb 8, 2013 at 1:00 AM, Sandell, Robert <
robert.sand...@sonymobile.com> wrote:

> https://wiki.jenkins-ci.org/display/JENKINS/External+Resource+Dispatcher**
> **
>
> ** **
>
> It is currently in beta, but the more feedback we get the better we can
> make it ;)
>
> ** **
>
> * *
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
> ** **
>
> *From:* jenkinsci-...@googlegroups.com [mailto:
> jenkinsci-...@googlegroups.com] *On Behalf Of *Justin Ryan
> *Sent:* den 8 februari 2013 02:26
> *To:* jenkinsci-...@googlegroups.com
> *Subject:* Hardware resource plugin
>
> ** **
>
> In there iOS plugin there some concepts of a physical device attached to a
> slave, and executors are assigned to each one. Is there a more generic
> plugin that can do the same thing for arbitrary devices? For example, I'd
> like to have a slave with 4 serial ports, and have one executor dedicated
> to each one, i.e. /dev/ttyS0 for the first executor. It would have to
> support many slaves with a similar setup. I swear seeing references to such
> a plugin but I can't find it right now.
>
> ** **
>
> What I'd be using it for is to mount EBS volumes on different /dev/sdb*
> devices, then doing a chroot'd install of system packages, then
> un-mounting. AWS requires a unique /dev device when mounting these volumes,
> and linux only support a limited number of them, i.e. I can't create them
> on the fly. Having them per-executor REALLY simplifies things for me.
>
> ** **
>
> -justin
>
> ** **
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Beta Build Environment

[Andrew Melo]

On Fri, Feb 8, 2013 at 2:42 PM, J Arrizza  wrote:
> Has anyone tried to put the Jenkins configuration directory tree (less the
> workspace sub-directory) under SCM control? (Similar to William Soula's
> suggestion)
>
> Creating a second Jenkins instance could be as simple as:
> - install Jenkins from scratch
> - configure it to put the workspace somewhere else
> - go command line and replace the existing Jenkins config tree by cloning
> the repository
> - in Jenkins: reload the config from disk
>
> I haven't done this (yet), but it seems plausible.

It works okay, the obnoxious problem is that reloading from disk bring
down the whole agent for however long it takes to load your configs.
Without the lazy-loading stuff (which isn't in LTS), it can take a
significant amount of time.

best,
Andrew

>
> John
>
>
> On Wed, Feb 6, 2013 at 1:22 PM, Andrew Melo  wrote:
>>
>> You could also go the other way around and use whatever configuration
>> management tool you use (like puppet) to provision your jenkins
>> instances.
>>
>> On Wed, Feb 6, 2013 at 3:21 PM, William Soula
>>  wrote:
>> > Also can look into Jenkins Job Builder to put your job configuration
>> > under version control.  And I second the cli for plugin loading, can load
>> > them all with one command you could put in version control.  Then you just
>> > need the war and the global config.
>> >
>> > https://github.com/openstack-infra/jenkins-job-builder
>> >
>> > Will
>> > 
>> > From: jenkinsci-users@googlegroups.com
>> > [jenkinsci-users@googlegroups.com] on behalf of Sami Tikka
>> > [sjti...@gmail.com]
>> > Sent: Wednesday, February 06, 2013 3:16 PM
>> > To: jenkinsci-users@googlegroups.com
>> > Subject: Re: Beta Build Environment
>> >
>> > I have developed instructions on how to set up Jenkins from scratch if
>> > our Jenkins would catch fire and burn to the ground.
>> >
>> > I have also used the instructions to set up a 2nd Jenkins to run a newer
>> > version of Jenkins before upgrading.
>> >
>> > You need the jenkins.war, the plugins, the global config.xml and
>> > config.xml files for every job. If you want to try your hand at automating,
>> > remember that the Jenkins cli can be used to upload plugins and job
>> > configurations.
>> >
>> > -- Sami
>> >
>> > "Mandeville, Rob"  kirjoitti 5.2.2013 kello
>> > 21.09:
>> >
>> >> I work for an agile development group, so we like to test everything,
>> >> including our build environment.  I have been challenged to figure out how
>> >> my team can create a second build environment to test enhancements on.  
>> >> This
>> >> would also involve creating a beta copy of our Jenkins instance.
>> >>
>> >> We need to be able to test changes to (in order of importance) job
>> >> configurations, slave configurations, and (possibly) plugin 
>> >> configurations.
>> >> Is there any way to do this?  Has anyone ever tried?
>> >>
>> >> Thanks in advance,
>> >>
>> >> --Rob Mandeville
>> >> The information in this message is for the intended recipient(s) only
>> >> and may be the proprietary and/or confidential property of Litle & Co., 
>> >> LLC,
>> >> and thus protected from disclosure. If you are not the intended
>> >> recipient(s), or an employee or agent responsible for delivering this
>> >> message to the intended recipient, you are hereby notified that any use,
>> >> dissemination, distribution or copying of this communication is 
>> >> prohibited.
>> >> If you have received this communication in error, please notify Litle & 
>> >> Co.
>> >> immediately by replying to this message and then promptly deleting it and
>> >> your reply permanently from your computer.
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups "Jenkins Users" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>> >> For more options, visit https://groups.google.com/groups/opt_out.
>> >>
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Jenkins Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to jenkinsci-users+unsubscr...@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Jenkins Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to jenkinsci-users+unsubscr...@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>>
>>
>> --
>> --
>> Andrew Melo
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit ht

Re: Beta Build Environment

[J Arrizza]

Has anyone tried to put the Jenkins configuration directory tree (less the
workspace sub-directory) under SCM control? (Similar to William Soula's
suggestion)

Creating a second Jenkins instance could be as simple as:
- install Jenkins from scratch
- configure it to put the workspace somewhere else
- go command line and replace the existing Jenkins config tree by cloning
the repository
- in Jenkins: reload the config from disk

I haven't done this (yet), but it seems plausible.

John


On Wed, Feb 6, 2013 at 1:22 PM, Andrew Melo  wrote:

> You could also go the other way around and use whatever configuration
> management tool you use (like puppet) to provision your jenkins
> instances.
>
> On Wed, Feb 6, 2013 at 3:21 PM, William Soula
>  wrote:
> > Also can look into Jenkins Job Builder to put your job configuration
> under version control.  And I second the cli for plugin loading, can load
> them all with one command you could put in version control.  Then you just
> need the war and the global config.
> >
> > https://github.com/openstack-infra/jenkins-job-builder
> >
> > Will
> > 
> > From: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com]
> on behalf of Sami Tikka [sjti...@gmail.com]
> > Sent: Wednesday, February 06, 2013 3:16 PM
> > To: jenkinsci-users@googlegroups.com
> > Subject: Re: Beta Build Environment
> >
> > I have developed instructions on how to set up Jenkins from scratch if
> our Jenkins would catch fire and burn to the ground.
> >
> > I have also used the instructions to set up a 2nd Jenkins to run a newer
> version of Jenkins before upgrading.
> >
> > You need the jenkins.war, the plugins, the global config.xml and
> config.xml files for every job. If you want to try your hand at automating,
> remember that the Jenkins cli can be used to upload plugins and job
> configurations.
> >
> > -- Sami
> >
> > "Mandeville, Rob"  kirjoitti 5.2.2013 kello
> 21.09:
> >
> >> I work for an agile development group, so we like to test everything,
> including our build environment.  I have been challenged to figure out how
> my team can create a second build environment to test enhancements on.
>  This would also involve creating a beta copy of our Jenkins instance.
> >>
> >> We need to be able to test changes to (in order of importance) job
> configurations, slave configurations, and (possibly) plugin configurations.
>  Is there any way to do this?  Has anyone ever tried?
> >>
> >> Thanks in advance,
> >>
> >> --Rob Mandeville
> >> The information in this message is for the intended recipient(s) only
> and may be the proprietary and/or confidential property of Litle & Co.,
> LLC, and thus protected from disclosure. If you are not the intended
> recipient(s), or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that any use,
> dissemination, distribution or copying of this communication is prohibited.
> If you have received this communication in error, please notify Litle & Co.
> immediately by replying to this message and then promptly deleting it and
> your reply permanently from your computer.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-users+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
>
>
> --
> --
> Andrew Melo
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

clearcase.jpi

[David Dey]

Where can I manually download the latest Clearcase plugin for Jenkins?  Is 
it still an hpi file or has its extension changed to jpi yet?

Thanks

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: forcing a build to run through all downstream jobs

[cjo]

Also, how does this prevent both "every commit job" and "tagged commits" 
appear as causes for a testjob build? 

It will prevent testjob being triggered twice as the parameter set will be 
different 
i.e "every commit job" will none or default set of parameters
"tagged commits" will have an extra random dummy parameter above "every 
commit job",

and therefore the ParametersAction will return true when checking to add a 
new item, or combine into existing when scheduling a new build 
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/ParametersAction.java#L148


Which means that the UpstreamCause will only have one parent job not the 
two that you are getting now.
This will also resolve issues that might occur when the testjob is queued 
but multiple runs of "tagged commits" occur, so limiting the UpstreamCause 
to a single build when a Random dummy parameter is used. 

Hope this explains it a bit better.

Chris


On Friday, 8 February 2013 18:03:53 UTC, Chris Withers wrote:
>
> On 08/02/2013 11:53, cjo wrote: 
> > I assume that you have the jobs set up as 
> > 
> > every commit job -> testjob 
> > tagged commits -> testjob 
>
> Yep. 
>
> > Try adding a dummy parameter that is passed from the tagged commits job, 
> > that is unique for each build, as the ParametersAction will cause a 
> > separate builds if there are different parameters passed to ones already 
> > in the queue. 
>
> Yeah, I thought of that, seem a bit of a hack though :-/ 
>
> Also, how does this prevent both "every commit job" and "tagged commits" 
> appear as causes for a testjob build? 
>
> This can't happen, as it causes artifacts to be copied from both, which 
> is wrong... 
>
> Chris 
>
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting 
>  - http://www.simplistix.co.uk 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "don't keep this build forever" button does nothing

[Chris Withers]

On 06/02/2013 21:22, Sami Tikka wrote:

Is there a lock icon next to the build in the sidebar build listing?


No.

Chris



If yes, then it could also be a case of some other build referring to fingerprints that 
were present in this build and that build has "Keep build logs of dependencies" 
box checked in its configuration.

-- Sami

Chris Withers  kirjoitti 5.2.2013 kello 12.20:


Hi Sami,

Not talking about deleting builds here, but toggling "keep build forever".

It appears for some builds, this toggle can't take place but there's no indication why 
that might be, and the build stays "kept" even though I don't want it to be.

How would I go about debugging this?

cheers,

Chris

On 03/02/2013 23:13, Sami Tikka wrote:

Jenkins only deletes builds when it runs the job. If you need the disk space 
vacated immediately, you can script it like described here:

http://jenkins.361315.n4.nabble.com/Is-there-a-way-to-make-quot-discard-old-builds-quot-happen-right-now-td3879634.html

-- Sami

Chris Withers   kirjoitti 20.1.2013 kello 0.43:


Hi All,

I'd like to delete this build:

http://jenkins.simplistix.co.uk/job/testfixtures-tox/83/

...however clicking the "don't keep this build forever" button does nothing.

What am I doing wrong?

Chris

--
Simplistix - Content Management, Batch Processing&   Python Consulting
   - http://www.simplistix.co.uk




--
Simplistix - Content Management, Batch Processing&  Python Consulting
- http://www.simplistix.co.uk


__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__


--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: forcing a build to run through all downstream jobs

[Chris Withers]

On 08/02/2013 11:53, cjo wrote:

I assume that you have the jobs set up as

every commit job -> testjob
tagged commits -> testjob


Yep.


Try adding a dummy parameter that is passed from the tagged commits job,
that is unique for each build, as the ParametersAction will cause a
separate builds if there are different parameters passed to ones already
in the queue.


Yeah, I thought of that, seem a bit of a hack though :-/

Also, how does this prevent both "every commit job" and "tagged commits" 
appear as causes for a testjob build?


This can't happen, as it causes artifacts to be copied from both, which 
is wrong...


Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Parallel execution of builds

[Chris Withers]

Yep, I use the Multi-Project Throttle Categories from this plugin:

http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin

...to solve this exact problem.

cheers,

Chris

On 08/02/2013 13:50, Foxgang wrote:

Maybe I'm not fully understanding your problem, but you could also take
a look at the Resource Exclusion Plugin.
(https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin)

It lets you define some string semaphores that prevent jobs from
interfering with each other's artifacts and resources.


On Thursday, February 7, 2013 6:38:49 AM UTC-6, alvin Antony wrote:

Hi Jenkins users,
I am new to this user group and new on administrating the jenkins. I
have requirement to enable the parallel execution of some maven
module bulilds but some of them are not parallelizable.
The reason is we have a test dependency in the database. i.e. if we
run multiple module builds from a branch in parallel it will run
into deadlock.
The set up look like this...
branch1(trunk)-> module 1, module 2, module 3
branch2(prod)-> module 1, module 2, moudle 3
The branch 1 and branch2 has dedicated databases i.e any module from
branch 1 can run in parallel with any module from branch 2 but none
of the modules from the same branch can run in parallel.
How can i configure this? is there any plugin which supports this?
Thanks in advance,
Alvin

--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__


--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Kamal Ahmed]

i increased the PermGen, like you suggested and for the last few minutes its 
working ok, i even have a build going.
Crossing Fingers.
It would be nice to have RELEASE NOTES with every new build, or at least have a 
place where we can share our experiences about a particular release.

Thanks,
-Kamal.





>
> From: Kamal Ahmed 
>To: "jenkinsci-users@googlegroups.com"  
>Sent: Friday, February 8, 2013 10:37 AM
>Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
>
>resolved for now, by downgrading jenkins to 1.494
>
>But all the slaves are now off line, how do i bring the slaves back on ?
>Thanks,
>-Kamal.
>
>
>
>
>
>
>>
>> From: Kamal Ahmed 
>>To: "jenkinsci-users@googlegroups.com"  
>>Sent: Friday, February 8, 2013 8:53 AM
>>Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>> 
>>
>>This was working with the same amount of PermGen Space yesterday BEFORE the 
>>upgrade.
>>
>>jenkins JVM options:
>>
>>
>>
>>/usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins 
>>--output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid 
>>-- /usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
>>--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
>>
>>
>>
>>/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
>>--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
>>
>>
>>Thiis is what i see when i do ps -ef | grep java
>>
>>
>>
>>
>>Java version:
>>
>>
>>java version "1.6.0_35"
>>Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
>>Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
>>
>>
>>
>>
>>
>>after i let the Jenkins stay initially at the main , i get the following 
>>error in by browser ( this is in addition to the CPU being pegged 100% ) 
>>
>>
>>
>>Content Encoding Error    
>>    
>>  The page you are trying to view cannot be shown because it uses an 
>>invalid or unsupported form of compression.
>>  Please contact the website owners to inform them of this problem.
>>
>>
>>Some build's ago in 2009, i saw someone complain about the exact coding 
>>error, and it was a plugin issue that Kohsuke fixed in the release plugin.
>>
>>
>>Thanks,
>>-Kamal.
>>
>>
>>>
>>> From: "Mandeville, Rob" 
>>>To: "jenkinsci-users@googlegroups.com"  
>>>Sent: Friday, February 8, 2013 8:02 AM
>>>Subject: RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>>> 
>>>
>>> 
>>>If you’re running out of PermGen space, your problem is with your JVM.  Your 
>>>CPU may be getting pegged because your JVM is desperately garbage collecting 
>>>to get every last byte of storage left, but I could be wrong.  Basically, 
>>>you’re going to have to tell the JVM running your Jenkins instance to give 
>>>you more PermGen space.
>>> 
>>>Find out (if you don’t already know) which application server you’re running 
>>>Jenkins with (if you’re launching it like “java –jar Jenkins.war”, you’re 
>>>using the onboard WinStone app server), and which JVM you’re running that 
>>>server in.  You’ll have to determine how much PermGen space you’re 
>>>allocating (likely the default that your JVM gives) and how to tell the JVM 
>>>running your App server to give it more.  Again, if you’re launching Jenkins 
>>>as a plain Java app and using WinStone, you can add the PermGen space 
>>>arguments right to the Java command line.
>>> 
>>>--Rob
>>> 
>>> 
>>>From:jenkinsci-users@googlegroups.com 
>>>[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
>>>Sent: Friday, February 08, 2013 7:47 AM
>>>To: jenkinsci-users@googlegroups.com
>>>Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>>> 
>>>Hi,
>>>After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting 
>>>java.lang.OutOfMemoryError: PermGen space
>>>After i click any link on Jenkins page, the CPU gets pegged 100%
>>> 
>>> 
>>>This also happens when i let the page stay there and not click on anything.
>>> 
>>>Anyone found a resolution for this?
>>>Thanks,
>>>-Kamal.
>>>-- 
>>>You received this message because you are subscribed to the Google Groups 
>>>"Jenkins Users" group.
>>>To unsubscribe from this group and stop receiving emails from it, send an 
>>>email to jenkinsci-users+unsubscr...@googlegroups.com.
>>>For more options, visit https://groups.google.com/groups/opt_out.
>>> 
>>> 
>>>The information in this message is for the intended recipient(s) only and 
>>>may be the proprietary and/or confidential property of Litle & Co., LLC, and 
>>>thus protected from disclosure. If you are not the intended recipient(s), or 
>>>an employee or agent responsible for delivering this message to the intended 
>>>recipient, you are hereby notified that any use, dissemination, distribution 
>>>or copying of this communication is prohibited. If you have received this 
>>>communication in error, please notify Litle

Error in Multi-module Maven Build

[John Cody]

I have a Jenkins build that runs the following Maven goals:

release:clean release:prepare release:perform

For a single maven module build everything works fine, however for a
muli-module build it fails. Also running the maven goals from the command
line works just fine.

Below is the output from the console which shows an svn lock on the working
copy. I've gone into the directory and run the 'svn cleanup' command, but
that doesn't fix anything.

[INFO] Svn command failed due to some locks in working copy. We try to run
a 'svn cleanup'. [INFO] Executing: cmd.exe /X /C "svn" [INFO] Working
directory: C:\Jenkins\workspace\TRIX mojoFailed
org.apache.maven.plugins:maven-release-plugin:2.2.2(default-cli)
projectFailed trs.trix:TRIX:0.0.12-SNAPSHOT sessionEnded [INFO]

[INFO] Reactor Summary: [INFO] [INFO] TRIX EJB
.. SUCCESS [2.344s] [INFO] TRIX WAR
.. SUCCESS [0.062s] [INFO] TRIX EAR
.. SUCCESS [0.078s] [INFO] TRIX
.. FAILURE [1:30.156s] [INFO]

[INFO] BUILD FAILURE [INFO]

[INFO] Total time: 1:34.719s [INFO] Finished at: Fri Feb 08 10:18:23 CST
2013 [INFO] Final Memory: 11M/26M [INFO]

Projects to build: [MavenProject: trs.trix.ejb:TRIXEJB:0.0.12-SNAPSHOT @
C:\jenkins\workspace\TRIX\TRIXEJB\pom.xml, MavenProject:
trs.trix.war:TRIXWAR:0.0.12-SNAPSHOT @
C:\jenkins\workspace\TRIX\TRIXWAR\pom.xml, MavenProject:
trs.trix.ear:TRIXEAR:0.0.12-SNAPSHOT @
C:\jenkins\workspace\TRIX\TRIXEAR\pom.xml, MavenProject:
trs.trix:TRIX:0.0.12-SNAPSHOT @ C:\Jenkins\workspace\TRIX\pom.xml]
[JENKINS] Archiving C:\jenkins\workspace\TRIX\TRIXWAR\pom.xml to
C:\Jenkins\jobs\TRIX\modules\trs.trix.war$TRIXWAR\builds\2013-02-08_10-16-46\archive\trs.trix.war\TRIXWAR\0.0.12-SNAPSHOT\TRIXWAR-0.0.12-SNAPSHOT.pom
[JENKINS] Archiving C:\jenkins\workspace\TRIX\TRIXEAR\pom.xml to
C:\Jenkins\jobs\TRIX\modules\trs.trix.ear$TRIXEAR\builds\2013-02-08_10-16-46\archive\trs.trix.ear\TRIXEAR\0.0.12-SNAPSHOT\TRIXEAR-0.0.12-SNAPSHOT.pom
[JENKINS] Archiving C:\Jenkins\workspace\TRIX\pom.xml to
C:\Jenkins\jobs\TRIX\modules\trs.trix$TRIX\builds\2013-02-08_10-16-46\archive\trs.trix\TRIX\0.0.12-SNAPSHOT\TRIX-0.0.12-SNAPSHOT.pom
[JENKINS] Archiving C:\jenkins\workspace\TRIX\TRIXEJB\pom.xml to
C:\Jenkins\jobs\TRIX\modules\trs.trix.ejb$TRIXEJB\builds\2013-02-08_10-16-46\archive\trs.trix.ejb\TRIXEJB\0.0.12-SNAPSHOT\TRIXEJB-0.0.12-SNAPSHOT.pom
Waiting for Jenkins to finish collecting data mavenExecutionResult
exceptions not empty message : Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli)
on project TRIX: Unable to commit files Provider message: The svn command
failed. Command output: svn: E155004: Commit failed (details follow): svn:
E155004: Working copy 'C:\Jenkins\workspace\TRIX' locked. svn: E155004:
'C:\Jenkins\workspace\TRIX' is already locked. svn: run 'svn cleanup' to
remove locks (type 'svn help cleanup' for details) Type 'svn help' for
usage. cause : Unable to commit files Provider message: The svn command
failed. Command output: svn: E155004: Commit failed (details follow): svn:
E155004: Working copy 'C:\Jenkins\workspace\TRIX' locked. svn: E155004:
'C:\Jenkins\workspace\TRIX' is already locked. svn: run 'svn cleanup' to
remove locks (type 'svn help cleanup' for details) Type 'svn help' for
usage. Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare
(default-cli) on project TRIX: Unable to commit files Provider message: The
svn command failed. Command output: svn: E155004: Commit failed (details
follow): svn: E155004: Working copy 'C:\Jenkins\workspace\TRIX' locked.
svn: E155004: 'C:\Jenkins\workspace\TRIX' is already locked. svn: run 'svn
cleanup' to remove locks (type 'svn help cleanup' for details) Type 'svn
help' for usage. at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at
org.apache.maven.DefaultMav

RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Mandeville, Rob]

It make sense to run out of PermGen space after upgrading.  Presumably, the 
upgrade has more classes to load, which fills up your PermGen space.

If you're using HotSpot 1.6, I believe (but could be wrong) that the option is 
-XX:MaxPermSize={size}.  For 1.6, the default size is 64m, so you may want to 
try -XX:MaxPermSize=128m.

I've seen the same Content Encoding Error you mention below, but I don't know 
what it means or if it's related to the PermGen space thing.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
Sent: Friday, February 08, 2013 8:53 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

This was working with the same amount of PermGen Space yesterday BEFORE the 
upgrade.

jenkins JVM options:

/usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins 
--output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- 
/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1

/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
Thiis is what i see when i do ps -ef | grep java


Java version:

java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)


after i let the Jenkins stay initially at the main , i get the following error 
in by browser ( this is in addition to the CPU being pegged 100% )

Content Encoding Error

  The page you are trying to view cannot be shown because it uses an 
invalid or unsupported form of compression.
  Please contact the website owners to inform them of this problem.

Some build's ago in 2009, i saw someone complain about the exact coding error, 
and it was a plugin issue that Kohsuke fixed in the release plugin.

Thanks,
-Kamal.

From: "Mandeville, Rob" mailto:rmandevi...@litle.com>>
To: "jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Sent: Friday, February 8, 2013 8:02 AM
Subject: RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

If you're running out of PermGen space, your problem is with your JVM.  Your 
CPU may be getting pegged because your JVM is desperately garbage collecting to 
get every last byte of storage left, but I could be wrong.  Basically, you're 
going to have to tell the JVM running your Jenkins instance to give you more 
PermGen space.

Find out (if you don't already know) which application server you're running 
Jenkins with (if you're launching it like "java -jar Jenkins.war", you're using 
the onboard WinStone app server), and which JVM you're running that server in.  
You'll have to determine how much PermGen space you're allocating (likely the 
default that your JVM gives) and how to tell the JVM running your App server to 
give it more.  Again, if you're launching Jenkins as a plain Java app and using 
WinStone, you can add the PermGen space arguments right to the Java command 
line.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
Sent: Friday, February 08, 2013 7:47 AM
To: jenkinsci-users@googlegroups.com
Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

Hi,
After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting
java.lang.OutOfMemoryError: PermGen space
After i click any link on Jenkins page, the CPU gets pegged 100%


This also happens when i let the page stay there and not click on anything.

Anyone found a resolution for this?
Thanks,
-Kamal.
--


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

[David Hoffman]

Looking at the release notes, the fix to CORE is on tap to be released in 
1.501, thanks to everyone who kept me from going off the deep end.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Kamal Ahmed]

resolved for now, by downgrading jenkins to 1.494

But all the slaves are now off line, how do i bring the slaves back on ?
Thanks,
-Kamal.





>
> From: Kamal Ahmed 
>To: "jenkinsci-users@googlegroups.com"  
>Sent: Friday, February 8, 2013 8:53 AM
>Subject: Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
>
>This was working with the same amount of PermGen Space yesterday BEFORE the 
>upgrade.
>
>jenkins JVM options:
>
>
>
>/usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins 
>--output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid 
>-- /usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
>--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
>
>
>
>/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
>--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1
>
>
>Thiis is what i see when i do ps -ef | grep java
>
>
>
>
>Java version:
>
>
>java version "1.6.0_35"
>Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
>Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
>
>
>
>
>
>after i let the Jenkins stay initially at the main , i get the following error 
>in by browser ( this is in addition to the CPU being pegged 100% ) 
>
>
>
>Content Encoding Error    
>    
>  The page you are trying to view cannot be shown because it uses an 
>invalid or unsupported form of compression.
>  Please contact the website owners to inform them of this problem.
>
>
>Some build's ago in 2009, i saw someone complain about the exact coding error, 
>and it was a plugin issue that Kohsuke fixed in the release plugin.
>
>
>Thanks,
>-Kamal.
>
>
>>
>> From: "Mandeville, Rob" 
>>To: "jenkinsci-users@googlegroups.com"  
>>Sent: Friday, February 8, 2013 8:02 AM
>>Subject: RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>> 
>>
>> 
>>If you’re running out of PermGen space, your problem is with your JVM.  Your 
>>CPU may be getting pegged because your JVM is desperately garbage collecting 
>>to get every last byte of storage left, but I could be wrong.  Basically, 
>>you’re going to have to tell the JVM running your Jenkins instance to give 
>>you more PermGen space.
>> 
>>Find out (if you don’t already know) which application server you’re running 
>>Jenkins with (if you’re launching it like “java –jar Jenkins.war”, you’re 
>>using the onboard WinStone app server), and which JVM you’re running that 
>>server in.  You’ll have to determine how much PermGen space you’re allocating 
>>(likely the default that your JVM gives) and how to tell the JVM running your 
>>App server to give it more.  Again, if you’re launching Jenkins as a plain 
>>Java app and using WinStone, you can add the PermGen space arguments right to 
>>the Java command line.
>> 
>>--Rob
>> 
>> 
>>From:jenkinsci-users@googlegroups.com 
>>[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
>>Sent: Friday, February 08, 2013 7:47 AM
>>To: jenkinsci-users@googlegroups.com
>>Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
>> 
>>Hi,
>>After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting 
>>java.lang.OutOfMemoryError: PermGen space
>>After i click any link on Jenkins page, the CPU gets pegged 100%
>> 
>> 
>>This also happens when i let the page stay there and not click on anything.
>> 
>>Anyone found a resolution for this?
>>Thanks,
>>-Kamal.
>>-- 
>>You received this message because you are subscribed to the Google Groups 
>>"Jenkins Users" group.
>>To unsubscribe from this group and stop receiving emails from it, send an 
>>email to jenkinsci-users+unsubscr...@googlegroups.com.
>>For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> 
>>The information in this message is for the intended recipient(s) only and may 
>>be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
>>protected from disclosure. If you are not the intended recipient(s), or an 
>>employee or agent responsible for delivering this message to the intended 
>>recipient, you are hereby notified that any use, dissemination, distribution 
>>or copying of this communication is prohibited. If you have received this 
>>communication in error, please notify Litle & Co. immediately by replying to 
>>this message and then promptly deleting it and your reply permanently from 
>>your computer.
>>
-- 
>>You received this message because you are subscribed to the Google Groups 
>>"Jenkins Users" group.
>>To unsubscribe from this group and stop receiving emails from it, send an 
>>email to jenkinsci-users+unsubscr...@googlegroups.com.
>>For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> 
>>
>>
>>
-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to jenkinsci-us

RE: Copy Existing Job throws stacktrace

[Matthew.Webber]

The plugin is not required (though highly recommended), so it you didn’t have 
it before, “upgrading” it would be unlikely to solve your problem.
It looks like the fix is in the not-yet-release 1.501 see 
http://jenkins-ci.org/changelog
The Jira ticket I originally pointed you to explains it all …
Matthew

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Hoffman
Sent: 08 February 2013 15:05
To: jenkinsci-users@googlegroups.com
Cc: Webber, Matthew (DLSLtd,RAL,DIA)
Subject: Re: Copy Existing Job throws stacktrace

H... I don't even have that plugin installed.  Is it required?


On Friday, February 8, 2013 8:39:45 AM UTC-6, 
matthew...@diamond.ac.uk wrote:
This is https://issues.jenkins-ci.org/browse/JENKINS-16499. Update the 
JobConfigHistory Plugin to at least 2.2




-- 

This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

 







-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

[Christoph Kutzinski]

That's a bug in Jenkins core: 
https://issues.jenkins-ci.org/browse/JENKINS-16499


You'll have to wait for Jenkins 1.501 (I wonder why it's not released 
yet) or downgrade.


Am 08.02.2013 16:21, schrieb David Hoffman:

I have also gone ahead and upgraded the Mercurial plugin to 1.43 with no
joy -  Error still happens.

--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

[David Hoffman]

I have also gone ahead and upgraded the Mercurial plugin to 1.43 with no 
joy -  Error still happens.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

[David Hoffman]

Went ahead and installed JobConfigHistory (v2.2) - same error :(

On Friday, February 8, 2013 9:05:13 AM UTC-6, David Hoffman wrote:
>
> H... I don't even have that plugin installed.  Is it required?
>
>
> On Friday, February 8, 2013 8:39:45 AM UTC-6, matthew...@diamond.ac.ukwrote:
>>
>>  This is https://issues.jenkins-ci.org/browse/JENKINS-16499. Update the 
>> JobConfigHistory Plugin to at least 2.2
>>
>>  
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

[David Hoffman]

H... I don't even have that plugin installed.  Is it required?


On Friday, February 8, 2013 8:39:45 AM UTC-6, matthew...@diamond.ac.uk 
wrote:
>
>  This is https://issues.jenkins-ci.org/browse/JENKINS-16499. Update the 
> JobConfigHistory Plugin to at least 2.2
>
>  
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Copy Existing Job throws stacktrace

[Matthew.Webber]

This is https://issues.jenkins-ci.org/browse/JENKINS-16499. Update the 
JobConfigHistory Plugin to at least 2.2

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Hoffman
Sent: 08 February 2013 14:18
To: jenkinsci-users@googlegroups.com
Subject: Copy Existing Job throws stacktrace

Using Jenkins 1.500 deployed on SuSE

When attempting to create a "New Job" and selecting "Copy existing job"; I get 
the following stacktrace.  This has worked previously, but I don't even know 
where to start looking.

Can someone point me in the right direction?

Incidently: the job does in fact get created, but the Mercurial configuration 
is "dropped".  Is it possible that this is because I have not upgrade the 
Mercurial Plugin (still using 1.3.9)?

SEVERE: Error while serving 
http://*/view//createItem
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.do

Copy Existing Job throws stacktrace

[David Hoffman]

Using Jenkins 1.500 deployed on SuSE

When attempting to create a "New Job" and selecting "Copy existing job"; I 
get the following stacktrace.  This has worked previously, but I don't even 
know where to start looking.

Can someone point me in the right direction?

Incidently: the job does in fact get created, but the Mercurial 
configuration is "dropped".  Is it possible that this is because I have not 
upgrade the Mercurial Plugin (still using 1.3.9)?


SEVERE: Error while serving 
>> http://*/view//createItem
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at 
>> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
>> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
>> at 
>> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
>> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
>> at 
>> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
>> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
>> at 
>> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
>> at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
>> at 
>> winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
>> at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
>> at 
>> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
>> at 
>> net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
>> at 
>> net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
>> at 
>> net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
>> at 
>> org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
>> at 
>> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
>> at 
>> hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
>> at 
>> winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
>> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
>> at 
>> winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
>> at 
>> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
>> at 
>> hudson.securit

Re: How does Jenkins checkout sources from svn to the slaves?

[Foxgang]

That error message means that the slave can't generate enough random data 
to make a secure key for the connection. 

Do some research on /dev/random and /dev/urandom... you might be able to 
solve that problem. Personally though, I don't see why you'd want to; is 
there some reason you don't want to use the Jenkins SVN plugin? 

On Thursday, February 7, 2013 5:08:16 AM UTC-6, Mehdi Hayani Soujaa wrote:
>
> Hi,
>
> I really have no idea on how SSL is disabled, because it's a client slave, 
> and i've said that SSL is disabled because if I do a checkout from the 
> command line directly on the slave I get this error :
>
>
>- SSL negotiation failed: SSL disabled due to lack of entropy..
>
>
> But, from Jenkins, with the job configured to execute on this slave, 
> checkout run without any problem, that's why i'm trying to undertand what 
> happen in this case :)
>
>
> Regards 
> Mehdi
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Building on 8 Operating Systems with 2 Systems

[Les Mikesell]

On Thu, Feb 7, 2013 at 11:37 PM, Raghavendra Achar  wrote:
> Thanks a lot Andrew for the quick reply, Will Jenkins work on the virtual
> configurations??Has it been tested by many??
> Can i make First system as Jenkins master and other 7 OS configurations as
> virtual Jenkins Slaves in other system.
> Will this be the best approach??Please suggest

Virtual machines are generally indistinguishable from real hardware
except for the limits on the resources they share.

-- 
   Les Mikesell
 lesmikes...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Kamal Ahmed]

This was working with the same amount of PermGen Space yesterday BEFORE the 
upgrade.

jenkins JVM options:



/usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins 
--output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- 
/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1


/usr/bin/java -Xmx2048m -jar /usr/share/jenkins/jenkins.war 
--webroot=/var/cache/jenkins/war --httpPort=9000 --ajp13Port=-1


Thiis is what i see when i do ps -ef | grep java


Java version:

java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)



after i let the Jenkins stay initially at the main , i get the following error 
in by browser ( this is in addition to the CPU being pegged 100% ) 


Content Encoding Error    
    
  The page you are trying to view cannot be shown because it uses an 
invalid or unsupported form of compression.
  Please contact the website owners to inform them of this problem.

Some build's ago in 2009, i saw someone complain about the exact coding error, 
and it was a plugin issue that Kohsuke fixed in the release plugin.

Thanks,
-Kamal.


>
> From: "Mandeville, Rob" 
>To: "jenkinsci-users@googlegroups.com"  
>Sent: Friday, February 8, 2013 8:02 AM
>Subject: RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
>
> 
>If you’re running out of PermGen space, your problem is with your JVM.  Your 
>CPU may be getting pegged because your JVM is desperately garbage collecting 
>to get every last byte of storage left, but I could be wrong.  Basically, 
>you’re going to have to tell the JVM running your Jenkins instance to give you 
>more PermGen space.
> 
>Find out (if you don’t already know) which application server you’re running 
>Jenkins with (if you’re launching it like “java –jar Jenkins.war”, you’re 
>using the onboard WinStone app server), and which JVM you’re running that 
>server in.  You’ll have to determine how much PermGen space you’re allocating 
>(likely the default that your JVM gives) and how to tell the JVM running your 
>App server to give it more.  Again, if you’re launching Jenkins as a plain 
>Java app and using WinStone, you can add the PermGen space arguments right to 
>the Java command line.
> 
>--Rob
> 
> 
>From:jenkinsci-users@googlegroups.com 
>[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
>Sent: Friday, February 08, 2013 7:47 AM
>To: jenkinsci-users@googlegroups.com
>Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500
> 
>Hi,
>After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting 
>java.lang.OutOfMemoryError: PermGen space
>After i click any link on Jenkins page, the CPU gets pegged 100%
> 
> 
>This also happens when i let the page stay there and not click on anything.
> 
>Anyone found a resolution for this?
>Thanks,
>-Kamal.
>-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to jenkinsci-users+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
>The information in this message is for the intended recipient(s) only and may 
>be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
>protected from disclosure. If you are not the intended recipient(s), or an 
>employee or agent responsible for delivering this message to the intended 
>recipient, you are hereby notified that any use, dissemination, distribution 
>or copying of this communication is prohibited. If you have received this 
>communication in error, please notify Litle & Co. immediately by replying to 
>this message and then promptly deleting it and your reply permanently from 
>your computer.
>
-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to jenkinsci-users+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: shell redirection

[Foxgang]

Seems like the wildcard is getting prematurely expanded by the shell. It 
would be helpful to see your actual shell command and build log; like the 
other guy said. 

If my guess is right, you can solve it by putting quotes around the 
wildcarded argument, i.e. [python -m "pep8*.py" > reports/pep8.report]

On Thursday, February 7, 2013 3:54:15 PM UTC-6, jonas wrote:
>
> Hello,
>
> I'm using Jenkins as my CI server for some python projects.
>
> I run all my tests,coverage reports etc .. using the shell script 
> buildstep.
> One line of the script redirect some output: python -m pep8 *.py > 
> reports/pep8.report
>
> But for some reason this fails, in the console log, the line is outputed 
> as: "python -m pep8 main.py tests.py".
>
> I think it has something to do with the redirect, although the file 
> reports/pep8.report is created and contains the expected data.
>
> If I move the line up or down it fails again, exactly at that line.
>
> Any advice is appreciated.
>
> Jonas.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Parallel execution of builds

[Foxgang]

Maybe I'm not fully understanding your problem, but you could also take a 
look at the Resource Exclusion Plugin. (
https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin)

It lets you define some string semaphores that prevent jobs 
from interfering with each other's artifacts and resources. 


On Thursday, February 7, 2013 6:38:49 AM UTC-6, alvin Antony wrote:
>
> Hi Jenkins users,
>  
> I am new to this user group and new on administrating the jenkins. I have 
> requirement to enable the parallel execution of some maven module bulilds 
> but some of them are not parallelizable.
>  
> The reason is we have a test dependency in the database.  i.e. if we run 
> multiple  module builds from a branch in parallel it will run into 
> deadlock. 
> The set up look like this...
>  
> branch1(trunk)-> module 1, module 2, module 3
> branch2(prod)-> module 1, module 2, moudle 3
>  
> The branch 1 and branch2 has dedicated databases  i.e any module from 
> branch 1 can run in parallel with any module from branch 2 but none of the 
> modules from the same branch can run in parallel. 
>  
> How can i configure this? is there any plugin which supports this?
>  
> Thanks in advance,
>  
> Alvin
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cygwin build step - quick question

[Eric Pyle]

You can use an "execute shell" step on windows. Just make sure to set 
the shell executable in Manage Jenkins>Configure System. If your Jenkins 
setup has both Linux and Windows slaves, you'll want to set the 
executable to "sh" and make sure sh.exe (windows) or sh (Linux) is on 
the system path on each slave.


Eric

On 2/8/2013 7:48 AM, Mandeville, Rob wrote:


My first guess is to write a Windows batch command step that just says 
something like "bash myBuildScript.sh".


*From:*jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] *On Behalf Of *zw

*Sent:* Thursday, February 07, 2013 4:35 PM
*To:* jenkinsci-users@googlegroups.com
*Subject:* cygwin build step - quick question

Hi All

How do we trigger a windows box to use cygwin and run its script?

In our build step, there isnt a choice for that.

Thanks

--
You received this message because you are subscribed to the Google 
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/groups/opt_out.

The information in this message is for the intended recipient(s) only 
and may be the proprietary and/or confidential property of Litle & 
Co., LLC, and thus protected from disclosure. If you are not the 
intended recipient(s), or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby 
notified that any use, dissemination, distribution or copying of this 
communication is prohibited. If you have received this communication 
in error, please notify Litle & Co. immediately by replying to this 
message and then promptly deleting it and your reply permanently from 
your computer.

--
You received this message because you are subscribed to the Google 
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Config File Provider Plugin" does not store new files

[Markus KARG]

Just noticed that it happens with IE 9 only while it runs well with Safari. 
Any ideas?

Am Freitag, 8. Februar 2013 14:04:01 UTC+1 schrieb Markus KARG:

> Frank, you don't see the actual problem. "Submit" actually does NOTHING, 
> hence, the file is NOT available anymore as soon as I click away from the 
> file edit page. THAT is my problem. "Submit" simply does not store the file.
> I have installed "Config File Provider 
> Plugin
>  2.4" 
> into "Jenkins 1.500" (running in TurnKeyLinux Jenkins appliance, based on 
> Debian 6).
>
>>  The "submit" button does not store any new config file I create using 
>> the "(cfg) Managed files" node. In fact, the "submit" button does not do 
>> *anything*.
>>  
>> The Jenkins log does not contain any error message since the key press.
>>  
>> This happens with all kinds of config file types.
>>  
>>  
>>  
>> What to do?
>>  
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Config File Provider Plugin" does not store new files

[Markus KARG]

Frank, you don't see the actual problem. "Submit" actually does NOTHING, 
hence, the file is NOT available anymore as soon as I click away from the 
file edit page. THAT is my problem. "Submit" simply does not store the file.

Am Freitag, 1. Februar 2013 17:53:02 UTC+1 schrieb Merrow, Frank:

>  Once you define a config file (hit submit) . . . you then go to each job 
> and say “add this config file to the workspace” . . . at least that is how 
> I use it.
>
>  
>
> We configure it so the path to the config file is left in a Environment 
> Variable and the program picks it up from there.
>
>  
>
> Nice when done this way, because if someone changes the definition, you 
> still have the definition that was USE FOR THE JOB in the workspace . . . 
> independent of the definition held by Jenkins.
>
>  
>
> Given the way I use it, no files are copied until the job starts to run . 
> . . “submit” defines, only “Build Now” (or other job startup) cause the 
> file to actually be moved into place.
>
>  
>
> Frank
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Markus KARG
> *Sent:* Friday, February 01, 2013 7:50 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* "Config File Provider Plugin" does not store new files
>
>  
>  
> I have installed "Config File Provider 
> Plugin
>  2.4" 
> into "Jenkins 1.500" (running in TurnKeyLinux Jenkins appliance, based on 
> Debian 6).
>  
> The "submit" button does not store any new config file I create using the 
> "(cfg) Managed files" node. In fact, the "submit" button does not do 
> *anything*.
>  
> The Jenkins log does not contain any error message since the key press.
>  
> This happens with all kinds of config file types.
>  
>  
>  
> What to do?
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Mandeville, Rob]

If you're running out of PermGen space, your problem is with your JVM.  Your 
CPU may be getting pegged because your JVM is desperately garbage collecting to 
get every last byte of storage left, but I could be wrong.  Basically, you're 
going to have to tell the JVM running your Jenkins instance to give you more 
PermGen space.

Find out (if you don't already know) which application server you're running 
Jenkins with (if you're launching it like "java -jar Jenkins.war", you're using 
the onboard WinStone app server), and which JVM you're running that server in.  
You'll have to determine how much PermGen space you're allocating (likely the 
default that your JVM gives) and how to tell the JVM running your App server to 
give it more.  Again, if you're launching Jenkins as a plain Java app and using 
WinStone, you can add the PermGen space arguments right to the Java command 
line.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kamal Ahmed
Sent: Friday, February 08, 2013 7:47 AM
To: jenkinsci-users@googlegroups.com
Subject: java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

Hi,
After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting
java.lang.OutOfMemoryError: PermGen space
After i click any link on Jenkins page, the CPU gets pegged 100%


This also happens when i let the page stay there and not click on anything.

Anyone found a resolution for this?
Thanks,
-Kamal.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: cygwin build step - quick question

[Mandeville, Rob]

My first guess is to write a Windows batch command step that just says 
something like "bash myBuildScript.sh".

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of zw
Sent: Thursday, February 07, 2013 4:35 PM
To: jenkinsci-users@googlegroups.com
Subject: cygwin build step - quick question

Hi All

How do we trigger a windows box to use cygwin and run its script?
In our build step, there isnt a choice for that.

Thanks
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

java.lang.OutOfMemoryError: PermGen space after upgrade to 1.500

[Kamal Ahmed]

Hi,
After i upgraded Jenkins to 1.500 on ubuntu 12.04 host. I am getting 
java.lang.OutOfMemoryError: PermGen space

After i click any link on Jenkins page, the CPU gets pegged 100%


This also happens when i let the page stay there and not click on anything.

Anyone found a resolution for this?

Thanks,
-Kamal.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: forcing a build to run through all downstream jobs

[cjo]

I assume that you have the jobs set up as 

every commit job -> testjob
tagged commits -> testjob

Try adding a dummy parameter that is passed from the tagged commits job, 
that is unique for each build, as the ParametersAction will cause 
a separate builds if there are different parameters passed to ones already 
in the queue.

This should then remove the "already in queue message".
Note you don't need to use the dummy parameter, or even declare it in the 
test job.
And as an easy way to generate the random parameter you could use the 
Random String parameter
if you don't use the tag itself.

https://wiki.jenkins-ci.org/display/JENKINS/Random+String+Parameter+Plugin

Chris.

On Friday, 8 February 2013 10:46:19 UTC, Chris Withers wrote:
>
> Hi All, 
>
> We have a job that continuously builds our distribution. 
>
> We also have a parameterized job that accepts a distribution from a tag, 
> for which we *need* to run all tests for audit/compliance reasons. 
>
> How can I make sure this second job actually causes all downstream jobs 
> to run? 
>
> Problems I've hit: 
>
> If the downstream test job is already running, the next test job that 
> runs has both the continuous build and parameterized build as causes, 
> which means it tries to copy artifacts from both, and blows up. 
>
> If the parameterized job is triggered twice, with two different 
> distributions, the second one never gets tested, as the build job for 
> the second build of the parameterized job says: 
>
> "test #10 is already in the queue" 
>
> Any help very gratefully received. 
>
> cheers, 
>
> Chris 
>
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting 
>  - http://www.simplistix.co.uk 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Jenkins] Running a project multiple times is leading to hungup

[cjo]

There is a known issue if the child jobs have "block if upstream is 
running" enabled as they see the triggering job as running,
which might be the issue that you are seeing.

If this is not the case, can you actually post the reasons that the pending 
jobs are not running (from the tooltip when hovering over the items in the 
Queue), as this will normally indicate the reason for the builds not 
running.

i.e. waiting for an Executor on slave1 or Waiting for Up/Downstream project 
to finish


Chris.


On Friday, 8 February 2013 07:58:58 UTC, Manjunath D G wrote:
>
> Hi All,
>
>  
>
> We have a project (parent) with multiple steps, one of the step being 
> configured as 'trigger/call a build on other projects' (i.e, child job)
>
> We have selected the option 'block until the triggered projects finish 
> their builds', so that Parent project will be on hold until the child 
> project gets completed.
>
> It works fine if we run the parent project one time.
> But, if we run another instance of the same Parent project, the child 
> project run (triggered from first run), goes into 'pending forever' state.
> Similarly, the second Parent project run also goes to 'pending forever'
>
> Please let us know if there is any fix/workaround.
>
> ===
> The projects are configured as:
>
> Parent Project:-
>
> -Step 1 (Some commands)
>
> -Step 2 (Invoke a “Child” project) – parent has to be in wait state until 
> the child completes
>
> -Step 3 (Some commands)
>
> Child Project:-
>
> -Step 1 (Some Commands)
> 
>  
> Regards,
> Manju
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

forcing a build to run through all downstream jobs

[Chris Withers]

Hi All,

We have a job that continuously builds our distribution.

We also have a parameterized job that accepts a distribution from a tag, 
for which we *need* to run all tests for audit/compliance reasons.


How can I make sure this second job actually causes all downstream jobs 
to run?


Problems I've hit:

If the downstream test job is already running, the next test job that 
runs has both the continuous build and parameterized build as causes, 
which means it tries to copy artifacts from both, and blows up.


If the parameterized job is triggered twice, with two different 
distributions, the second one never gets tested, as the build job for 
the second build of the parameterized job says:


"test #10 is already in the queue"

Any help very gratefully received.

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Error while building maven2 project.

[Роман Бесолов]

 I think this doesn't matter in this case. This project have no any 
dependencies from maven.glassfish.com. I think Jenkins have added them, but 
i don't know why.


Jenkins is running as different user and that user's cache dir does not 
> have the same files as yours has, maybe.
>
> -- Sami
>
> Роман Бесолов > kirjoitti 7.2.2013 kello 
> 14.24:
>
> I'm trying to build javamail1.4.5 (
> http://kenai.com/projects/javamail/downloads). I can build it manually 
> (by typing mvn install -DskipTests=true in terminal), but jenkins can't 
> build it. Jenkins is trying to download 
> http://maven.glassfish.org/content/groups/glassfish-group//org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom,
>  
> which doen't exists. I have no idea why it tries to download it. 
>
> [INFO] [enforcer:enforce {execution: enforce-maven}]
>> [INFO] [enforcer:enforce {execution: enforce-version}]
>> Downloading: 
>> http://maven.glassfish.org/content/groups/glassfish-group//org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom
>> 185b downloaded  (maven-plugin-api-2.0.4.pom)
>> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
>> '6c9fd3d150b8a5f0ca676f49b8ed603793cabebb'; remote = '
>> 301' - RETRYING
>> Downloading: 
>> http://maven.glassfish.org/content/groups/glassfish-group//org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom
>> 185b downloaded  (maven-plugin-api-2.0.4.pom)
>> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
>> '6c9fd3d150b8a5f0ca676f49b8ed603793cabebb'; remote = '
>> 301' - IGNORING
>> [WARNING] POM for 'org.apache.maven:maven-plugin-api:pom:2.0.4:runtime' is 
>> invalid.
>>
>>
>
> Full log you can see in attachment. Thanks for help!
>
>  -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>
> 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Parallel execution of builds

[JonathanRRogers]

 There are several ways to run jobs in parallel. I'm currently using a 
matrix job for this.

On Thursday, February 7, 2013 7:38:49 AM UTC-5, alvin Antony wrote:
>
> Hi Jenkins users,
>  
> I am new to this user group and new on administrating the jenkins. I have 
> requirement to enable the parallel execution of some maven module bulilds 
> but some of them are not parallelizable.
>  
> The reason is we have a test dependency in the database.  i.e. if we run 
> multiple  module builds from a branch in parallel it will run into 
> deadlock. 
> The set up look like this...
>  
> branch1(trunk)-> module 1, module 2, module 3
> branch2(prod)-> module 1, module 2, moudle 3
>  
> The branch 1 and branch2 has dedicated databases  i.e any module from 
> branch 1 can run in parallel with any module from branch 2 but none of the 
> modules from the same branch can run in parallel. 
>  
> How can i configure this? is there any plugin which supports this?
>  
> Thanks in advance,
>  
> Alvin
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Hardware resource plugin

[Sandell, Robert]

https://wiki.jenkins-ci.org/display/JENKINS/External+Resource+Dispatcher

It is currently in beta, but the more feedback we get the better we can make it 
;)


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkinsci-...@googlegroups.com [mailto:jenkinsci-...@googlegroups.com] On 
Behalf Of Justin Ryan
Sent: den 8 februari 2013 02:26
To: jenkinsci-...@googlegroups.com
Subject: Hardware resource plugin

In there iOS plugin there some concepts of a physical device attached to a 
slave, and executors are assigned to each one. Is there a more generic plugin 
that can do the same thing for arbitrary devices? For example, I'd like to have 
a slave with 4 serial ports, and have one executor dedicated to each one, i.e. 
/dev/ttyS0 for the first executor. It would have to support many slaves with a 
similar setup. I swear seeing references to such a plugin but I can't find it 
right now.

What I'd be using it for is to mount EBS volumes on different /dev/sdb* 
devices, then doing a chroot'd install of system packages, then un-mounting. 
AWS requires a unique /dev device when mounting these volumes, and linux only 
support a limited number of them, i.e. I can't create them on the fly. Having 
them per-executor REALLY simplifies things for me.

-justin

--
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 
jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.