date:20140218















































Christian Matzat
 commented on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















Maybe in can be done like in the xframe-filter-plugin, what does the same as the change for SECURITY-80, but with configuration option.

See here for details:
https://wiki.jenkins-ci.org/display/JENKINS/XFrame+Filter+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] [subversion] (JENKINS-21843) Unable to wipe out workspace on Windows Server

2014-02-18 Thread fr...@bushlife.com.au (JIRA)















































sweetfa
 updated  JENKINS-21843


Unable to wipe out workspace on Windows Server
















As can be seen by the screen shot the process that has the file open is the Jenkins java server.

For some reason it does not appear to be releasing the file





Change By:


sweetfa
(18/Feb/14 9:26 AM)




Attachment:


Screen Shot 2014-02-18 at 7.24.45 PM.png



























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-setup] (JENKINS-21844) java.net.UnknownHostException is "unexpected" when starting slave

2014-02-18 Thread mar...@headcrashing.eu (JIRA)















































Markus KARG
 created  JENKINS-21844


java.net.UnknownHostException is "unexpected" when starting slave















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


slave-setup



Created:


18/Feb/14 9:31 AM



Description:


It is a rather typical failure that a typo in the slave name leads to the fact that Jenkins simply cannot find the slave.

It is rather strange that Jenkins 1.514 says this type of problem is "unknown" to him, and it might be a bug in Jenkins:

Connecting to Jenkins-Slave-4-34
ERROR: Unexpected failure ... Possibly it is a bug in Jenkins. (previous text translated from German L10N)
java.net.UnknownHostException: Jenkins-Slave-4-34
	at java.net.InetAddress.getAllByName0(InetAddress.java:1201)
	at java.net.InetAddress.getAllByName(InetAddress.java:1128)
	at java.net.InetAddress.getAllByName(InetAddress.java:1064)
	at java.net.InetAddress.getByName(InetAddress.java:1014)
	at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:202)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223)
	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:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)

As the problem is really typical, I follow Jenkins' advice and report this as a bug. An UnknownHostException should not be "unknown" to Jenkins.




Project:


Jenkins



Priority:


Minor



Reporter:


Markus KARG

























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2014-02-18 Thread m...@protel.net (JIRA)















































m r
 created  JENKINS-21845


Command "git rev-parse /develop^{commit}" returned status code 128















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


18/Feb/14 9:37 AM



Description:


I wanted to use the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ). I configured my job a described with the integration branch (Branch to merge to) configured to "developAutoMerge" and leaved the 'branch' field in the Git SCM blank.

When I "Build now" I get following exception:

Fetching changes from the remote Git repository
Fetching upstream changes from g...@repository.git
Seen branch in repository origin/develop
Seen branch in repository origin/developAutoMerge
Seen branch in repository origin/feature/blabla
[...]
Seen branch in repository origin/master
Seen branch in repository origin/release/2.6.1
Seen branch in repository origin/release/2.6.2
Seen 13 remote branches
Multiple candidate revisions
Scheduling another build to catch up with blaServerBuild_developAutoMerge
Merging Revision 6474f8ef91822e58edc55aad707d2725ff5a8431 (origin/feature/blabla) onto /developAutoMerge using resolve strategy
FATAL: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128:
stdout: /developAutoMerge^{commit}

stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

hudson.plugins.git.GitException: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128:
stdout: /developAutoMerge^{commit}

stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:947)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:401)
	at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
	at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:62)
	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:795)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:862)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1415)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
	at hudson.model.Run.execute(Run.java:1678)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)

I found a similar problem by googling: https://groups.google.com/forum/#!topic/jenkinsci-dev/ek4hYR-z08k
The proposed solution there was downgrading the Jenkins Git plugin from 2.0 to 1.4.0.




Environment:


Linux Ubuntu 3.2.0-58-generic x86_64

Jenkins ver. 1.546

Git Plugin 2.0 (also with 2.0.1 not working)

Git server plugin 1.3

Jenkins GIT client plugin 1.6.2




Project:


Jenkins



Labels:


plugin
git
exception




Priority:


Major



Reporter:


m r

[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















































Christian Matzat
 started work on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
















Change By:


Christian Matzat
(18/Feb/14 9:46 AM)




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] [xcode] (JENKINS-21846) Xcode plugin always uses sgvtool with -all modifier















































Al Briggs
 created  JENKINS-21846


Xcode plugin always uses sgvtool with -all modifier 















Issue Type:


New Feature



Assignee:


Unassigned


Components:


xcode



Created:


18/Feb/14 9:44 AM



Description:


We have changed our OS X project to have 3 main targets and each of these targets now uses a framework that contains all the common code of the project.

Unfortunately we have discovered that the jenkins build and auto versioning is now broken because all of the info.plist files are updated so that the CFBundleVersion is updated in all info.plist.

We need only the requested target's info.plist to be updated.




Project:


Jenkins



Priority:


Major



Reporter:


Al Briggs

























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-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















































Christian Matzat
 stopped work on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
















Change By:


Christian Matzat
(18/Feb/14 9:46 AM)




Status:


In Progress
Open



























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-auth] (JENKINS-21847) Project based authentication not showing in configure project

2014-02-18 Thread deportivo2...@gmail.com (JIRA)















































Simon Garcia
 created  JENKINS-21847


Project based authentication not showing in configure project















Issue Type:


Bug



Affects Versions:


current



Assignee:


Jesse Glick



Components:


matrix-auth



Created:


18/Feb/14 9:49 AM



Description:


Hi,

We configured a job to use project based authentication using the "Matrix Authorization Strategy Plugin"

We then upgraded Jenkins versions to the latest, and this option no longer appears within the project configuration page.

The plugin is installed and loads fine as per the log output.

If you require more information let me know.




Environment:


Ubuntu 12.04




Project:


Jenkins



Priority:


Critical



Reporter:


Simon Garcia

























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-21394) Avoid queuing request for workspace while node is offline















































Jens  Brejner
 started work on  JENKINS-21394


Avoid queuing request for workspace while node is offline
















Change By:


Jens  Brejner
(18/Feb/14 10:04 AM)




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] [vs-code-metrics] (JENKINS-21848) CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration

2014-02-18 Thread kristian.p...@hotmail.de (JIRA)















































Kris P
 created  JENKINS-21848


CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


vsCodeMetrics_1.png, vsMetrics_1.png



Components:


vs-code-metrics



Created:


18/Feb/14 10:05 AM



Description:


The codemetric displays CyclomaticComplexity/LineOfCodes always 0 if the checked library contains an enumeration with calculated CC/LoC = 0 (there are multiple lines of code in the enumeration), see attached image vsCodeMetrics_1.png.

CodeMetrics calculation result in VS2010 shows the same values for the ExampleEnum, but the CC/LoC at upper levels shows a value != 0, see image vsMetrics_1.png.

Level 1: checked .dll
Level 2: namespace
Level 3: classes/enums

Example Enum:
/// ...
public enum ExampleEnum
{
A,
B
}




Environment:


VM with Windows 7 (x64), used as Master and Build Jenkins, Visual Studio 2010, Metrics-Version: 10.0




Project:


Jenkins



Labels:


plugin




Priority:


Minor



Reporter:


Kris P

























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-21394) Avoid queuing request for workspace while node is offline
















































Jens  Brejner
 resolved  JENKINS-21394 as Fixed


Avoid queuing request for workspace while node is offline
















created pull request with fix





Change By:


Jens  Brejner
(18/Feb/14 10:06 AM)




Status:


In Progress
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] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline















































Jens  Brejner
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















Pull request 1092  ( https://github.com/jenkinsci/jenkins/pull/1092  ) created



























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-17467) CoverityPublisher aborted due to NullPointerException

2014-02-18 Thread vladic...@gmail.com (JIRA)













































  
Vlad Aginsky
 edited a comment on  JENKINS-17467


CoverityPublisher aborted due to NullPointerException
















i still see something very similar in 1.3.0
22:14:32 ERROR: Publisher jenkins.plugins.coverity.CoverityPublisher aborted due to exception
22:14:32 java.lang.NullPointerException
22:14:32 	at jenkins.plugins.coverity.analysis.CoverityToolHandler.getHandler(CoverityToolHandler.java:44)
22:14:33 	at jenkins.plugins.coverity.CoverityPublisher.perform(CoverityPublisher.java:233)
22:14:33 	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
22:14:33 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
22:14:33 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756)
22:14:33 	at hudson.model.Build$BuildExecution.post2(Build.java:183)
22:14:33 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705)
22:14:33 	at hudson.model.Run.execute(Run.java:1695)
22:14:33 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
22:14:33 	at hudson.model.ResourceController.execute(ResourceController.java:88)
22:14:33 	at hudson.model.Executor.run(Executor.java:231)
22:14:33 Finished: FAILURE

Reopening,



























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] [xcode] (JENKINS-21846) Xcode plugin always uses sgvtool with -all modifier















































Al Briggs
 commented on  JENKINS-21846


Xcode plugin always uses sgvtool with -all modifier 















An example of the error this generates is:

ld: malformed 64-bit a.b.c.d.e version number: 201402181110

This is because the info.plist for all projects is updated in addition to the DYLIB_CURRENT_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] [release] (JENKINS-21849) Maven Release Plugin throws Authentication Required error

2014-02-18 Thread vijayd1...@gmail.com (JIRA)

Vijay D
created JENKINS-21849

Maven Release Plugin throws Authentication Required error

Issue Type:

Task

Assignee:

Peter Hayes

Attachments:

child pom1.xml, child pom2.xml, jenkinsconfig.png, jenkins_job_output.txt, parent pom.xml, settings.xml

Components:

release, subversion

Created:

18/Feb/14 10:31 AM

Description:

I am trying to configure Maven Release plugin in Jenkins job. I am getting authentication exception. For invoking maven release plugin do we need to have svn client from where we are invoking the release? The requirement is as follows:

My requirement is to configure maven release plugin as follows:

1. My current version is at 1.0.0-SNAPSHOT and once testing is done and ready for movement to production the maven release plugin will be invoked from Jenkins job to move the code from branch to trunk.
2. The configuration has to check out the source from branch, update all the POMs to version 1.0.0, tag the source code and check in the code at trunk location. The tags folder will contain the tagged version at 1.0.0 (as best practice we need to change the version from 1.0.0-SNAPSHOT to 1.0.0 once the product is ready for production, right? or while moving to UAT itself it should be done?).
3. Also, the next snapshot version will be updated to 1.0.1-SNAPSHOT(which is configurable in release plugin) and checked in at branch level for the next development.

I am able to configure this, but somehow it is not working. I am getting authentication exception.
svn: Authentication required for ''.

Project:

Jenkins

Priority:

Major

Reporter:

Vijay D

[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































podskalsky
 commented on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















Here are some additional LOG messages ... it seems taht there is a problem with Credentials or 


Please look at pictures and Error.log  at Attachments!



Failed to instantiate Key[type=hudson.scm.SubversionSCM$DescriptorImpl, annotation=[none]]; skipping this component
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, hudson.security.AccessDeniedException2: anonymous is missing the Credentials/ManageDomains permission
  at hudson.scm.SubversionSCM$DescriptorImpl.(Unknown Source)

1 error
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
	at com.google.inject.Scopes$1$1.get(Scopes.java:65)



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































podskalsky
 updated  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
















Change By:


podskalsky
(18/Feb/14 10:33 AM)




Attachment:


Error.log



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































podskalsky
 updated  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
















Change By:


podskalsky
(18/Feb/14 10:34 AM)




Attachment:


2014-02-18 11_25_06-Jenkins.png



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































podskalsky
 updated  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
















Change By:


podskalsky
(18/Feb/14 10:34 AM)




Attachment:


2014-02-18 11_12_22-production_scripts Config [Jenkins].png



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)













































  
podskalsky
 edited a comment on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
















Also a test with 2.1 of that plugin failed 



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































podskalsky
 commented on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















Also a test with 2.1 of that plugin faild 



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)













































  
podskalsky
 edited a comment on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
















Here are some additional LOG messages ... it seems taht there is a problem with "Credentials" and "Role-based Authorization Strategy Plugin" ... where should I add "anonymous" (a default/alias User) at Credentials?


Please look at pictures and Error.log  at Attachments!



Failed to instantiate Key[type=hudson.scm.SubversionSCM$DescriptorImpl, annotation=[none]]; skipping this component
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, hudson.security.AccessDeniedException2: anonymous is missing the Credentials/ManageDomains permission
  at hudson.scm.SubversionSCM$DescriptorImpl.(Unknown Source)

1 error
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
	at com.google.inject.Scopes$1$1.get(Scopes.java:65)



























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] [claim] (JENKINS-21850) The Claim report should not include disabled projects

2014-02-18 Thread david.pars...@gmail.com (JIRA)















































David Pärsson
 created  JENKINS-21850


The Claim report should not include disabled projects















Issue Type:


Bug



Assignee:


Christian Åkerström



Components:


claim



Created:


18/Feb/14 10:46 AM



Description:


To me it makes no sense to include disabled projects in the claim report. When looking at it, I want to be able to find currently broken builds that are claimed or unclaimed. If this list includes a lot of disabled projects, it's hard to get an actual view of the current state.




Project:


Jenkins



Priority:


Major



Reporter:


David Pärsson

























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















































SCM/JIRA link daemon
 commented on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















Code changed in jenkins
User: Stephen Connolly
Path:
 src/main/java/hudson/scm/SubversionSCM.java
http://jenkins-ci.org/commit/subversion-plugin/176c45164b28c839fb3ece53cf668623b52d558b
Log:
  JENKINS-21679 Permissions problem causing some credential migration to fail





























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-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter

2014-02-18 Thread l.wol...@his.de (JIRA)















































Lars W
 created  JENKINS-21851


No combinations are built in a scheduled build with Matrix Combinations Parameter















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


matrix-combinations-parameter



Created:


18/Feb/14 11:08 AM



Description:


Steps to reproduce:
Create a matrix job, add one axis, add some values
Add the matrix combinations parameter
Schedule the build

When the scheduled build is started, it is built with no combinations.
Expected: scheduled builds are built with all combinations




Project:


Jenkins



Priority:


Major



Reporter:


Lars W

























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-21760) Unable to attach pdf as an attachment in email-ext plugin

2014-02-18 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-21760


Unable to attach pdf as an attachment in email-ext plugin















I still can't replicate this issue, the unit test works fine and trying something similar in a normal standalone jenkins instance works fine for me too.



























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] [xcode] (JENKINS-21846) Xcode plugin always uses sgvtool with -all modifier















































Al Briggs
 commented on  JENKINS-21846


Xcode plugin always uses sgvtool with -all modifier 















OK - I thought the solution to this would be to update the plugin so that the -all option was not called on sgvtool for newversion - but it turned out this did not fix the problem.

In the end the issue was related to just the DYLIB_CURRENT_VERSION - which was being set to 201402181110 and there is no option to alter the sgvtool to not do this.

In the end we have altered our target for the core framework to use a xcconfig file and set DYLIB_CURRENT_VERSION to 1 in this file and made sure it is no longer in the project file for the core target. By doing this sgvtool does find the value for DYLIB_CURRENT_VERSION and therefore doesn't update it.



























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] [xcode] (JENKINS-21846) Xcode plugin always uses sgvtool with -all modifier
















































Al Briggs
 resolved  JENKINS-21846 as Not A Defect


Xcode plugin always uses sgvtool with -all modifier 
















This did not require a change to the plugin





Change By:


Al Briggs
(18/Feb/14 11:37 AM)




Status:


Open
Resolved





Assignee:


Al Briggs





Resolution:


Not A Defect



























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] [xcode] (JENKINS-21846) Xcode plugin always uses sgvtool with -all modifier
















































Al Briggs
 closed  JENKINS-21846 as Not A Defect


Xcode plugin always uses sgvtool with -all modifier 
















Change By:


Al Briggs
(18/Feb/14 11:37 AM)




Status:


Resolved
Closed



























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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)

2014-02-18 Thread stephenconno...@java.net (JIRA)















































stephenconnolly
 commented on  JENKINS-21679


After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)















Try 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] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.

2014-02-18 Thread jcrinc...@gmail.com (JIRA)















































julio rincon
 commented on  JENKINS-20682


Starting Jenkins with defined --webroot or JETTY_HOME not working.















I bumped into this issue trying to run jenkins in my NAS where the tmp is just 30MBs. Overriding the java system property (java.io.tmpdir) worked for me!

E.g.

nohup java -Djava.io.tmpdir=./webroot -jar jenkins.war --httpPort= > ./jenkins.log 2>&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] [build-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin

2014-02-18 Thread veronikakrup...@yandex.ru (JIRA)















































Veronika Makeeva
 commented on  JENKINS-19210


The problem with parameterized build and subversion plugin















It does not work. See the attachment "Error.doc".



























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128















































Mark Waite
 commented on  JENKINS-21845


Command "git rev-parse /develop^{commit}" returned status code 128















I think you may have a different issue than is described in that posting on the mailing list.  The "ambiguous argument" may be due to the absence of a remote name in the call to "git rev-parse".  The failing seems to be "git rev-parse /developAutoMerge^{commit}", but I think it should be something like "git rev-parse origin/developAutoMerge^{commit}".

In the "Advanced" section of the git repository portion of the job definition, you'll find a field labeled "Name".  That field needs a value for the merge use case you're attempting.  I set mine to "upstream" and "downstream" to remind myself which one should be the destination of the push.



























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] [clearcase-ucm] (JENKINS-17993) Wrongful error message on failed update, case 9239
















































Jens  Brejner
 closed  JENKINS-17993 as Fixed


Wrongful error message on failed update, case 9239
















Missing information... Don't know what to fix, closing





Change By:


Jens  Brejner
(18/Feb/14 12:27 PM)




Status:


Resolved
Closed



























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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials

2014-02-18 Thread heinzeprel...@java.net (JIRA)















































heinzepreller
 commented on  JENKINS-21797


Subversion-Tagging Plugin can't create tag because of missing credentials















Same to me:

After Upgrade to Jenkins 1.551 and Subversion Plugin 2.1 we aren't able to VCS Tag after "Release Staging" Build. 
Also pom commit fails with Subversion Plug-in: "Failure in post build SCM action: svn: E200015: OPTIONS"

I don't know where to specify credentials for Artifactory Plugin or something else.



























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-21228) add "shell" variable into "pre-send" groovy script context

2014-02-18 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-21228


add "shell" variable into "pre-send" groovy script context















So, is this specific issue closed then since I added managed scripts? Can you open separate issues for the other items you requested? That way they won't get lost in the fray.



























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] [crowd2] (JENKINS-21852) Allow configuration of HTTPS proxy for connection to Crowd

2014-02-18 Thread tsucha...@gmail.com (JIRA)

Toby Sucharov
created JENKINS-21852

Allow configuration of HTTPS proxy for connection to Crowd

Issue Type:

Improvement

Assignee:

Thorsten Heit

Components:

crowd2

Created:

18/Feb/14 1:03 PM

Description:

Jenkins 1.549
Crowd 2 Plugin 1.6

The Crowd2 plugin provides integration to Crowd but its currently not possible to setup an Https proxy for that integration through Crowd2/Jenkins.

I have tried a few things to get this working:

1. Added the https proxy information into the proxy tab of the PluginManager

2. Added -Dhttps.proxyHost= -Dhttps.proxyPort= to the command line arguments in the jenkins startup script.

This has given Jenkins access to Crowd via the https proxy (as can be seen by launching a https request using a groovy script)

However this doesn't seem to allow access to Crowd2 plugin. There is a No route to host exception in the log when a connection is attempted.

com.atlassian.crowd.exception.OperationFailedException: java.net.NoRouteToHostException: No route to host
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:353)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:495)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.testConnection(RestCrowdClient.java:484)

Due Date:

18/Feb/14 12:00 AM

Project:

Jenkins

Priority:

Blocker

Reporter:

Toby Sucharov

[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "

2014-02-18 Thread oram...@redhat.com (JIRA)















































Oded Ramraz
 commented on  JENKINS-21717


openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "















Any updates ? did you managed to bypass this issue somehow ? 

Thanks,
Oded.



























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] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "

2014-02-18 Thread oram...@redhat.com (JIRA)















































Oded Ramraz
 commented on  JENKINS-21717


openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "















I managed to bypass this issue meanwhile by downgrading my java version ( yum downgrade java )



























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2014-02-18 Thread m...@protel.net (JIRA)















































m r
 commented on  JENKINS-21845


Command "git rev-parse /develop^{commit}" returned status code 128















Thanks! Your hints have helped me solve the problem!

One more question for understanding only: Your naming ("upstream" and "downstream") makes sense only when I have more then one Git repository. Am I right?



























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-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin

2014-02-18 Thread yoichi.nakay...@gmail.com (JIRA)













































  
Yoichi Nakayama
 edited a comment on  JENKINS-19210


The problem with parameterized build and subversion plugin
















Did you check "Validate repository URLs up to the first variable name" in the global configuration?



























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-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin

2014-02-18 Thread yoichi.nakay...@gmail.com (JIRA)















































Yoichi Nakayama
 commented on  JENKINS-19210


The problem with parameterized build and subversion plugin















Did you checked "Validate repository URLs up to the first variable name" in the global configuration?



























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-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL















































Mark Waite
 commented on  JENKINS-21553


Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL















I tried to duplicate this problem with a maven test job using git-client-plugin as the git repository with Jenkins 1.532.2, git-client-plugin 1.6.2 and git-plugin 2.0.1.  I could not duplicate the problem.  The job creation steps I used were:


	Create new job named "JENKINS-21553-maven-https-NPE" -> Maven job type
	Git source control, use "https://github.com/jenkinsci/git-client-plugin.git" as the repository
	maven version, use 3.1.1 downloaded from apache.org automatically
	maven goal, "-Dmaven.test.failure.ignore=true install"



Can you provide a more detailed description of your configuration?

What Jenkins and plugin versions were you using?

Were you using an https server with a self-signed certificate?

Does the same problem happen if you use the https URL I tried?



























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128















































Mark Waite
 commented on  JENKINS-21845


Command "git rev-parse /develop^{commit}" returned status code 128















Yes, you're right.  Unless you're using multiple repositories in a single job, it is probably best to name the repository "origin" so that it will have the typical name provided by git as a default.



























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128
















































Mark Waite
 closed  JENKINS-21845 as Not A Defect


Command "git rev-parse /develop^{commit}" returned status code 128
















Change By:


Mark Waite
(18/Feb/14 1:47 PM)




Status:


Resolved
Closed



























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-21845) Command "git rev-parse /develop^{commit}" returned status code 128
















































Mark Waite
 resolved  JENKINS-21845 as Not A Defect


Command "git rev-parse /develop^{commit}" returned status code 128
















It would be better if we could find a way to provide a much better error message than a failure from git rev-parse when the origin field is left empty, but I'm not sure if that failure message would be enough either.





Change By:


Mark Waite
(18/Feb/14 1:47 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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-20991) Git checkout fails in some projects

Mark Waite
edited a comment on JENKINS-20991

Git checkout fails in some projects

That message "Result has multiple lines" is not clear enough about what is really happening. Sorry about that.

I suspect the root cause of the problem is that the command "git rev-parse master^{commit}" (or some variant) is reporting more than one line of output. That is unexpected, since master^{commit} should report that the working repository used by Jenkins for that specific job has an ambiguously revision named "master". There are two or more things which can legitimately resolve the name "master^{commit}" for the "git rev-parse" command.

If you're interested in seeing the test case in the git-client-plugin which shows the problem, look at test_jenkins_11177 in https://github.com/jenkinsci/git-client-plugin/blob/master/src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java#L766 . The bug report which inspired that test was JENKINS-11177 .

I'm not sure what's causing the case you've detected, since that bug was fixed over 6 months ago. Could you run the "git rev-parse master^{commit}" command in that repository and attach its output? There must be more cases where that is not handled correctly.

Looking at the source code, and making guesses based on the stack trace, I think the problem comes from the revParse which is used to read the names of the branches.

[JIRA] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins
















































Mark Waite
 resolved  JENKINS-18303 as Fixed


Cannot do checkout of a git repository in BitBucket in Jenkins
















The addition of credentials support to the git-client-plugin and the git-plugin has made this type of failure much less frequent.  I have a bitbucket test job which regularly performs a checkout and build of the git-client-plugin source code from a copy I keep on bitbucket.

Could you check if this bug is fixed with git-client-plugin 1.6.2 (or later) and git-plugin 2.0.1 (or later)?





Change By:


Mark Waite
(18/Feb/14 1:58 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] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
















































Mark Waite
 resolved  JENKINS-17413 as Cannot Reproduce


Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM 
















I tried to duplicate this problem using git-client-plugin 1.6.2 and git-plugin 2.0.1 without success.

Does the original submitter or the first person who commented still see the problem with the most recent versions of those plugins?





Change By:


Mark Waite
(18/Feb/14 2:07 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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
















































Mark Waite
 resolved  JENKINS-16693 as Fixed


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
















As far as I can tell, there are no uses of "git show" in the git-client-plugin 1.6.2 or in the git-plugin 2.0.1.  There is a single use of the "git whatchanged" command which might cause this type of problem, but was not listed in the original analysis of the bug.

Can the original submitter or others who have seen the problem confirm it is fixed?





Change By:


Mark Waite
(18/Feb/14 2:16 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] [git] (JENKINS-16523) Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version)
















































Mark Waite
 resolved  JENKINS-16523 as Fixed


Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command:  --version)
















The current git-client-plugin and git-plugin releases do not call "git --version", so I believe this is resolved





Change By:


Mark Waite
(18/Feb/14 2:20 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] [git] (JENKINS-15020) Fails to build a successful build
















































Mark Waite
 resolved  JENKINS-15020 as Fixed


Fails to build a successful build
















The current git-client-plugin and git-plugin no longer call git --version, so I believe this is resolved.





Change By:


Mark Waite
(18/Feb/14 2:20 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] [git] (JENKINS-12703) jenkins and git over windows7 permission denied‏
















































Mark Waite
 closed  JENKINS-12703 as Fixed


jenkins and git over windows7 permission denied‏
















Change By:


Mark Waite
(18/Feb/14 2:24 PM)




Status:


Resolved
Closed



























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-12703) jenkins and git over windows7 permission denied‏
















































Mark Waite
 resolved  JENKINS-12703 as Fixed


jenkins and git over windows7 permission denied‏
















Credentials support has been added to git-client-plugin and git-plugin to simplify both the use and the diagnosis of this type of failure.  Try credentials with the most recent plugins and the long term support version of Jenkins.





Change By:


Mark Waite
(18/Feb/14 2:24 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] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant

2014-02-18 Thread da...@walend.net (JIRA)















































David Walend
 commented on  JENKINS-17413


Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM 















Don't worry about reproducing it. It's been eleven months! 

Can you change the message to something telling us what's wrong with the ref spec? That'd be most helpful. I was able to provide a ref spec that the code could digest, even though they worked fine with command-line git.




























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-12103) git polling constantly triggers for new (empty) git repos

Mark Waite
resolved JENKINS-12103 as Fixed

git polling constantly triggers for new (empty) git repos

As far as I can tell from my initial verification attempt, this bug is resolved in git-plugin 2.0.1 and git-client-plugin 1.6.2.

I don't have a gerrit server, so I created an empty bare repository using git protocol on my Debian git server, then defined a job which read that git protocol repository. I ran the job interactively once. It failed because there was no version to build. I then confirmed that the polling did not cause further jobs to be launched.

I think failing because there is no version to build is a reasonable behavior, since an empty repository is quite exceptional and I'd rather have the failure indicate that exceptional condition, rather than having to read log files to realize that a successful job had no revision to build.

Change By:

Mark Waite
(18/Feb/14 2:33 PM)

Status:

Open
Resolved

Resolution:

Fixed

[JIRA] [git] (JENKINS-12103) git polling constantly triggers for new (empty) git repos
















































Mark Waite
 closed  JENKINS-12103 as Fixed


git polling constantly triggers for new (empty) git repos
















Change By:


Mark Waite
(18/Feb/14 2:33 PM)




Status:


Resolved
Closed



























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-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
















































Mark Waite
 closed  JENKINS-17413 as Cannot Reproduce


Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM 
















Unfortunately, I don't think the exception you were seeing is related to the refspec.  I'm not sure what causes those types of JSON conversion errors, but the cases I've detected have seem to be related to jobs defined with git-plugin 1.x versions that are now being edited with git-plugin 2.x.  

There were significant improvements in usability with git-plugin 2.x, but those improvements caused some compatibility changes.





Change By:


Mark Waite
(18/Feb/14 2:36 PM)




Status:


Resolved
Closed



























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-21139) Git client fails to handle slashes in branch refs
















































Mark Waite
 closed  JENKINS-21139 as Fixed


Git client fails to handle slashes in branch refs
















Change By:


Mark Waite
(18/Feb/14 2:40 PM)




Status:


Resolved
Closed



























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-21139) Git client fails to handle slashes in branch refs
















































Mark Waite
 resolved  JENKINS-21139 as Fixed


Git client fails to handle slashes in branch refs
















Submitter notes that the problem was a configuration issue.  Previous versions of the plugin assumed "origin" if the remote name field from the advanced tab was left blank.  Current versions seem to require that field when referring to the remote.





Change By:


Mark Waite
(18/Feb/14 2:40 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] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect















































Mark Waite
 updated  JENKINS-21309


Git plugins changes URL for Bitbucket is incorrect
















Removed git-client-plugin from the list of components, since the bitbucket URL is included in the git-plugin, not in the git-client-plugin





Change By:


Mark Waite
(18/Feb/14 2:41 PM)




Component/s:


git-client



























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-21853) Assigned node text field should be made an editable combo box















































Jesse Glick
 created  JENKINS-21853


Assigned node text field should be made an editable combo box















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


18/Feb/14 3:03 PM



Description:


While the typing completion in the label _expression_ field is nice, it is lousy for exploring available labels, since it only starts to offer completion after you have typed the first letter, which only lets you see them all if you go through all 26! An editable combo box listing all known label atoms would be more helpful. (Must be editable, since you can type in boolean expressions, and it is legal to request a label which does not correspond to any slave yet attached.)




Project:


Jenkins



Labels:


ui
usability
slaves
labels




Priority:


Major



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] [matrix-auth] (JENKINS-21847) Project based authentication not showing in configure project
















































Jesse Glick
 resolved  JENKINS-21847 as Cannot Reproduce


Project based authentication not showing in configure project
















Working fine for me in 1.553-SNAPSHOT. Make sure you have selected Project-based Matrix Authorization Strategy, not Matrix-based security. If you still encounter the issue you will need to debug it yourself I think.





Change By:


Jesse Glick
(18/Feb/14 3:09 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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] [maven2] (JENKINS-12843) Failure with maven 3 jobs and shade plugin

2014-02-18 Thread ever...@free.fr (JIRA)
















































evernat
 resolved  JENKINS-12843 as Incomplete


Failure with maven 3 jobs and shade plugin
















No response from the reporter, so resolving as incomplete.





Change By:


evernat
(18/Feb/14 3:25 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-11920) All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris

2014-02-18 Thread ever...@free.fr (JIRA)
















































evernat
 resolved  JENKINS-11920 as Incomplete


All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris
















No response from the reporter, so resolving as incomplete.





Change By:


evernat
(18/Feb/14 3:27 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-16871) Inconsistent use of XML escaping in config.xml when uploading through API

2014-02-18 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-16871


Inconsistent use of XML escaping in config.xml when uploading through API















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-failure-analyzer] (JENKINS-21854) Allow failure reason to propogate to upstream jobs

2014-02-18 Thread aidan.mcgin...@wonga.com (JIRA)















































Aidan McGinley
 created  JENKINS-21854


Allow failure reason to propogate to upstream jobs















Issue Type:


New Feature



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


18/Feb/14 3:28 PM



Description:


If we could get an option added to a job's configuration to propogate the failure reason to upstream jobs that would be very beneficial.  
Right now if a triggered job fails because of one of it's downstream jobs then you must navigate through the build graph to the failed job, it would be nice if the failure surfaced on the parent job instead. 




Project:


Jenkins



Priority:


Major



Reporter:


Aidan McGinley

























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] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
















































SCM/JIRA link daemon
 resolved  JENKINS-18237 as Fixed


Multiple hg repos vs matrix job - the same revision used for all repositories.
















Change By:


SCM/JIRA link daemon
(18/Feb/14 3:33 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] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.

SCM/JIRA link daemon
commented on JENKINS-18237

Multiple hg repos vs matrix job - the same revision used for all repositories.

Code changed in jenkins
User: Brandon Turner
Path:
src/main/java/hudson/plugins/mercurial/MercurialSCM.java
src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java
http://jenkins-ci.org/commit/mercurial-plugin/1a33ebc7d1337659d07d995fc55a008cb9155897
Log:
Fix matrix builds with multiple SCMs

This fixes a bug that causes Matrix Builds to fail when using two or
more Mercurial repositories (via the multiple-scms plugin).

Previously, each SCM tried to checkout the changeset from the first
Mercurial repository. This checks for the presence of the
multiple-scms plugin and, if the build uses it, looks up the parent
changeset using multiple-scms.

I also modified the MatrixBuild tests to fail faster when builds fail
(added an await timeout).

JENKINS-18237

[JIRA] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.















































SCM/JIRA link daemon
 commented on  JENKINS-18237


Multiple hg repos vs matrix job - the same revision used for all repositories.















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
 src/main/java/hudson/plugins/mercurial/MercurialSCM.java
 src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java
 src/test/java/hudson/plugins/mercurial/MultiSCM.java
 src/test/java/hudson/plugins/mercurial/MultiSCMChangeLogParser.java
 src/test/java/hudson/plugins/mercurial/MultiSCMChangeLogSet.java
 src/test/java/hudson/plugins/mercurial/SCMTestBase.java
http://jenkins-ci.org/commit/mercurial-plugin/5dfe7720d202bc8102f87f9eed26e144761eadb0
Log:
  Merge pull request #55 from blt04/fix-matrix-multi

[FIXED JENKINS-18237] Fix matrix multiple scm builds


Compare: https://github.com/jenkinsci/mercurial-plugin/compare/1b5c20155dd0...5dfe7720d202




























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] [cli] (JENKINS-20023) Make CLI interface help more accesible















































Daniel Beck
 commented on  JENKINS-20023


Make CLI interface help more accesible















Noting inclusion of partial solution in LTS.



























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-19004) Channel's executorService's pool should have a name
















































Daniel Beck
 resolved  JENKINS-19004 as Fixed


Channel's executorService's pool should have a name
















Change By:


Daniel Beck
(18/Feb/14 3:41 PM)




Status:


Reopened
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] [core] (JENKINS-19004) Channel's executorService's pool should have a name















































Daniel Beck
 reopened  JENKINS-19004


Channel's executorService's pool should have a name
















Reopening temporarily to note inclusion in LTS.





Change By:


Daniel Beck
(18/Feb/14 3:40 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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-19004) Channel's executorService's pool should have a name

2014-02-18 Thread magnus.jacobs...@netinsight.net (JIRA)















































Daniel Beck
 updated  JENKINS-19004


Channel's executorService's pool should have a name
















Change By:


Daniel Beck
(18/Feb/14 3:40 PM)




Labels:


1.532.2-fixed
remoting



























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-16871) Inconsistent use of XML escaping in config.xml when uploading through API















































Magnus Jacobsson
 commented on  JENKINS-16871


Inconsistent use of XML escaping in config.xml when uploading through API















Yes, I just tried with version 1.544 and it was the same issue.

At the moment, I cannot upgrade Jenkins to try an even later 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] [www] (JENKINS-13125) HTTP Content-Range Header one byte past file length and missing "bytes" unit















































Daniel Beck
 updated  JENKINS-13125


HTTP Content-Range Header one byte past file length and missing "bytes" unit
















Change By:


Daniel Beck
(18/Feb/14 3:43 PM)




Labels:


1.532.2-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] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "

2014-02-18 Thread matthew.fisc...@twcable.com (JIRA)















































Matt Fischer
 commented on  JENKINS-21717


openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "















I have not tried since this as I got tired of fighting with it. What version of Java works for you? 



























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-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException















































SCM/JIRA link daemon
 commented on  JENKINS-20618


upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException















Code changed in jenkins
User: Jesse Glick
Path:
 core/pom.xml
http://jenkins-ci.org/commit/jenkins/2ae83f6ab099d46d01a2f70c77be069d3050267d
Log:
  Corrected a (now-)misleading comment.
JENKINS-20618 diagnostics (also in 1.532.2) are on top of jzlib 1.1.3.





























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-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551

2014-02-18 Thread reynald.bo...@gmail.com (JIRA)















































Reynald Borer
 commented on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















I'm having the same issue here, and unfortunately the X-Frame-Filter plugin cannot help as it's adding another X-Frame-Options header. This plugin should use  to replace the header content instead (https://github.com/stapler/stapler/blob/master/jelly/src/main/java/org/kohsuke/stapler/jelly/SetHeaderTag.java)

That of course does not solve this issue, seems stapler does not provide any tag to remove a header. And the HttpServletResponse API does not provide this ability too.



























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-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working

2014-02-18 Thread onur.ozardic....@gmail.com (JIRA)















































Onur Ozardic
 commented on  JENKINS-20607


GIT Plugin 2.0: Polling ignores commit from certain users not working















I also hit the issue, the workaround does not work for me, too.
I am using Jenkins ver. 1.551 with Git Plugin 2.01. I upgraded from 1.543 and 2.0 which it was not working too.



























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-21855) Add markup formatter preview for parameter descriptions















































Daniel Beck
 created  JENKINS-21855


Add markup formatter preview for parameter descriptions















Issue Type:


Improvement



Assignee:


Daniel Beck



Components:


core



Created:


18/Feb/14 4:25 PM



Project:


Jenkins



Priority:


Major



Reporter:


Daniel Beck

























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-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















































Christian Matzat
 commented on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















No, the xframe-filter-plugin won't help, sorry for misunderstanding.

I put this hint for how to integrate a configuration option into Jenkins.
The whole xframe-filter-plugin will be obsolete once this is done.



























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-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551

2014-02-18 Thread reynald.bo...@gmail.com (JIRA)















































Reynald Borer
 commented on  JENKINS-21842


Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551















Ok thanks for the clarification and sorry for my misunderstanding then. I also vote in favor of a configuration parameter as proposed in x-frame-filter 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] [core] (JENKINS-13905) install IPS jenkins package failed

2014-02-18 Thread adam.p...@oracle.com (JIRA)















































Adam Paul
 reopened  JENKINS-13905


install IPS jenkins package failed
















This issue still exists in the current Jenkins build, and prevents us from using the otherwise very-convenient IPS packages provided:

~ $ pkg publisher jenkins

Publisher: jenkins
Alias: 
   Origin URI: http://ips.jenkins-ci.org/ips/
Proxy: 
  SSL Key: None
 SSL Cert: None
  Client UUID: 5c6cd1cc-97fd-11e3-98fc-80144ffa0831
  Catalog Updated: February 14, 2014 04:28:34 PM 
  Enabled: Yes

~ $ sudo pkg install jenkins
Creating Plan (Checking for conflicting actions): /
pkg install: The requested change to the system attempts to install multiple actions
for dir 'var/lib' with conflicting attributes:

1 package delivers 'dir group=sys mode=0755 owner=root path=var/lib':
pkg://jenkins/jenkins@1.551,0-0:20140215T002823Z
2 packages deliver 'dir group=other mode=0755 owner=root path=var/lib':
pkg://solaris/file/slocate@3.1,5.11-0.175.1.0.0.15.0:20120501T195037Z
pkg://solaris/system/library/dbus@1.2.28,5.11-0.175.1.0.0.24.2:20120919T184016Z

These packages may not be installed together.  Any non-conflicting set may
be, or the packages must be corrected before they can be installed.

The fix is to simply remove the system directory entries in the package manifest, and only provide dir entries for directories owned by the jenkins package.





Change By:


Adam Paul
(18/Feb/14 5:02 PM)




Resolution:


Incomplete





Status:


Resolved
Reopened



























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-21309) Git plugins changes URL for Bitbucket is incorrect

2014-02-18 Thread johntd...@gmail.com (JIRA)















































John Dyer
 commented on  JENKINS-21309


Git plugins changes URL for Bitbucket is incorrect















Hello,

 Sorry, I am not sure I understand your last comment..

-John



























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-21309) Git plugins changes URL for Bitbucket is incorrect

2014-02-18 Thread timothy.j.bass...@uscis.dhs.gov (JIRA)















































Mark Waite
 commented on  JENKINS-21309


Git plugins changes URL for Bitbucket is incorrect















The bug was originally assigned to two components, the git-plugin and the git-client-plugin.  I investigated the source code and confirmed that in order to fix this bug, the only component that needs to change is the git-plugin, not the git-client-plugin.

Since no change would be required to the git-client-plugin to fix this bug, I removed it from list of components.



























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] [authorize-project] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect

Tim Bassett
created JENKINS-21856

Authorization - Matrix-based security - Removing Cancel Right Has No Effect

Issue Type:

Bug

Affects Versions:

current

Assignee:

Jesse Glick

Attachments:

auth-problem.JPG

Components:

authorize-project, matrix, matrix-auth, security

Created:

18/Feb/14 5:21 PM

Description:

We are using LDAP to authenticate users.
For "Authenticated Users" we have removed the "Job-Cancel" right by unchecking the checkbox.
We have four build masters that are specifically added with their LDAP user name that have more rights.

All authenicated users still have the ability to cancel (abort) a build job run.

In the attached screenshot, you should see that all "authenticated" users have the "Cancel" right taken away.

Please advise.

Environment:

RHEL

LDAP Plugin 1.2

Matrix Auth Strategy Plugin 1.1

Project:

Jenkins

Priority:

Minor

Reporter:

Tim Bassett

[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

2014-02-18 Thread jos...@java.net (JIRA)















































Jose Sa
 commented on  JENKINS-21785


Check for changes in folders linked via svn:externals fails due to missing credentials















I see similar issue with some externals (not all) with following exception:

Feb 18, 2014 7:19:48 PM hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify
WARNING: Failed to handle Subversion commit notification
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svnroot/repo/path/to/external failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148)
at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2700)
at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:202)
at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:136)
at sun.reflect.GeneratedMethodAccessor348.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
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.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:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurity

[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives

2014-02-18 Thread lauri.taal...@gmail.com (JIRA)















































Lauri Taaleš
 commented on  JENKINS-20663


file name encoding broken in zip archives















I have the same problem with filenames that contain 'õ', 'ä', 'ö' or 'ü'. Prior to version 1.532 it could be fixed by adding -Dfile.encoding=Cp775 to  element in jenkins.xml. I have traced this particular "regression" back to this commit, which replaced usage of hudson.util.io.ZipArchiver with java.util.zip.ZipOutputStream in hudson.model.DirectoryBrowserSupport. As a temporary work-around I have compiled version 1.532.1 from source on Java 7, which adds an additional Charset parameter to ZipOutputStream constructor and passed in the value of System.getProperty("file.encoding"), but I don't feel like doing this for every update.



























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] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable















































Jesse Glick
 commented on  JENKINS-5723


Allow setting arbitrary command line arguments when defining a mercurial executable















By the way the original request is now better handled by the Credentials plugin integration. So now treating this as a variant option to JENKINS-19719.



























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] [mercurial] (JENKINS-19719) Integration with Config File Provider plugin















































SCM/JIRA link daemon
 commented on  JENKINS-19719


Integration with Config File Provider plugin















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
 src/main/java/hudson/plugins/mercurial/MercurialIniConfig.java
 src/main/resources/hudson/plugins/mercurial/MercurialIniConfig/MercurialIniConfigProvider/newInstanceDetail.jelly
 src/main/resources/hudson/plugins/mercurial/MercurialIniConfig/edit-config.jelly
http://jenkins-ci.org/commit/mercurial-plugin/d5ba22010daea9503b7f6e02f46d403c075e1609
Log:
  JENKINS-19719 Sketch of Config File Provider plugin integration.





























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] [mercurial] (JENKINS-19719) Integration with Config File Provider plugin