Re: Is simple theme plugin not supported anymore ?

[Baptiste Mathus]

I guess this is due to the numerous changes in the Jenkins UI redesign that
started around 1.572 and after.
With the way that plugin seems to work (overriding/adding CSS IIUC), I
guess this is gonna be difficult if not impossible to be backward
compatible.

>From the last release date, it does not seem very active (so, unmaintained
now?) but maybe it's because it's simple & small and didn't need much work
(at least now I guess there should be some work to make it usable with last
versions).

HTH
Cheers

2015-02-18 4:49 GMT+01:00 Maneesh M P :

> Hello,
>
> I have the jenkins version 1.580.3, I am trying to add a css file using
> simple theme plugin to change the look and feel of our server but the css
> appears to be masking all jenkins options(left side bar) and build executer
> status etc.
> Same css file I am using on another jenkins(version  1.565.2
> )  works fine.  Is simple theme plugin no longer
> supported ? Is there any alternative?
>
>
> Thanks,
> M
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e14f2292-3788-4bb5-92aa-3c69be20f1b9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4mLmFy2YCFUuFOAH5R4bc_6rhsq1Y_%2BUXSNqDDggpO4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Quotes added to path?

[Les Mikesell]

Is the 'bad path environment set by Jenkins" issue:
https://issues.jenkins-ci.org/browse/JENKINS-21621
fixed in the LTS version?

-- 
  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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpwtBtjcCgquoVdbk1xqRD8E1W2iFFvg4o9CCyd_NFm_0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Remote Host Build using Jenkins

[Prasanth .K]

Is it possible to build the remote host file using jenkins?   If possible 
means can anyone suggest me,how to proceed the steps for build the remote 
host files using jenkins? 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3c06e61f-b1a1-4169-bc8e-e8747e2b7012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build using devenv.exe from Jenkins

[Anitha Kabil Raj]

Thanks for the suggestion. I tried using msbuild now. But there is there a 
way to get the INCLUDE path set. All except the projects using files from 
Windows DDK path is getting built successfully.


On Tuesday, 17 February 2015 19:26:36 UTC+5:30, rginga wrote:

>  I use MSBUILD a lot. This is what my steps look like:
>
>  
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *kfhickel
> *Sent:* Tuesday, February 17, 2015 7:33 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Build using devenv.exe from Jenkins
>
>  
>  
> In your script, add /useenv as an argument to devenv.exe.
>  
>  
>  
> e.g.: instead of "devenv.exe proj.sln", you want to issue "devenv /useenv 
> proj.sln".
>  
>  
>  
> -Kelly
>  
>
> On Tuesday, February 17, 2015 at 5:32:29 AM UTC-6, Anitha Kabil Raj wrote:
>  
> Hello Group,
>  
> I have recently started using Jenkins for automating builds. I tried using 
> MSBUILD plugin for building VC++ project using devnev.exe. I couldn't use 
> it as the quotes around the configuration I was trying to build, 
> "Release|Win32" was getting stripped. Is there any update available on this 
> issue, or any workaround on same?
>  
> Now running devenev.exe from batch script. Here I see that the INCLUDE 
> environment variable that I set is not getting picked by the project while 
> build, hence the build fails. It is failing to include files from Windows 
> DDK path, even after providing the path in INCLUDE variable. Anyone in 
> group faced similar issue. 
>  
> Since none of the these methods worked, I'm stuck and not able to proceed 
> further.
>  
> Thanks in advance for the help,
>  
> Anitha
>   
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c7a7258d-c128-4833-a651-b52632298232%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6fef84c4-7d14-4f82-bd92-518c3695a2a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is simple theme plugin not supported anymore ?

[Maneesh M P]

Hello,

I have the jenkins version 1.580.3, I am trying to add a css file using 
simple theme plugin to change the look and feel of our server but the css 
appears to be masking all jenkins options(left side bar) and build executer 
status etc. 
Same css file I am using on another jenkins(version  1.565.2 
)  works fine.  Is simple theme plugin no longer 
supported ? Is there any alternative?


Thanks,
M

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e14f2292-3788-4bb5-92aa-3c69be20f1b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error cloning remote repo 'origin'

[Mark Waite]

I'm very glad that helped.  We're currently evaluating that commit to
decide if it is the right approach for easier failure diagnostics in using
the command line git plugin.

In your case, we could have inserted a git version check and warned you,
but we have many users that run versions which are older than the official
versions.  Apparently none of them run versions as old as 1.6.0.2, but I
know there are versions at least as old as 1.7.2.5, since that is the
default version shipped with Debian 6 (and is a version I test in my
personal CI setup).

Thanks,
Mark Waite


On Tue, Feb 17, 2015 at 3:36 PM, Thom Ellis  wrote:

> Doh!  Sometimes I just move a little too quickly for my own good.
>
> I've got it running now, and it seems to be accomplishing what was
> intended, in that it gives me some extra details:
>
> Started by user anonymous
> Building in workspace /var/lib/jenkins/workspace/test-default
> Cloning the remote Git repository
> Cloning repository file:///home/repos/test.git
>  > /usr/bin/git init /var/lib/jenkins/workspace/test-default # timeout=10
> * >> GitException message: Command "/usr/bin/git init
> /var/lib/jenkins/workspace/test-default" returned status code 129:*
> *stdout: *
> *stderr: usage: git init [-q | --quiet] [--bare]
> [--template=] [--shared[=]]*
>
> * >> stderr: usage: git init [-q | --quiet] [--bare]
> [--template=] [--shared[=]]*
>
> ERROR: Error cloning remote repo 'origin'
> ERROR: Error cloning remote repo 'origin'
> Finished: FAILURE
>
> I believe error 129 is returned anytime you specify improper parameters to
> a git command (?), which seems to explain why it's echo'ing out usage
> details here.  The issue I believe then is that the server I'm using is on
> an older version of git (1.6.0.2), and it appears at that time, "git init"
> didn't accept a directory in the command.  It looks like the plugin
> requires 1.7.9 as a minimum.
>
> Anyways all that to say, I should have checked the versions earlier, but
> this build this did exactly what I needed, and at least gave me something
> to go after.  I was able to install a newer version of git, and now
> everything seems to be working fine.
>
> Thanks a lot for your help, and speedy response.  If there is anything you
> need from me, please let me know.
>
> Cheers!
> --thom
>
> On Tuesday, February 17, 2015 at 10:16:36 AM UTC-8, Mark Waite wrote:
>>
>>
>> On Tue, Feb 17, 2015 at 11:05 AM, Thom Ellis  wrote:
>>
>>> Hey Mark,
>>>
>>> I was trying to play it safe, so I uninstalled the existing git-plugin,
>>> and then installed the version you pointed to on dropbox.  I can see it
>>> listed under installed plugins as version "1.16.2-SNAPSHOT (private
>>> 744b9fe-mwaite), however, git no longer shows up as an option (no radio
>>> button) under "Source Code Management" when configuring my job.  What did I
>>> do wrong here?
>>>
>>>
>> You either uninstalled too much, or didn't install enough (depending on
>> your perspective).  It would have been enough to install the prototype
>> version of git-client-plugin, without an uninstall of any plugin.
>>
>> Since you uninstalled the git plugin, you should install the git plugin
>> (latest release, 2.3.4).  That should be enough to again show you the git
>> plugin fields in the user interface, and should allow you to see the
>> failure message from the call to "git init".
>>
>> The git plugin and the git client plugin are separate plugins so that the
>> git client API can be separated from the more detailed workflow and user
>> interface components in the git plugin.
>>
>> Thanks,
>> Mark Waite
>>
>>
>>
>>> Thanks,
>>> --thom
>>>
>>> On Saturday, February 14, 2015 at 8:59:58 PM UTC-8, Mark Waite wrote:

 I spent some time this weekend writing tests and evaluating possible
 code changes to ease diagnosis of git command line failures.

 If you're willing to "test drive" an unreleased version of the
 git-client-plugin (which encapsulates the command line git calls used by
 the git-plugin), I'd like to use your case to evaluate the impact of the
 changes.

 The unreleased version has passed its automated tests on multiple
 Windows versions, multiple Linux versions, and multiple git versions.

 You can download and install that unreleased version of the plugin from:

 https://www.dropbox.com/l/0nHPJ7eTaLOJnmgUfVT8bp

 Mark Waite

 On Fri, Feb 13, 2015 at 4:01 PM, Thom Ellis  wrote:

> I'm brand new to Jenkins, and just trying to set up a simple test to
> try and play around with it a bit, but I'm hitting a snag, and not sure
> what the issue is.  I have a very basic git repository, and which I used 
> to
> create a bare shared repository, and I'm just pointing directly to the
> repository itself in my configuration.  Whenver I run a build job however 
> I
> get the following:
>
> Started by user anonymous
> Building in workspace /var/lib/jenkins/workspace/test-defaul

Re: Error cloning remote repo 'origin'

[Thom Ellis]

Doh!  Sometimes I just move a little too quickly for my own good.

I've got it running now, and it seems to be accomplishing what was 
intended, in that it gives me some extra details:

Started by user anonymous
Building in workspace /var/lib/jenkins/workspace/test-default
Cloning the remote Git repository
Cloning repository file:///home/repos/test.git
 > /usr/bin/git init /var/lib/jenkins/workspace/test-default # timeout=10
* >> GitException message: Command "/usr/bin/git init 
/var/lib/jenkins/workspace/test-default" returned status code 129:*
*stdout: *
*stderr: usage: git init [-q | --quiet] [--bare] 
[--template=] [--shared[=]]*

* >> stderr: usage: git init [-q | --quiet] [--bare] 
[--template=] [--shared[=]]*

ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Finished: FAILURE

I believe error 129 is returned anytime you specify improper parameters to 
a git command (?), which seems to explain why it's echo'ing out usage 
details here.  The issue I believe then is that the server I'm using is on 
an older version of git (1.6.0.2), and it appears at that time, "git init" 
didn't accept a directory in the command.  It looks like the plugin 
requires 1.7.9 as a minimum.  

Anyways all that to say, I should have checked the versions earlier, but 
this build this did exactly what I needed, and at least gave me something 
to go after.  I was able to install a newer version of git, and now 
everything seems to be working fine.

Thanks a lot for your help, and speedy response.  If there is anything you 
need from me, please let me know.

Cheers!
--thom

On Tuesday, February 17, 2015 at 10:16:36 AM UTC-8, Mark Waite wrote:
>
>
> On Tue, Feb 17, 2015 at 11:05 AM, Thom Ellis  > wrote:
>
>> Hey Mark,
>>
>> I was trying to play it safe, so I uninstalled the existing git-plugin, 
>> and then installed the version you pointed to on dropbox.  I can see it 
>> listed under installed plugins as version "1.16.2-SNAPSHOT (private 
>> 744b9fe-mwaite), however, git no longer shows up as an option (no radio 
>> button) under "Source Code Management" when configuring my job.  What did I 
>> do wrong here?
>>
>>
> You either uninstalled too much, or didn't install enough (depending on 
> your perspective).  It would have been enough to install the prototype 
> version of git-client-plugin, without an uninstall of any plugin.
>
> Since you uninstalled the git plugin, you should install the git plugin 
> (latest release, 2.3.4).  That should be enough to again show you the git 
> plugin fields in the user interface, and should allow you to see the 
> failure message from the call to "git init".
>
> The git plugin and the git client plugin are separate plugins so that the 
> git client API can be separated from the more detailed workflow and user 
> interface components in the git plugin.
>
> Thanks,
> Mark Waite
>
>  
>
>> Thanks,
>> --thom
>>
>> On Saturday, February 14, 2015 at 8:59:58 PM UTC-8, Mark Waite wrote:
>>>
>>> I spent some time this weekend writing tests and evaluating possible 
>>> code changes to ease diagnosis of git command line failures.
>>>
>>> If you're willing to "test drive" an unreleased version of the 
>>> git-client-plugin (which encapsulates the command line git calls used by 
>>> the git-plugin), I'd like to use your case to evaluate the impact of the 
>>> changes.
>>>
>>> The unreleased version has passed its automated tests on multiple 
>>> Windows versions, multiple Linux versions, and multiple git versions.
>>>
>>> You can download and install that unreleased version of the plugin from:
>>>
>>> https://www.dropbox.com/l/0nHPJ7eTaLOJnmgUfVT8bp
>>>
>>> Mark Waite
>>>
>>> On Fri, Feb 13, 2015 at 4:01 PM, Thom Ellis  wrote:
>>>
 I'm brand new to Jenkins, and just trying to set up a simple test to 
 try and play around with it a bit, but I'm hitting a snag, and not sure 
 what the issue is.  I have a very basic git repository, and which I used 
 to 
 create a bare shared repository, and I'm just pointing directly to the 
 repository itself in my configuration.  Whenver I run a build job however 
 I 
 get the following:

 Started by user anonymous
 Building in workspace /var/lib/jenkins/workspace/test-default
 Cloning the remote Git repository
 Cloning repository file:///home/repos/test.git
  > /usr/bin/git init /var/lib/jenkins/workspace/test-default # 
 timeout=10
 ERROR: Error cloning remote repo 'origin'
 ERROR: Error cloning remote repo 'origin'
 Finished: FAILURE

 I'm able to clone the repo just fine from the command line, and I was 
 also able to clone it just fine by creating a new build job where instead 
 of linking to git, I just execute the clone command itself in Jenkins, 
 with 
 no issues.  Anyone have any tips/ideas?  With the limited error output, 
 I'm 
 not really sure what else to check.

 Thanks in advance!

 -- 
 You receiv

Jenkins UX

[Gus Reiber]

At the end of last summer, my friend and co-worker, Tom Fennelly 
, along with the help of Kevin Burke 
, Daniel Beck 
, and others began the first steps of 
improving and modernizing the Jenkins user experience. In addition to some 
of the superficial enhancements, these changes are meant to add a bit of 
responsiveness and cross-device usability to the Jenkins GUI, as well as 
adding a means of creating and swapping new CSS based display themes. This 
effort is best summarized by this article from Jenkins-ci.org, and this 
thread from the Jenkinsci-users group:

   - *User Interface Refresh 
   :* 
   http://jenkins-ci.org/node/501#disqus_thread
   - *Any comments on the UI changes in 1.572 
   
:*
 
   
https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J

As part of our second wave effort here at CloudBees, I am looking at ways 
of improving the usability of the Jelly based form controls used in the 
item creation and configuration pages and the responsiveness and 
interactivity of the main dashboard grid control.

In my investigations so far, I believe there are essentially 3 
non-exclusive paths forward for enhancing these elements:

   1. *CSS only --* Building on the last round of enhancements, we can 
   offer a set of theme extensions that will allow the Jenkins users and 
   community to customize basic layout, iconography, and typeface to tailor 
   Jenkins to their own tastes.
   2. *UI component expansion and refactoring --* By modifying and adding 
   to the existing set of Jelly files and their corresponding data binding 
   rules we can significantly modernize the way Jenkins views and configs draw 
   themselves and potentially streamline plugin creation.
   3. *Client side MVC veneers --* In a manner similar to what CloudBees 
   has recently done with the new Workflow visualization, we can rethink our 
   approach to new feature UIs by using a REST API based architecture coupled 
   with client-side rendering widgets. This would allow us to use newer 
   framework libraries like Angular.js and newer component libraries like 
   Bootstrap and JQuery UI to add greater richness to the Jenkins user 
   experience.
   
These are likely not the only paths forward, but merely the first I can 
think of.  With that reality in mind, I am hoping to reach out to you the 
Jenkins community to help ground and sculpt our thinking about what is both 
possible and desirable. 

If you are at all interested in the Jenkins user experience, I would love 
to get your feedback of any sort on this thread, which could be as simple 
as a "+1" or as involved as a PHD thesis or as much as you have time to 
type into a response box.

To the extent that it helps conversation along, I also have a handful of 
questions to which I would love responses:

   1. For plugin builders, can you tell me a bit about creating the UI 
   portion of your plugin (did you use the data binding form controls, what 
   was hard, what did you have to invent)?
   2. For regular Jenkins users, what are the UX areas of Jenkins you would 
   most like to see improved (I think it is the item create/config and the 
   dashboard/job list grid, but would love to hear others and general 
   feedback)?
   3. For UXers and other Jenkins contributors, how do my 3 forward paths 
   seem (are there others, do you have experience with any yourself, do any 
   seem scary)?
   4. Has anyone tried to make their own themes with the new capabilities 
   Tom has added or would you appreciate and handful of canned options to 
   choose between?
   5. Has anyone started using Workflow on a regular basis, and in 
   particular used the new workflow progress visualization enough to offer 
   feedback?
   

Again, if any of you all are at all interested in the Jenkins UX, we at 
CloudBees are interested in helping move this ball forward and would love 
to hear your feedback.

Thanks for your help,
Gus

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1959f2f8-770e-4eef-81a6-6c88360ef104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Redirect loop with Google Login Plugin

[Mike Chaberski]

I administer a Jenkins instance running on Tomcat 7. I have the Google 
Login Plugin 
 enabled 
for authentication.

When I am logged in to my Google account and I visit 

https://jenkins.mydomain.com/jenkins/

...I am taken, as expected, to my instance's home page (or redirected to 
log in with Google and then redirected back correctly).

However, when I am logged in to my Google account and I visit 

https://jenkins.mydomain.com/jenkins

...(with no trailing slash) I am sent into an infinite redirect loop, 
instead of being redirected to my instance's home page.

The same behavior is exhibited if I am not already logged in to my Google 
account, except there is a middle step where I am redirected to the Google 
login page.

Does anyone know how I can resolve this issue?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fc3d1a98-d35e-4b67-ad96-5ee61adb5049%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slaves are killing jobs with a linux kernal memory error

[Sean Last]

My understanding of jenkins is that all the executors on a slave run in the 
same JVM?  Is that correct? Or does it launch separate JVMs for each 
executor?  If I manually set the heap size (Xmx) for each executor, could I 
know exactly how much RAM was being used?

On Tuesday, February 17, 2015 at 12:45:40 PM UTC-5, Sean Last wrote:
>
> Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java) score 
> 139 or sacrifice child
> [Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java) score 
> 140 or sacrifice child
> [Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java) score 
> 143 or sacrifice child
> [Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java) score 
> 162 or sacrifice child
> [Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java) score 
> 163 or sacrifice child
> [Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java) score 
> 165 or sacrifice child
> [Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java) score 
> 166 or sacrifice child
> [Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java) score 
> 163 or sacrifice child
> [Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java) score 
> 112 or sacrifice child
> [Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java) score 
> 140 or sacrifice child
> [Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java) score 
> 115 or sacrifice child
> [Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java) score 
> 121 or sacrifice child
> [Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java) score 
> 121 or sacrifice child
> [Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java) score 
> 121 or sacrifice child
> [Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java) score 
> 127 or sacrifice child
> [Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java) score 
> 127 or sacrifice child
>
> Should I reduce the number of executors, or how can I solve this?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fdffd9ea-085f-405e-a66e-9aaf0ba36645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slaves are killing jobs with a linux kernal memory error

[Scott Evans]

Sean,

Without knowing your specifics of memory capacity, number of current
executors, executor usage, etc., it's hard to give any hard guidelines.
Perhaps try to reduce by 25% the number of executors and see what happens.
There's no magic number as each installation is different.

Scott


On Tue, Feb 17, 2015 at 12:33 PM, Sean Last  wrote:

> Is there a good metric to reduce the number of executors by?
>
> On Tuesday, February 17, 2015 at 1:18:29 PM UTC-5, Mark Waite wrote:
>>
>> I think that message usually means you've exhausted virtual memory.  With
>> most systems, if you've exhausted virtual memory, you've already been
>> suffering poor performance due to thrashing of your paging system (swap
>> space).
>>
>> Reduce the number of executors, or increase the physical memory and
>> possibly the size of the paging file(s).
>>
>> Mark Waite
>>
>> On Tue, Feb 17, 2015 at 10:45 AM, Sean Last  wrote:
>>
>>> Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java)
>>> score 139 or sacrifice child
>>> [Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java)
>>> score 140 or sacrifice child
>>> [Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java)
>>> score 143 or sacrifice child
>>> [Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java)
>>> score 162 or sacrifice child
>>> [Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java)
>>> score 163 or sacrifice child
>>> [Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java)
>>> score 165 or sacrifice child
>>> [Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java)
>>> score 166 or sacrifice child
>>> [Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java)
>>> score 163 or sacrifice child
>>> [Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java)
>>> score 112 or sacrifice child
>>> [Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java)
>>> score 140 or sacrifice child
>>> [Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java)
>>> score 115 or sacrifice child
>>> [Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java)
>>> score 127 or sacrifice child
>>> [Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java)
>>> score 127 or sacrifice child
>>>
>>> Should I reduce the number of executors, or how can I solve this?
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-users/4915c03a-d298-4059-b410-
>>> d14e2a9d981e%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9b95be75-2f69-43d8-8fdc-af0e04a7baf3%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAAPjsPb2REy3B%3DX_%3DBy1F_%2BjgbDS%2BxdoTE3tczVG9DxLx4VXvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slaves are killing jobs with a linux kernal memory error

[Mark Waite]

On Tue, Feb 17, 2015 at 11:33 AM, Sean Last  wrote:

> Is there a good metric to reduce the number of executors by?
>
>
My heuristic is that I try to keep the number of executors down to no more
than one less than the number of processors on the computer.  However,
another heuristic might be to watch the memory use of your jobs and limit
the number of executors so that your jobs never exceed the physical memory
available on the system.

I'm sure others have different heuristics based on their job types.  My job
types tend to be more CPU bound than memory bound.

Mark Waite


> On Tuesday, February 17, 2015 at 1:18:29 PM UTC-5, Mark Waite wrote:
>>
>> I think that message usually means you've exhausted virtual memory.  With
>> most systems, if you've exhausted virtual memory, you've already been
>> suffering poor performance due to thrashing of your paging system (swap
>> space).
>>
>> Reduce the number of executors, or increase the physical memory and
>> possibly the size of the paging file(s).
>>
>> Mark Waite
>>
>> On Tue, Feb 17, 2015 at 10:45 AM, Sean Last  wrote:
>>
>>> Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java)
>>> score 139 or sacrifice child
>>> [Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java)
>>> score 140 or sacrifice child
>>> [Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java)
>>> score 143 or sacrifice child
>>> [Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java)
>>> score 162 or sacrifice child
>>> [Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java)
>>> score 163 or sacrifice child
>>> [Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java)
>>> score 165 or sacrifice child
>>> [Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java)
>>> score 166 or sacrifice child
>>> [Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java)
>>> score 163 or sacrifice child
>>> [Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java)
>>> score 112 or sacrifice child
>>> [Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java)
>>> score 140 or sacrifice child
>>> [Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java)
>>> score 115 or sacrifice child
>>> [Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java)
>>> score 121 or sacrifice child
>>> [Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java)
>>> score 127 or sacrifice child
>>> [Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java)
>>> score 127 or sacrifice child
>>>
>>> Should I reduce the number of executors, or how can I solve this?
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-users/4915c03a-d298-4059-b410-
>>> d14e2a9d981e%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9b95be75-2f69-43d8-8fdc-af0e04a7baf3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHr0mgNue0vLU8n-qyC5ZdV%2BmOdX0OLVtpzC75%2B%3Dh_5Yg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slaves are killing jobs with a linux kernal memory error

[Sean Last]

Is there a good metric to reduce the number of executors by?

On Tuesday, February 17, 2015 at 1:18:29 PM UTC-5, Mark Waite wrote:
>
> I think that message usually means you've exhausted virtual memory.  With 
> most systems, if you've exhausted virtual memory, you've already been 
> suffering poor performance due to thrashing of your paging system (swap 
> space).
>
> Reduce the number of executors, or increase the physical memory and 
> possibly the size of the paging file(s).
>
> Mark Waite
>
> On Tue, Feb 17, 2015 at 10:45 AM, Sean Last  > wrote:
>
>> Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java) score 
>> 139 or sacrifice child
>> [Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java) 
>> score 140 or sacrifice child
>> [Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java) 
>> score 143 or sacrifice child
>> [Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java) 
>> score 162 or sacrifice child
>> [Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java) score 
>> 163 or sacrifice child
>> [Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java) score 
>> 165 or sacrifice child
>> [Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java) score 
>> 166 or sacrifice child
>> [Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java) score 
>> 163 or sacrifice child
>> [Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java) score 
>> 112 or sacrifice child
>> [Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java) score 
>> 140 or sacrifice child
>> [Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java) score 
>> 115 or sacrifice child
>> [Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java) score 
>> 121 or sacrifice child
>> [Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java) score 
>> 121 or sacrifice child
>> [Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java) score 
>> 121 or sacrifice child
>> [Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java) 
>> score 127 or sacrifice child
>> [Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java) 
>> score 127 or sacrifice child
>>
>> Should I reduce the number of executors, or how can I solve this?
>>
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/4915c03a-d298-4059-b410-d14e2a9d981e%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Thanks!
> Mark Waite
>  

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9b95be75-2f69-43d8-8fdc-af0e04a7baf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins slaves are killing jobs with a linux kernal memory error

[Mark Waite]

I think that message usually means you've exhausted virtual memory.  With
most systems, if you've exhausted virtual memory, you've already been
suffering poor performance due to thrashing of your paging system (swap
space).

Reduce the number of executors, or increase the physical memory and
possibly the size of the paging file(s).

Mark Waite

On Tue, Feb 17, 2015 at 10:45 AM, Sean Last  wrote:

> Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java) score
> 139 or sacrifice child
> [Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java) score
> 140 or sacrifice child
> [Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java) score
> 143 or sacrifice child
> [Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java) score
> 162 or sacrifice child
> [Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java) score
> 163 or sacrifice child
> [Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java) score
> 165 or sacrifice child
> [Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java) score
> 166 or sacrifice child
> [Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java) score
> 163 or sacrifice child
> [Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java) score
> 112 or sacrifice child
> [Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java) score
> 140 or sacrifice child
> [Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java) score
> 115 or sacrifice child
> [Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java) score
> 121 or sacrifice child
> [Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java) score
> 121 or sacrifice child
> [Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java) score
> 121 or sacrifice child
> [Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java) score
> 127 or sacrifice child
> [Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java) score
> 127 or sacrifice child
>
> Should I reduce the number of executors, or how can I solve this?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/4915c03a-d298-4059-b410-d14e2a9d981e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEJO6VyT_Z-oN8mAfoR3Kt1rR0r67j4N6WvY80cBhMDQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error cloning remote repo 'origin'

[Mark Waite]

On Tue, Feb 17, 2015 at 11:05 AM, Thom Ellis  wrote:

> Hey Mark,
>
> I was trying to play it safe, so I uninstalled the existing git-plugin,
> and then installed the version you pointed to on dropbox.  I can see it
> listed under installed plugins as version "1.16.2-SNAPSHOT (private
> 744b9fe-mwaite), however, git no longer shows up as an option (no radio
> button) under "Source Code Management" when configuring my job.  What did I
> do wrong here?
>
>
You either uninstalled too much, or didn't install enough (depending on
your perspective).  It would have been enough to install the prototype
version of git-client-plugin, without an uninstall of any plugin.

Since you uninstalled the git plugin, you should install the git plugin
(latest release, 2.3.4).  That should be enough to again show you the git
plugin fields in the user interface, and should allow you to see the
failure message from the call to "git init".

The git plugin and the git client plugin are separate plugins so that the
git client API can be separated from the more detailed workflow and user
interface components in the git plugin.

Thanks,
Mark Waite



> Thanks,
> --thom
>
> On Saturday, February 14, 2015 at 8:59:58 PM UTC-8, Mark Waite wrote:
>>
>> I spent some time this weekend writing tests and evaluating possible code
>> changes to ease diagnosis of git command line failures.
>>
>> If you're willing to "test drive" an unreleased version of the
>> git-client-plugin (which encapsulates the command line git calls used by
>> the git-plugin), I'd like to use your case to evaluate the impact of the
>> changes.
>>
>> The unreleased version has passed its automated tests on multiple Windows
>> versions, multiple Linux versions, and multiple git versions.
>>
>> You can download and install that unreleased version of the plugin from:
>>
>> https://www.dropbox.com/l/0nHPJ7eTaLOJnmgUfVT8bp
>>
>> Mark Waite
>>
>> On Fri, Feb 13, 2015 at 4:01 PM, Thom Ellis  wrote:
>>
>>> I'm brand new to Jenkins, and just trying to set up a simple test to try
>>> and play around with it a bit, but I'm hitting a snag, and not sure what
>>> the issue is.  I have a very basic git repository, and which I used to
>>> create a bare shared repository, and I'm just pointing directly to the
>>> repository itself in my configuration.  Whenver I run a build job however I
>>> get the following:
>>>
>>> Started by user anonymous
>>> Building in workspace /var/lib/jenkins/workspace/test-default
>>> Cloning the remote Git repository
>>> Cloning repository file:///home/repos/test.git
>>>  > /usr/bin/git init /var/lib/jenkins/workspace/test-default #
>>> timeout=10
>>> ERROR: Error cloning remote repo 'origin'
>>> ERROR: Error cloning remote repo 'origin'
>>> Finished: FAILURE
>>>
>>> I'm able to clone the repo just fine from the command line, and I was
>>> also able to clone it just fine by creating a new build job where instead
>>> of linking to git, I just execute the clone command itself in Jenkins, with
>>> no issues.  Anyone have any tips/ideas?  With the limited error output, I'm
>>> not really sure what else to check.
>>>
>>> Thanks in advance!
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-users/bcdd2e54-3afa-4f60-9881-
>>> 8c8b83eac7b6%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d0e670e6-8dba-46c9-b81b-5da6496e5257%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHUvXjRuQ-qwzMqpRWUDcOSaWvvYSQ50KYa-ZxUJ4vKsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error cloning remote repo 'origin'

[Thom Ellis]

Hey Mark,

I was trying to play it safe, so I uninstalled the existing git-plugin, and 
then installed the version you pointed to on dropbox.  I can see it listed 
under installed plugins as version "1.16.2-SNAPSHOT (private 
744b9fe-mwaite), however, git no longer shows up as an option (no radio 
button) under "Source Code Management" when configuring my job.  What did I 
do wrong here?

Thanks,
--thom

On Saturday, February 14, 2015 at 8:59:58 PM UTC-8, Mark Waite wrote:
>
> I spent some time this weekend writing tests and evaluating possible code 
> changes to ease diagnosis of git command line failures.
>
> If you're willing to "test drive" an unreleased version of the 
> git-client-plugin (which encapsulates the command line git calls used by 
> the git-plugin), I'd like to use your case to evaluate the impact of the 
> changes.
>
> The unreleased version has passed its automated tests on multiple Windows 
> versions, multiple Linux versions, and multiple git versions.
>
> You can download and install that unreleased version of the plugin from:
>
> https://www.dropbox.com/l/0nHPJ7eTaLOJnmgUfVT8bp
>
> Mark Waite
>
> On Fri, Feb 13, 2015 at 4:01 PM, Thom Ellis  > wrote:
>
>> I'm brand new to Jenkins, and just trying to set up a simple test to try 
>> and play around with it a bit, but I'm hitting a snag, and not sure what 
>> the issue is.  I have a very basic git repository, and which I used to 
>> create a bare shared repository, and I'm just pointing directly to the 
>> repository itself in my configuration.  Whenver I run a build job however I 
>> get the following:
>>
>> Started by user anonymous
>> Building in workspace /var/lib/jenkins/workspace/test-default
>> Cloning the remote Git repository
>> Cloning repository file:///home/repos/test.git
>>  > /usr/bin/git init /var/lib/jenkins/workspace/test-default # timeout=10
>> ERROR: Error cloning remote repo 'origin'
>> ERROR: Error cloning remote repo 'origin'
>> Finished: FAILURE
>>
>> I'm able to clone the repo just fine from the command line, and I was 
>> also able to clone it just fine by creating a new build job where instead 
>> of linking to git, I just execute the clone command itself in Jenkins, with 
>> no issues.  Anyone have any tips/ideas?  With the limited error output, I'm 
>> not really sure what else to check.
>>
>> Thanks in advance!
>>
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/bcdd2e54-3afa-4f60-9881-8c8b83eac7b6%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Thanks!
> Mark Waite
>  

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d0e670e6-8dba-46c9-b81b-5da6496e5257%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins slaves are killing jobs with a linux kernal memory error

[Sean Last]

Thu Jan 29 15:48:45 2015] Out of memory: Kill process 19422 (java) score 
139 or sacrifice child
[Thu Jan 29 18:24:25 2015] Out of memory: Kill process 19422 (java) score 
140 or sacrifice child
[Thu Jan 29 20:23:21 2015] Out of memory: Kill process 19422 (java) score 
143 or sacrifice child
[Fri Jan 30 20:25:04 2015] Out of memory: Kill process 19422 (java) score 
162 or sacrifice child
[Tue Feb 3 19:19:10 2015] Out of memory: Kill process 19422 (java) score 
163 or sacrifice child
[Wed Feb 4 14:16:41 2015] Out of memory: Kill process 19422 (java) score 
165 or sacrifice child
[Wed Feb 4 16:22:11 2015] Out of memory: Kill process 19422 (java) score 
166 or sacrifice child
[Wed Feb 4 19:20:27 2015] Out of memory: Kill process 19422 (java) score 
163 or sacrifice child
[Fri Feb 6 14:16:21 2015] Out of memory: Kill process 25783 (java) score 
112 or sacrifice child
[Mon Feb 9 06:20:54 2015] Out of memory: Kill process 31175 (java) score 
140 or sacrifice child
[Mon Feb 9 08:55:12 2015] Out of memory: Kill process 25783 (java) score 
115 or sacrifice child
[Mon Feb 9 16:55:25 2015] Out of memory: Kill process 25783 (java) score 
121 or sacrifice child
[Mon Feb 9 16:55:59 2015] Out of memory: Kill process 25783 (java) score 
121 or sacrifice child
[Mon Feb 9 17:01:16 2015] Out of memory: Kill process 25783 (java) score 
121 or sacrifice child
[Wed Feb 11 10:13:51 2015] Out of memory: Kill process 25783 (java) score 
127 or sacrifice child
[Wed Feb 11 10:16:37 2015] Out of memory: Kill process 25783 (java) score 
127 or sacrifice child

Should I reduce the number of executors, or how can I solve this?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4915c03a-d298-4059-b410-d14e2a9d981e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Does current svn plugin use native binaries?

[Les Mikesell]

I see a note in the changelog for 2.5:
"Replace custom svnkit library in exchange for using the default binaries."

Does that mean that to use this version, all of the nodes have to have
an appropriate svn client installed?   And be then careful about
changing versions since subversion doesn't like different-version
clients re-using a workspace?


-- 
   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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpwTk3fMdhYvMeeDzGsnd715Xug%2B1Z9mBO1A5CNZvkM5tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Gradle Artifactory Integration with Jenkins Job DSL

[goodav]

 

We are using the Jenkins DSL to define our jobs and have had very good 
success with it.  However, when writing a job for our projects that use 
Gradle, where a successful build publishes to Artifactory, we have to 
manually configure Artifactory on the jobs first run even though we defined 
all the Artifactory config in the DSL. 

Our DSL job results in the following config.xml snippet for our job:

  http://my.artifactory.server/artifactory
  artifactory
  *libs-snapshot-local*
  libs-snapshot-local
  libs-snapshot-local

  libs-snapshot-local

  
  None
  
  None



When we run the job for the first time it fails because the "Publishing 
Repository" has not been populated (see below).



After clicking the refresh button the "Publishing Repository" field is then 
populated with a value (although it is not the correct value from our DSL 
config:  see xml above).




This seems like a defect with the plugin because after clicking the refresh 
button and saving the job configuration, there is not a single change the 
the above xml snippet.  Comparing the config.xml for the job before and 
after results in no differences.

Has anyone else encountered this or found a way around it?




-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/57791067-6b91-4b11-b99f-ba39a339109f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git Parameter Plug-in does not list tags or branches

[Amedee Van Gasse]

It seems that I have stumbled upon a known bug: the Git Parameters plugin 
does not work for private repositories because it ignores the SSH 
credentials in the Jenkins setup:
https://issues.jenkins-ci.org/browse/JENKINS-23396

I made a workaround with the Extensible Choice Parameter plugin 

:
http://stackoverflow.com/a/28565446/766786

It's a kludge, but it works for me.

PS: I want to subscribe to bug JENKINS-23396, but I can't register due to 
spam. Halp?

On Monday, February 16, 2015 at 1:01:36 PM UTC+1, Amedee Van Gasse wrote:
>
> Jenkins version: 1.593
> Git Parameter Plug-In 
> : 0.4.0
> GIT client plugin 
> : 1.16.1
>
>
> I have a parameterized build.
> My parameter is Git Parameter.
>
> Name: TAG_TO_BUILD
> Description:
> Parameter type: Branch or tag
> Branch filter: *
> Tag filter: *
> Tag sort mode: DESCENDING_SMART
> Default value: master
>
> Source code management:
> Branches to build: origin/${TAG_TO_BUILD}
>
>
> When I Build with parameters, I always get "Retrieving Git references...":
>
> This build requires parameters:
>  TAG_TO_BUILD
> Retrieving Git references…
> You must have built the project at least once, to get entries in the list 
> above.
> If you wipe out your workspace, the plugin needs to clone the repository 
> before it can list the tags/revisions. This may take some time if you have 
> a slow connection or the repository is big.
>
> I always get this, the box is never filled with branches or tags, even 
> after I built the project without specifying a parameter (it was 
> successfully built with branch master).
>
> Is there something else that I am missing here?
>
> -- 
> Amedee
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f21d4708-0ea4-4302-852f-4668b9fcad92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Deadlock running out of executors waiting on subjobs via parameterized trigger plugin

[Ginga, Dick]

You can use 2 locks, one locks A from running until B completes and one for C 
and D.

In a different approach, IF C and D ONLY need the built artifacts from A and B, 
then you can have A and B “archive the artifacts” and then have C and D “Copy 
the artifacts” into their workspace and run the tests.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver
Sent: Tuesday, February 17, 2015 9:16 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Deadlock running out of executors waiting on subjobs via 
parameterized trigger plugin


Hmm, if I do that, while it remedies the deadlock, it means I no longer can 
have multiple runs in parallel in different workspaces, correct?

On Tue, Feb 17, 2015 at 9:10 AM, Ginga, Dick 
mailto:dick.gi...@perkinelmer.com>> wrote:
You can use locks to prevent them from running again via the Lock and Latches 
plugin or maybe the Block build when downstream project is building under 
advanced project options will work. I have used the first but not the second.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of Brent Scriver
Sent: Tuesday, February 17, 2015 9:02 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Deadlock running out of executors waiting on subjobs via 
parameterized trigger plugin


Unfortunately I do need A & B to wait to make sure A & B do not run again until 
C & D are done with those workspaces.

On Tue, Feb 17, 2015 at 7:54 AM, Ginga, Dick 
mailto:dick.gi...@perkinelmer.com>> wrote:
If you do not need A and B to wait for C and D to complete, then trigger them 
using a post-build trigger using the Trigger Parameterized Build plugin. This 
will run before A completes but not cause A to wait. Then an executor will 
become available as A terminates

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of Brent Scriver
Sent: Friday, February 13, 2015 4:27 PM
To: jenkinsci-users@googlegroups.com
Subject: Deadlock running out of executors waiting on subjobs via parameterized 
trigger plugin


I'm looking for some help/direction at resolving an odd problem.  We currently 
only have one node (still in the midst of setting up/configuring hardware), and 
we encountered a scenario where we have just a couple executors that can run on 
the machine at once (say 2).  If I start jobs A & B which run jobs C & D via 
the parameterized trigger plugin and wait for those to complete, no jobs ever 
finish.  C & D are never started due to lack of executors and A & B cannot 
complete waiting for those jobs.

We are using Perforce and I am trying to be efficient with workspaces as 
syncing new workspaces is really expensive (we are already at gigs of data) 
part of the objective is to reuse the workspace between the jobs (so C & D can 
run within the workspaces set up by A & B).

Is there a detail I'm missing?  None of the jobs are set up to block waiting 
for upstream or downstream jobs to finish.

I'm on (with versions of job related plugins in case there is an interaction):
* Jenkins 1.592
* Build Pipeline Plugin 1.4.5
* External Job Monitor Plugin 1,4
* Join Plugin 1.15
* Matrix Project Plugin 1.4
* Node & Label Parameter Plugin 1.5.1
* Parameterized Trigger Plugin 2.25

I did have the job weight plugin at one point, but no longer.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1fc6b4ef-f34d-4e45-a4aa-96e22cb57a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/iR4GsaOWHAQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F997C%40AMERMBX02.PERKINELMER.NET.

For more options, visit https://groups.googl

Re: envinject plugin - how to set up for specific slave nodes

[Mark Sinclair]

I understand the problem now.  The slave envinject requires a slave 
reboot.  It is working as expected.  

Unfortunately what I want to do is be able to change the contents of the 
slaves global parameters without rebooting the slave every time.  This does 
not appear possible.

As a workaround, I will setup each job to pull in the same global 
parameters file.  This should work for now.

The problem is if any jobs want to include their own properties file.  I 
read something about an include directive in properties files, but not sure 
this works with Jenkins.  Anyone tried this?


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/73a8c0dd-82f1-4639-a766-7ff4f27bbd71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deadlock running out of executors waiting on subjobs via parameterized trigger plugin

[Brent Scriver]

Hmm, if I do that, while it remedies the deadlock, it means I no longer can
have multiple runs in parallel in different workspaces, correct?

On Tue, Feb 17, 2015 at 9:10 AM, Ginga, Dick 
wrote:

>  You can use locks to prevent them from running again via the Lock and
> Latches plugin or maybe the Block build when downstream project is
> building under advanced project options will work. I have used the first
> but not the second.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:* Tuesday, February 17, 2015 9:02 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Deadlock running out of executors waiting on subjobs via
> parameterized trigger plugin
>
>
>
>
>
> Unfortunately I do need A & B to wait to make sure A & B do not run again
> until C & D are done with those workspaces.
>
>
>
> On Tue, Feb 17, 2015 at 7:54 AM, Ginga, Dick 
> wrote:
>
> If you do not need A and B to wait for C and D to complete, then trigger
> them using a post-build trigger using the Trigger Parameterized Build
> plugin. This will run before A completes but not cause A to wait. Then an
> executor will become available as A terminates
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:* Friday, February 13, 2015 4:27 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Deadlock running out of executors waiting on subjobs via
> parameterized trigger plugin
>
>
>
>
>
> I'm looking for some help/direction at resolving an odd problem.  We
> currently only have one node (still in the midst of setting up/configuring
> hardware), and we encountered a scenario where we have just a couple
> executors that can run on the machine at once (say 2).  If I start jobs A &
> B which run jobs C & D via the parameterized trigger plugin and wait for
> those to complete, no jobs ever finish.  C & D are never started due to
> lack of executors and A & B cannot complete waiting for those jobs.
>
>
>
> We are using Perforce and I am trying to be efficient with workspaces as
> syncing new workspaces is really expensive (we are already at gigs of data)
> part of the objective is to reuse the workspace between the jobs (so C & D
> can run within the workspaces set up by A & B).
>
>
>
> Is there a detail I'm missing?  None of the jobs are set up to block
> waiting for upstream or downstream jobs to finish.
>
>
>
> I'm on (with versions of job related plugins in case there is an
> interaction):
>
> * Jenkins 1.592
>
> * Build Pipeline Plugin 1.4.5
>
> * External Job Monitor Plugin 1,4
>
> * Join Plugin 1.15
>
> * Matrix Project Plugin 1.4
>
> * Node & Label Parameter Plugin 1.5.1
>
> * Parameterized Trigger Plugin 2.25
>
>
>
> I did have the job weight plugin at one point, but no longer.
>
>
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1fc6b4ef-f34d-4e45-a4aa-96e22cb57a79%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/iR4GsaOWHAQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F997C%40AMERMBX02.PERKINELMER.NET
> 
> .
>
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCSwvG-Y%3DPn1c-pw21fBBBsKhWwQuL%2B4TcQZ1XFjCBgMcw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>   --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from t

RE: Deadlock running out of executors waiting on subjobs via parameterized trigger plugin

[Ginga, Dick]

You can use locks to prevent them from running again via the Lock and Latches 
plugin or maybe the Block build when downstream project is building under 
advanced project options will work. I have used the first but not the second.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver
Sent: Tuesday, February 17, 2015 9:02 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Deadlock running out of executors waiting on subjobs via 
parameterized trigger plugin


Unfortunately I do need A & B to wait to make sure A & B do not run again until 
C & D are done with those workspaces.

On Tue, Feb 17, 2015 at 7:54 AM, Ginga, Dick 
mailto:dick.gi...@perkinelmer.com>> wrote:
If you do not need A and B to wait for C and D to complete, then trigger them 
using a post-build trigger using the Trigger Parameterized Build plugin. This 
will run before A completes but not cause A to wait. Then an executor will 
become available as A terminates

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of Brent Scriver
Sent: Friday, February 13, 2015 4:27 PM
To: jenkinsci-users@googlegroups.com
Subject: Deadlock running out of executors waiting on subjobs via parameterized 
trigger plugin


I'm looking for some help/direction at resolving an odd problem.  We currently 
only have one node (still in the midst of setting up/configuring hardware), and 
we encountered a scenario where we have just a couple executors that can run on 
the machine at once (say 2).  If I start jobs A & B which run jobs C & D via 
the parameterized trigger plugin and wait for those to complete, no jobs ever 
finish.  C & D are never started due to lack of executors and A & B cannot 
complete waiting for those jobs.

We are using Perforce and I am trying to be efficient with workspaces as 
syncing new workspaces is really expensive (we are already at gigs of data) 
part of the objective is to reuse the workspace between the jobs (so C & D can 
run within the workspaces set up by A & B).

Is there a detail I'm missing?  None of the jobs are set up to block waiting 
for upstream or downstream jobs to finish.

I'm on (with versions of job related plugins in case there is an interaction):
* Jenkins 1.592
* Build Pipeline Plugin 1.4.5
* External Job Monitor Plugin 1,4
* Join Plugin 1.15
* Matrix Project Plugin 1.4
* Node & Label Parameter Plugin 1.5.1
* Parameterized Trigger Plugin 2.25

I did have the job weight plugin at one point, but no longer.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1fc6b4ef-f34d-4e45-a4aa-96e22cb57a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/iR4GsaOWHAQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F997C%40AMERMBX02.PERKINELMER.NET.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCSwvG-Y%3DPn1c-pw21fBBBsKhWwQuL%2B4TcQZ1XFjCBgMcw%40mail.gmail.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.
To view this discussion on t

Re: Deadlock running out of executors waiting on subjobs via parameterized trigger plugin

[Brent Scriver]

Unfortunately I do need A & B to wait to make sure A & B do not run again
until C & D are done with those workspaces.

On Tue, Feb 17, 2015 at 7:54 AM, Ginga, Dick 
wrote:

>  If you do not need A and B to wait for C and D to complete, then trigger
> them using a post-build trigger using the Trigger Parameterized Build
> plugin. This will run before A completes but not cause A to wait. Then an
> executor will become available as A terminates
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:* Friday, February 13, 2015 4:27 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Deadlock running out of executors waiting on subjobs via
> parameterized trigger plugin
>
>
>
>
>
> I'm looking for some help/direction at resolving an odd problem.  We
> currently only have one node (still in the midst of setting up/configuring
> hardware), and we encountered a scenario where we have just a couple
> executors that can run on the machine at once (say 2).  If I start jobs A &
> B which run jobs C & D via the parameterized trigger plugin and wait for
> those to complete, no jobs ever finish.  C & D are never started due to
> lack of executors and A & B cannot complete waiting for those jobs.
>
>
>
> We are using Perforce and I am trying to be efficient with workspaces as
> syncing new workspaces is really expensive (we are already at gigs of data)
> part of the objective is to reuse the workspace between the jobs (so C & D
> can run within the workspaces set up by A & B).
>
>
>
> Is there a detail I'm missing?  None of the jobs are set up to block
> waiting for upstream or downstream jobs to finish.
>
>
>
> I'm on (with versions of job related plugins in case there is an
> interaction):
>
> * Jenkins 1.592
>
> * Build Pipeline Plugin 1.4.5
>
> * External Job Monitor Plugin 1,4
>
> * Join Plugin 1.15
>
> * Matrix Project Plugin 1.4
>
> * Node & Label Parameter Plugin 1.5.1
>
> * Parameterized Trigger Plugin 2.25
>
>
>
> I did have the job weight plugin at one point, but no longer.
>
>
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1fc6b4ef-f34d-4e45-a4aa-96e22cb57a79%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/iR4GsaOWHAQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F997C%40AMERMBX02.PERKINELMER.NET
> 
> .
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCSwvG-Y%3DPn1c-pw21fBBBsKhWwQuL%2B4TcQZ1XFjCBgMcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins CI setup on RedHat machine

[John Mellor]

Jenkins is a standard rpm package for RedHat-based distros.  Just use yum or 
dnf to install it normally.  It will install an old-style daemon, so run 
“/etc/init.d/Jenkins start” for the initial startup.  Give it 30 seconds (it’s 
a really slow startup cuz its java under tomcat), and browse to port 8080.  
Remember to make allowances for /home/Jenkins getting really big.  That’s it, 
you can now prototype.  Unless you have a java-based product, you probably want 
a freestyle project, and call a bash or korn script to do the actual build.  
Good Luck!

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mohamed Sathack
Sent: February-17-15 04:38
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins CI setup on RedHat machine

Thanks Richard!

On Tuesday, 17 February 2015 13:03:49 UTC+5:30, Richard Bywater wrote:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions
 ?
Richard.

On Tue, Feb 17, 2015 at 8:28 PM, Mohamed Sathack 
> wrote:
Hi Everyone,

Good Morning!

I am exploring various options for CI in our project and came across through 
Hudson and Jenkins. Initial challenge in front of me is to set up everything in 
a Unix based mode. We have both Unix/Linux based servers.

I need to know Where to start my activity. I have gone through the below link. 
Jenkins installation and Tomcat configuration has been explained in that link. 
But I am not sure How to install Jenkins in Unix/Linux machine and which 
installables I have to use it for installation? For my initial analysis, I will 
be using Linux machine (RedHat Enterprise Server)

https://wiki.jenkins-ci.org/display/JENKINS/JenkinsLinuxStartupScript

Your suggestions are much appreciated!!!

Regards,
Sathack
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f3afa3d6-6683-44b4-9bc0-c530150e38cb%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d599141-0248-49f7-8fdd-f67ca196d914%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/26d4ebb4c45e449fa2a55ed52360b8c2%40mbx01colo01p.esentire.local.
For more options, visit https://groups.google.com/d/optout.

RE: Build using devenv.exe from Jenkins

[Ginga, Dick]

I use MSBUILD a lot. This is what my steps look like:

[cid:image001.png@01D04A8F.9D93C3F0]

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of kfhickel
Sent: Tuesday, February 17, 2015 7:33 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build using devenv.exe from Jenkins

In your script, add /useenv as an argument to devenv.exe.

e.g.: instead of "devenv.exe proj.sln", you want to issue "devenv /useenv 
proj.sln".

-Kelly

On Tuesday, February 17, 2015 at 5:32:29 AM UTC-6, Anitha Kabil Raj wrote:
Hello Group,
I have recently started using Jenkins for automating builds. I tried using 
MSBUILD plugin for building VC++ project using devnev.exe. I couldn't use it as 
the quotes around the configuration I was trying to build, "Release|Win32" was 
getting stripped. Is there any update available on this issue, or any 
workaround on same?
Now running devenev.exe from batch script. Here I see that the INCLUDE 
environment variable that I set is not getting picked by the project while 
build, hence the build fails. It is failing to include files from Windows DDK 
path, even after providing the path in INCLUDE variable. Anyone in group faced 
similar issue.
Since none of the these methods worked, I'm stuck and not able to proceed 
further.
Thanks in advance for the help,
Anitha
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c7a7258d-c128-4833-a651-b52632298232%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F9D85%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: ‘**/*.apk’ doesn’t match anything: ‘**’ exists but not ‘**/*.apk’

[Daniel Beck]

After a workspace has been created, the form field checks whether the pattern 
matches existing files in the workspace (and prints an error otherwise). Since 
there's no _successful_ build yet, it'll complain. Just ignore it. The 
assumption is that either you haven't run a build yet (no workspace, no 
validation), or the build was successful and the workspace contains whatever 
you want to archive.

On 17.02.2015, at 14:09, Ginga, Dick  wrote:

> I find that the Archive Artifacts plugin is very good at telling you “there 
> are no such files in the workspace” and that is what it is telling you. I am 
> guessing that there are no .apk file because your build failed to create them.
>  
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Prasanth .K
> Sent: Monday, February 16, 2015 5:19 AM
> To: jenkinsci-users@googlegroups.com
> Subject: ERROR: ‘**/*.apk’ doesn’t match anything: ‘**’ exists but not 
> ‘**/*.apk’
>  
> while i give extension as **/*.apk in the Archiving artifacts it will shows 
> error like this "**/*.apk’ doesn’t match anything: ‘**’ exists but not 
> ‘**/*.apk".How can i solve this.any one suggest me.
>  
> My console Output :
>  
> Started by user anonymous
> Building in workspace C:\Users\Prasanth\.jenkins\workspace\Test
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-parse --is-inside-work-tree # 
> timeout=10
> Fetching changes from the remote Git repository
>  > C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url 
> https://github.com/Prasanthkarthick/samp.git # timeout=10
> Fetching upstream changes from https://github.com/Prasanthkarthick/samp.git
>  > C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10
> using .gitcredentials to set credentials
>  > C:\Program Files (x86)\Git\cmd\git.exe config --local credential.helper 
> store 
> --file=\"C:\Users\Prasanth\AppData\Local\Temp\git2187987975379449027.credentials\"
>  # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe -c core.askpass=true fetch --tags 
> --progress https://github.com/Prasanthkarthick/samp.git 
> +refs/heads/*:refs/remotes/origin/*
>  > C:\Program Files (x86)\Git\cmd\git.exe config --local --remove-section 
> credential # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
> "refs/remotes/origin/master^{commit}" # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
> "refs/remotes/origin/origin/master^{commit}" # timeout=10
> Checking out Revision e379cc050db983a21f82e40e1a77015d3401cce1 
> (refs/remotes/origin/master)
>  > C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout # 
> timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe checkout -f 
> e379cc050db983a21f82e40e1a77015d3401cce1
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-list 
> e379cc050db983a21f82e40e1a77015d3401cce1 # timeout=10
> [Test] $ cmd.exe /C '"C:\apache-ant-1.9.3\bin\ant.bat clean debug && exit 
> %%ERRORLEVEL%%"'
> Buildfile: C:\Users\Prasanth\.jenkins\workspace\Test\build.xml
>  
> -check-env:
>  [checkenv] Android SDK Tools Revision 24.0.0
>  [checkenv] Installed at 
> C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk
>  
> -setup:
>  [echo] Project Name: androidtestapp
>   [gettype] Project Type: Application
>  
> -pre-clean:
>  
> clean:
>[delete] Deleting directory C:\Users\Prasanth\.jenkins\workspace\Test\bin
>[delete] Deleting directory C:\Users\Prasanth\.jenkins\workspace\Test\gen
> [getlibpath] Library dependencies:
> [getlibpath] No Libraries
>[subant] No sub-builds to iterate on
>  
> -set-mode-check:
>  
> -set-debug-files:
>  
> -check-env:
>  [checkenv] Android SDK Tools Revision 24.0.0
>  [checkenv] Installed at 
> C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk
>  
> -setup:
>  [echo] Project Name: androidtestapp
>   [gettype] Project Type: Application
>  
> -set-debug-mode:
>  
> -debug-obfuscation-check:
>  
> -pre-build:
>  
> -build-setup:
> [getbuildtools] Using latest Build Tools: 21.1.1
>  [echo] Resolving Build Target for androidtestapp...
> [gettarget] Project Target:   Android 5.0
> [gettarget] API level:21
>  [echo] --
>  [echo] Creating output directories if needed...
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\res
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\rsObj
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\rsLibs
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\gen
> [mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\classes
> [mkdir] Created dir: 
> C:\Users\Prasanth\.jenkins\workspace\Test\bin\dexedLibs
>  [echo] --
>  [echo] Resolving Dependencies for androidtestapp...
> [dependency] Ordered libraries:
> [dependency] 
> [dependency] --
>  [echo] --
>  [echo] Building Libraries with 'de

RE: Groovy build script: What triggered the build

[Ginga, Dick]

There is a BUILD_CAUSE environment variable that can have values like: 
SCMTRIGGER, MANUALTRIGGER, and others

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Sverre Moe
Sent: Monday, February 16, 2015 7:06 AM
To: jenkinsci-users@googlegroups.com
Subject: Groovy build script: What triggered the build

Is it possible to find out who or what triggered the build from a Groovy 
script? Either an SCM change, another project or user. I have just begun 
reading a little about Groovy and the Jenkins API.

I want to check for the following conditions and build accordingly.

if (trigger == scm) {
  build_with_automake
  new_version = git tag exist for version
  if (new_version) {
tag new release candidate in Git
publish rc
  }
}
else if (trigger == "Build other projects") {
  build_with_automake
}

The project should build on every SCM change, but only tag and publish if 
version has been increased. It should also build when a build has been 
triggered by another project.
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a4a10f09-9846-4c6e-b572-ed5123f0977d%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F9B58%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Using python scripts from scriptler?

[Wojciech Korzenny]

Hi, 

Do you know if exists/existed any plugin for jenkins that allows writing 
scripts for scriptler in Python instead of groovy which seems to be the 
only option? 

W. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5381ee07-7378-4d12-8efc-fa30a84611c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: ERROR: ‘**/*.apk’ doesn’t match anything: ‘**’ exists but not ‘**/*.apk’

[Ginga, Dick]

I find that the Archive Artifacts plugin is very good at telling you “there are 
no such files in the workspace” and that is what it is telling you. I am 
guessing that there are no .apk file because your build failed to create them.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Prasanth .K
Sent: Monday, February 16, 2015 5:19 AM
To: jenkinsci-users@googlegroups.com
Subject: ERROR: ‘**/*.apk’ doesn’t match anything: ‘**’ exists but not 
‘**/*.apk’

while i give extension as **/*.apk in the Archiving artifacts it will shows 
error like this "**/*.apk’ doesn’t match anything: ‘**’ exists but not 
‘**/*.apk".How can i solve this.any one suggest me.

My console Output :


Started by user anonymous

Building in workspace C:\Users\Prasanth\.jenkins\workspace\Test

 > C:\Program Files (x86)\Git\cmd\git.exe rev-parse --is-inside-work-tree # 
 > timeout=10

Fetching changes from the remote Git repository

 > C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/Prasanthkarthick/samp.git # timeout=10

Fetching upstream changes from https://github.com/Prasanthkarthick/samp.git

 > C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10

using .gitcredentials to set credentials

 > C:\Program Files (x86)\Git\cmd\git.exe config --local credential.helper 
 > store 
 > --file=\"C:\Users\Prasanth\AppData\Local\Temp\git2187987975379449027.credentials\"
 >  # timeout=10

 > C:\Program Files (x86)\Git\cmd\git.exe -c core.askpass=true fetch --tags 
 > --progress https://github.com/Prasanthkarthick/samp.git 
 > +refs/heads/*:refs/remotes/origin/*

 > C:\Program Files (x86)\Git\cmd\git.exe config --local --remove-section 
 > credential # timeout=10

 > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/master^{commit}" # timeout=10

 > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/master^{commit}" # timeout=10

Checking out Revision e379cc050db983a21f82e40e1a77015d3401cce1 
(refs/remotes/origin/master)

 > C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout # 
 > timeout=10

 > C:\Program Files (x86)\Git\cmd\git.exe checkout -f 
 > e379cc050db983a21f82e40e1a77015d3401cce1

 > C:\Program Files (x86)\Git\cmd\git.exe rev-list 
 > e379cc050db983a21f82e40e1a77015d3401cce1 # timeout=10

[Test] $ cmd.exe /C '"C:\apache-ant-1.9.3\bin\ant.bat clean debug && exit 
%%ERRORLEVEL%%"'

Buildfile: C:\Users\Prasanth\.jenkins\workspace\Test\build.xml



-check-env:

 [checkenv] Android SDK Tools Revision 24.0.0

 [checkenv] Installed at C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk



-setup:

 [echo] Project Name: androidtestapp

  [gettype] Project Type: Application



-pre-clean:



clean:

   [delete] Deleting directory C:\Users\Prasanth\.jenkins\workspace\Test\bin

   [delete] Deleting directory C:\Users\Prasanth\.jenkins\workspace\Test\gen

[getlibpath] Library dependencies:

[getlibpath] No Libraries

   [subant] No sub-builds to iterate on



-set-mode-check:



-set-debug-files:



-check-env:

 [checkenv] Android SDK Tools Revision 24.0.0

 [checkenv] Installed at C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk



-setup:

 [echo] Project Name: androidtestapp

  [gettype] Project Type: Application



-set-debug-mode:



-debug-obfuscation-check:



-pre-build:



-build-setup:

[getbuildtools] Using latest Build Tools: 21.1.1

 [echo] Resolving Build Target for androidtestapp...

[gettarget] Project Target:   Android 5.0

[gettarget] API level:21

 [echo] --

 [echo] Creating output directories if needed...

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\res

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\rsObj

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\rsLibs

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\gen

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\classes

[mkdir] Created dir: C:\Users\Prasanth\.jenkins\workspace\Test\bin\dexedLibs

 [echo] --

 [echo] Resolving Dependencies for androidtestapp...

[dependency] Ordered libraries:

[dependency]

[dependency] --

 [echo] --

 [echo] Building Libraries with 'debug'...

   [subant] No sub-builds to iterate on



-code-gen:

[mergemanifest] Merging AndroidManifest files into one.

[mergemanifest] Manifest merger disabled. Using project manifest only.

 [echo] Handling aidl files...

 [aidl] No AIDL files to compile.

 [echo] --

 [echo] Handling RenderScript files...

 [echo] --

 [echo] Handling Resources...

 [aapt] Generating resource IDs...

 [echo] --

 [echo] Handling BuildConfig class...

[buildconfig] Generating BuildConfig class

RE: Deadlock running out of executors waiting on subjobs via parameterized trigger plugin

[Ginga, Dick]

If you do not need A and B to wait for C and D to complete, then trigger them 
using a post-build trigger using the Trigger Parameterized Build plugin. This 
will run before A completes but not cause A to wait. Then an executor will 
become available as A terminates

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver
Sent: Friday, February 13, 2015 4:27 PM
To: jenkinsci-users@googlegroups.com
Subject: Deadlock running out of executors waiting on subjobs via parameterized 
trigger plugin


I'm looking for some help/direction at resolving an odd problem.  We currently 
only have one node (still in the midst of setting up/configuring hardware), and 
we encountered a scenario where we have just a couple executors that can run on 
the machine at once (say 2).  If I start jobs A & B which run jobs C & D via 
the parameterized trigger plugin and wait for those to complete, no jobs ever 
finish.  C & D are never started due to lack of executors and A & B cannot 
complete waiting for those jobs.

We are using Perforce and I am trying to be efficient with workspaces as 
syncing new workspaces is really expensive (we are already at gigs of data) 
part of the objective is to reuse the workspace between the jobs (so C & D can 
run within the workspaces set up by A & B).

Is there a detail I'm missing?  None of the jobs are set up to block waiting 
for upstream or downstream jobs to finish.

I'm on (with versions of job related plugins in case there is an interaction):
* Jenkins 1.592
* Build Pipeline Plugin 1.4.5
* External Job Monitor Plugin 1,4
* Join Plugin 1.15
* Matrix Project Plugin 1.4
* Node & Label Parameter Plugin 1.5.1
* Parameterized Trigger Plugin 2.25

I did have the job weight plugin at one point, but no longer.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1fc6b4ef-f34d-4e45-a4aa-96e22cb57a79%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E4F997C%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Re: Build using devenv.exe from Jenkins

[kfhickel]

In your script, add /useenv as an argument to devenv.exe.

e.g.: instead of "devenv.exe proj.sln", you want to issue "devenv /useenv 
proj.sln".

-Kelly

On Tuesday, February 17, 2015 at 5:32:29 AM UTC-6, Anitha Kabil Raj wrote:
>
> Hello Group,
> I have recently started using Jenkins for automating builds. I tried using 
> MSBUILD plugin for building VC++ project using devnev.exe. I couldn't use 
> it as the quotes around the configuration I was trying to build, 
> "Release|Win32" was getting stripped. Is there any update available on this 
> issue, or any workaround on same?
> Now running devenev.exe from batch script. Here I see that the INCLUDE 
> environment variable that I set is not getting picked by the project while 
> build, hence the build fails. It is failing to include files from Windows 
> DDK path, even after providing the path in INCLUDE variable. Anyone in 
> group faced similar issue. 
> Since none of the these methods worked, I'm stuck and not able to proceed 
> further.
> Thanks in advance for the help,
> Anitha
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c7a7258d-c128-4833-a651-b52632298232%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build using devenv.exe from Jenkins

[Anitha Kabil Raj]

Hello Group,
I have recently started using Jenkins for automating builds. I tried using 
MSBUILD plugin for building VC++ project using devnev.exe. I couldn't use 
it as the quotes around the configuration I was trying to build, 
"Release|Win32" was getting stripped. Is there any update available on this 
issue, or any workaround on same?
Now running devenev.exe from batch script. Here I see that the INCLUDE 
environment variable that I set is not getting picked by the project while 
build, hence the build fails. It is failing to include files from Windows 
DDK path, even after providing the path in INCLUDE variable. Anyone in 
group faced similar issue. 
Since none of the these methods worked, I'm stuck and not able to proceed 
further.
Thanks in advance for the help,
Anitha

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/411cb15f-6a0e-45a9-9127-d4d4be35c396%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CI setup on RedHat machine

[Mohamed Sathack]

Thanks Richard! 

On Tuesday, 17 February 2015 13:03:49 UTC+5:30, Richard Bywater wrote:
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions
>  
> ?
>
> Richard.
>
> On Tue, Feb 17, 2015 at 8:28 PM, Mohamed Sathack  > wrote:
>
>> Hi Everyone,
>>
>> Good Morning!
>>
>> I am exploring various options for CI in our project and came across 
>> through Hudson and Jenkins. Initial challenge in front of me is to set up 
>> everything in a Unix based mode. We have both Unix/Linux based servers.
>>
>> I need to know Where to start my activity. I have gone through the below 
>> link. Jenkins installation and Tomcat configuration has been explained in 
>> that link. But I am not sure How to install Jenkins in Unix/Linux machine 
>> and which installables I have to use it for installation? For my initial 
>> analysis, I will be using Linux machine (RedHat Enterprise Server)
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/JenkinsLinuxStartupScript 
>> 
>>
>> Your suggestions are much appreciated!!!
>>
>> Regards,
>> Sathack
>>
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/f3afa3d6-6683-44b4-9bc0-c530150e38cb%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d599141-0248-49f7-8fdd-f67ca196d914%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SIGSERV 0x00007f9475ebde80

[Marc Leforestier]

Hello

Le lundi 16 février 2015 15:59:53 UTC+1, Baptiste Mathus a écrit :
>
> Can you please try with a less bleeding edge version, e.g. the latest LTS 
> like the 1.580.3 to see if this still crashes for you? That would help 
> narrow the issue down.
>
>
 Yes, I've just finished to install a new server with lts version. I will 
post here if it's still crashing or not.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/82fdf884-1a85-4b17-9c9d-195821c0543f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.