date:20140306















































Monique Maker
 commented on  JENKINS-15386


Cannot tag builds using cvs plugin















Is it possible to add CVS tagging as a build and/or post-build action?
The current solution with clicking on an additional link is not convenient because does not allow the tag verification against (team, company) rules.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs-tag] (JENKINS-17399) CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.















































Monique Maker
 commented on  JENKINS-17399


CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.















Is it possible to add CVS tagging to CVS plug-in as a build and/or post-build action?
The current solution in the CVS plug-in with clicking on an additional link is not convenient because does not allow the tag verification against (team, company) rules.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18313) "H" cron syntax - cannot specify "between 10 pm and 6 am"

2014-03-06 Thread xen...@gmail.com (JIRA)















































Jerzy Zagorski
 commented on  JENKINS-18313


"H" cron syntax - cannot specify "between 10 pm and 6 am"















Dave, you can try this:

H H(22-23),H(0-5) * * *



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs] (JENKINS-15386) Cannot tag builds using cvs plugin













































  
Monique Maker
 edited a comment on  JENKINS-15386


Cannot tag builds using cvs plugin
















Is it possible to add CVS tagging to CVS plug-in as a build and/or post-build action?
The current solution with clicking on an additional link is not convenient because does not allow the tag verification against (team, company) rules.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-22029) Build period cannot span midnight

2014-03-06 Thread xen...@gmail.com (JIRA)















































Jerzy Zagorski
 commented on  JENKINS-22029


Build period cannot span midnight















Hi, maybe you can split it into two time spans:

"H H(22-23)/2,H(0-6)/2 * * *"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

2014-03-06 Thread david.fr...@datacomm.ch (JIRA)















































David Frank
 commented on  JENKINS-21256


Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory















I see a very similar class-loading issue with FindBugsPublisher and dom4j on v1.551 with jobs that previously run fine on v1.544!!

Stacktrace for me is:


ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception
java.io.IOException: remote file operation failed: /app/jenkins/workspace/authserver at hudson.remoting.Channel@7cbae009:C_inttl10153_jenkins
	at hudson.FilePath.act(FilePath.java:910)
	at hudson.FilePath.act(FilePath.java:887)
	at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161)
	at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:144)
	at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705)
	at hudson.model.Run.execute(Run.java:1695)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: java.io.IOException: Remote call on C_inttl10153_jenkins failed
	at hudson.remoting.Channel.call(Channel.java:731)
	at hudson.FilePath.act(FilePath.java:903)
	... 13 more
Caused by: java.lang.NoClassDefFoundError: org/dom4j/DocumentException
	at java.lang.Class.getDeclaredFields0(Native Method)
	at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
	at java.lang.Class.getDeclaredField(Class.java:1880)
	at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1605)
	at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:50)
	at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:423)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.io.ObjectStreamClass.(ObjectStreamClass.java:411)
	at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:308)
	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:545)
	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582)
	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
	at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
	at hudson.remoting.UserRequest.perform(UserRequest.java:98)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: org.dom4j.DocumentException (WebAppClassLoader=Jenkins v1.551@59d0d45b did not find class file)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch2(RemoteClassLoader.java:727)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:777)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:784)
	at sun.reflect.GeneratedMethodAccessor2462.invoke(Unknown Source)
	at

[JIRA] [plugin] (JENKINS-22065) docker-build-step-plugin: Create image from Dockerfile

2014-03-06 Thread marcus.li...@gmx.de (JIRA)















































Marcus Linke
 commented on  JENKINS-22065


docker-build-step-plugin: Create image from Dockerfile















https://github.com/jenkinsci/docker-build-step-plugin/pull/1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git-client] (JENKINS-19001) Git polling not detecting changes since 1.1.1

2014-03-06 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-19001


Git polling not detecting changes since 1.1.1















Code changed in jenkins
User: Nicolas De Loof
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
 src/main/java/hudson/plugins/git/extensions/GitSCMExtension.java
 src/main/java/hudson/plugins/git/extensions/impl/AuthorInChangelog.java
 src/main/java/hudson/plugins/git/extensions/impl/DisableRemotePoll.java
 src/main/java/hudson/plugins/git/extensions/impl/PathRestriction.java
 src/main/java/hudson/plugins/git/extensions/impl/UserExclusion.java
 src/main/java/hudson/plugins/git/util/BuildChooser.java
 src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java
http://jenkins-ci.org/commit/git-plugin/d8338ce4bca957a555a8dd02e9681550ce3f4566
Log:
  [FIXED JENKINS-19001] extension can declare requirement for a workspace during polling





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs] (JENKINS-15386) Cannot tag builds using cvs plugin













































  
Monique Maker
 edited a comment on  JENKINS-15386


Cannot tag builds using cvs plugin
















Is it possible to add to CVS plug-in a build and/or post-build action for tagging?
The current tagging solution with clicking on an additional link is not convenient (for us) because requires additional human interaction, which can not be controlled.
Adding a build or post-build CVS tagging action, which to run on certain build results, will allow to:
1. Impose the build tagging (on success, for example);
2. Validate the tag (content) against some rules, using the Validating String Parameter Plugin for example;
3. Generate a tag based on other job run information.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs-tag] (JENKINS-17399) CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.













































  
Monique Maker
 edited a comment on  JENKINS-17399


CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.
















Is it possible to add to CVS plug-in a build and/or post-build action for tagging?
See this comment for more details.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)

2014-03-06 Thread kacynski.w...@aoins.com (JIRA)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















When will you be publishing 2.37.2.1 as an official fix?  I can help pursue the groovy script at a later point in time?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-03-06 Thread mar...@headcrashing.eu (JIRA)

Markus KARG
commented on JENKINS-16706

Configure provided settings.xml at the Maven plugin level, not at the Maven job level

Ok I am a step further now and have it running, and I think I know what the problem is.
First of all, I confirm that "Use default maven global settings" is working very well and it effectively leads to using the configured global settings.xml provided by the Config File Provider plugin.
Also I confirm that the option "provided settings.xml" is working well and it effectievely leads to using the configured settings.xml provided by the Config File Provider plugin – but that one has to be told in each and every Maven job description!
What not work is "Use default maven settings". It leads to the fact that Jenkins still is using a "vanilly" Maven config instead of the settings.xml provided by the Config File Provider plugin. And it looks like this is a known "limitation" (I would say: "bug") of the plugin.

Can someone please please please fix this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes















































Mark Waite
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















git-client-plugin 1.6.4 has been released and includes this change.  It should be visible on the update center within the next 8 hours.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit















































Mark Waite
 commented on  JENKINS-21936


Git Plugin 2.0.2 and later NullPointerException onNotifyCommit















Nicolas plans to release git-plugin 2.0.4 very soon.  I assume it will be available within the next few days.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes













































  
Mark Waite
 edited a comment on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes
















git-client-plugin 1.6.4 has been released and includes this change.  It should be visible on the update center within the next 8 hours.

Refer to https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin#GitClientPlugin-ChangeLog for the description of the changes in 1.6.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore















































Mark Waite
 commented on  JENKINS-22064


Git Repository Browser URL not saved anymore















That sounds like an upgrade compatibility issue.  Since there were major changes from git-plugin 1.x to git-plugin 2.x, there are some cases where the upgrade does not behave correctly.  It appears you've detected one of those cases.

Could you upload a copy of your job definition XML file so that we can consider eventually including it in a git-plugin upgrade compatibility test suite?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs] (JENKINS-15386) Cannot tag builds using cvs plugin













































  
Monique Maker
 edited a comment on  JENKINS-15386


Cannot tag builds using cvs plugin
















Is it possible to extend the CVS plug-in with a build and/or post-build actions for tagging?
The current tagging solution with clicking on an additional link is not convenient (for us) because requires additional human interaction, which can not be controlled.
Adding a build or post-build CVS tagging action, which to run on certain build results, will allow to:
1. Impose the build tagging (on success, for example);
2. Validate the tag (content) against some rules, using the Validating String Parameter Plugin for example;
3. Generate a tag based on other job run information.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs-tag] (JENKINS-17399) CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.













































  
Monique Maker
 edited a comment on  JENKINS-17399


CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.
















Is it possible to extend the CVS plug-in with a build and/or post-build actions for tagging?
See this comment for more details.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [plugin] (JENKINS-22066) PTC plugin has massive memory leak if scm names are not unique

2014-03-06 Thread lone...@gmail.com (JIRA)















































Robert Bitel
 created  JENKINS-22066


PTC plugin has massive memory leak if scm names are not unique















Issue Type:


Bug



Assignee:


Unassigned


Components:


plugin



Created:


06/Mar/14 3:23 PM



Description:


Our Jenkins server has 100+ jobs. We have been dealing with a severe memory leak after we updated our PTC plugin. After trying many things I noticed that if all configurations have unique scm names that this problem goes away.

To recreate this just create a number of jobs with the same scm config name. force a run of all these jobs at the same time ( you might need to have multiple executors ). you should see that some derby write threads never get cleaned up and memory is leaking. 




Project:


Jenkins



Labels:


PTC
scm




Priority:


Major



Reporter:


Robert Bitel

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [coverity] (JENKINS-22067) Coverity Plugin 1.3.0 + Coverity 7.0.3 = 503: Service Unavailable when Fetching Defects

2014-03-06 Thread ez2c...@java.net (JIRA)















































ez2cwhy
 created  JENKINS-22067


Coverity Plugin 1.3.0 + Coverity 7.0.3 = 503: Service Unavailable when Fetching Defects















Issue Type:


Bug



Affects Versions:


current



Assignee:


Ken Dang



Components:


coverity



Created:


06/Mar/14 3:31 PM



Description:


The plugin works perfectly when executing the analysis phase and committing the defects.  However, when it attempts to fetch the defects from the stream in order to update the Jenkins build page, it fails with a "HTTP status code 503: Service Unavailable."  Is there a change in the Web Services API that the plugin does not support?




Environment:


RHEL 6.3, Jenkins 1.547, Coverity Plugin 1.3.0




Project:


Jenkins



Priority:


Major



Reporter:


ez2cwhy

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-22068) Clicking "Build Now" on Promotion causes hanging promtion and requires Jenkins restart

2014-03-06 Thread kthiel...@amcomsoft.com (JIRA)

Kevin Thieling
created JENKINS-22068

Clicking "Build Now" on Promotion causes hanging promtion and requires Jenkins restart

Issue Type:

Bug

Assignee:

Unassigned

Components:

core, promoted-builds

Created:

06/Mar/14 3:33 PM

Description:

We came across an issue with promoting a build. Someone had gone into the jobs main page and clicked on "Promotion Status" on the left hand side, clicked on one of the promotions, and then just clicked the "Build Now" on the left side. This caused a promotion to queue up in this window only, not in any other view. The promotions just hangs. When you hover over it, it just says "Started null ago estimated time remaining: null" In order to get it to clear, I have to restart the core Jenkins service.

Normally we promote by clicking on the actual build number and then go to promotion status and then approve it, but I don't think the build now should break like this.

I understand that doing it through the build now isn't pointing at a specific build so I assume that is why it hangs, but it should maybe grab the latest build when you do it that way, or the build now link should not be an option on that page...

I have tried updating to the latest promoted plugin of 2.17 as well as the latest Jenkins version of 1.553 with no luck.
I can submit screen shots if needed.

Environment:

VM - Windows Server 2008 R2 64 bit

4 GB RAM

2 2.10 GHz processors

Jenkins Core - 1.530

Promoted Builds Plugin - 2.13, also tried 2.17

Project:

Jenkins

Priority:

Major

Reporter:

Kevin Thieling

[JIRA] [core] (JENKINS-22068) Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart

2014-03-06 Thread kthiel...@amcomsoft.com (JIRA)















































Kevin Thieling
 updated  JENKINS-22068


Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart
















Change By:


Kevin Thieling
(06/Mar/14 3:39 PM)




Summary:


Clicking "Build Now" on Promotion causes hanging
 promtion
 promotion
 and requires Jenkins restart



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-22068) Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart

2014-03-06 Thread kthiel...@amcomsoft.com (JIRA)















































Kevin Thieling
 updated  JENKINS-22068


Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart
















Change By:


Kevin Thieling
(06/Mar/14 3:46 PM)




Description:


We came across an issue with promoting a build.  Someone had gone into the jobs main page and clicked on "Promotion Status" on the left hand side, clicked on one of the promotions, and then just clicked the "Build Now" on the left side.  This caused a promotion to queue up in this window only, not in any other view.  The promotions just hangs.  When you hover over it, it just says "Started null ago estimated time remaining: null"
.  When clicking on Console output, I get a 404 error.
  In order to get it to clear, I have to restart the core Jenkins service.  Normally we promote by clicking on the actual build number and then go to promotion status and then approve it, but I don't think the build now should break like this.  I understand that doing it through the build now isn't pointing at a specific build so I assume that is why it hangs, but it should maybe grab the latest build when you do it that way, or the build now link should not be an option on that page...I have tried updating to the latest promoted plugin of 2.17 as well as the latest Jenkins version of 1.553 with no luck.

I can submit screen shots if needed.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline

2014-03-06 Thread public.thom...@gmail.com (JIRA)















































cici thomson
 commented on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline















Same problem:

Ubuntu 12.04.4 LTS
Jenkins: 1.551
Build Pipeline Plugin: 1.4.2
Not using Parameterized Triggers, but plugin 2.22 is installed for other projects



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-21091) Config flip-flopping















































Rob Petti
 commented on  JENKINS-21091


Config flip-flopping















If you manually deleted it, then it would just re-add it on the next run. It's used for configuring whether which change to start pulling changes from, so that the first build of an old project does not try to get a million changes from your SCM.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading

2014-03-06 Thread recampb...@java.net (JIRA)















































recampbell
 commented on  JENKINS-21003


ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading















Same problem here. CPU was at 200% thanks to about 27 threads trying to calculate disk usage for the same project. Disabling the disk-usage plugin fixed the issue.

I think this is critical to fix because it's problems like this that give Jenkins a bad name. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git-client] (JENKINS-22017) Git client: NoClassDefFoundError

2014-03-06 Thread martijn.po...@ga.amgate.com (JIRA)















































Martijn Polak
 commented on  JENKINS-22017


Git client: NoClassDefFoundError















I've bypassed the issue for now by creating a simple shell script that clones/pulls the repo passed as command line argument into the workspace (depending on whether the workspace contains a .git dir) and run that as first build step instead of a VCS checkout. No git-client needed 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [selenium] (JENKINS-22069) Client can not register to Selenium grid if jenkins is served via a proxy

2014-03-06 Thread bjoern.peder...@frm2.tum.de (JIRA)















































Björn Pedersen
 created  JENKINS-22069


Client can not  register to Selenium grid if jenkins is served via a proxy















Issue Type:


Bug



Affects Versions:


current



Assignee:


Richard Lavoie



Components:


selenium



Created:


06/Mar/14 4:40 PM



Description:


[VirtualBox] Stage 2 launcher completed
adding seleniumProtocol=WebDriver,browserName=firefox,maxInstances=1
Mrz 06, 2014 5:24:20 PM org.openqa.grid.internal.utils.SelfRegisteringRemote startRemoteServer
WARNING: error getting the parameters from the hub. The node may end up with wrong timeouts.Connection to http://: refuse

Actually the proxy does not  listen on port , these requests should go directly to the "real" jenkinshost.




Project:


Jenkins



Priority:


Major



Reporter:


Björn Pedersen

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cvs] (JENKINS-15386) Cannot tag builds using cvs plugin

2014-03-06 Thread michael.m.cla...@gmail.com (JIRA)















































Michael Clarke
 commented on  JENKINS-15386


Cannot tag builds using cvs plugin















Monique:  Does the CVS tag plugin not do what you want?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher

2014-03-06 Thread ke...@ludyte.net (JIRA)















































Kevin German
 commented on  JENKINS-21493


NullPointerException in Publisher















I see the problem on Jenkins 1.532.1 with Plot 1.6, but
I am unable to reproduce on Jenkins 1.532.1 with Plot 1.5 with the same data.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)

2014-03-06 Thread crawfish...@java.net (JIRA)















































crawfish101
 commented on  JENKINS-19059


[ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)















I actually like the idea of polling the spot instance and looking for an instance id associated with a fulfilled request.  The requirement of forcing the Jenkins master to be publicly accessible is a serious limitation.  This new polling mechanism could be a separate user configurable option, but if was actually working as expected then I don't know why a user would want to use the current inbound connection approach.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline

2014-03-06 Thread khanna.sa...@gmail.com (JIRA)















































Sagar Khanna
 commented on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline















Same issue:

CentOS release 6.4
Jenkins: 1.553
Build Pipeline Plugin: 1.4.2
Parameterized Trigger plugin: 2.22



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [promoted-builds] (JENKINS-22070) I want to be able to use the Promoted_user_name variable but it's not displayed when i'm executing the set command.

2014-03-06 Thread hv...@onemind.co (JIRA)















































hau vong
 created  JENKINS-22070


I want to be able to use the Promoted_user_name variable but it's not displayed when i'm executing the set command. 















Issue Type:


Bug



Assignee:


Unassigned


Components:


promoted-builds



Created:


06/Mar/14 6:44 PM



Description:


I want to be able to use the promoted_user_name variable and pass it as a parameter into a powershell script. but I can't get the environment variable to display when i execute the 'set' command. I'm running the promoted builds plugin ver 2.17. what am i doing wrong? How can i get the variable to be accessible?




Due Date:


24/Mar/14 12:00 AM




Environment:


Windows 2008 r2. running as  a service. using Jenkins ver 1.501. promoted builds plugin ver 2.17. 




Fix Versions:


current



Project:


Jenkins



Labels:


plugin




Priority:


Minor



Reporter:


hau vong

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-21554) NPE after "Waiting for Jenkins to finish collecting data"

2014-03-06 Thread tehran...@gmail.com (JIRA)















































Daniel Tehranian
 commented on  JENKINS-21554


NPE after "Waiting for Jenkins to finish collecting data"















ping - Juha?  Are you using DSL to generate your jobs?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [github] (JENKINS-22071) 'pull_request' type webhook from Github throws an exception

2014-03-06 Thread m...@nukulb.com (JIRA)















































Nukul Bhasin
 created  JENKINS-22071


'pull_request' type webhook from Github throws an exception















Issue Type:


Bug



Assignee:


Unassigned


Components:


github



Created:


06/Mar/14 7:25 PM



Description:


When configuring a Webhook from github of type 'push' the post is succesfully processed by the plugin.

When a Webhook from github is configured of type 'pull_request' the post, the plugin throws an exception complaining that there is no payload. 
Github support seems to suggest that they are sending the correct payload.

Exact line throwing the exception maps to this line -
https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubWebHook.java#L152
which maps to exception cause here
Caused by: java.lang.IllegalArgumentException: Not intended to be browsed interactively (must specify payload parameter)
	at com.cloudbees.jenkins.GitHubWebHook.doIndex(GitHubWebHook.java:154)

Fully detailed exception returned is right here.
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79)
	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:67)
	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 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doF

[JIRA] [core] (JENKINS-22072) Multi-configuration parent consumes an executor when build is queued with slave offline

2014-03-06 Thread ksm...@java.net (JIRA)

ksmyth
created JENKINS-22072

Multi-configuration parent consumes an executor when build is queued with slave offline

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

jenkins_config.xml, job_config.xml

Components:

core

Created:

06/Mar/14 7:57 PM

Description:

I have a multi-configuration job where "Restrict where this project can be run" is set to node1, and Configuration Matrix>Slaves is also set to node1. node1 has 1 executor.

If a build is started when node1 is online, the parent build doesn't consume an executor and the build completes successfully. If a build is started when node1 is offline, then when node1 is brought online, the parent build consumes the executor and the build is deadlocked, since the "node1" configuration has nowhere to run.

To repro:
Start with no Jenkins configuration
java -jar jenkins.war
Create node1 with 1 executor, started with JNLP. Don't connect it yet
Create multi-configuration job with both "Restrict where this project can be run" and the Configuration Matrix>Slaves set to node1
Schedule a build for the job
Run the node1 JNLP client. (It can be run on the same machine as the master)
The job never completes, as it is deadlocked

Environment:

Jenkins 1.552

Windows 7 master and slave

Project:

Jenkins

Priority:

Major

Reporter:

ksmyth

[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size















































Michal Turek
 updated  JENKINS-22073


ProjectAction should render graph, optimize build.xml size
















Change By:


Michal Turek
(06/Mar/14 8:09 PM)




Description:


The trend graph is part of project/job page and should be created in CppcheckProjectAction instead of in CppcheckBuildAction. Every build.xml file contains full plugin configuration
 now
 including all information for rendering of trend graph, this is not needed.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size















































Michal Turek
 started work on  JENKINS-22073


ProjectAction should render graph, optimize build.xml size
















Change By:


Michal Turek
(06/Mar/14 8:08 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size















































Michal Turek
 created  JENKINS-22073


ProjectAction should render graph, optimize build.xml size















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Michal Turek



Components:


cppcheck



Created:


06/Mar/14 8:08 PM



Description:


The trend graph is part of project/job page and should be created in CppcheckProjectAction instead of in CppcheckBuildAction. Every build.xml file contains full plugin configuration now including all information for rendering of trend graph, this is not needed.




Environment:


All




Project:


Jenkins



Priority:


Minor



Reporter:


Michal Turek

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size















































Michal Turek
 updated  JENKINS-22073


ProjectAction should render graph, optimize build.xml size
















Change By:


Michal Turek
(06/Mar/14 8:11 PM)




Description:


The trend graph is part of project/job page and should be created in CppcheckProjectAction instead of in CppcheckBuildAction. Every build.xml file contains full plugin configuration including all information for rendering of trend graph, this is not needed.
{noformat}  cppcheck.xmlfalsefalse  42  42  42  42  42  42  true  true  true  true  true  true  true  42  42  true  true  true  true  true  true  true  true  {noformat}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [matrix] (JENKINS-9531) choose matrix build nodes based on label matches

2014-03-06 Thread unmob...@gmail.com (JIRA)















































Phil Miller
 commented on  JENKINS-9531


choose matrix build nodes based on label matches















This would be very helpful to me as well. I've implemented the slave label axis work-around, but it's a seriously non-scalable hack. It'd be much preferable to have axes represent actual desired configurations, with whatever filters applied, and then separate logic to match enabled configurations with nodes on which to run them.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [downstream-buildview] (JENKINS-6256) Builds are listed under the wrong job

2014-03-06 Thread jel...@serena.com (JIRA)















































Joshua Ellis
 commented on  JENKINS-6256


Builds are listed under the wrong job















I'm experiencing a similar problem. The build.xml files are being placed in the wrong job files and messing up the last good build number. Is there a known work around? Would a Jenkins clean install help?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [matrix] (JENKINS-7542) Matrix jobs tied to label executed consecutively even if there are free nodes of this label

2014-03-06 Thread unmob...@gmail.com (JIRA)















































Phil Miller
 updated  JENKINS-7542


Matrix jobs tied to label executed consecutively even if there are free nodes of this label
















Change By:


Phil Miller
(06/Mar/14 8:37 PM)




Summary:


Matrix jobs tied to label executed
 consequently
 consecutively
 even if there are free nodes of this label



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-22027) Perforce Fire Storm . . .
















































Rob Petti
 assigned  JENKINS-22027 to Unassigned



Perforce Fire Storm . . . 
















Change By:


Rob Petti
(06/Mar/14 8:39 PM)




Assignee:


Rob Petti



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)

2014-03-06 Thread johnny.galam...@gmail.com (JIRA)

John Galambos
reopened JENKINS-21278

java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)

This does not fix the issue for me. I have a feeling it is because there are two places I am using this plugin:
1) Process xUnit Test result report (during the build)
2) Publish xUnit Test result report (during the post-build actions)

Step 1 works fine. Step 2 still results in the the original exception.

I have a feeling this is due to how the plugin affects the job config.xml.
Step 1 results in the following being added to the config file:

Build/TestResults/_javascript_Unit/*/.xml
false
true
true
true

Build/TestResults/NUnit/*/.xml
false
true
true
true

0
0
0
0

3000

Step 2 results in the following:

3000

Note that there is no types section in the publishers section. Could this be the issue?

Change By:

John Galambos
(06/Mar/14 8:46 PM)

Resolution:

Fixed

Status:

Resolved
Reopened

[JIRA] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)

2014-03-06 Thread johnny.galam...@gmail.com (JIRA)

John Galambos
edited a comment on JENKINS-21278

java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)

Step 1 works fine. Step 2 still results in the the original exception.

I have a feeling this is due to how the plugin affects the job config.xml.
Step 1 results in the following being added to the config file:

"xunit@1.84">

Build/TestResults/_javascript_Unit/**/*.xml
false
true
true
true

Build/TestResults/NUnit/**/*.xml
false
true
true
true

0
0
0
0

3000

Step 2 results in the following:

"xunit@1.84">

3000

Note that there is no types section in the publishers section. Could this be the issue?

[JIRA] [perforce] (JENKINS-21939) Perforce Clean Workspace "Full Wipe" should not add "-f" option to sync.















































Rob Petti
 commented on  JENKINS-21939


Perforce Clean Workspace "Full Wipe" should not add "-f" option to sync. 















Yes, actually, it should assume a force sync, otherwise the user won't get all the files unless their client's have table is also cleared, which the plugin doesn't do. Simply preventing a force sync from occurring will break the clean functionality for the majority of users.

I believe this is a bug in Perforce itself. '-f' and '-p' should not conflict with each other, as their functionality is not mutually exclusive. One option doesn't record the new state of the client while syncing, and the other syncs files even if the client reports them as being synced already.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-18464) Build Pipeline and Join plugin do not play nicely together















































John McGehee
 commented on  JENKINS-18464


Build Pipeline and Join plugin do not play nicely together















Workaround: Use the Multijob Plugin alone without the Build Pipeline Plugin.

The Multijob Plugin gives you the functionality of the Join Plugin, and its configuration is more straightforward. I actually like how it displays my running build better than the Build Pipeline Plugin.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-18464) Build Pipeline and Join plugin do not play nicely together













































  
John McGehee
 edited a comment on  JENKINS-18464


Build Pipeline and Join plugin do not play nicely together
















WORKAROUND: Use the Multijob Plugin alone without the Build Pipeline Plugin.

The Multijob Plugin gives you the functionality of the Join Plugin, and its configuration is more straightforward. I actually like how it displays my running build better than the Build Pipeline Plugin.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [security] (JENKINS-17081) Permission "hudson.model.Item.Read:anonymous" coming from nowhere















































evernat
 commented on  JENKINS-17081


Permission "hudson.model.Item.Read:anonymous" coming from nowhere















Is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-17056) Hanging Maven module builds















































evernat
 commented on  JENKINS-17056


Hanging Maven module builds















Is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [slave-status] (JENKINS-17082) Jenkins Job failed because slave was done in the middle of the run















































evernat
 commented on  JENKINS-17082


Jenkins Job failed because slave was done in the middle of the run















Is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [plugin] (JENKINS-17089) Role Stretegy Plugin doesn't work in 1.502~1.504.
















































evernat
 resolved  JENKINS-17089 as Incomplete


Role Stretegy Plugin doesn't work in 1.502~1.504.
















I think that this issue is incomplete, so resolving as incomplete.
If reproduced with recent Jenkins and plugin versions, please take a look at jenkins logs for example.





Change By:


evernat
(06/Mar/14 9:03 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)

2014-03-06 Thread johnny.galam...@gmail.com (JIRA)















































John Galambos
 commented on  JENKINS-21278


java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)















I have confirmed that manually copying the types section to the from the builders xunit section to the publishers xunit section stops the exception from being thrown.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [plugin] (JENKINS-17089) Role Stretegy Plugin doesn't work in 1.502~1.504.













































  
evernat
 edited a comment on  JENKINS-17089


Role Stretegy Plugin doesn't work in 1.502~1.504.
















I think that this issue is incomplete, so resolving as incomplete.
If reproduced with recent Jenkins and plugin versions, please take a look at jenkins logs for example. Then reopen the issue of course.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17098) Wipe out workspace does not remove parallel workspaces correctly















































evernat
 commented on  JENKINS-17098


Wipe out workspace does not remove parallel workspaces correctly















Is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17107) Jenkins runs for a bit and then stops responding
















































evernat
 resolved  JENKINS-17107 as Incomplete


Jenkins runs for a bit and then stops responding
















I think that this issue is incomplete, so resolving as incomplete.
If it happens again please take a look at logs and please take thread dumps.





Change By:


evernat
(06/Mar/14 9:09 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17109) ComputerListener onConfigurationChange should provide computer object















































evernat
 updated  JENKINS-17109


ComputerListener onConfigurationChange should provide computer object
















An api change can't be a bug, so changing the issue.





Change By:


evernat
(06/Mar/14 9:13 PM)




Issue Type:


Bug
Improvement



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [plugin] (JENKINS-22065) docker-build-step-plugin: Create image from Dockerfile

2014-03-06 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-22065


docker-build-step-plugin: Create image from Dockerfile















Code changed in jenkins
User: Marcus Linke
Path:
 pom.xml
http://jenkins-ci.org/commit/docker-build-step-plugin/be11d526b16ec4184d4696061372300929f7e3f6
Log:
  JENKINS-22065


Compare: https://github.com/jenkinsci/docker-build-step-plugin/compare/61a311ea7932...be11d526b16e




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gui] (JENKINS-16802) Using Apache proxysettings breaks several GUI functions















































evernat
 commented on  JENKINS-16802


Using Apache proxysettings breaks several GUI functions















Is it fixed or perhaps reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17114) Reason for job starvation icon is wrong















































evernat
 commented on  JENKINS-17114


Reason for job starvation icon is wrong















Good catch, we can be glad of this issue.
But, is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-22074) Build Pipeline Plugin displays Multijobs in alphabetical order

John McGehee
created JENKINS-22074

Build Pipeline Plugin displays Multijobs in alphabetical order

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

jenkins-multiview-in-pipeline.png

Components:

build-pipeline

Created:

06/Mar/14 9:21 PM

Description:

When I put a multijob into a build pipeline, it is rendered completely incorrectly. The multijob appears in the center column, and the jobs within the multijob are displayed in alphabetical order (not build order) vertically on the right (see the attached image).

The jobs are executed in the correct order, and they turn green or red at the correct times. It is just their placement that is incorrect. Also I suppose that the multijob should not be displayed.

WORKAROUND: Use the Multijob Plugin alone without the Build Pipeline Plugin.

Environment:

Red Hat Enterprise Linux 5, kernel 2.6.18-238.el5

FireFox 17.0.8

Project:

Jenkins

Priority:

Minor

Reporter:

John McGehee

[JIRA] [plugin] (JENKINS-22065) docker-build-step-plugin: Create image from Dockerfile

2014-03-06 Thread vjura...@java.net (JIRA)
















































vjuranek
 resolved  JENKINS-22065 as Fixed


docker-build-step-plugin: Create image from Dockerfile
















Included in ver. 1.1 (released right now).





Change By:


vjuranek
(06/Mar/14 9:21 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-pipeline] (JENKINS-22074) Jobs within a Multijob are placed incorrectly in Build Pipeline Plugin display















































John McGehee
 updated  JENKINS-22074


Jobs within a Multijob are placed incorrectly in Build Pipeline Plugin display
















Change By:


John McGehee
(06/Mar/14 9:24 PM)




Summary:


Jobs within a Multijob are placed incorrectly in
Build Pipeline Plugin
 displays Multijobs in alphabetical order
 display



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven-info] (JENKINS-21450) NPE on "Selected Module Last Version" when Jenkins Job Name != artifactId

2014-03-06 Thread danki...@comcast.net (JIRA)















































Daniel Kirkdorffer
 commented on  JENKINS-21450


NPE on "Selected Module Last Version" when Jenkins Job Name != artifactId















Just to confirm the new version, 0.2.0, fixes the problems I was seeing.  Thanks.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17113) Job starvation icon does not show tool tip















































evernat
 commented on  JENKINS-17113


Job starvation icon does not show tool tip















Good catch again, thanks for the issue.
Is it reproduced with a recent Jenkins version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [customtools-plugin] (JENKINS-22075) null pointer

2014-03-06 Thread b...@mathews2000.com (JIRA)















































Ben Mathews
 created  JENKINS-22075


null pointer















Issue Type:


Bug



Affects Versions:


current



Assignee:


Oleg Nenashev



Components:


customtools-plugin



Created:


06/Mar/14 10:20 PM



Description:


Started getting a stack trace on project using custom tool plugin

FATAL: null
java.lang.NullPointerException
	at com.cloudbees.jenkins.plugins.customtools.CustomToolInstallWrapper.decorateLauncher(CustomToolInstallWrapper.java:162)
	at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:631)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:543)
	at hudson.model.Run.execute(Run.java:1670)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)




Environment:


RHEL5, installed via rpm




Project:


Jenkins



Priority:


Major



Reporter:


Ben Mathews

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [customtools-plugin] (JENKINS-22075) null pointer

2014-03-06 Thread b...@mathews2000.com (JIRA)















































Ben Mathews
 commented on  JENKINS-22075


null pointer















This is with v 0.4.1 of the plugin and 1.552 of jenkins



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [scm-sync-configuration] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL

2014-03-06 Thread jan_ruzi...@java.net (JIRA)

jan_ruzicka
created JENKINS-22076

SCM Sync Configuration crashes after enter repository URL

Issue Type:

Bug

Assignee:

Frédéric Camblor

Attachments:

SCMSyncException.txt

Components:

scm-sync-configuration

Created:

06/Mar/14 10:51 PM

Description:

After updating Jenkins and Jenkins plugins the SCM Sync Configuration Plugin is not able to sync with repository.
Following steps mentioned in the wiki "ScmSyncConfig Troubleshootings" confirmed access to repository. The temporary job was able to connect and checkout the configuration files.

The System configuration page shows "ERROR" link under the repository URL box in the subversion section of the SCM Sync configuration area.

Problem does not go away after Jenkins restart.

The scm_sync_configuration shows lines :
aborted (scm manipulator not settled !)

Environment:

Jenkins 1.532.2, SCM Sync Configuration Plugin 0.0.7.4, Credentials Plugin 1.10

Project:

Jenkins

Priority:

Major

Reporter:

jan_ruzicka

[JIRA] [scm-sync-configuration] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL

2014-03-06 Thread jan_ruzi...@java.net (JIRA)















































jan_ruzicka
 commented on  JENKINS-22076


SCM Sync Configuration crashes after enter repository URL















During restart Jenkins log shows:

WARNING: null
java.lang.RuntimeException: Error during ScmSyncConfiguration initialisation !
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.init(ScmSyncConfigurationPlugin.java:154)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationItemListener.onLoaded(ScmSyncConfigurationItemListener.java:24)
	at jenkins.model.Jenkins.(Jenkins.java:861)
	at hudson.model.Hudson.(Hudson.java:81)
	at hudson.model.Hudson.(Hudson.java:77)
	at hudson.WebAppMain$3.run(WebAppMain.java:221)
Caused by: java.lang.NullPointerException
	at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:51)
	at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:63)
	at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:69)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:64)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.init(ScmSyncConfigurationPlugin.java:152)
	... 5 more



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [promoted-builds] (JENKINS-16063) Add USER_ID variable to be available at the time of promotion if promoted manually

2014-03-06 Thread egues...@java.net (JIRA)















































eguess74
 commented on  JENKINS-16063


Add USER_ID variable to be available at the time of promotion if promoted manually
















Thanks for taking care of that!
It would probably be a little bit simpler to use if it would be USER_ID and not the full name. 
I needed to send email to the promotion user from promotion script and to get the address i used the following workaround:

create groovy script

import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*

name = args[0]
user = Jenkins.getInstance().getUser(name)
properties = user.getPrperties()

for (item in properties){
   if (item.value instanceof hudson.tasks.Mailer.UserProperty){}
   println(item.value.getAddress())
}

Then execute this during the promotion and pass the $PROMOTED_USER_NAME to get the email address for further work.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [promoted-builds] (JENKINS-16063) Add USER_ID variable to be available at the time of promotion if promoted manually

2014-03-06 Thread egues...@java.net (JIRA)













































  
eguess74
 edited a comment on  JENKINS-16063


Add USER_ID variable to be available at the time of promotion if promoted manually
















Thanks for taking care of that!
It would probably be a little bit simpler to use if it would be USER_ID and not the full name. 
I needed to send email to the promotion user from promotion script and to get the address i used the following workaround:

create groovy script

import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*

name = args[0]
user = Jenkins.getInstance().getUser(name)
properties = user.getProperties()

for (item in properties){
   if (item.value instanceof hudson.tasks.Mailer.UserProperty){}
   println(item.value.getAddress())
}

Then execute this during the promotion and pass the $PROMOTED_USER_NAME to get the email address for further work.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-21939) Perforce Clean Workspace "Full Wipe" should not add "-f" option to sync.