Scripted Cloud plugin busy queue race condition

[blaz]

I'm attempting to use Scripted Cloud plugin to orchestrate system tests for 
a product. For most part I was able to achieve my goal.
Only remaining problem is that Scripted Cloud plugin fails to shutdown and 
restore virtual machine in time if another test (job) is already pending in 
build queue. In such case Jenkins slave on VM managed by Scripted Cloud 
plugin reconnects to master before plugin is able to shutdown VM. Queued 
test starts but is interrupted by virtual machine shutdown only seconds 
after it starts.
Slave is configured to use Java Web Start. Attached log should illustrate 
the problem.

I was unable to find solution for this problem. Is there any way to prevent 
queued job to start execution before Scripted Cloud plugin is able to 
shutdown VM?

My guess is that Scripted Cloud plugin should somehow instruct slave to 
stay disconnected and reconnect only after it is restarted by container.
Marking slave as temporarily offline is probably not a good solution, since 
this feature is needed to keep slave offline for VM maintenance.

Acceptable workaround would be to increase reconnect delay for a slave, but 
I cannot find any documentation about that.
Current reconnect delay seems to be 10 seconds. Connection from slave is 
reset only 16 seconds after reconnect. Increasing slave reconnect delay to 
60 seconds would probably solve problem for me.

-- 
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/d/optout.


jenkins.err.log
Description: Binary data

RE: Email only after all retries fail

[Slide]

There currently is not, but email-ext had an extension point for triggers,
so someone could implement a trigger for naginator that only sent on the
last attempt.
On Aug 5, 2014 2:41 PM, "Harpel, Craig"  wrote:

>  Naginator knows the last attempt, because it knows when to give up.
>
> What I’m asking is whether there is any integration between Naginator and
> one of the email plugins that will let me do this without writing scripts.
> It sounds like the answer is “no”.
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Tuesday, August 05, 2014 5:25 PM
> *To:* Jenkins User Mailing List
> *Subject:* Re: Email only after all retries fail
>
>
>
> How do you determine if the job will be the last attempt? If there is
> something in the environment or something like that which tells you it is
> the last attempt, you could use a pre-send script to cancel sending the
> email unless that condition was met.
>
>
>
> On Tue, Aug 5, 2014 at 1:44 PM, Harpel, Craig  wrote:
>
>   I’m trying to get Jenkins to send email to recipients only after the
> last attempted retry of a job fails.  In other words, I don’t want them
> getting email for all the failures; just if they **all** fail.  Is there
> a way to do that with the email-ext plugin and naginator?
>
>
>
> Thanks.
>
> Craig
>
>
>
> --
> 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/d/optout.
>
>
>
>
>
> --
> Website: http://earl-of-code.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/d/optout.
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

Re: Is Jenkins doing a git pull between each matrix element?

[Brian Moffat]

Hi Les,
In my case, I'm not bothered by the actual build time, which is under 1 
minute per solution.  The problem is that the matrix build does a full 
repository pull before each matrix element, when, in my case, it is 
completely unnecessary, and adds 30+ minutes to the build time.  Using 
slave servers to parallel-ize the builds would still each need to do the 
pull, but it would reduce it from 30+ to around 6 minutes (if I had 7 or 8 
slaves).  Seems like a high price to pay when I can use a single server and 
get it to 11 minutes total.  Couple that with our near-term future being 
one with a decreasing number of solutions (ultimately to 1), the need to 
parallel-ize (and the matrix project itself) will be removed.

The great thing about Jenkins, though, is that it provides a lot of 
flexibility in how to achieve your needs, and provides a lot of useful 
features.

On Tuesday, August 5, 2014 2:29:30 PM UTC-4, LesMikesell wrote:
>
> On Tue, Aug 5, 2014 at 1:16 PM, Brian Moffat  > wrote: 
> > Hi Mark, 
> > The advantage of using my kludge as opposed to using a script to iterate 
> > through the builds is that Jenkins has all this great messaging (hipchat 
> / 
> > email) and log capture that I would have to "re-implement". And I have a 
> > monitoring/reporting infrastructure in place that is based on the 
> current 
> > matrix-based process - that too would need to change.  Certainly not 
> > insurmountable, but extra work.  I do appreciate your input and will 
> make 
> > use of it in designing the evolution of our CI/CD process as our 
> development 
> > environment evolves. 
> > 
>
> Keep in mind that you do have the option of throwing resources at it 
> to speed the jobs up - that is add slave nodes that would do 
> independent checkouts and run the builds in parallel.  If you are 
> bothered by a few extra minutes in a serialized run, it seems like the 
> way you should be thinking for a real speedup. 
>
> -- 
>Les Mikesell 
>  lesmi...@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/d/optout.

RE: Email only after all retries fail

[Harpel, Craig]

Naginator knows the last attempt, because it knows when to give up.
What I’m asking is whether there is any integration between Naginator and one 
of the email plugins that will let me do this without writing scripts.  It 
sounds like the answer is “no”.


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Tuesday, August 05, 2014 5:25 PM
To: Jenkins User Mailing List
Subject: Re: Email only after all retries fail

How do you determine if the job will be the last attempt? If there is something 
in the environment or something like that which tells you it is the last 
attempt, you could use a pre-send script to cancel sending the email unless 
that condition was met.

On Tue, Aug 5, 2014 at 1:44 PM, Harpel, Craig 
mailto:char...@mitre.org>> wrote:
I’m trying to get Jenkins to send email to recipients only after the last 
attempted retry of a job fails.  In other words, I don’t want them getting 
email for all the failures; just if they *all* fail.  Is there a way to do that 
with the email-ext plugin and naginator?

Thanks.
Craig

--
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/d/optout.



--
Website: http://earl-of-code.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/d/optout.

-- 
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/d/optout.

Re: Email only after all retries fail

[Slide]

How do you determine if the job will be the last attempt? If there is
something in the environment or something like that which tells you it is
the last attempt, you could use a pre-send script to cancel sending the
email unless that condition was met.


On Tue, Aug 5, 2014 at 1:44 PM, Harpel, Craig  wrote:

>  I’m trying to get Jenkins to send email to recipients only after the
> last attempted retry of a job fails.  In other words, I don’t want them
> getting email for all the failures; just if they **all** fail.  Is there
> a way to do that with the email-ext plugin and naginator?
>
>
>
> Thanks.
>
> Craig
>
>
>
> --
> 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/d/optout.
>



-- 
Website: http://earl-of-code.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/d/optout.

Email only after all retries fail

[Harpel, Craig]

I'm trying to get Jenkins to send email to recipients only after the last 
attempted retry of a job fails.  In other words, I don't want them getting 
email for all the failures; just if they *all* fail.  Is there a way to do that 
with the email-ext plugin and naginator?

Thanks.
Craig

-- 
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/d/optout.

Re: Tag this Build - How to tag that build's workspace?

[Les Mikesell]

On Tue, Aug 5, 2014 at 10:22 AM, Eric  wrote:
> Is it safe to create a tag the following way so that I can do what I want?
>
> svn upgrade
> svn copy -m "Creating a Tag"
> https:/url/svn/test/HelloWorld/trunk@%PROMOTED_SVN_REVISION%
> https://url/svn/test/HelloWorld/tags/%Tst Tag%
> copy
> C:\Users\user\.jenkins\jobs\HelloWorld_Promote\builds\%PROMOTED_ID%\archive\Test\buildnum.txt
> C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test
> svn delete -m "Deleting file before updating"
> https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test
> svn copy -m "Adding updated file to tag"
> C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test
> https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test
>
> Doing it this way, I can select a build and promote it using the promote
> build plugin. It first creates a tag at the builds revision. It then copies
> that builds artifacts to the workspace so it can then add it to the tag that
> was just created.
>

If that 'svn upgrade' command actually changes the working copy to a
different client level format than jenkins uses, the next build won't
be able to update to the next revision.

-- 
   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/d/optout.

Re: Best Practices to get metrics from Hudson server about jobs

[Alexy Thomas]

Hi,

Is there any plugin in Jenkins that would give me data/reports based on the
entire pipeline? For example:
1. Time stamp of the green build at the end of the pipeline.
2. Cycle Time that took for the particular snapshot to go through the
pipeline before it became succesful green.
3. Number of times it failed before becoming green at the end of pipeline. 

Any kind of feedback would be appreciated.

Thank you!



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Best-Practices-to-get-metrics-from-Hudson-server-about-jobs-tp2270614p4713086.html
Sent from the Jenkins users mailing list archive at Nabble.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/d/optout.

Re: Is Jenkins doing a git pull between each matrix element?

[Les Mikesell]

On Tue, Aug 5, 2014 at 1:16 PM, Brian Moffat  wrote:
> Hi Mark,
> The advantage of using my kludge as opposed to using a script to iterate
> through the builds is that Jenkins has all this great messaging (hipchat /
> email) and log capture that I would have to "re-implement". And I have a
> monitoring/reporting infrastructure in place that is based on the current
> matrix-based process - that too would need to change.  Certainly not
> insurmountable, but extra work.  I do appreciate your input and will make
> use of it in designing the evolution of our CI/CD process as our development
> environment evolves.
>

Keep in mind that you do have the option of throwing resources at it
to speed the jobs up - that is add slave nodes that would do
independent checkouts and run the builds in parallel.  If you are
bothered by a few extra minutes in a serialized run, it seems like the
way you should be thinking for a real speedup.

-- 
   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/d/optout.

Re: Is Jenkins doing a git pull between each matrix element?

[Brian Moffat]

Hi Mark,
The advantage of using my kludge as opposed to using a script to iterate 
through the builds is that Jenkins has all this great messaging (hipchat / 
email) and log capture that I would have to "re-implement". And I have a 
monitoring/reporting infrastructure in place that is based on the current 
matrix-based process - that too would need to change.  Certainly not 
insurmountable, but extra work.  I do appreciate your input and will make 
use of it in designing the evolution of our CI/CD process as our 
development environment evolves.

Thanks!
Brian

On Monday, August 4, 2014 10:43:07 PM UTC-4, Mark Waite wrote:
>
>
>
>
> On Mon, Aug 4, 2014 at 3:02 PM, Brian Moffat  > wrote:
>
>> Hi Mark,
>> Ok - I can see that my use-case is not universal and is likely on the 
>> "very simple" end of the spectrum.  I am currently not using distributed 
>> builds. My builds of multiple portals use the same code base and are 
>> serialized - therefore one checkout is all that is needed to build all of 
>> them.  In the short term, I'm thinking of doing the following - please tell 
>> me if this is an abomination in the Jenkins world.
>>
>
> Not an abomination, but it seems complicated to me. 
>  
>
>> I will create a new project that is not a matrix job and is triggered by 
>> an SCM change.  All it will do is the git checkout, and call a single 
>> downstream project, which will be the existing matrix project (without a 
>> trigger) that has the git section deleted and simply invokes the downstream 
>> build project iterating through the matrix elements.  My assumption is that 
>> since the SCM-triggered project will only do one checkout (explicitly or 
>> implicitly - since it is not a matrix project), and since the downstream 
>> projects do not have any git configurations, they will not do any checkouts 
>> either.
>>
>
> I'm not sure what benefit you gain from a matrix job in that case.  Since 
> builds are serialized, and able to use a single project which iterates 
> through the matrix elements one at a time, why not just create a single 
> freestyle project which calls a script that iterates through the projects 
> and builds each project?
>
> Using a starter job to do the checkout, then a matrix job to build the 
> configurations seems like an interesting way to iterate through the 
> configurations, but aren't the configurations already expressed in the 
> source code, so you can write a script (MSBuild, perl, python, Java, etc.) 
> which iterates through those configurations and builds each of them.
>  
>
>> Feels like a kludge, but i think the result will be a complete build in 
>> 11 minutes as opposed to 30.
>>
>> Do you agree?
>>
>> Thanks,
>> Brian
>>
>> On Monday, August 4, 2014 2:47:01 PM UTC-4, Mark Waite wrote:
>>>
>>>
>>> On Mon, Aug 4, 2014 at 12:24 PM, Brian Moffat  wrote:
>>>
 Thanks Mark.
 I have a couple of follow-up questions, if you don't mind.

 1.  I've seen it work - meaning that the matrix project would do one 
 checkout and the downstream projects would run one after the other with no 
 lengthy pause between.  So I'm left feeling like there should be a way to 
 "get back to that" without the suggestions you made - since I've not 
 modified the project configs since seeing it work.  It may be that at the 
 time it was an "unintended feature" that got removed by a plug-in update, 
 but that's pure conjecture on my part.

>>>
>>> I'm reasonably sure that it has always behaved that way.  Each job in a 
>>> matrix (multi-configuration) project may be on a separate machine, so each 
>>> job performs a "git fetch" followed by a "git checkout".  However, if you 
>>> can find versions of the git plugin and the git client plugin which behave 
>>> the way you want, you could compare the source code of the current plugin 
>>> and the version behaving the way you want to see if you can identify the 
>>> cause of the behavioral change.
>>>  
>>>
 2.  Why does the matrix job always do a "get a full copy" of the 
 repository before invoking the downstream job?  If that's what I wanted, I 
 would have the downstream job do the pull.  To me it looks like a bug, not 
 an enhancement request.  What am I missing?

>>>
>>> I believe that each job in the matrix job needs an independent copy of 
>>> the repository so that it can work independent of the other jobs in the 
>>> matrix.
>>>  
>>>
 -Brian

 On Monday, August 4, 2014 1:41:08 PM UTC-4, Mark Waite wrote:
>
>
>
>
> On Mon, Aug 4, 2014 at 10:11 AM, Brian Moffat  
> wrote:
>
>> I have a matrix project to build different C# projects/solutions. 
>>  There is one git repository for all solutions.
>>
>> The matrix job is configured for Git to checkout the master branch to 
>> a local directory, and then invokes a downstream project for each matrix 
>> element (solution).  That downstream project has not Git configuration, 
>>

How to use Measurements Plot Plugin?

[Andrew Pritykin]

Hi everyone,

I have a JS file that looks to see how long it takes to load a webpage. 
Once the page loads it saves the result (time in ms) to a file. After 
looking at the Measurements Plugin I see its a extension to the Junit Test 
result post build.

currently my script writes to a file "time_load.xml" and writes the 
following for example: 

Time (ms)11352


When my build finishes it fails and this is the console output:


Loading time 11352 msec
Recording test results
None of the test reports contained any result
Build step 'Publish JUnit test result report' changed build result to FAILURE
Finished: FAILURE


Anyone have experience with this plugin or understand how to get this to work?


https://wiki.jenkins-ci.org/display/JENKINS/Measurement+Plots+Plugin


Thanks,

Andrew

-- 
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/d/optout.

Re: Tag this Build - How to tag that build's workspace?

[Eric]

Is it safe to create a tag the following way so that I can do what I want?

svn upgrade
svn copy -m "Creating a Tag" 
https:/url/svn/test/HelloWorld/trunk@%PROMOTED_SVN_REVISION% 
https://url/svn/test/HelloWorld/tags/%Tst Tag% 
copy 
C:\Users\user\.jenkins\jobs\HelloWorld_Promote\builds\%PROMOTED_ID%\archive\Test\buildnum.txt
 
C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test
svn delete -m "Deleting file before updating" 
https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test
svn copy -m "Adding updated file to tag" 
C:\Users\user\.jenkins\jobs\HelloWorld_Promote\workspace\Test 
https://url/svn/test/HelloWorld/tags/%Tst Tag%/Test

Doing it this way, I can select a build and promote it using the promote 
build plugin. It first creates a tag at the builds revision. It then copies 
that builds artifacts to the workspace so it can then add it to the tag 
that was just created.

On Thursday, July 17, 2014 4:27:37 PM UTC-4, pcampbell wrote:
>
> You can only tag revisions of a file that have been committed to your scm. 
> You would have to commit the change to the buildnum.txt file which would 
> increment the revision number and tag that.  
>
> Tagging does not make a copy of files from your workspace, it just makes a 
> list of pointers within the scm to specific revisions of a file.  If you 
> haven't committed the change, there is no new revision to tag so you will 
> get the last revision that was committed.
>
>
>
>
> On Thu, Jul 17, 2014 at 1:10 PM, Eric > 
> wrote:
>
>> I'm trying to tag a build with "Tag this build" and use that build's 
>> workspace, not the workspace revision.
>>
>> For instance, I set up Jenkins with my repository. Every time it does a 
>> build it creates a text file called buildnum.txt. The only thing in this 
>> text file is the current build number. So build #4 has 4 inside the text 
>> file, Build #16 has 16... etc. This buildnum.txt is packaged inside of a 
>> .war file. The reason for this, is so that I later know which build the war 
>> file came from.
>>
>> So If I go back to build #4 (and the latest build is #16) and tag it, I 
>> want, in the tags part of the repository, to have the war file with 
>> buildnum.txt that says "4"
>>
>> I believe the issue I'm having right now, is that I'm doing manual builds 
>> where the repository hasn't changed (right now just for testing). 
>> Therefore, the revision number is staying the same, but the buildnum.txt is 
>> changing. 
>>
>> For instance, I just clicked "Build Now" and Build #364 succeeded. A .war 
>> file was created with buildnum.txt inside that says 364. The build says 
>> "Revision: 220 No changes" and when I click "Tag this Build" the Module URL 
>> says "https://name/svn/test/HelloWorld/trunk (rev.220)"
>> If I click tag and go to the repository and under tags select the new tag 
>> I just created. The text file says "344" not "364" as I want. 
>>
>> I'm assuming this is because the trunk hasn't changed at all since build 
>> 344, so it is using what was last changed. 
>>
>> Is there a way to do this? I'm also open to better ideas.
>>
>> 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-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/d/optout.

Re: Need some helps on Jenkin SCM Polling....

[Johan Wranker]

Try to add /opt/rational/clearcase/bin in the .cshrc file (depending on 
shell of cause) of the jenkins-user.
Without the -login flag isn't shell startup file read.
/Johan 

Den måndagen den 4:e augusti 2014 kl. 17:55:07 UTC+2 skrev lingfei ouyang:
>
> Hello All,
>
> Im currently created the jenkin builds with Simple Dynamic ClearCase 
> Pollings and when it start polling I got below error:
>
> $ cleartool setview -exec 'cleartool lshistory -branch branch1 -last 10 -fmt 
> "%Nd| |%u| |%En| |%Vn| |%e| |%o| |%Nc\n" -nco /vobs/arch' view1
> FATAL: Cannot run program "cleartool" (in directory "X"): error=2, No 
> such file or directoryjava.io.IOException 
> : Cannot 
> run program "cleartool" (in directory "X"): error=2, No such file or 
> directory
>   at java.lang.ProcessBuilder.start(ProcessBuilder.java:459) 
> 
>   at hudson.Proc$LocalProc.(Proc.java:244) 
> 
>   at hudson.Proc$LocalProc.(Proc.java:216) 
> 
>   at hudson.Launcher$LocalLauncher.launch(Launcher.java:780) 
> 
>   at hudson.Launcher$ProcStarter.start(Launcher.java:360) 
> 
>   at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:) 
> 
>   at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1078) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:118) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:48) 
> 
>   at hudson.remoting.Request$2.run(Request.java:328) 
> 
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>  
> 
>   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 
> 
>   at java.util.concurrent.FutureTask.run(FutureTask.java:138) 
> 
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  
> 
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  
> 
>   at java.lang.Thread.run(Thread.java:619) 
> 
> Caused by: java.io.IOException 
> : error=2, 
> No such file or directory
>   at java.lang.UNIXProcess.forkAndExec(Native Method)
>   at java.lang.UNIXProcess.(UNIXProcess.java:53)
>   at java.lang.ProcessImpl.start(ProcessImpl.java:65)
>   at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)
>   ... 15 more
> Done. Took 0.85 sec
> No changes
>
>
>
> And I do tried setup the PATH = /opt/rational/clearcase/bin in both 
> Environment Variables under the Global Properties and also under the Notes' 
> Properties. and restarted the jenkins and it still getting the same error.
>
>
> So I'm stuck in here and need some help on this.
>
>
> Thanks
> Ling
>
>

-- 
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/d/optout.

HowTo trigger 'needed' jobs instead of all (2 jobs instead of 100+ )

[Johan Wranker]

Some background since Autosar  isn't standard Jenkins 
environment.
- The produced artifacts are called SWC (Autosar Software Components)
- The interfaces between the SWCs are stored in a database and from that is 
the interface Contract for a specific SWC extracted.
- There are 100+ SWCs and the generation/compilation/tests of those takes 
many hours. 
- The job-history is relevant for each SWC i.e. individual pipelines. 
- A change in the interface database does only affect one or a few of the 
SWCs.
- It is fast to generate extracts of the interface Contract for each SWC 
(and to get the fingerprint) 

I do think you see the goal here; Only rebuild/retest the affected SWCs 
when the interface database is updated.

Below are my ideas but I would like to have your recommendations how to do 
that.
A) Generate Contracts for all SWCs and locate the updated - trigger the 
build job for specific SWC(s). 
I haven't seen a plugin which can do that and thereby I expect that 
there is a better way to do it.

B) Generate and push the updated Contracts as artifacts to an artifact 
repository and let that trigger the build job (Maven style).

C) Include the Contract fingerprint in the SWC artifact pushed to artifact 
repository. Generate Contracts (as in A) and trigger a job if there is no 
SWC artifact stored with that id.

D) Something completely different...

-- 
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/d/optout.

Re: Reg: jenkins build Error

[Jason Korth]

export ANT_OPTS=-Xmx256m







On Tue, Aug 5, 2014 at 7:38 AM, bandi pavankumar reddy <
pavanreddy...@gmail.com> wrote:

> Hi friends i am doing java source files building in Jenkins...some
> build.xml files having huge source file's in Jenkins i am trying to build
> in compile target it was displaying error showing to solve that error give
> to me any suggestion's i am sending that error
> I am getting this error for building ant file's
>
> *pre-initi*:
> *compile*:
> [javac] Compiling 30450 source files to D:\Build\ClientBuild1\Client\build
> [javac]
> [javac]
> [javac] The system is out of resources.
> [javac] Consult the following stack trace for details.
> [javac] java.lang.OutOfMemoryError: Java heap space
> [javac]   at com.sun.tools.javac.util.ListBuffer.clear(ListBuffer.java:55)
> [javac]   at com.sun.tools.javac.util.ListBuffer.
>
>  --
> 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/d/optout.
>

-- 
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/d/optout.

Reg: jenkins build Error

[bandi pavankumar reddy]

Hi friends i am doing java source files building in Jenkins...some
build.xml files having huge source file's in Jenkins i am trying to build
in compile target it was displaying error showing to solve that error give
to me any suggestion's i am sending that error
I am getting this error for building ant file's

*pre-initi*:
*compile*:
[javac] Compiling 30450 source files to D:\Build\ClientBuild1\Client\build
[javac]
[javac]
[javac] The system is out of resources.
[javac] Consult the following stack trace for details.
[javac] java.lang.OutOfMemoryError: Java heap space
[javac] at com.sun.tools.javac.util.ListBuffer.clear(ListBuffer.java:55)
[javac] at com.sun.tools.javac.util.ListBuffer.

-- 
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/d/optout.

Jenkins Module Build Behaviour

[Grueneberger, Franz Josef]

Hi all,

I have a multi-module maven project in Jenkins and observe the following build 
behavior from time to time.

The multi-module project has concurrent builds enabled. In most of the cases 
everything is fine and the output is as follows:

[cid:image005.png@01CFB0A6.7F77EFA0]

However, from time to time for two subsequently started builds the following 
behavior can be observed:

[cid:image006.png@01CFB0A6.7F77EFA0]

While the next build shows then:
[cid:image007.png@01CFB0A6.7F77EFA0]

Any ideas what is going wrong there and how I can circumvent the behavior?

Thanks and best,
Franz

-- 
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/d/optout.