Re: priority sorter plugin

[Jayaprakash D B]

Did you enable concurrent builds on the project configuration page? If not,
you should do that.


On Wed, Jun 11, 2014 at 4:29 PM,  wrote:

> Hi Jayaprakash D B,
>
> thank you for this post. I am facing the same problem like you did and
> wanted to ask you, whether you were able to solve it in between?
>
> I've chosen "Use Priority from Build Parameter" and tried to forward the
> Parameter via URL the following way:
>
> http://localhost:8080/job/myJobName/buildWithParameters?PARAM1=value1&PARAM2=value2&BuildPriority=1
>
>
> Where the last argument "BuildPriority" is the standard name defined by the 
> Plugin (didn't change it).
>
>
> I tried to start the build process from this stage with no more changes but 
> found, that every parameter works but not the "BuildPriority".
>
> Because I realized, that I added all other parameters manually to the build 
> job, but didn't do this for "BuildPriority" I tried to add
>
> parameters with exactly that name. Once I tried as string paramater, another 
> time as option box parameter. But none of the ways worked for me.
>
> Starting th eprocess and passing parameters works fine, but not the priority.
>
>
> Thank you very much
>
>  --
> 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.

stop jenkins stop with success status

[Maneesh M P]

Hello,

  Is there a way I can stop/exit a build with success status? 
  I need this feature top my build triggering one dowstream job based on a 
condition

Thanks
Maneesh

-- 
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.

[ANN] Continuous Delivery with Jenkins events: NYC 6/19 and Berlin 6/24

[Kohsuke Kawaguchi]

If you will be on the US East Coast or in Berlin for JUC, some of the 
JUC sponsors are organizing separate events called Continuous Delivery 
Seminar, which might be of interest to you. These events focus more on 
higher-level business value questions as well as vendor solutions that 
are difficult in community-focused JUC.


  * New York City on June 19 [1],the day after JUC US East -€“ headlined
by Forrester Research analyst Kurt Bittner

  * Berlin on June 24 [2], the day before JUC Europe - headlined by Jan
Hagen, author of "Confronting Mistakes: Lessons from the Aviation
Industry when Dealing with Errors"

I'm one of the speakers, and I'll be talking about Jenkins, as always!

[1] http://www.cloudbees.com/cdsummit/nyc
[2] http://www.cloudbees.com/cdsummit/berlin
--
Kohsuke Kawaguchi

--
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-events mailing list
jenkins-eve...@lists.jenkins-ci.org
http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events

Re: Build Fails with Failed to install JDK. Exit code=1,603

[Patrick Auld]

I'm also seeing this problem. It appears that the auto installers for the 
JDK we had were "mixed up", non of the Java versions had the correct 
installers after updating Jenkins to 1.5.67. Deleting the JDK's directory 
from the hudson.model.JDK directory to force a reinstall didn't work. Non 
did correcting the installer versions in the Jenkins config. Any insight 
would be very helpful us anyone has any ideas.

On Friday, March 14, 2014 1:42:18 AM UTC-7, ka...@quipsy.de wrote:
>
> That is not a solution to the cause of the problem but just a workaround 
> for people being happy with the JDK preinstalled on the host already. You 
> just skip installation of the JDK, but you do not make it work using this. 
> People suffering from the same problem but NEED the a particular JDK 
> installation for a job still need a real solution!
>
> Am Mittwoch, 4. Dezember 2013 10:39:25 UTC+1 schrieb Michael Martfel:
>>
>> Found the solution:
>>
>>
>>
>>1. Go to the URL on your Jenkins master server: 
>>http://jenkins-master1:8080/configure#section3
>>2. Click on "Configuration" on the upper left side of the screen and 
>>choose "JDK"
>>3. Delete all JDK installers which are shown in the JDK section --> "JDK 
>>installations".
>>
>>
>> Worked for me.
>>
>> Good luck.
>>
>> Michael
>>
>> בתאריך יום חמישי, 28 בנובמבר 2013 18:18:36 UTC+2, מאת Michael Martfel:
>>>
>>>
>>> Hello,
>>>
>>> I am having issues with my first build with Jenkins.
>>>
>>> My Master Jenkins is on Ubuntu 12.03 LTS. Jenkins ver. 1.509.4
>>> Trying to run a build on a Windows 2008 R2 slave.
>>>
>>> I am a newbie with Jenkins and your help is much appreciated. 
>>>
>>> *This is the error I receive in the Windows Jenkins Slave:*
>>>
>>> Product: Java SE Development Kit 7 Update 45 (64-bit) -- Error 
>>> 1722.There is a problem with this Windows Installer package. A program run 
>>> as part of the setup did not finish as expected. Contact your support 
>>> personnel or package vendor.  Action charsets, location: C:\Program 
>>> Files\Java\jdk1.7.0_45\jre\lib\, command: "C:\Program 
>>> Files\Java\jdk1.7.0_45\jre\lib\\launcher.exe" "C:\Program 
>>> Files\Java\jdk1.7.0_45\bin\\unpack200.exe" -r -v -l "" "C:\Program 
>>> Files\Java\jdk1.7.0_45\\jre\lib\charsets.pack" "C:\Program 
>>> Files\Java\jdk1.7.0_45\\jre\lib\charsets.jar" 
>>>
>>> *This is the error I receive in the Jenkins build log:*
>>>
>>> Started by user anonymous
>>> Building remotely on jenkins-winslave in workspace 
>>> C:\Jenkins\workspace\Discovery Build and UT
>>> Installing C:\Jenkins\tools\hudson.model.JDK\JDK7u45\jdk.exe
>>> [JDK7u45] $ C:\Jenkins\tools\hudson.model.JDK\JDK7u45\jdk.exe /s /v /qn 
>>> /L "C:\Jenkins\tools\hudson.model.JDK\JDK7u45\jdk.exe.install.log" 
>>> REBOOT=ReallySuppress INSTALLDIR="C:\Jenkins\tools\hudson.model.JDK\JDK7u45"
>>> Failed to install JDK. Exit code=1,603
>>> === Logging started: 28/11/2013  18:02:40 ===
>>> Action start 18:02:40: INSTALL.
>>> Action start 18:02:40: AppSearch.
>>> Action ended 18:02:40: AppSearch. Return value 1.
>>> Action start 18:02:40: LaunchConditions.
>>> Action ended 18:02:40: LaunchConditions. Return value 1.
>>> Action start 18:02:40: FindRelatedProducts.
>>> Action ended 18:02:40: FindRelatedProducts. Return value 0.
>>> Action start 18:02:40: ValidateProductID.
>>> Action ended 18:02:40: ValidateProductID. Return value 1.
>>> Action start 18:02:40: setUserProfileNT.
>>> Action ended 18:02:40: setUserProfileNT. Return value 1.
>>> Action start 18:02:40: setAllUsersProfile2K.
>>> Action ended 18:02:40: setAllUsersProfile2K. Return value 1.
>>> Action start 18:02:40: CostInitialize.
>>> Action ended 18:02:40: CostInitialize. Return value 1.
>>> Action start 18:02:40: FileCost.
>>> Action ended 18:02:40: FileCost. Return value 1.
>>> Action start 18:02:40: IsolateComponents.
>>> Action ended 18:02:40: IsolateComponents. Return value 1.
>>> Action start 18:02:40: CostFinalize.
>>> Action ended 18:02:40: CostFinalize. Return value 1.
>>> Action start 18:02:40: SetARPReadme.
>>> Action ended 18:02:40: SetARPReadme. Return value 1.
>>> Action start 18:02:40: SetODBCFolders.
>>> Action ended 18:02:40: SetODBCFolders. Return value 1.
>>> Action start 18:02:40: MigrateFeatureStates.
>>> Action ended 18:02:40: MigrateFeatureStates. Return value 0.
>>> Action start 18:02:40: InstallValidate.
>>> Action ended 18:02:40: InstallValidate. Return value 1.
>>> Action start 18:02:40: RemoveExistingProducts.
>>> Action ended 18:02:40: RemoveExistingProducts. Return value 0.
>>> Action start 18:02:40: InstallInitialize.
>>> Action ended 18:02:42: InstallInitialize. Return value 1.
>>> Action start 18:02:42: ProcessComponents.
>>> Action ended 18:02:42: ProcessComponents. Return value 1.
>>> Action start 18:02:42: UnpublishComponents.
>>> Action ended 18:02:42: UnpublishComponents. Return value 1.
>>> Action start 18:02:42: MsiUnpublishAssemblies.
>>> Action ended 18:02:42: MsiUnpublishAssemblies. Return value 1.
>>> Action sta

Re: jenkins CI with docker

[Richard Bywater]

Sorry, ignore my previous reply - I didn't realise that you were already
using the Docker Plugin and that we'd already communicated in another
thread. Presumably you are looking for more of a discussion around usage of
Docker & Jenkins in general :)

Richard.


On Thu, Jun 12, 2014 at 6:28 AM, Gallagher Polyn 
wrote:

> I'm new to Jenkins and to Docker, so, naturally, I'm attempting use of
> both together :)
>
> I've successfully duplicated the Docker-Jenkins CI steps shown at
> www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins
> and I've looked with interest also at the approaches described in the two
> additional Docker-CI references, farther below.
>
> Writers on Docker-CI assert that the lightweight nature of Docker
> containers allow faster testing, because Docker test environments can very
> easily be created, modified and reused by the CI server.
>
> My question is whether Docker's lightweight nature also allows better
> exploitation of Jenkins' master-slave paradigm. Under this, I might expect
> that several Docker slaves on some slave Docker host could run in parallel.
> Thus, test suites would be broken down and run in parallel on a slave host
> and not sequentially.
>
> But are there already established techniques for the full exploitation of
> the compute power of slave hosts, whatever the role of Docker?
>
> Thanks, G
>
>
> http://developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html
>
> http://www.ebaytechblog.com/2014/05/12/delivering-ebays-ci-solution-with-apache-mesos-part-ii/#.U5d-VJRdXCd
>
>  --
> 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: Chaining Security Realm for fallback

[alex ouzounis]

Hi Momin,

I would be really interested to know if you found an answer to your 
question. 

I have a similar issue I am trying to resolve.

Many thanks,

Alex

On Wednesday, March 5, 2014 4:28:35 AM UTC, Momin wrote:
>
> Hi Guys, 
>
> Does jenkins have a fallback mechanism for its security realm? 
>
> I am using the Active Directory plugin. 
>
> Use Case:  If one has AD based user auth configured (typical corporate 
> environment), but also needs a few technical users (like a Jenkins 
> instance) 
> which are not in the corporate AD. 
> A side benefit for that is, that one can hard-code a 
> "backup-administrator" 
> which can be used, if one accidentally breaks the AD configuration or if 
> the 
> AD isn't available at all. 
>
> Please let me know if anybody knows how to configure such a setup. 
>
> Best Regards, 
> Momin Noor Khan 
>
>
>
> -- 
> View this message in context: 
> http://jenkins-ci.361315.n4.nabble.com/Chaining-Security-Realm-for-fallback-tp4693044.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: jenkins CI with docker

[Richard Bywater]

On my phone so can't check those links fully yet but you probably want to
give the Jenkins Docker plugin a go. This exposes Docker as a cloud slave
provider so you can dynamically spin up a slave of a particular flavour to
run your job on.

HTH
Richard

On Thursday, June 12, 2014, Gallagher Polyn 
wrote:

> I'm new to Jenkins and to Docker, so, naturally, I'm attempting use of
> both together :)
>
> I've successfully duplicated the Docker-Jenkins CI steps shown at
> www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins
> and I've looked with interest also at the approaches described in the two
> additional Docker-CI references, farther below.
>
> Writers on Docker-CI assert that the lightweight nature of Docker
> containers allow faster testing, because Docker test environments can very
> easily be created, modified and reused by the CI server.
>
> My question is whether Docker's lightweight nature also allows better
> exploitation of Jenkins' master-slave paradigm. Under this, I might expect
> that several Docker slaves on some slave Docker host could run in parallel.
> Thus, test suites would be broken down and run in parallel on a slave host
> and not sequentially.
>
> But are there already established techniques for the full exploitation of
> the compute power of slave hosts, whatever the role of Docker?
>
> Thanks, G
>
>
> http://developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html
>
> http://www.ebaytechblog.com/2014/05/12/delivering-ebays-ci-solution-with-apache-mesos-part-ii/#.U5d-VJRdXCd
>
>  --
> 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.

jenkins CI with docker

[Gallagher Polyn]

I'm new to Jenkins and to Docker, so, naturally, I'm attempting use of both 
together :)

I've successfully duplicated the Docker-Jenkins CI steps shown at 
www.activestate.com/blog/2014/01/using-docker-run-ruby-rspec-ci-jenkins and 
I've looked with interest also at the approaches described in the two 
additional Docker-CI references, farther below.

Writers on Docker-CI assert that the lightweight nature of Docker 
containers allow faster testing, because Docker test environments can very 
easily be created, modified and reused by the CI server.

My question is whether Docker's lightweight nature also allows better 
exploitation of Jenkins' master-slave paradigm. Under this, I might expect 
that several Docker slaves on some slave Docker host could run in parallel. 
Thus, test suites would be broken down and run in parallel on a slave host 
and not sequentially.

But are there already established techniques for the full exploitation of 
the compute power of slave hosts, whatever the role of Docker?

Thanks, G

http://developer.rackspace.com/blog/move-fast-and-dont-break-things-testing-with-jenkins-ansible-and-docker.html
http://www.ebaytechblog.com/2014/05/12/delivering-ebays-ci-solution-with-apache-mesos-part-ii/#.U5d-VJRdXCd

-- 
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: Multijob plugin: Using same commit everywhere

[Drew Van Stone]

Did you ever get this worked out? I'm having the same issue.

On Tuesday, November 12, 2013 7:42:24 AM UTC-7, Kevin Fleming wrote:
>
> That's how matrix (multi) jobs work; the master job learns what the proper 
> SCM commit is, then it is communicated to all of the subjobs in the matrix 
> when they are launched.
>
> If your subjobs have child jobs, then you'd need to communicate the commit 
> information to them the same as you would with any other parent/child job 
> relationship.
>
> - Original Message -
> From: jenkins...@googlegroups.com 
> To: jenkins...@googlegroups.com 
> At: Nov 12 2013 00:06:38
>
> How does one configure the MultiJob plugin to use the same commit for all 
> the jobs?
>
> I am creating a MultiJob "Foo" which then kicks off multiple phases and 
> steps in each phase which should use the same git commit as the parent job.
>
> Thanks.
>
> R,
> rahul
> -- 
> 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/d/optout.

Set number of executors on slave with Groovy

[David Engster]

I have the problem that I need to run a job on a slave exclusively,
meaning without any other jobs running on that slave at the same time. I
know there's the "Exclusive Execution" plugin, but that is taking the
master offline during that time, which I find rather drastic. I'd like
to do this in a less disruptive way with a Groovy system script:

- Job starts on Slave and first sets its number of executors with
  setNumExecutors() to '1'. This will not interrupt running jobs, but
  will make the slave not accept any new ones, which is exactly what I'd
  like.

- Job waits until all other jobs on the slave are finished (by checking
  countBusy())

- Job does whatever it needs to do exclusively.

- Job sets number of executors to old value and exits.

I've pretty much figured it out, except for one thing: setting the
number of executors on a slave. I tried doing

Hudson.instance.getComputer("SlaveName").setNumExecutors(1)

but that does not work, since 'SlaveComputer' does not implement this
method:

  groovy.lang.MissingMethodException: No signature of method:
 hudson.slaves.SlaveComputer.setNumExecutors() is applicable for
 argument types: (java.lang.Integer) values: [2]
  Possible solutions: getNumExecutors(), getExecutors()

I can only call 'setNumExecutors' on the Jenkins instance itself, but
that will always apply to the master node.

As an alternative, I did set the slave temporarily offline, which is
possible with the 'Computer' object, but that doesn't play well with
jobs which are already running: while they don't get aborted, it seems
those jobs can often not exit cleanly when they still need to work on
the remote file system.

Any ideas?

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

Re: svn update work on running client from JNLP but not as Windows service

[Eric Pyle]

By default a Windows service runs as the Local User account, which has 
no access to network resources. Try configuring the service to run as a 
particular user who has permission for the SVN repo in question.


Regards,
Eric

On 6/11/2014 8:42 AM, Juan Pablo Hernandez Vogt wrote:

Hello,

I tried to find an answer in the list but I did not find what is 
wrong. Probably is a stupid thing...


The job only execute a command *svn update* in my Windows 8.1 machine:

a) If I start the client from JNLP file, the job is executed.

b) If I install it as service, it holds waiting... waiting for 
password maybe?

D:\AAA\nt>svn update
Updating '.':

then after 5 minutes I decide to abort the job:
Build was aborted
Aborted byanonymous  
Finished: ABORTED
Stopping the service, executing a mandatory svn cleanup from an 
independent cmd, and launching again from JNLP, works like a charm.



Why the svn update command does not work from service? Where to read 
to understand how Jenkins works on this mode?



Notes:
1) My user is defined in a domain server, not in my local machine. For 
that I configured the service to use my specific user@domain and password.
2) I'm using Pagent.exe, all svn commands (checkout, update, commit, 
status..) from my cmd.exe work well.

3) The command svn status works perfect from JNLP and from Service.
4) Seems that the connection with Pagent.exe is broken. Printing some 
environment variables inside the job I find the expected values:

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\jpvogt\AppData\Roaming
BASE=D:\Jenkins
SERVICE_ID=jenkinsslave-D__Jenkins
SVN_SSH=C:/putty/plink.exe



Thanks for your time reading this issue.

Best regards,
JP

--
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.

svn update work on running client from JNLP but not as Windows service

[Juan Pablo Hernandez Vogt]

Hello,

I tried to find an answer in the list but I did not find what is wrong. 
Probably is a stupid thing...

The job only execute a command *svn update* in my Windows 8.1 machine:

a) If I start the client from JNLP file, the job is executed.

b) If I install it as service, it holds waiting... waiting for password 
maybe?

D:\AAA\nt>svn update 
Updating '.':

then after 5 minutes I decide to abort the job:

Build was aborted
Aborted by anonymous 
Finished: ABORTED


Stopping the service, executing a mandatory svn cleanup from an independent 
cmd, and launching again from JNLP, works like a charm.


Why the svn update command does not work from service? Where to read to 
understand how Jenkins works on this mode?


Notes: 
1) My user is defined in a domain server, not in my local machine. For that 
I configured the service to use my specific user@domain and password.
2) I'm using Pagent.exe, all svn commands (checkout, update, commit, 
status..) from my cmd.exe work well.
3) The command svn status works perfect from JNLP and from Service.
4) Seems that the connection with Pagent.exe is broken. Printing some 
environment variables inside the job I find the expected values:

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\jpvogt\AppData\Roaming
BASE=D:\Jenkins

SERVICE_ID=jenkinsslave-D__Jenkins
SVN_SSH=C:/putty/plink.exe




Thanks for your time reading this issue.

Best regards,
JP

-- 
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: JUnit test result

[Mohamed Djadlou]

PS : by 'much more readable' I mean failed tests (the thin red line at the 
bottom) would be more visible if compared to total number of suites (2.000 
max)

-- 
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.

JUnit test result

[Mohamed Djadlou]

Hello,


I've implemented the JUnit test result in my Java code and everything looks 
fine : Test Result Trend is displayed and every failed test has its own URL 
leading to its details.  So far so good.

However I noticed the ordering by 'Test Name' has an issue : default order 
is based on the 'Age' column (ascending).  Fine.  But then click on the 
'Test Name' header.  List is properly re-ordered (alphabetically 
descending) EXCEPT for the last item !
Are you also experiencing the same problem ?

I've got another concern about this topic : is there a way to consider test 
suites (I mean the  block in the test result xml file) rather than 
test cases ( block in the same xml file) ? 
Actually information about test suites is much more relevant in the context 
of my project as it's linked to a business test scenario.  
Every time a case fails, next cases are skipped and next test suite 
starts.  Therefore the number of failed tests corresponds to what I 
expect.  It's just the total number of tests that is not.  It would also 
make the trend graph much more readable (see screenshot above)...

Jenkins : 1.562
OS : Win 7 Enterprise

Thanks a lot for your help.
Momo



-- 
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.

CppNCSS plugin not generating reports

[Thomas Schober]

Hi,

i am using CppNCSS plugin to visualize the results from 
https://code.google.com/p/headerfile-free-cyclomatic-complexity-analyzer/. 
The analyzer is working perfectly and generates the expected xml file but 
it seems, that the plugin is not doing anything. It does not generate any 
report and i don't see anything in the build log.

I am also not able to add a report to a dashboard, because the point for 
CppNCss plugin is not shown anywhere. Could anyone manage to run the plugin 
successfully ?

I am using following versions:

CppNCSS plugin Version 1.1
Jenkins Version 1.555

Regards
Tom

-- 
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: Setting global variables without using parameterized build in job

[Amir Katz]

Use the EnvInject plugin

On Thursday, June 5, 2014 5:15:31 PM UTC+3, eric...@rocketmail.com wrote:
>
> Can I set global variables and then use in jobs without using 
> parameterized builds.  This forces me into a manual response mode that does 
> not work in my scenario.
>
> Thanks, Eric
>

-- 
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: priority sorter plugin

[mail4m . mueller]

Hi Jayaprakash D B,

thank you for this post. I am facing the same problem like you did and 
wanted to ask you, whether you were able to solve it in between?

I've chosen "Use Priority from Build Parameter" and tried to forward the 
Parameter via URL the following way:

http://localhost:8080/job/myJobName/buildWithParameters?PARAM1=value1&PARAM2=value2&BuildPriority=1


Where the last argument "BuildPriority" is the standard name defined by the 
Plugin (didn't change it).


I tried to start the build process from this stage with no more changes but 
found, that every parameter works but not the "BuildPriority".

Because I realized, that I added all other parameters manually to the build 
job, but didn't do this for "BuildPriority" I tried to add 

parameters with exactly that name. Once I tried as string paramater, another 
time as option box parameter. But none of the ways worked for me. 

Starting th eprocess and passing parameters works fine, but not the priority.


Thank you very much

-- 
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: question on docker plugin

[Richard Bywater]

As an aside, so far with my trial of the plugin there's a couple of things
that would be nice to add in - one is to have the option to retain the
container if the build fails (so you can jump into it to see if you can
find out what was failing), and the other is to be able to pass some more
arguments into docker (e.g. volumes info)

Also there seems something strange is going on in that it seems to start a
container, and then seem to switch to another container before the build
kicks off. I haven't been able to troubleshoot this behaviour yet but
wonder if something like that is expected?

But it seems good at what it does so far so thanks for the plugin!

Richard.


On Wed, Jun 11, 2014 at 7:25 PM, Nigel Magnay 
wrote:

>
> The docker plugin deals with images not containers - basically it does a
>> docker run on the image, and then can, optionally, keep the container at
>> the end of the run (but cannot be reused in a subsequent job I believe)
>>
>> ​It currently always tears down the container at the end of the Jenkins
> run​, as I suspect this is what most people want, as they're so cheap to
> spin up.
>
> The later versions allow you to also optionally tag and push to a
> centralised repository at the end of the run. This could, in theory, allow
> you to build a CI pipeline based on docker images.
>
> I.E: (Job A)-+->(Job B)
>|
>--->(Job C)
>
> Job A completes, pushes it's container back to a centralised repo and
> marks the build with the ID of the container. Jobs B and C both pull that
> container on start.
>
> It's a bit nascent at the moment. The registry push is there but it's not
> hugely tested (pesky time constraints).
>
>
> --
> 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.

Grails 2.4

[Florian Müller]

Hi guys,

did anyone manage to install Grails 2.4 to Jenkins via Jenkins Web UI? The 
2.4 version is not displayed within the mirrors dropdown and adding via zip 
download does "nothing" in terms of not downloading anything...any idea?

cheers, Florian;



-- 
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: question on docker plugin

[Nigel Magnay]

> The docker plugin deals with images not containers - basically it does a
> docker run on the image, and then can, optionally, keep the container at
> the end of the run (but cannot be reused in a subsequent job I believe)
>
> ​It currently always tears down the container at the end of the Jenkins
run​, as I suspect this is what most people want, as they're so cheap to
spin up.

The later versions allow you to also optionally tag and push to a
centralised repository at the end of the run. This could, in theory, allow
you to build a CI pipeline based on docker images.

I.E: (Job A)-+->(Job B)
   |
   --->(Job C)

Job A completes, pushes it's container back to a centralised repo and marks
the build with the ID of the container. Jobs B and C both pull that
container on start.

It's a bit nascent at the moment. The registry push is there but it's not
hugely tested (pesky time constraints).

-- 
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.