date:20130318















































SCM/JIRA link daemon
 commented on  JENKINS-17263


"Leave this machine for tied jobs only" does not stick on "(master)"















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/resources/jenkins/model/Jenkins/MasterComputer/configure.jelly
http://jenkins-ci.org/commit/jenkins/f2508b36ed38c548debad02d12205b72f5840c59
Log:
  [FIXED JENKINS-17263] Correctly display current Jenkins.mode.





























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] (JENKINS-17263) "Leave this machine for tied jobs only" does not stick on "(master)"
















































SCM/JIRA link daemon
 resolved  JENKINS-17263 as Fixed


"Leave this machine for tied jobs only" does not stick on "(master)"
















Change By:


SCM/JIRA link daemon
(18/Mar/13 10:32 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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist















































SCM/JIRA link daemon
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they don't exist















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/98869558a3c7b6183c60f492153b45384dd36db5
Log:
  JENKINS-10502 This was an RFE, not a bug.





























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] (JENKINS-17263) "Leave this machine for tied jobs only" does not stick on "(master)"















































Jesse Glick
 created  JENKINS-17263


"Leave this machine for tied jobs only" does not stick on "(master)"















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


18/Mar/13 10:24 PM



Description:


Node usage mode can be set for the master computer but the current mode is not displayed when you revisit the configuration page.




Project:


Jenkins



Priority:


Minor



Reporter:


Jesse Glick

























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] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters

2013-03-18 Thread shaun.kru...@gmail.com (JIRA)

Shaun Kruger
created JENKINS-17262

Remotely triggered build with parameters failing with extended choice parameters

Issue Type:

Bug

Assignee:

Unassigned

Components:

extended-choice-parameter

Created:

18/Mar/13 10:19 PM

Description:

I have converted one of the parameters in my project from a statically defined Choice dropdown box to an Extended Choice Parameter in Single select mode. When I execute builds from the web interface everything works fine. When I try to remotely trigger a build using the HTTP GET interface I get an error and my extended choice parameter does not appear in the list of parameters for the build.

I did notice that I'm running one minor release behind, but there was nothing in the diff from 0.26 to 0.27 that made me think it could impact this issue. I will be upgrading as soon as there are not currently executing jobs.

Environment:

Jenkins 1.500

Extended Choice Parameter 0.26

Project:

Jenkins

Priority:

Major

Reporter:

Shaun Kruger

[JIRA] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.

2013-03-18 Thread markwa...@yahoo.com (JIRA)















































Mark Waite
 commented on  JENKINS-16693


Heap error while polling Git Plug-in after upgrade to 1.1.26.















Yes, if you want to use the new version (1.3.0), then you'll need to stop using include/exclude paths/users.

The new version (1.3.0) still uses "git show" to compute "isRevExcluded" just as versions 1.1.25 and later did.  In your case, you're probably best to stay with 1.1.21 until there is evidence that the problem is resolved.

The new version (1.3.0) is still in the midst of a refactoring which will allow it to use JGit or the command line interface.  That refactoring has caused some instability and loss of functionality compared to 1.1.26.  You may want to avoid the new version (1.3.0) until it stabilizes further.

Refer to JENKINS-17204, JENKINS-17242, JENKINS-17198, JENKINS-16941, and others in the git plugin bug list.



























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] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result

2013-03-18 Thread l...@tikalk.com (JIRA)















































Liya Katz
 commented on  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result















[Cobertura] Publishing Cobertura coverage report...
FATAL: Unable to find coverage results
java.io.IOException: /opt/jenkins/jobs/xxx/workspace/xxx/xxx/target/coverage/index.html is not a cobertura coverage report, please check your report pattern
	at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:546)
	at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:519)
	at hudson.FilePath.act(FilePath.java:865)
	at hudson.FilePath.act(FilePath.java:838)
	at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:337)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:947)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733)
	at hudson.model.Run.execute(Run.java:1592)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
[Cobertura] No coverage results were found using the pattern '**/target/coverage/index.html' relative to '/opt/jenkins/jobs/xxx/workspace'.  Did you enter a pattern relative to the correct directory?  Did you generate the XML report(s) for Cobertura?
[Cobertura] Skipped cobertura reports.
Build step 'Publish Cobertura Coverage Report' changed build result to FAILURE



























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] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+

2013-03-18 Thread pet...@standingwave.org (JIRA)















































Peter Loron
 commented on  JENKINS-17204


GIT plugin fetch failing since update Git Plugin to 1.2.0+















Also having this issue with save versions as OP.



























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] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
















































Jesse Glick
 resolved  JENKINS-14546 as Duplicate


Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
















JENKINS-13429 was fixed in 1.467. @martinkutter your comment about getACL is missing the point, which is that you need to grant View.READ for people to see the views. The block you quote is only for backward compatibility with old versions of Jenkins that did not define View.READ at all.





Change By:


Jesse Glick
(18/Mar/13 8:51 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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] (JENKINS-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)

2013-03-18 Thread egrumb...@gmail.com (JIRA)















































Emmanuel Grumbach
 commented on  JENKINS-16847


Support for copying artifacts from other builds being part of the same MultiJob (previous phases)















I would also be very interested in this feature 



























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] (JENKINS-12924) FSTrigger triggers builds on jenkins restart

2013-03-18 Thread dumg...@gmail.com (JIRA)















































Ghenadie Dumitru
 commented on  JENKINS-12924


FSTrigger triggers builds on jenkins restart















Hi,

The issue was isolated.
It happens every time the Master is restarted (Jenkins master is started under Tomcat) and master has a number of slaves connected through SSH on different machines: all machines (master+slave) are CentOS.
I have configured few jobs on each master, jobs are tied to specific slaves. On some slaves, jobs are triggered to run as described in issue once the master is restarted. Not on all slaves, which is little weird.



























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] (JENKINS-15423) Instance type selector should be text field

2013-03-18 Thread da...@walend.net (JIRA)















































David Walend
 commented on  JENKINS-15423


Instance type selector should be text field















I'm interested in cr1.8xlarge myself. 

The better long-term fix would be to use an AWS API, but there doesn't seem to be one yet. https://forums.aws.amazon.com/message.jspa?messageID=385373 



























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] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.

2013-03-18 Thread d...@gweep.net (JIRA)















































Don Ross
 commented on  JENKINS-16693


Heap error while polling Git Plug-in after upgrade to 1.1.26.















So, my only resource if I want to use the new version is to stop using included/exclude paths?



























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] (JENKINS-17086) Use IAM Role when creating instance

2013-03-18 Thread da...@walend.net (JIRA)















































David Walend
 commented on  JENKINS-17086


Use IAM Role when creating instance















I was about to put in a request for this feature, too. As well as having the Jenkins master use its own IAM role instead of being a user.



























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] (JENKINS-15826) CVS plugin excluded regions no longer match on the file path

2013-03-18 Thread michael.m.cla...@gmail.com (JIRA)















































Michael Clarke
 commented on  JENKINS-15826


CVS plugin excluded regions no longer match on the file path















I can't see why there would be an issue here - the upgraded CVS plugin uses Matcher#matches so looks for the full String to match. Could you try re-applying your exclude regions and see if you still get the same issue?



























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] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.

2013-03-18 Thread nwhollo...@gmail.com (JIRA)















































Nick Holloway
 commented on  JENKINS-16693


Heap error while polling Git Plug-in after upgrade to 1.1.26.















The change from "whatchanged" to "show" was made after 1.1.25 to address JENKINS-13368.  Before this the plugin only used the most recent commit to evaluate included paths and could omit builds.



























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] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0

2013-03-18 Thread cinh...@gmail.com (JIRA)















































Tan Nguyen
 commented on  JENKINS-13465


Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0















Well, you can vote for it. During the transition you can apply the patch above yourself or take the patched hpi and replace it in your jenkins/hudson installation. hth



























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] (JENKINS-17259) Option for not expanding parameters

2013-03-18 Thread eder_ste...@gmx.at (JIRA)













































  
Stefan Eder
 edited a comment on  JENKINS-17259


Option for not expanding parameters 
















In the meantime I did a workaround to prevent this error:

	Upgraded to token-macro plugin 1.6
	Used "expandAll" method with the "throwException" parameter set to "false"



This will return the value of the parameter, if no defined build or environment variable is found. It might be a cheap solution for the stated problem but might not be the behaviour every user of this plugin is looking for (e.g. would pass on ${someVar} if not expandable to the script instead of stopping with an error).

However it works for me.

I attached the patch file. Maybe it is of some use.



























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] (JENKINS-17259) Option for not expanding parameters

2013-03-18 Thread eder_ste...@gmx.at (JIRA)















































Stefan Eder
 updated  JENKINS-17259


Option for not expanding parameters 
















In the meantime I did a workaround to prevent this error:

	Upgraded to token-macro plugin 1.6
	Used "expandAll" method with the "throwException" parameter set to "false"



This will return the value of the parameter, if no defined build or environment variable is found. It might be a cheap solution for the stated problem but might not be the behaviour every user of this plugin is looking for (would pass on ${someVar} if not expanded instead of stopping with an error).

However it works for me.

I attached the patch file. Maybe it is of some use.





Change By:


Stefan Eder
(18/Mar/13 6:38 PM)




Attachment:


scriptler-plugin_no_token_exceptions.patch



























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] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0

2013-03-18 Thread bruno...@gmail.com (JIRA)















































Bruno Medeiros
 commented on  JENKINS-13465


Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0















I have the same issue. Any expected release date for the pull request above?



























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] (JENKINS-10266) Set grails.work.dir to something unique by default

2013-03-18 Thread mtak...@gmail.com (JIRA)













































  
Mark Takacs
 edited a comment on  JENKINS-10266


Set grails.work.dir to something unique by default
















I'd actually like the ability to do this as well.

Consider two builds (one from a legacy branch, one from a current branch).  Both builds will store their work.dir stuff in the same location, causing confusion.  

see http://jira.grails.org/browse/GRAILS-5359



























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] (JENKINS-10266) Set grails.work.dir to something unique by default

2013-03-18 Thread mtak...@gmail.com (JIRA)















































Mark Takacs
 commented on  JENKINS-10266


Set grails.work.dir to something unique by default















I'd actually like the ability to do this as well.

Consider two builds (one from a legacy branch, one from a current branch).  Both builds will store their work.dir stuff in the same location, causing confusion.  



























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] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)

2013-03-18 Thread recampb...@java.net (JIRA)















































recampbell
 commented on  JENKINS-14901


Emulator start failed on Ubuntu (SDK 20.0.3)















We were having this precise issue. As indicated by this stackoverflow thread, we fixed the issue by setting the LD_LIBRARY_PATH as follows (using EnvInject):


LD_LIBRARY_PATH=/opt/android/android-sdk-linux/tool/lib


I think the fix is for the Android Emulator plugin to populate this for us?



























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] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.

2013-03-18 Thread d...@gweep.net (JIRA)















































Don Ross
 commented on  JENKINS-16693


Heap error while polling Git Plug-in after upgrade to 1.1.26.















Upgrading our test environment to the entirely-new version 1.3.0 of the plug-in still shows the same behavior.  For now, we are okay with keeping our production environment at version 1.1.21, but the time will come when we want some feature available in a new version, and we won't be able to upgrade.



























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] (JENKINS-17261) Trac plugin not working with Jenkins 1.506

2013-03-18 Thread hudson.8467...@mstier.de (JIRA)















































Mark S.
 created  JENKINS-17261


Trac plugin not working with Jenkins 1.506















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


trac



Created:


18/Mar/13 5:05 PM



Description:


The first strange thing I detected was that there is no possibility to enter the trac frontend url when choosing trac as a repository browser for subversion on the jobs configuration page. In addition to that, I cannot see any links either on the job overview page or in the changes/history display.

I'm using svn://$ip/..-style svn urls.




Project:


Jenkins



Priority:


Major



Reporter:


Mark S.

























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] (JENKINS-17260) Mercurial Push Notifications: URLs should be compared in canonical form















































Elifarley
 updated  JENKINS-17260


Mercurial Push Notifications: URLs should be compared in canonical form
















Change By:


Elifarley
(18/Mar/13 4:57 PM)




Description:


The comparison of a job's repository URL and the URL passed to notifyCommit will fail when the 2 URLs differ slightly, even though they point to the same place.Example that triggers the problem:Repository URL
 (in job configuration screen)
: http://mymercurialrepo.com.br/hg/main/myproj/hook configuration:[hooks]commit.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">incoming.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">The URL comparison should first transform both URLs to their canonical form (by appending a slash at the end if one is missing, for instance).I guess it will also fail if one of the URLs includes an HTTP redirect.



























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] (JENKINS-17260) Mercurial Push Notifications: URLs should be compared in canonical form















































Elifarley
 updated  JENKINS-17260


Mercurial Push Notifications: URLs should be compared in canonical form
















Change By:


Elifarley
(18/Mar/13 4:56 PM)




Environment:


Linux, Jenkis 1.506, Mercurial extension v. 1.44, mercurial 2.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] (JENKINS-17260) Mercurial Push Notifications: URLs should be compared in canonical form















































Elifarley
 created  JENKINS-17260


Mercurial Push Notifications: URLs should be compared in canonical form















Issue Type:


Bug



Affects Versions:


current



Assignee:


Jesse Glick



Components:


mercurial



Created:


18/Mar/13 4:55 PM



Description:


The comparison of a job's repository URL and the URL passed to notifyCommit will fail when the 2 URLs differ slightly, even though they point to the same place.

Example that triggers the problem:

Repository URL: http://mymercurialrepo.com.br/hg/main/myproj/
hook configuration:
[hooks]
commit.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">
incoming.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">


The URL comparison should first transform both URLs to their canonical form (by appending a slash at the end if one is missing, for instance).

I guess it will also fail if one of the URLs includes an HTTP redirect.





Project:


Jenkins



Priority:


Major



Reporter:


Elifarley

























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated
















































Elifarley
 assigned  JENKINS-17258 to Jesse Glick



Mercurial repository is always cloned instead of being updated
















Change By:


Elifarley
(18/Mar/13 4:56 PM)




Assignee:


Kohsuke Kawaguchi
Jesse Glick



























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] (JENKINS-17259) Option for not expanding parameters

2013-03-18 Thread eder_ste...@gmx.at (JIRA)















































Stefan Eder
 created  JENKINS-17259


Option for not expanding parameters 















Issue Type:


New Feature



Assignee:


domi



Components:


scriptler, token-macro



Created:


18/Mar/13 4:45 PM



Description:


When executing a groovy script which accepts some parameters as input and some parameters contain a '$' (e.g. some$pass!) the following happens:

17:04:13 Execution of script [somescript.groovy] failed - Unrecognized macro 'pass' in 'some$pass!'org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'pass' in 'some$pass!'
17:04:13 	at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:185)
17:04:13 	at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:219)
17:04:13 	at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:208)
17:04:13 	at org.jenkinsci.plugins.scriptler.builder.ScriptlerBuilder.perform(ScriptlerBuilder.java:104)


If I understand the code correctly the behaviour of the token-macro plugin trying to expand the contents of the parameters is wanted (JENKINS-11914 is related to this). However it is problematic when passing on parameters which contain a '$' and should not be expanded.

Therefore a feature which lets the user define whether a specific parameter or all parameters should be expanded would be useful.




Environment:


scriptler 2.5.1, token-macro 1.6




Project:


Jenkins



Priority:


Minor



Reporter:


Stefan Eder

























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated















































Elifarley
 commented on  JENKINS-17258


Mercurial repository is always cloned instead of being updated















Adding the "--quiet" option will probably fix it, as in:

hg --quiet showconfig paths.default

This way the output should be stable no matter what the system-level hgrc file says about ui.debug



























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated















































Elifarley
 updated  JENKINS-17258


Mercurial repository is always cloned instead of being updated
















Change By:


Elifarley
(18/Mar/13 4:38 PM)




Description:


My system-level hgrc file sets debug to on:
hg showconfig|grep ui.debug/etc/mercurial/hgrc:28: ui.debug=true
This seems to cause problems when parsing the output of hg.
Here's the log output:13:25:37 Building remotely on myslave in workspace /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 $ hg clone --rev 2.8.4 --noupdate http://mymercurialrepo.com.br/hg/main/myjob /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 using http://mymercurialrepo.com.br/hg/main/myjob13:25:38 sending capabilities command13:25:38 sending lookup command13:25:38 query 1; heads13:25:38 sending batch command13:25:38 sending getbundle command13:25:38 adding changesets13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...]



























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated















































Elifarley
 updated  JENKINS-17258


Mercurial repository is always cloned instead of being updated
















Change By:


Elifarley
(18/Mar/13 4:36 PM)




Description:


hg showconfig|grep ui.debug/etc/mercurial/hgrc:28: ui.debug=true
Here's the log output:13:25:37 Building remotely on myslave in workspace /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 $ hg clone --rev 2.8.4 --noupdate http://mymercurialrepo.com.br/hg/main/myjob /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 using http://mymercurialrepo.com.br/hg/main/myjob13:25:38 sending capabilities command13:25:38 sending lookup command13:25:38 query 1; heads13:25:38 sending batch command13:25:38 sending getbundle command13:25:38 adding changesets13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...]



























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated















































Elifarley
 updated  JENKINS-17258


Mercurial repository is always cloned instead of being updated
















Change By:


Elifarley
(18/Mar/13 4:33 PM)




Environment:


Linux, Jenkis 1.
458
506
,
 mercurial
 Mercurial extension v.
 1.
7
44, mercurial 2.2





Description:


JENKINS-4672 gives possibility to setup Marcurial debug flag.When I switch it on, the all mercurial call is done with option "--debug".The first command, during the build, checks if configuration of repository wasn
Here
'
t changed.This check is done by comparision result of commad "hg showconfig paths.default" with jenkins configuration.But there is a different output if
s
 the
 debug option is ON.Without debug option
 log output
 : 
 $ hg showconfig paths.default

 https
13
:
25:37 Building remotely on myslave in workspace
/
var
/
hg
data
/
hg
jenkins-slave
/
zpis
workspace/MYJOB-2.8.4

With debug option
13
 :
 
25:38 $
 hg
 clone
 --
debug showconfig paths
rev 2
.
default read config from
8.4 --noupdate http
: /
etc
/
mercurial/hgrc read config from: /data/hudson/
mymercurialrepo
.
hgrc none: https:
com.br
/
/
hg/
hg
main
/
zpisSo with the debug option, the mercurial configuration is always different as jenkins configuration.Result is : ---Building in workspace
myjob
 /
var/
data/
hudson/jobs/vlk
jenkins
-
pokus
slave
/workspace
[workspace] $ hg
/MYJOB
 -
-debug showconfig paths
2
.
default
8.4

read config from
13
:
 /etc/mercurial/hgrcread config from
25
:
38 using http:
 /
data
/
hudson/
mymercurialrepo
.
hgrcnone: https:
com.br
/
/
hg/
hg
main
/
zpis
myjob

which looks different than https
13
:
//hg/hg/zpis
25:38 sending capabilities command

so falling back to fresh clone rather than incremental update
13:25:38 sending lookup command

13:25:38 query 1; heads

13:25:38 sending batch command

Workaround
13
 :
 Switch off the degug option.
25:38 sending getbundle command

13:25:38 adding changesets

13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...]



























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] (JENKINS-17258) Mercurial repository is always cloned instead of being updated

Elifarley
created JENKINS-17258

Mercurial repository is always cloned instead of being updated

Issue Type:

Bug

Affects Versions:

current

Assignee:

Kohsuke Kawaguchi

Components:

mercurial

Created:

18/Mar/13 4:30 PM

Description:

JENKINS-4672 gives possibility to setup Marcurial debug flag.
When I switch it on, the all mercurial call is done with option "--debug".

The first command, during the build, checks if configuration of repository wasn't changed.
This check is done by comparision result of commad "hg showconfig paths.default" with jenkins configuration.

But there is a different output if the debug option is ON.
Without debug option :
$ hg showconfig paths.default
https://hg/hg/zpis

With debug option :
hg --debug showconfig paths.default
read config from: /etc/mercurial/hgrc
read config from: /data/hudson/.hgrc
none: https://hg/hg/zpis

So with the debug option, the mercurial configuration is always different as jenkins configuration.

Result is :
---
Building in workspace /data/hudson/jobs/vlk-pokus/workspace
[workspace] $ hg --debug showconfig paths.default
read config from: /etc/mercurial/hgrc
read config from: /data/hudson/.hgrc
none: https://hg/hg/zpis
which looks different than https://hg/hg/zpis
so falling back to fresh clone rather than incremental update

Workaround : Switch off the degug option.

Environment:

Linux, Jenkis 1.458, mercurial 1.7

Project:

Jenkins

Priority:

Minor

Reporter:

Elifarley

[JIRA] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist

2013-03-18 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they don't exist















Integrated in  jenkins_main_trunk #2381
 JENKINS-10502 Option to make the build NOT fail if there is nothing to archive (Revision d3096819f6a70c107399fbcf2df23718098c926e)
JENKINS-10502 Noting. (Revision e88932956f78dc8c89835256b820cca671756286)

 Result = SUCCESS
pjrodriguezt : d3096819f6a70c107399fbcf2df23718098c926e
Files : 

	test/src/test/java/hudson/tasks/ArtifactArchiverTest.java
	test/src/test/java/hudson/model/AbstractProjectTest.java
	core/src/main/java/hudson/tasks/ArtifactArchiver.java
	core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties
	core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly
	test/src/test/java/hudson/tasks/LogRotatorTest.java



Jesse Glick : e88932956f78dc8c89835256b820cca671756286
Files : 

	changelog.html





























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] (JENKINS-17257) EC2 plugin fails to launch slave (IndexOutOfBoundsException)

2013-03-18 Thread jai.ride...@gmail.com (JIRA)















































Jai Ram Rideout
 created  JENKINS-17257


EC2 plugin fails to launch slave (IndexOutOfBoundsException)















Issue Type:


Bug



Assignee:


Francis Upton



Components:


ec2



Created:


18/Mar/13 4:20 PM



Description:


Using the latest dev version of the EC2 plugin from GitHub, the launching of slaves sometimes fails due to an IndexOutOfBoundsException.

Relevant stack trace from Jenkins logs:


WARNING: Provisioned slave QIIME 1.6.0 AMI (Ubuntu 64-bit) (ami-10b12f79) failed to launch
java.util.concurrent.ExecutionException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:344)
at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:329)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:142)
at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:125)
at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:101)
at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:56)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222)
... 5 more


This results in a disconnected node (from Jenkins' point of view) but the instance is still running on Amazon EC2. The Jenkins logs indicate that the slave is idle, but it is never terminated by the EC2 plugin, even though I have the idle termination time set to 10 minutes:


...
QIIME 1.6.0 AMI (Ubuntu 64-bit) (i-54fb093e) idle: 32412220
QIIME 1.6.0 AMI (Ubuntu 64-bit) (i-54fb093e) idle: 32532221
...


Other slaves using the same AMI are automatically launched just fine after this failure occurs.




Environment:


Ubuntu 12.04 LTS (64-bit)

Jenkins 1.505

EC2 plugin from GitHub repo (commit 76c95f9c4a02917d09e28e4e4efa705c845f30df)




Project:


Jenkins



Labels:


plugin
slave
jenkins
exception
plugins




Priority:


Major



Reporter:


Jai Ram Rideout

























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] (JENKINS-17256) Unexpected error in launching a slave (NegativeArraySizeException)

2013-03-18 Thread bogdan.dumitr...@altom.ro (JIRA)















































bogdan d
 created  JENKINS-17256


Unexpected error in launching a slave (NegativeArraySizeException)















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Attachments:


System Information [Jenkins].htm, Thread dump [Jenkins].htm



Components:


ssh, ssh-slaves



Created:


18/Mar/13 3:57 PM



Description:


Jenkins running on Windows and trying to start OSx slave via ssh (using private key)

LOG:

[03/18/13 17:45:56] [SSH] Opening SSH connection to 192.168.1.35:22.
[03/18/13 17:45:56] [SSH] Authenticating as Jenkins with C:\Jenkins\ssh_keys\private.ppk.
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
java.lang.NegativeArraySizeException
	at org.kohsuke.putty.KeyReader.read(KeyReader.java:59)
	at org.kohsuke.putty.KeyReader.readInt(KeyReader.java:71)
	at org.kohsuke.putty.PuTTYKey.toOpenSSH(PuTTYKey.java:198)
	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:730)
	at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:278)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
[03/18/13 17:45:56] [SSH] Connection closed.




Environment:


CPU:Intel Xeon 

OS:Windows Server 2008 R2 Standard




Project:


Jenkins



Priority:


Major



Reporter:


bogdan d

























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] (JENKINS-16314) cvs plugin removes sticky branch tag

2013-03-18 Thread jamesdmor...@gmail.com (JIRA)















































James Morgan
 commented on  JENKINS-16314


cvs plugin removes sticky branch tag















Thanks for looking into 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] (JENKINS-17248) java.lang.NullPointerException by start

2013-03-18 Thread mat...@corti.li (JIRA)















































Matteo Corti
 commented on  JENKINS-17248


java.lang.NullPointerException by start















Removing the global-build-stats plugin I was able to restart Jenkins.

Although the problem is caused by a plugin the application should not crash.



























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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist















































SCM/JIRA link daemon
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they don't exist















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/e88932956f78dc8c89835256b820cca671756286
Log:
  JENKINS-10502 Noting.


Compare: https://github.com/jenkinsci/jenkins/compare/aeb887c12d60...e88932956f78

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






























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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
















































SCM/JIRA link daemon
 resolved  JENKINS-10502 as Fixed


Add an option to make archiving the artifacts non-fatal if they don't exist
















Change By:


SCM/JIRA link daemon
(18/Mar/13 3: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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist















































SCM/JIRA link daemon
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they don't exist















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/tasks/ArtifactArchiver.java
 core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly
 core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties
 core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html
 test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy
 test/src/test/java/hudson/model/AbstractProjectTest.java
 test/src/test/java/hudson/tasks/ArtifactArchiverTest.java
 test/src/test/java/hudson/tasks/LogRotatorTest.java
http://jenkins-ci.org/commit/jenkins/aeb887c12d60987745ed40a55d0f6ddcee503426
Log:
  Merge pull request #732 from pjrt/JENKINS-10502

[FIXED JENKINS-10502] Option to make the build not fail if there is nothing to archive


Compare: https://github.com/jenkinsci/jenkins/compare/77e011a3dae3...aeb887c12d60

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






























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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist















































SCM/JIRA link daemon
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they don't exist















Code changed in jenkins
User: Pedro Rodriguez
Path:
 core/src/main/java/hudson/tasks/ArtifactArchiver.java
 core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly
 core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties
 test/src/test/java/hudson/model/AbstractProjectTest.java
 test/src/test/java/hudson/tasks/ArtifactArchiverTest.java
 test/src/test/java/hudson/tasks/LogRotatorTest.java
http://jenkins-ci.org/commit/jenkins/d3096819f6a70c107399fbcf2df23718098c926e
Log:
  JENKINS-10502 Option to make the build NOT fail if there is nothing to archive





























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] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart

2013-03-18 Thread riftwea...@hotmail.com (JIRA)

Jason Karney
commented on JENKINS-16475

Build stats graph configuration lost after Jenkins Restart

I am experiencing a similar – or perhaps the same – problem. I just noticed it last week, because I happened to be reviewing the Jenkins (tomcat) log and noticed a SEVERE startup error related to global-build-stats.

We are running Jenkins 1.455 and global build stats 1.3. We have been using this same version of Jenkins and plugin for many months now. I did some testing, and the problems seems to be that one of our jobResults.xml files contained the value "null." That is, the file jobResults-2012-01.xml contained one line, and it was "". Renaming the file did not help, but removing the file allowed Jenkins to start without reporting the error. Further testing is required to verify that chart data is saved after restart.

Interestingly, this error was occurring on two Jenkins servers, both of which are kept to identical configuration in terms of plugins but not jobs.

The specific error in the Jenkins log at startup time is:
SEVERE: Unable to read jenkins/home/global-build-stats.xml
hudson.util.IOException2: Unable to read jenkins/home/global-build-stats.xml
... [stacktrace]
Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null

I'm sure it is showing that "" couldn't be unmarshalled. The question is, why is that jobResult.xml's value null to begin with?

Maxfield – if you could check your JENKINS_HOME/global-build-stats/jobresults directory for file(s) with the value null, you might verify having the same problem; and try to fix it by removing any "null" files. I'd be curious to see if you have the same thing happening.

I hope this helps.

[JIRA] (JENKINS-17073) Support specifying logger for phing

2013-03-18 Thread s.sog...@gmail.com (JIRA)















































sogabe
 commented on  JENKINS-17073


Support specifying logger for phing















I've just released Phing Plugin 0.12. 



























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] (JENKINS-17255) Dropdwon not compatible with cloudbees folder

2013-03-18 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-17255


Dropdwon not compatible with cloudbees folder















Issue Type:


Bug



Assignee:


jieryn



Components:


dropdown-viewstabbar



Created:


18/Mar/13 2:47 PM



Description:


views inside Folders (cloudbees folder plugin), appear as tabs, not dropdwon.
Can be reproduced installing the cloudbees FREE plugins

Seems dropdown-views-tabbar don't handle nested ItemGroups in Jenkins






Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























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] (JENKINS-17255) Dropdwon not compatible with cloudbees folder

2013-03-18 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 updated  JENKINS-17255


Dropdwon not compatible with cloudbees folder
















Change By:


Nicolas De Loof
(18/Mar/13 2:48 PM)




Labels:


folders



























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] (JENKINS-17177) wrong build result in post build steps after failed pre build step in maven project

2013-03-18 Thread lostinberlin2...@gmail.com (JIRA)















































Steve Boardwell
 commented on  JENKINS-17177


wrong build result in post build steps after failed pre build step in maven project















Thanks for the quick response. 



























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] (JENKINS-16967) Allow environment variables in phing properties
















































SCM/JIRA link daemon
 resolved  JENKINS-16967 as Fixed


Allow environment variables in phing properties  
















Change By:


SCM/JIRA link daemon
(18/Mar/13 2:30 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] (JENKINS-16967) Allow environment variables in phing properties

2013-03-18 Thread jenkins.u...@jeremy.smallinfinity.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-16967


Allow environment variables in phing properties  















Code changed in jenkins
User: Seiji Sogabe
Path:
 src/main/java/hudson/plugins/phing/PhingBuilder.java
http://jenkins-ci.org/commit/phing-plugin/720a99e5e4e9616d0a3e307068ea62d5b0dccaa0
Log:
  [FIXED JENKINS-16967] Allow environment variables in phing properties



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






























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] (JENKINS-15826) CVS plugin excluded regions no longer match on the file path















































Jeremy Michelson
 commented on  JENKINS-15826


CVS plugin excluded regions no longer match on the file path















Sorry I wasn't clear.  The issue is that the build doesn't run if excluded regions are set.

Suppose you've the hierarchy


file.c
dir1/
dir1/file1.c
dir2/
dir2/file2.c
...



With version 1.6 of the CVS plugin, one could set an excluded region of "[^/]*.c".  Then changes to "file.c" would (correctly!) not trigger a build, but changes to "dir1/file1.c" would trigger a build.  Now, neither triggers a build.

I'm not sure how useful the job config would be.  Because of this bug, we had to remove the excluded regions (at the cost of a large increase in spurious builds) in order to get the builds we needed, due to changes in subdirectories.



























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] (JENKINS-17254) Multijob view last succes / last failure columns shows status instead of #of days/hours since

2013-03-18 Thread jurgen.van.boucha...@gmail.com (JIRA)















































Jurgen Van Bouchaute
 updated  JENKINS-17254


Multijob view last succes / last failure columns shows status instead of  #of days/hours since
















Change By:


Jurgen Van Bouchaute
(18/Mar/13 1:55 PM)




Summary:


Multijon
Multijob
 view last succes / last failure columns shows status instead of  #of days/hours since



























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] (JENKINS-17254) Multijon view last succes / last failure columns shows status instead of #of days/hours since

2013-03-18 Thread jurgen.van.boucha...@gmail.com (JIRA)















































Jurgen Van Bouchaute
 created  JENKINS-17254


Multijon view last succes / last failure columns shows status instead of  #of days/hours since















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


18-03-2013 14-50-04.png



Components:


jenkins-multijob-plugin



Created:


18/Mar/13 1:55 PM



Description:


The last success / last failure columns on the multijob view should mention the number of days / hours since this last success/failure, not a status ball

See screenshot.




Project:


Jenkins



Priority:


Major



Reporter:


Jurgen Van Bouchaute

























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] (JENKINS-3907) Mercurial updates on matrix projects aren't synced properly















































Jesse Glick
 commented on  JENKINS-3907


Mercurial updates on matrix projects aren't synced properly















So much for Kohsuke’s original proposal to generalize this, I guess.



























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] (JENKINS-17247) Exception while trigger downstream projects















































Jesse Glick
 updated  JENKINS-17247


Exception while trigger downstream projects
















Change By:


Jesse Glick
(18/Mar/13 1:45 PM)




Assignee:


Jesse Glick





Component/s:


core





Component/s:


secret



























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] (JENKINS-17221) "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam















































Jesse Glick
 commented on  JENKINS-17221


"You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value















Edited.



























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] (JENKINS-17253) In tomcat localhost logs "java.lang.IllegalStateException: getOutputStream() has already been called for this response"

2013-03-18 Thread da...@orionrobots.co.uk (JIRA)















































Danny Staple
 created  JENKINS-17253


In tomcat localhost logs "java.lang.IllegalStateException: getOutputStream() has already been called for this response"















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


18/Mar/13 1:32 PM



Description:


In our localhost..log files, we are seeing it flooded with errors like this:


Mar 3, 2013 12:04:12 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet Stapler threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
at org.apache.catalina.connector.Response.getWriter(Response.java:610)
at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
at javax.servlet.ServletResponseWrapper.getWriter(ServletResponseWrapper.java:112)
at org.kohsuke.stapler.compression.CompressionServletResponse.getWriter(CompressionServletResponse.java:58)
at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:68)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:574)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1527)
at java.lang.Thread.run(Thread.java:619)


We are seeing them approximately twice a minute, and have had performance issues on the master node.




Environment:


Jenkins ver. 1.480.2, Tomcat 6, Linux X86_64




Project:


Jenkins



Priority:


Major



Reporter:


Danny Staple

























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] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result















































Jesse Glick
 commented on  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result















@liya please show the exact error message you now get, so developers can confirm that you are really running 1.8, and that the error is really the same.



























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] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith















































SCM/JIRA link daemon
 commented on  JENKINS-13669


NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/hudson/plugins/mercurial/MercurialSCM.java
http://jenkins-ci.org/commit/mercurial-plugin/1576c70a2c753480857391757b8c059b39fda880
Log:
  JENKINS-13669 willemv advocates simply failing the polling operation if possiblyCachedRepo is null.



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






























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] (JENKINS-17073) Support specifying logger for phing

2013-03-18 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-17073


Support specifying logger for phing















What is the approximate date of 0.12 version release (I think this fix will go into that 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] (JENKINS-17073) Support specifying logger for phing

SCM/JIRA link daemon
commented on JENKINS-17073

Support specifying logger for phing

Code changed in jenkins
User: Seiji Sogabe
Path:
src/main/java/hudson/plugins/phing/PhingBuilder.java
src/main/resources/hudson/plugins/phing/PhingBuilder/config.jelly
src/main/resources/hudson/plugins/phing/PhingBuilder/config_ja.properties
src/test/java/hudson/plugins/phing/PhingBuilderConfigSubmitTest.java
http://jenkins-ci.org/commit/phing-plugin/0c5382aedae969c9bca903d15b4becd0a7ccfcdf
Log:
[FIXED JENKINS-17073] added Options field to specify logger

Compare: https://github.com/jenkinsci/phing-plugin/compare/ffdc5f67a923...0c5382aedae9

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

[JIRA] (JENKINS-17073) Support specifying logger for phing