Re: Builds of new configuration in a matrix build are lost after some time.

2012-11-28 Thread B.Latinville

I created a new job yesterday, copy from one existing matrix job.
I run a single build, could see the build results.
This morning it was not visible any more.
I upgraded to 1.492, and my build result is back.
Rebooting jenkins did not solve the problem when it occurred.
Hopefully the upgrade will solve the issue even though I did not 
see anything related to it in jenkin's changelog.



Re: Configuration file

2012-11-28 Thread Jean-Marc Bourguet
On Tue, 27 Nov 2012 20:13:49 -0800 (PST), Jerry
gpjerrymalo...@gmail.com wrote:
 Hi, Jean-Marc. You should be able to do this by adding a build step
 before you run the rest of your job that executes a shell script to
 modify the config file. 

If you are suggesting something like

if ! cmp proposedConfig previousConfig ; then
   cp proposedConfig trueConfig
   cp proposedConfig previousConfig
fi

with the reset done as

cp defaultConfig trueConfig

It would have the problems
1/ what is presented in the editor is proposedConfig, not trueConfig,
thus error prone as the person who edit it would have to know that some
differences have to be undone and know which.
2/ undoing a reset is not possible in the editor without making a non
significant change, again making the process error prone.

 You might also make it a parameterized build
 (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) to
 automate it further.

I don't see how to use this for my purpose. It looks like it would
suffer for the same problems as the previous solution and then some
more, providing all potential changes as parameters in a parametrized
build would be painful and some won't be modified for years.

Again, what I want is the possibility to modify the configuration for
the next builds until something reset them automatically to their
default. Currently the reset is done by copying a default to the
configuration file used, and modifying trueConfig is done by hand.

Thanks for your idea.

Yours,

-- 
Jean-Marc


Re: Jenkins on Windows box

2012-11-28 Thread cjo
You might also want to check what build steps and post build steps you have 
enabled in the job, as some of them such as the warnings plugin require the 
previous build to have completed. 

As they declare that the step needs the previous build to complete, to 
perform the correct actions. 
they use the BuildStepMonitor as used in [1]. 
e.g. the warnings plugin needs the previous build to be complete so that it 
can calculate new / fixed warnings counts.

[1] 
http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

Chris.

On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com javascript: [mailto:
 jenkins...@googlegroups.com javascript:] *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com javascript:
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com javascript:
 *To:* jenkins...@googlegroups.com javascript: 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but when 
 I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before pausing).  Anyone seen anything like this before?  Any 
 idea what I can do to fix it?

  

 If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP machine.

  

 Thanks!

  

 Bill

  



How can i get build number when using remote API

2012-11-28 Thread Shen,Hui
Hi guys,

I try to programmatically schedule a new build by posting a message to
http://HOSTNAME:PORT/jenkins/job/JOBNAME/build

This is worked, a new build was fired, but how can I get the build number it 
just fired.

I had try using http://HOSTNAME:PORT/jenkins/job/JOBNAME/lastBuild/, but it's 
not exactly the build number it fired.
Since there are cases two builds are fired in short time period.


Can anybody help with this. Thanks very much.


Shen Hui
BB - F2 - AW264|x28530



Re: Jenkins on Windows box

2012-11-28 Thread Bill Wonch
Hi everyone -

Thanks for your quick responses!

This isn't for a build (at least in the sense that it generates an 
artifact) it's part of an automated deployment process that we have set up. 
 The first step calls a small batch script which verifies that the user is 
in a specific group if the ENVIRONMENT parameter is not dev (using the 
Conditional Build Step plugin).  It seems to get through the condition 
checking fine, then stalls when it hits the batch file.  Here is what the 
configuration looks like for the first step:

  concurrentBuildtrue/concurrentBuild
  builders

org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder
  condition class=org.jenkins_ci.plugins.run_condition.logic.Not
condition 
class=org.jenkins_ci.plugins.run_condition.core.StringsMatchCondition
  arg1${ENV,var=quot;ENVIRONMENTquot;}/arg1
  arg2dev/arg2
  ignoreCasefalse/ignoreCase
/condition
  /condition
  buildStep class=hudson.tasks.BatchFile
commandauthorization\environment_authorization.bat/command
  /buildStep
  runner 
class=org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail/

/org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder

As you can see, I've got it configured to run multiple builds concurrently, 
which seems to work - it definitely takes up two executors when I try to 
run two jobs at the same time, and makes it as far as checking the 
conditions specified in the step above.  It only stalls when it hits 
authorization\environment_authorization.bat. 

The contents of that batch script are:

@echo off
set i=0
set group=DTCA_APD_JENKINS_ADMI
set user=%BUILD_USER_ID%
echo Checking if %user% is member of %group%...
for /f %%f in ('net user %user% /domain | findstr /i %group%') do set /a 
i=%i%+1
if %i% gtr 0 (goto :member)
:nomember
echo FAILURE: Authentication check failed.  You are not authorized to 
deploy in this environment.
exit 1
:member
echo SUCCESS: Authentication check passed
exit 0
   
So ti really just requests a user's group info from the domain, and fails 
the build if the user is not in the correct group.  At first I thought it 
might be a file locking issue of some sort, but these are in two separate 
workspaces, each with their own copy of the script...

As far as post-build steps go, for this job I only have a small postbuild 
groovy step that publishes some audit information on the build page.  We 
use a similar pattern on a couple of other jobs, and all have this same 
problem.

If it woulld help I can post the config.xml file for the job?

Thanks again!

Bill

On Wednesday, November 28, 2012 4:49:40 AM UTC-7, cjo wrote:

 You might also want to check what build steps and post build steps you 
 have enabled in the job, as some of them such as the warnings plugin 
 require the previous build to have completed. 

 As they declare that the step needs the previous build to complete, to 
 perform the correct actions. 
 they use the BuildStepMonitor as used in [1]. 
 e.g. the warnings plugin needs the previous build to be complete so that 
 it can calculate new / fixed warnings counts.

 [1] 
 http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

 Chris.

 On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] 
 *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com
 *To:* jenkins...@googlegroups.com 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but 
 when I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before pausing).  Anyone seen anything like this before?  Any 
 idea what I can do to fix it?

  

 If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP 
 machine.

  

 Thanks!

  

 Bill

  



Re: Configuration file

2012-11-28 Thread Jerry
OK, I'm getting a clearer idea of what you're trying to do. I had thought 
you were trying to generate a config on the fly, and that's why I suggested 
the parameterized build, but you're right, that's not relevant to your 
issue.

If I understand it correctly, maybe you can keep numerous config files in 
different branches in source control, then pull an appropriate branch in 
Jenkins to get the right config?



On Wednesday, November 28, 2012 4:31:55 AM UTC-5, Jean-Marc Bourguet wrote:

 On Tue, 27 Nov 2012 20:13:49 -0800 (PST), Jerry 
 gpjerry...@gmail.com javascript: wrote: 
  Hi, Jean-Marc. You should be able to do this by adding a build step 
  before you run the rest of your job that executes a shell script to 
  modify the config file. 

 If you are suggesting something like 

 if ! cmp proposedConfig previousConfig ; then 
cp proposedConfig trueConfig 
cp proposedConfig previousConfig 
 fi 

 with the reset done as 

 cp defaultConfig trueConfig 

 It would have the problems 
 1/ what is presented in the editor is proposedConfig, not trueConfig, 
 thus error prone as the person who edit it would have to know that some 
 differences have to be undone and know which. 
 2/ undoing a reset is not possible in the editor without making a non 
 significant change, again making the process error prone. 

  You might also make it a parameterized build 
  (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) to 
  automate it further. 

 I don't see how to use this for my purpose. It looks like it would 
 suffer for the same problems as the previous solution and then some 
 more, providing all potential changes as parameters in a parametrized 
 build would be painful and some won't be modified for years. 

 Again, what I want is the possibility to modify the configuration for 
 the next builds until something reset them automatically to their 
 default. Currently the reset is done by copying a default to the 
 configuration file used, and modifying trueConfig is done by hand. 

 Thanks for your idea. 

 Yours, 

 -- 
 Jean-Marc 



Re: Jenkins on Windows box

2012-11-28 Thread Bill Wonch
I think I found the problem: 
 https://issues.jenkins-ci.org/browse/JENKINS-13871

It looks like a fix may have been committed.  I'm going to move my variable 
checking into the batch file until I see a fix on that issue.  Thanks 
everyone!

On Wednesday, November 28, 2012 8:28:42 AM UTC-7, Bill Wonch wrote:

 Hi everyone -

 Thanks for your quick responses!

 This isn't for a build (at least in the sense that it generates an 
 artifact) it's part of an automated deployment process that we have set up. 
  The first step calls a small batch script which verifies that the user is 
 in a specific group if the ENVIRONMENT parameter is not dev (using the 
 Conditional Build Step plugin).  It seems to get through the condition 
 checking fine, then stalls when it hits the batch file.  Here is what the 
 configuration looks like for the first step:

   concurrentBuildtrue/concurrentBuild
   builders
 
 org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder
   condition class=org.jenkins_ci.plugins.run_condition.logic.Not
 condition 
 class=org.jenkins_ci.plugins.run_condition.core.StringsMatchCondition
   arg1${ENV,var=quot;ENVIRONMENTquot;}/arg1
   arg2dev/arg2
   ignoreCasefalse/ignoreCase
 /condition
   /condition
   buildStep class=hudson.tasks.BatchFile
 commandauthorization\environment_authorization.bat/command
   /buildStep
   runner 
 class=org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail/
 
 /org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder

 As you can see, I've got it configured to run multiple builds 
 concurrently, which seems to work - it definitely takes up two executors 
 when I try to run two jobs at the same time, and makes it as far as 
 checking the conditions specified in the step above.  It only stalls when 
 it hits authorization\environment_authorization.bat. 

 The contents of that batch script are:

 @echo off
 set i=0
 set group=DTCA_APD_JENKINS_ADMI
 set user=%BUILD_USER_ID%
 echo Checking if %user% is member of %group%...
 for /f %%f in ('net user %user% /domain | findstr /i %group%') do set /a 
 i=%i%+1
 if %i% gtr 0 (goto :member)
 :nomember
 echo FAILURE: Authentication check failed.  You are not authorized to 
 deploy in this environment.
 exit 1
 :member
 echo SUCCESS: Authentication check passed
 exit 0

 So ti really just requests a user's group info from the domain, and fails 
 the build if the user is not in the correct group.  At first I thought it 
 might be a file locking issue of some sort, but these are in two separate 
 workspaces, each with their own copy of the script...

 As far as post-build steps go, for this job I only have a small postbuild 
 groovy step that publishes some audit information on the build page.  We 
 use a similar pattern on a couple of other jobs, and all have this same 
 problem.

 If it woulld help I can post the config.xml file for the job?

 Thanks again!

 Bill

 On Wednesday, November 28, 2012 4:49:40 AM UTC-7, cjo wrote:

 You might also want to check what build steps and post build steps you 
 have enabled in the job, as some of them such as the warnings plugin 
 require the previous build to have completed. 

 As they declare that the step needs the previous build to complete, to 
 perform the correct actions. 
 they use the BuildStepMonitor as used in [1]. 
 e.g. the warnings plugin needs the previous build to be complete so that 
 it can calculate new / fixed warnings counts.

 [1] 
 http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

 Chris.

 On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] 
 *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com
 *To:* jenkins...@googlegroups.com 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but 
 when I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before 

All build executors permanently dead!

2012-11-28 Thread tortoise74
Hi, 
 All my build executor threads on all nodes have died simultaneously 
shortly following upgrade to 1.491 and don't seem to come back no matter 
what I try restarting. I have filed a bug report here:

https://issues.jenkins-ci.org/browse/JENKINS-15957

Anyone have an idea how I can fix this?
I tried upgrading to 1.492 in case it had a fix and have lost the ability 
to downgrade to something earlier directly from the UI. Is there a log of 
when the update was a applied?

Regards,

Bruce.



Re: Installing Jenkins on Windows Server 2012 Standard fails

2012-11-28 Thread Drew Mace
Well first I want to say thank you to all that replied.

I finally figured out the issue.  Windows Server 2012 has the .Net 
Framework 4 installed by default.  Jenkins needs the 3.5 Framework.  Once I 
installed the 3.5 framework, things installed perfectly.  Hope this helps 
other users in the future.

On Sunday, November 25, 2012 9:26:07 PM UTC-5, Drew Mace wrote:

 I'm trying to install Jenkins on a Windows Server 2012 Standard edition 
 box but hit a snag - I am getting an error: Service 'Jenkins' (Jenkins) 
 failed to start.  Verify that you have sufficient privileges to start 
 system services.  I ran the installer as administrator (elevated privs).  
 Anyone have any ideas what i could try?



buildWithParameters: setting build parameters via a json object HELP

2012-11-28 Thread jenkinophyte

Folks,

I cant seem to get this to work.
I have a large number of parameters I want to pass to a build that requires 
me to use post and a JSON object.
As a test I created a job (myTest) that has one string param (my_param) 
with a default value of 0. 
Following the example in the docs I trigger the build via curl passing a 
json object with the my_param set to 1.
The build is triggered just fine but the parameter never picks up the value 
passed.

This is what the formatting of my json object looks like:
json={\parameter\: [{\name\: \my_param\, \value\: \1\}], 
\\:\\}

And the command:
url=http:\\mysite.com/builds/view/All%20Enabled/job/myTest/buildWithParameters
curl -X POST $url -d token=MYTOKEN --data-urlencode json=$json

Again I am using json with post as the final length of my parameter list 
will exceed the byte limit allowed when sending params directly via the url.
Anyone have an example of this working? What am I doing wrong... banging 
head on this for a full day now..

Jenkinophyte


Re: How can i get build number when using remote API

2012-11-28 Thread jenkinophyte
Don't know if this is the best way to do this but 2 solutions come to mind..
1.) You can use the jenkins pyhon api to get at this information see module 
docs.
2.) The job will inject the variable $BUILD_NUMBER into the running 
environment so publish it to yourself via Jython or bash dumping to a file 
etc.

On Wednesday, November 28, 2012 4:00:02 AM UTC-8, Shen,Hui wrote:

 Hi guys,

  

 I try to programmatically schedule a new build by posting a message to

 http://HOSTNAME:PORT/jenkins/job/JOBNAME/build

  

 This is worked, a new build was fired, but how can I get the build number 
 it just fired.

  

 I had try using http://HOSTNAME:PORT/jenkins/job/JOBNAME/lastBuild/, but 
 it’s not exactly the build number it fired.

 Since there are cases two builds are fired in short time period.

  

  

 Can anybody help with this. Thanks very much.

  

  

 Shen Hui

 BB - F2 - AW264|x28530

  



Re: NullPointerException while trying to save job configuration

2012-11-28 Thread Christopher Orr

Did you install the Build Failure Analyzer plugin?

I started having the exact same problems -- as mentioned in the Known 
Issues for that plugin -- after I installed it.  Disabling the plugin 
fixed things again.



On 26/11/2012 07:01, David Resnick wrote:

Pushing Apply brings up an empty error window; pushing Save brings the
below error 500 stack trace.

I'm running Jenkins 1.491 with countless plugins. Any suggestions?

Thanks,
David


  Status Code: 500

Exception: java.lang.NullPointerException
Stacktrace:

javax.servlet.ServletException: java.lang.NullPointerException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
  

Re: NullPointerException while trying to save job configuration

2012-11-28 Thread Larry Shatzer, Jr.
Someone asked a question on the wiki page for the plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer?focusedCommentId=65668033#comment-65668033

I also ran into the same issue, and had to disable this plugin. I just have
not had time to dig into the plugin to find out what is broken with newer
versions.


On Wed, Nov 28, 2012 at 2:20 PM, Christopher Orr ch...@orr.me.uk wrote:

 Did you install the Build Failure Analyzer plugin?

 I started having the exact same problems -- as mentioned in the Known
 Issues for that plugin -- after I installed it.  Disabling the plugin
 fixed things again.



 On 26/11/2012 07:01, David Resnick wrote:

 Pushing Apply brings up an empty error window; pushing Save brings the
 below error 500 stack trace.

 I'm running Jenkins 1.491 with countless plugins. Any suggestions?

 Thanks,
 David


   Status Code: 500

 Exception: java.lang.NullPointerException
 Stacktrace:

 javax.servlet.**ServletException: java.lang.NullPointerException
 at org.kohsuke.stapler.Stapler.**tryInvoke(Stapler.java:615)
 at org.kohsuke.stapler.Stapler.**invoke(Stapler.java:658)
 at org.kohsuke.stapler.MetaClass$**6.doDispatch(MetaClass.java:**
 241)
 at org.kohsuke.stapler.**NameBasedDispatcher.dispatch(**
 NameBasedDispatcher.java:53)
 at org.kohsuke.stapler.Stapler.**tryInvoke(Stapler.java:573)
 at org.kohsuke.stapler.Stapler.**invoke(Stapler.java:658)
 at org.kohsuke.stapler.Stapler.**invoke(Stapler.java:487)
 at org.kohsuke.stapler.Stapler.**service(Stapler.java:164)
 at javax.servlet.http.**HttpServlet.service(**
 HttpServlet.java:45)
 at winstone.ServletConfiguration.**execute(ServletConfiguration.*
 *java:248)
 at winstone.RequestDispatcher.**forward(RequestDispatcher.**
 java:333)
 at winstone.RequestDispatcher.**doFilter(RequestDispatcher.**
 java:376)
 at hudson.util.**PluginServletFilter$1.**
 doFilter(PluginServletFilter.**java:95)
 at net.bull.javamelody.**MonitoringFilter.doFilter(**
 MonitoringFilter.java:206)
 at net.bull.javamelody.**MonitoringFilter.doFilter(**
 MonitoringFilter.java:179)
 at net.bull.javamelody.**PluginMonitoringFilter.**doFilter(**
 PluginMonitoringFilter.java:**86)
 at org.jvnet.hudson.plugins.**monitoring.**
 HudsonMonitoringFilter.**doFilter(**HudsonMonitoringFilter.java:**84)
 at hudson.util.**PluginServletFilter$1.**
 doFilter(PluginServletFilter.**java:98)
 at hudson.plugins.greenballs.**GreenBallFilter.doFilter(**
 GreenBallFilter.java:58)
 at hudson.util.**PluginServletFilter$1.**
 doFilter(PluginServletFilter.**java:98)
 at hudson.plugins.audit_trail.**AuditTrailFilter.doFilter(**
 AuditTrailFilter.java:66)
 at hudson.util.**PluginServletFilter$1.**
 doFilter(PluginServletFilter.**java:98)
 at hudson.util.**PluginServletFilter.doFilter(**
 PluginServletFilter.java:87)
 at winstone.FilterConfiguration.**execute(FilterConfiguration.**
 java:194)
 at winstone.RequestDispatcher.**doFilter(RequestDispatcher.**
 java:366)
 at hudson.security.csrf.**CrumbFilter.doFilter(**
 CrumbFilter.java:47)
 at winstone.FilterConfiguration.**execute(FilterConfiguration.**
 java:194)
 at winstone.RequestDispatcher.**doFilter(RequestDispatcher.**
 java:366)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:84)
 at hudson.security.**UnwrapSecurityExceptionFilter.**doFilter(**
 UnwrapSecurityExceptionFilter.**java:51)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at org.acegisecurity.ui.**ExceptionTranslationFilter.**doFilter(*
 *ExceptionTranslationFilter.**java:166)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at org.acegisecurity.providers.**anonymous.**
 AnonymousProcessingFilter.**doFilter(**AnonymousProcessingFilter.**
 java:125)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at org.acegisecurity.ui.**rememberme.**
 RememberMeProcessingFilter.**doFilter(**RememberMeProcessingFilter.**
 java:142)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at org.acegisecurity.ui.**AbstractProcessingFilter.**doFilter(**
 AbstractProcessingFilter.java:**271)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at org.acegisecurity.ui.**basicauth.**BasicProcessingFilter.**
 doFilter(**BasicProcessingFilter.java:**173)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at jenkins.security.**ApiTokenFilter.doFilter(**
 ApiTokenFilter.java:63)
 at hudson.security.**ChainedServletFilter$1.**
 doFilter(ChainedServletFilter.**java:87)
 at 

Build flow plugin parallel builds are not parallel

2012-11-28 Thread Mike Finneran
When I execute the following build flow script on a cluster of four 
identical nodes, only one node is used to execute all twelve instances of 
job-Build.
If I pull that node, All instances are still build on only one node, just 
the next node that is still on line.
I would have thought that all four nodes would be used to execute the 
Job-Build instances four at a time in parallel.
Am I doing something wrong in the code?
Also, I'm using the latest jenkins (build 1.492) and the latest build flow 
plugin (build 0.6) 

build(Job-Init);
parallel (
{ build(Job-Build, JOB_NUMBER: 1) },
{ build(Job-Build, JOB_NUMBER: 2) },
{ build(Job-Build, JOB_NUMBER: 3) },
{ build(Job-Build, JOB_NUMBER: 4) },
{ build(Job-Build, JOB_NUMBER: 5) },
{ build(Job-Build, JOB_NUMBER: 6) },
{ build(Job-Build, JOB_NUMBER: 7) },
{ build(Job-Build, JOB_NUMBER: 8) },
{ build(Job-Build, JOB_NUMBER: 9) },
{ build(Job-Build, JOB_NUMBER: 10) },
{ build(Job-Build, JOB_NUMBER: 11) },
{ build(Job-Build, JOB_NUMBER: 12) },
)
build(Job-report);




RE: Cygpath Cygwin Git

2012-11-28 Thread William Soula
Possibly /cygdrive/c/usr/local/bin/git for the path instead of 
/usr/local/bin/git.  Just my thoughts, I dont know beyond that.

Will

From: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com] on 
behalf of Ryan Lovelett [ryan.lovel...@gmail.com]
Sent: Wednesday, November 28, 2012 4:00 PM
To: jenkinsci-users@googlegroups.com
Subject: Cygpath Cygwin Git

I would have thought that through the use of the Cygpath plugin my Windows 
system I would be able to use the Cygwin installed git.

I know that the git executable is installed:

[Ryan@Windows /cygdrive/c/Projects]
$ cygpath -C ANSI -w `which git`
C:\cygwin\usr\local\bin\git

I have provided the Tool Location for the Windows node: /user/local/bin/git

This provides an error. I have the full error if it is relavant. But I think 
these two errors say everything necessary.

Error trying to determine the git version: Error performing command: 
/user/local/bin/git --version
...
Caused by: java.io.IOException: Cannot run program /user/local/bin/git: 
CreateProcess error=2, The system cannot find the file specified

So I said to heck with Cygpath; I will just provide the full executable from 
Windows (e.g., C:\cygwin\usr\local\bin\git) in the Tool Location for the 
Windows node. Which led to this error

Error trying to determine the git version: Command C:\cygwin\usr\local\bin\git 
--version returned status code -1073741515:
...
Caused by: hudson.plugins.git.GitException: Command 
C:\cygwin\usr\local\bin\git clone -o origin g...@our-git-repo.com:testing.git 
C:\jenkins\workspace\Git Clone\label\Windows returned status code -1073741515:

These errors have to do with the Cygwin environment not being loaded. I am not 
sure what to do about that.

Suggestions?


Re: Cygpath Cygwin Git

2012-11-28 Thread Urivan Flores
Maybe too obvious but did you try to double backslash? Otherwise it will
take it as a scape sequences.

Regards,

-Urivan
On Nov 28, 2012 2:00 PM, Ryan Lovelett ryan.lovel...@gmail.com wrote:

 I would have thought that through the use of the Cygpath plugin my Windows
 system I would be able to use the Cygwin installed git.

 I know that the git executable is installed:

 [Ryan@Windows /cygdrive/c/Projects]
 $ cygpath -C ANSI -w `which git`
 C:\cygwin\usr\local\bin\git

 I have provided the Tool Location for the Windows node:
 /user/local/bin/git

 This provides an error. I have the full error if it is relavant. But I
 think these two errors say everything necessary.

 Error trying to determine the git version: Error performing command:
 /user/local/bin/git --version
 ...
 Caused by: java.io.IOException: Cannot run program /user/local/bin/git:
 CreateProcess error=2, The system cannot find the file specified

 So I said to heck with Cygpath; I will just provide the full executable
 from Windows (e.g., C:\cygwin\usr\local\bin\git) in the Tool Location for
 the Windows node. Which led to this error

 Error trying to determine the git version: Command
 C:\cygwin\usr\local\bin\git --version returned status code -1073741515:
 ...
 Caused by: hudson.plugins.git.GitException: Command
 C:\cygwin\usr\local\bin\git clone -o origin g...@our-git-repo.com:testing.git
 C:\jenkins\workspace\Git Clone\label\Windows returned status code
 -1073741515:

 These errors have to do with the Cygwin environment not being loaded. I am
 not sure what to do about that.

 Suggestions?



Re: Installing Jenkins on Windows Server 2012 Standard fails

2012-11-28 Thread bearrito
Haha. Didn't think about that. Would be great if the installer would check 
for that.

On Wednesday, November 28, 2012 11:54:52 AM UTC-5, Drew Mace wrote:

 Well first I want to say thank you to all that replied.

 I finally figured out the issue.  Windows Server 2012 has the .Net 
 Framework 4 installed by default.  Jenkins needs the 3.5 Framework.  Once I 
 installed the 3.5 framework, things installed perfectly.  Hope this helps 
 other users in the future.

 On Sunday, November 25, 2012 9:26:07 PM UTC-5, Drew Mace wrote:

 I'm trying to install Jenkins on a Windows Server 2012 Standard edition 
 box but hit a snag - I am getting an error: Service 'Jenkins' (Jenkins) 
 failed to start.  Verify that you have sufficient privileges to start 
 system services.  I ran the installer as administrator (elevated privs).  
 Anyone have any ideas what i could try?



Re: Cygpath Cygwin Git

2012-11-28 Thread Ryan Lovelett
Caused by: java.io.IOException: Cannot run program 
/cygdrive/c/usr/local/bin/git: CreateProcess error=2, The system cannot 
find the file specified

On Wednesday, November 28, 2012 4:18:23 PM UTC-6, William Soula wrote:

  Possibly /cygdrive/c/usr/local/bin/git for the path instead of 
 /usr/local/bin/git.  Just my thoughts, I dont know beyond that.

 Will
  --
 *From:* jenkins...@googlegroups.com javascript: [
 jenkins...@googlegroups.com javascript:] on behalf of Ryan Lovelett [
 ryan.l...@gmail.com javascript:]
 *Sent:* Wednesday, November 28, 2012 4:00 PM
 *To:* jenkins...@googlegroups.com javascript:
 *Subject:* Cygpath Cygwin Git

  I would have thought that through the use of the Cygpath plugin my 
 Windows system I would be able to use the Cygwin installed git. 

  I know that the git executable is installed:

  [Ryan@Windows /cygdrive/c/Projects]
 $ cygpath -C ANSI -w `which git`
 C:\cygwin\usr\local\bin\git
  
  I have provided the Tool Location for the Windows node: 
 /user/local/bin/git

  This provides an error. I have the full error if it is relavant. But I 
 think these two errors say everything necessary.

  Error trying to determine the git version: Error performing command: 
 /user/local/bin/git --version
  ...
 Caused by: java.io.IOException: Cannot run program /user/local/bin/git: 
 CreateProcess error=2, The system cannot find the file specified
  
  So I said to heck with Cygpath; I will just provide the full executable 
 from Windows (e.g., C:\cygwin\usr\local\bin\git) in the Tool Location for 
 the Windows node. Which led to this error

  Error trying to determine the git version: Command 
 C:\cygwin\usr\local\bin\git --version returned status code -1073741515:
  ...
 Caused by: hudson.plugins.git.GitException: Command 
 C:\cygwin\usr\local\bin\git clone -o origin 
 g...@our-git-repo.com:testing.git C:\jenkins\workspace\Git 
 Clone\label\Windows returned status code -1073741515:
  
  These errors have to do with the Cygwin environment not being loaded. I 
 am not sure what to do about that.

  Suggestions?
   


Re: Cygpath Cygwin Git

2012-11-28 Thread Ryan Lovelett
It returns the same status code.

On Wednesday, November 28, 2012 4:23:21 PM UTC-6, Urivan Flores wrote:

 Maybe too obvious but did you try to double backslash? Otherwise it will 
 take it as a scape sequences.

 Regards,

 -Urivan
 On Nov 28, 2012 2:00 PM, Ryan Lovelett ryan.l...@gmail.comjavascript: 
 wrote:

 I would have thought that through the use of the Cygpath plugin my 
 Windows system I would be able to use the Cygwin installed git.

 I know that the git executable is installed:

 [Ryan@Windows /cygdrive/c/Projects]
 $ cygpath -C ANSI -w `which git`
 C:\cygwin\usr\local\bin\git

 I have provided the Tool Location for the Windows node: 
 /user/local/bin/git

 This provides an error. I have the full error if it is relavant. But I 
 think these two errors say everything necessary.

 Error trying to determine the git version: Error performing command: 
 /user/local/bin/git --version
 ...
 Caused by: java.io.IOException: Cannot run program /user/local/bin/git: 
 CreateProcess error=2, The system cannot find the file specified

 So I said to heck with Cygpath; I will just provide the full executable 
 from Windows (e.g., C:\cygwin\usr\local\bin\git) in the Tool Location 
 for the Windows node. Which led to this error

 Error trying to determine the git version: Command 
 C:\cygwin\usr\local\bin\git --version returned status code -1073741515:
 ...
 Caused by: hudson.plugins.git.GitException: Command 
 C:\cygwin\usr\local\bin\git clone -o origin 
 g...@our-git-repo.com:testing.git C:\jenkins\workspace\Git 
 Clone\label\Windows returned status code -1073741515:

 These errors have to do with the Cygwin environment not being loaded. I 
 am not sure what to do about that.

 Suggestions?



Re: Installing Jenkins on Windows Server 2012 Standard fails

2012-11-28 Thread Steven Scott
I have not used that OS, but as rule with Windows 7+, I run the Command
prompt as Administrator, and even File Explorer as administrator, then do
the install.  If I can when running the actual installer, I try to right
click and run it as Administrator as well.  Not running the command prompt
as administrator usually causes the failures.


On Sun, Nov 25, 2012 at 9:26 PM, Drew Mace dmac...@gmail.com wrote:

 I'm trying to install Jenkins on a Windows Server 2012 Standard edition
 box but hit a snag - I am getting an error: Service 'Jenkins' (Jenkins)
 failed to start.  Verify that you have sufficient privileges to start
 system services.  I ran the installer as administrator (elevated privs).
 Anyone have any ideas what i could try?