date:20150119















































Harald Albers
 commented on  JENKINS-26437


Display problem in localization dialog















This also applies to other languages, e.g. French. See screenshot (Translation Assistence Plugin 1.12 on Jenkins 1.593 viewed with current Firefox and Chrome).
Other example: English (Translation Assistence Plugin 1.11 on Jenkins 1.593 viewed with current Firefox and Chrome).



























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







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

[JIRA] [core] (JENKINS-25381) Build history widget verbosity

2015-01-19 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-25381


Build history widget verbosity















what now if I am not happy with this new feature.

Downgrade and live with the problems this fixed, tolerate it and wait for a fix, or fix it yourself and submit a PR.



























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







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

[JIRA] [locale-plugin] (JENKINS-26437) Display problem in localization dialog















































Harald Albers
 updated  JENKINS-26437


Display problem in localization dialog
















Change By:


Harald Albers
(19/Jan/15 8:17 AM)




Attachment:


french-v1.12.png





Attachment:


english-v1.11.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/d/optout.

[JIRA] [subversion-plugin] (JENKINS-26443) Checkout to root directory deletes ALL files in the directory

2015-01-19 Thread david.tad...@seebyte.com (JIRA)















































Dave Taddei
 commented on  JENKINS-26443


Checkout to root directory deletes ALL files in the directory















I have also tried excluding the .svn folder from the workspace cleanup but the problem persists.  I have also tried excluding all .svn folders from the structure but the plugin still deletes everything in the workspace.  A workaround for this is possible by checking out the SVN repo into a specific folder in the workspace but this can cause problems with the SonarQube code analysis plugin as it requires the workspace root to be the same as the source directory.



























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







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

[JIRA] [locale-plugin] (JENKINS-26437) Display problem in localization dialog















































Harald Albers
 commented on  JENKINS-26437


Display problem in localization dialog















Layout is broken since Jenkins 1.572 (see screenshots 1.571 vs 1.572). In this release, layout was heavily reworked.
I will ask tfennelly to have a look at this issue.



























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







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

[JIRA] [locale-plugin] (JENKINS-26437) Display problem in localization dialog















































Harald Albers
 updated  JENKINS-26437


Display problem in localization dialog
















layout was first broken in 1.572





Change By:


Harald Albers
(19/Jan/15 9:03 AM)




Attachment:


jenkins-1.571.png





Attachment:


jenkins-1.572.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/d/optout.

[JIRA] [git-plugin] (JENKINS-26482) Git trigger build on push in any branch

2015-01-19 Thread faisalalirabb...@gmail.com (JIRA)

Faisal Rabbani
created JENKINS-26482

Git trigger build on push in any branch

Issue Type:

Bug

Assignee:

Nicolas De Loof

Components:

git-plugin

Created:

19/Jan/15 8:03 AM

Description:

I want to trigger build if someone commit in Bitbuket's specific branch. Current...
I want to trigger build if someone commit in Bitbuket's specific branch. Currently we can mention which branch to build but on setting remote triggers it trigger build on code commit in any branch not only in given branch.
I set Jenkins hook as well as post receive hook which triggers build remotely but by giving branch name it give error that no git repo or branch is set.

[http://server/jenkins/git/notifyCommit?url="" class="error">branches=dev]
Gives Response:
No git jobs using repository: g...@bitbucket.org:myrepo,git[ and branches: dev]
No Git consumers using SCM API plugin for: g...@bitbucket.org:myrepo.git[

http://jenkins/git/notifyCommit?url="">
works fine and triggers build but as soon as I mention branch in url like:
http://server/jenkins/git/notifyCommit?url="">branches=dev

No git jobs using repository: g...@bitbucket.org:myrepo,git[ and branches: dev]
No Git consumers using SCM API plugin for: g...@bitbucket.org:myrepo.git[

Project:

Jenkins

Priority:

Major

Reporter:

Faisal Rabbani

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

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

[JIRA] [core] (JENKINS-20606) Wrong spelling in Russian localization

2015-01-19 Thread jbeeck...@compliancesystems.com (JIRA)















































Harald Albers
 updated  JENKINS-20606


Wrong spelling in Russian localization
















Change By:


Harald Albers
(19/Jan/15 8:19 AM)




Component/s:


core





Component/s:


translation-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/d/optout.

[JIRA] [tfs-plugin] (JENKINS-26479) TFS plugin does not fail on error retrieving file

2015-01-19 Thread ian.willia...@telus.com (JIRA)















































Ian Williams
 updated  JENKINS-26479


TFS plugin does not fail on error retrieving file
















Some investigation into the source indicates TFTool.java says:
static final int SUCCESS_EXIT_CODE = 0;
static final int PARTIAL_SUCCESS_EXIT_CODE = 1;

LOGGER.fine(String.format("The TFS command '%s' returned with an error code of %d", toolArguments1, result));
if ((result == SUCCESS_EXIT_CODE) || (result == PARTIAL_SUCCESS_EXIT_CODE)) {
return new InputStreamReader(new ByteArrayInputStream(consoleStream.toByteArray()));
} else {
listener.fatalError(String.format("Executable returned an unexpected result code [%d]", result));
throw new AbortException();
}


TF result codes (http://msdn.microsoft.com/en-us/library/cc31bk2e.aspx#exit_codes) show:

0 	Success.
1 	Partial success; this means at least something, or possibly everything, failed to succeed.
2 	Unrecognized command.
100 	Nothing succeeded.

Only Exit "0" should be treated as SUCCESS. All else are Exceptions





Change By:


Ian Williams
(20/Jan/15 6:17 AM)




Description:



SourceCodeMangementoptionfromTeamFoundationServer:Logsreport:Summary:0conflicts,0warnings,1errorsLocalpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/telus/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.TheitemwillnotberetrievedFromthecommandline:[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$tfget.-recursive-version:D2015-01-16T23:07:14Z-nopromptLocalpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/corp/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.Theitemwillnotberetrieved[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$echo$?1Pluginisnotraisingtheexceptionandcausingthebuildtofail.TheactualTFSfilepath($/java)is240chars



























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







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

[JIRA] [tfs-plugin] (JENKINS-26479) TFS plugin does not fail on error retrieving file

2015-01-19 Thread ian.willia...@telus.com (JIRA)















































Ian Williams
 updated  JENKINS-26479


TFS plugin does not fail on error retrieving file
















Change By:


Ian Williams
(20/Jan/15 6:18 AM)




Description:


SourceCodeMangementoptionfromTeamFoundationServer:Logsreport:Summary:0conflicts,0warnings,1errorsLocalpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/telus/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.TheitemwillnotberetrievedFromthecommandline:[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$

tfget.-recursive-version:D2015-01-16T23:07:14Z-noprompt

Localpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/corp/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.Theitemwillnotberetrieved[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$echo$?1Pluginisnotraisingtheexceptionandcausingthebuildtofail.TheactualTFSfilepath($/java)is240chars



























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







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

[JIRA] [tfs-plugin] (JENKINS-26479) TFS plugin does not fail on error retrieving file

2015-01-19 Thread ian.willia...@telus.com (JIRA)















































Ian Williams
 updated  JENKINS-26479


TFS plugin does not fail on error retrieving file
















Change By:


Ian Williams
(20/Jan/15 6:18 AM)




Description:


SourceCodeMangementoptionfromTeamFoundationServer:Logsreport:Summary:0conflicts,0warnings,1errorsLocalpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/telus/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.TheitemwillnotberetrievedFromthecommandline:[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$tfget.-recursive-version:D2015-01-16T23:07:14Z-nopromptLocalpath/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr/wps-ws/paymentdeviceadminsvc-1-1-war-deploy/paymentdeviceadminsvc-1-1-service/src/main/java/com/corp/wsdl/eo/financialmgmt/paymentdeviceadminservice_1/PaymentDeviceAdminService_v1_1_PaymentDeviceAdminServicePortImpl.javaistoolong.Theitemwillnotberetrieved[/build/workspace/BillPay/TEST_jenkins_wps_build_tfserr][bldadm]$echo$?1Pluginisnotraisingtheexceptionandcausingthebuildtofail.TheactualTFSfilepath($/java)is240chars



























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







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

[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category

2015-01-19 Thread akerstrom.christ...@gmail.com (JIRA)















































Christian Bremer
 commented on  JENKINS-12092


Allow a job to completely block a category















300$ is up for grabs for solving this issue at: https://freedomsponsors.org/issue/618/allow-a-job-to-completely-block-a-category?alert=SPONSOR#



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-16360) Print DSL formatted config.xml for an existing Job

2015-01-19 Thread akerstrom.christ...@gmail.com (JIRA)















































Christian Bremer
 commented on  JENKINS-16360


Print DSL formatted config.xml for an existing Job















http://job-dsl.herokuapp.com/ ?

We also generate all config.xml in gradle by executing javaposse.jobdsl.Run and passing in our dsl files.



























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







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

[JIRA] [core] (JENKINS-26496) Trying to get the DateFormat as build ID

2015-01-19 Thread sven.finsterwal...@edict.de (JIRA)















































Sven Finsterwalder
 commented on  JENKINS-26496


Trying to get the DateFormat as build ID















We have the same problem and the design of the job-overview-page is broken (see Screenshot)



























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







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

[JIRA] [core] (JENKINS-26496) Trying to get the DateFormat as build ID

2015-01-19 Thread sven.finsterwal...@edict.de (JIRA)













































 
Sven Finsterwalder
 edited a comment on  JENKINS-26496


Trying to get the DateFormat as build ID
















After updating from 1.596 to 1.597, we have the same problem and the design of the job-overview-page is broken (see Screenshot)



























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







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

[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category

2015-01-19 Thread akerstrom.christ...@gmail.com (JIRA)















































Christian Bremer
 commented on  JENKINS-12092


Allow a job to completely block a category















I think the ideal way to solve this is to have a multi-project throttle category that you assign to all your jobs.
The multi-project throttle category should be able to have high limitations or no limitations at all.

If you then create:
jobA and jobB with the limitations 0/0 they should be able to run concurrently up to the multi-project throttle category limitations.
jobC with the limitations 1 per node, jobC should only run on a node if no other job with the throttle category runs on the node.
jobD with the limitations 1 in total, jobD should only run if no other jobs of this category is running.

The UI to support this is already there, I have tried to set this up since I thought that it should work before I saw this issue 



























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







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

[JIRA] [docker-plugin] (JENKINS-26388) Jenkins think the image cap is reached although it's not and cannot spawn new slaves

2015-01-19 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-26388


Jenkins think the image cap is reached although its not and cannot spawn new slaves















Do you have any other running containers on this node?
I'm patching locally to exclude not templated containers from total list.



























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







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

[JIRA] [core] (JENKINS-26496) Trying to get the DateFormat as build ID

2015-01-19 Thread sven.finsterwal...@edict.de (JIRA)















































Sven Finsterwalder
 updated  JENKINS-26496


Trying to get the DateFormat as build ID
















Change By:


Sven Finsterwalder
(20/Jan/15 7:11 AM)




Attachment:


2015-01-20_0808.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/d/optout.

[JIRA] [core] (JENKINS-26497) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException

2015-01-19 Thread gdb...@yahoo.com (JIRA)















































Nam Nguyen
 created  JENKINS-26497


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


Screen Shot 2015-01-19 at 11.49.22 PM.png



Components:


core



Created:


20/Jan/15 7:49 AM



Description:


A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.
Stack trace

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/opt/tomcat/webapps/jenkins/WEB-INF/lib/jenkins-core-1.597.jar!/lib/hudson/project/projectActionFloatingBox.jelly:38:74: st:include hudson.model.Run.getIDFormatter()Ljava/text/DateFormat;
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at

[JIRA] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page















































Jay Beeckman
 updated  JENKINS-26077


Multiple Test Reports Graphs and Links in Job Page
















Screenshot of duplicate information.





Change By:


Jay Beeckman
(19/Jan/15 9:49 PM)




Attachment:


DuplicateTestResults.jpg



























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







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

[JIRA] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page

2015-01-19 Thread jbeeck...@compliancesystems.com (JIRA)













































 
Jay Beeckman
 edited a comment on  JENKINS-26077


Multiple Test Reports Graphs and Links in Job Page
















I'm seeing the same problem, we are using MSTEST, and the xUnit plugin.

Jenkins 1.596
xUnit 1.93.



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















I understand what the problem is now - I think it was this change:

https://github.com/jenkinsci/docker-build-publish-plugin/pull/3

before the push would have pushed all the tags - including the latest.

But after the change it only pushed the version with the explicit tag e.g. kafka:0.8.1 or kafka:VERSION_28 depending on how you generated the tag, but not kafka:latest. 

So the solution is not to add any additional tags, but to push the one tagged latest as well as the one with the explicit tag. I have tried this and it works.

There is a new revised PR here - I can confirm that this does work:

https://github.com/jenkinsci/docker-build-publish-plugin/pull/7

Maybe though the checkbox is unnecessary - latest should automatically be pushed as well as the explicit tag?



























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







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

[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger

2015-01-19 Thread rsand...@cloudbees.com (JIRA)















































rsandell
 commented on  JENKINS-23152


builds getting lost due to GerritTrigger















Released a fix in version 2.13.0-beta-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/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-26488) Add support for Bitbucket Pull Request Builder plugin

2015-01-19 Thread mgreben...@gmail.com (JIRA)















































Maksym Grebenets
 created  JENKINS-26488


Add support for Bitbucket Pull Request Builder plugin















Issue Type:


New Feature



Assignee:


Daniel Spilker



Attachments:


config.xml



Components:


job-dsl-plugin



Created:


19/Jan/15 1:37 PM



Description:


Bitbucket PR Builder plugin is similar to GitHub PR Builder plugin.

And Job DSL plugin already supports GitHub.

This is feature request to support Bitbucket PR Builder.
I have attached config.xml for a job using it.

Per my understanding, the important sections of that XML are

SCM configuration

scm class="hudson.plugins.git.GitSCM" plugin="git@2.3.4"
configVersion2/configVersion
userRemoteConfigs
  hudson.plugins.git.UserRemoteConfig
urlg...@bitbucket.org:${repositoryOwner}/${repositoryName}.git/url
  /hudson.plugins.git.UserRemoteConfig
/userRemoteConfigs
branches
  hudson.plugins.git.BranchSpec
name*/${sourceBranch}/name
  /hudson.plugins.git.BranchSpec
/branches
doGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurations
submoduleCfg class="list"/
extensions
  hudson.plugins.git.extensions.impl.PreBuildMerge
options
  mergeRemoteorigin/mergeRemote
  mergeTarget${targetBranch}/mergeTarget
  mergeStrategydefault/mergeStrategy
/options
  /hudson.plugins.git.extensions.impl.PreBuildMerge
/extensions
  /scm
 

Build trigger

triggers
bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger plugin="bitbucket-pullrequest-builder@1.4.3-SNAPSHOT"
  specH/1 * * * */spec
  cronH/1 * * * */cron
  usernamemycompany/username
  passwordmypassword/password
  repositoryOwnermyteam/repositoryOwner
  repositoryNamemyrepo/repositoryName
  ciSkipPhrases/ciSkipPhrases
  checkDestinationCommittrue/checkDestinationCommit
/bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger
  /triggers
 

This is a follow up to question on Google Group




Environment:


Jenkins version:1.596




Project:


Jenkins



Labels:


plugin
bitbucket
pull_request




Priority:


Major



Reporter:


Maksym Grebenets

























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







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

[JIRA] [vault-scm-plugin] (JENKINS-26487) NPE during SCM polling

2015-01-19 Thread ken.ove...@gmail.com (JIRA)















































Ken Overly
 updated  JENKINS-26487


NPE during SCM polling
















Change By:


Ken Overly
(19/Jan/15 1:37 PM)




Description:


ANullPointerExceptionoccurswhenJenkinsattemptstoperformanSCMpollforanyjob.ThestacktracewouldseemtoindicateFilePathexecisnullinline326ofVaultSCM.java.AVaultSCMcheckoutcompletessuccessfullywhenabuildiskickedoffmanually.
ItriedleavingthePathtoVaultexecutablefieldblankandusingthedefaultvalueconfiguredbutwithoutsuccess.
Stacktrace:Jan19,20158:26:00AMorg.jvnet.hudson.plugins.VaultSCMcompareRemoteRevisionWithINFO:LastBuildDatesettoWedJan1410:19:55EST2015Jan19,20158:26:00AMhudson.triggers.SCMTrigger$RunnerrunPollingSEVERE:FailedtorecordSCMpollingforhudson.model.FreeStyleProject@3ab722[FAB22_FABMain]java.lang.NullPointerException	atorg.jvnet.hudson.plugins.VaultSCM.getVaultPath(VaultSCM.java:334)	atorg.jvnet.hudson.plugins.VaultSCM.determineChangeCount(VaultSCM.java:521)	atorg.jvnet.hudson.plugins.VaultSCM.compareRemoteRevisionWith(VaultSCM.java:293)	athudson.scm.SCM.poll(SCM.java:397)	athudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462)	athudson.model.AbstractProject._poll(AbstractProject.java:1433)	athudson.model.AbstractProject.poll(AbstractProject.java:1344)	athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515)	athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544)	athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)	atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource)	atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource)	atjava.util.concurrent.FutureTask.run(UnknownSource)	atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource)	atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource)	atjava.lang.Thread.run(UnknownSource)





Priority:


Minor
Major



























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







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

[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy

2015-01-19 Thread slawo...@ezono.com (JIRA)















































Slawomir Czarko
 commented on  JENKINS-26458


org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy















For me this started happening after updating subversion plugin from version 2.4.5 to 2.5. Downgrading subversion plugin back to 2.4.5 fixes the problem.



























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







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

[JIRA] [core] (JENKINS-25146) When the anonymous user has no access rights, userContent is inaccessible

2015-01-19 Thread jeebitesh.kalan...@adp.com (JIRA)















































Jeebitesh Kalantri
 commented on  JENKINS-25146


When the anonymous user has no access rights, userContent is inaccessible















In windows as well we have issues with userContent folder on login page, because of which many js/css files fail to load, it seems anonymous user does not have access to this folder.



























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







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

[JIRA] [vault-scm-plugin] (JENKINS-26487) NPE during SCM polling

2015-01-19 Thread ken.ove...@gmail.com (JIRA)















































Ken Overly
 created  JENKINS-26487


NPE during SCM polling















Issue Type:


Bug



Assignee:


Stuart Whelan



Components:


vault-scm-plugin



Created:


19/Jan/15 1:29 PM



Description:


A NullPointerException occurs when Jenkins attempts to perform an SCM poll for any job.  The stack trace would seem to indicate FilePath exec is null in line 326 of VaultSCM.java.

A Vault SCM checkout completes successfully when a build is kicked off manually.

Stack trace:
Jan 19, 2015 8:26:00 AM org.jvnet.hudson.plugins.VaultSCM compareRemoteRevisionWith
INFO: Last Build Date set to Wed Jan 14 10:19:55 EST 2015
Jan 19, 2015 8:26:00 AM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@3ab722FAB22_FABMain
java.lang.NullPointerException
	at org.jvnet.hudson.plugins.VaultSCM.getVaultPath(VaultSCM.java:334)
	at org.jvnet.hudson.plugins.VaultSCM.determineChangeCount(VaultSCM.java:521)
	at org.jvnet.hudson.plugins.VaultSCM.compareRemoteRevisionWith(VaultSCM.java:293)
	at hudson.scm.SCM.poll(SCM.java:397)
	at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1462)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1433)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1344)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)




Environment:


Jenkins 1.596, Win7-64, Vault SCM Plugin 1.1.1, SourceGear Vault Pro 6.0.1




Project:


Jenkins



Labels:


plugin
vault-scm




Priority:


Minor



Reporter:


Ken Overly

























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins
















































Jerry Cai
 resolved  JENKINS-26480 as Not A Defect


The /jenkins/pluginManager/available cant list plugins
















@Daniel , This issue get resolved base on Daniel's suggestion: Click "Check Now" button on "Advanced" Tab of pluginManager page , Wait for while when "Check updates..." done , Then every thing works well . So close this issue now , Suggest to enhance this user experience in future release for automatically loading when click "Available" tab . Thanks Daniel for your comments and solution .





Change By:


Jerry Cai
(19/Jan/15 1:57 PM)




Status:


Reopened
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins

2015-01-19 Thread bochenski.kuba+jenk...@gmail.com (JIRA)













































 
Jerry Cai
 edited a comment on  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins
















@Daniel , This issue get resolved by Daniel's suggestion: Click "Check Now" button on "Advanced" Tab of pluginManager page , Wait for while when "Check updates..." done , Then every thing works well . So close this issue now , Suggest to enhance this user experience in future release for automatically loading when click "Available" tab . Thanks Daniel for your comments and solution .



























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







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

[JIRA] [bitbucket-plugin] (JENKINS-26489) Action report for the bitbucket polling log on web UI

2015-01-19 Thread fbelz...@gmail.com (JIRA)















































Félix  Belzunce Arcos
 created  JENKINS-26489


Action report for the bitbucket polling log on web UI















Issue Type:


Bug



Assignee:


Félix  Belzunce Arcos



Components:


bitbucket-plugin



Created:


19/Jan/15 2:23 PM



Description:


Add an action report for the bitbucket polling log on web UI at project level.




Project:


Jenkins



Priority:


Minor



Reporter:


Félix  Belzunce Arcos

























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







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

[JIRA] [p4-plugin] (JENKINS-26486) Workspace fails to update when Replace missing/modified files is checked

2015-01-19 Thread sse...@tiscali.it (JIRA)















































Sebastiano Mandala
 created  JENKINS-26486


Workspace fails to update when Replace missing/modified files is checked















Issue Type:


Bug



Assignee:


Unassigned


Components:


p4-plugin



Created:


19/Jan/15 12:46 PM



Description:


When Auto cleanup and sync option is selected WITH REPLACE missing/modified files option checked, the following error happens always:

ERROR: Unable to update workspace: com.perforce.p4java.exception.ConnectionException: Java heap space




Environment:


Windows 7, java 1.7, version 1.1.2, p4 server version: P4D/NTX86/2012.2/585708 (2013/02/01), jenkins 1.596




Project:


Jenkins



Priority:


Minor



Reporter:


Sebastiano Mandala

























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







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

[JIRA] [job-restrictions-plugin] (JENKINS-26485) need global slave/build permission when using job restriction at slaves

2015-01-19 Thread bockelm...@dkrz.de (JIRA)















































hbockelmann
 created  JENKINS-26485


need global slave/build permission when using job restriction at slaves















Issue Type:


Bug



Assignee:


Oleg Nenashev



Components:


job-restrictions-plugin, role-strategy-plugin



Created:


19/Jan/15 12:41 PM



Description:


When restricting job execution at slave to LDAP groupID via job restriction plugin, one needs to set additional "slave/build" permission for the user in the global role.
For the "slave/connect" and "slave/disconnect" permission this is not needed, here it is enough to assign this via a slave role.




Environment:


CentOS release 5.11

jenkins core 1.580.2

job restriction plugin 0.4

role strategy plugin 2.2.0

LDAP plugin 1.11






Project:


Jenkins



Priority:


Major



Reporter:


hbockelmann

























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







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

[JIRA] [multijob-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in

2015-01-19 Thread jenkins-ci.jmdl...@xoxy.net (JIRA)















































JM D
 commented on  JENKINS-26318


Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in















Nope, I don't. Just getting sources thanks to the Subversion plugin, and enabled "Poll SCM" in "Build Triggers"



























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







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

[JIRA] [git-plugin] (JENKINS-26482) Git trigger build on push in any branch

2015-01-19 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-26482


Git  trigger build on push in any branch















Have you tried using the "branches to build" field to limit the branches which can be built by the job?

Can you upload the config.xml file for that job so that the precise definition of the job is available?



























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







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

[JIRA] [core] (JENKINS-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}

2015-01-19 Thread ra...@coofercat.com (JIRA)















































Ralph Bolton
 commented on  JENKINS-23273


RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}















Tommy's point about only chown'ing files that are in the RPM seems like a bright idea to me. I'm not sure if you can do an "rpm -qvl" during a post-install script though (has the package been installed enough to get this during post-install?). However, this would be a good solution.

In the short term, Tommy's other point about only attempting any sort of chown if the JENKINS_USER is not "jenkins" also makes a lot of sense, and would be easier to implement. It still penalises people who don't run as 'jenkins', but I'm guessing they're a pretty small minority. It'd help everyone else while working out the better solution in the future.

Cheers,

...Ralph



























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







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

[JIRA] [multijob-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems

2015-01-19 Thread cgroba...@muellerbbm-vas.de (JIRA)















































Christian Grobauer
 updated  JENKINS-26318


Subversion Plug in 2.5 causes sporadic problems
















Change By:


Christian Grobauer
(19/Jan/15 2:32 PM)




Summary:


SubversionPlugin2.5causessporadicproblems
withMultiJobPlugin



























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







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

[JIRA] [extended-choice-parameter-plugin] (JENKINS-26490) Extended Choice Parameter - Parsing values different for on demand builds and builds started by timer

2015-01-19 Thread david.ru...@seebyte.com (JIRA)















































David Rubio
 updated  JENKINS-26490


Extended Choice Parameter - Parsing values different for on demand builds and builds started by timer
















Change By:


David Rubio
(19/Jan/15 3:15 PM)




Summary:


ExtendedChoiceParameter-
Parsingvaluesdifferentforondemandbuildsandbuildsstartedbytimer



























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







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

[JIRA] [multijob-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems

2015-01-19 Thread cgroba...@muellerbbm-vas.de (JIRA)















































Christian Grobauer
 commented on  JENKINS-26318


Subversion Plug in 2.5 causes sporadic problems















No, I also use only the subversion plugin for updating/reverting the source code. 



























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







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

[JIRA] [extended-choice-parameter-plugin] (JENKINS-26490) Parsing values different for on demand builds and builds started by timer

2015-01-19 Thread david.ru...@seebyte.com (JIRA)















































David Rubio
 created  JENKINS-26490


Parsing values different for on demand builds and builds started by timer















Issue Type:


Bug



Assignee:


vimil



Components:


extended-choice-parameter-plugin



Created:


19/Jan/15 3:14 PM



Description:


I am observing different behaviours of the plugin when triggering the build manually and when the build is triggered by the timer. The field is configured this way:

	Parameter type: check boxes
	Delimiter: (a space)
	Source for Value: Value = -p,-t,-v
	Default Value: Value = -p, -t




	If I run a build manually (leaving the defaults) to print the value of the variable which holds the param the output is:

+ echo -p -t
-p -t

	If I the build runs with a timer the output is:

+ echo -p, -t
-p, -t




I've tried the following configuration, which works as expected, however, the default options are not marked when clicking Build with parameters

	Parameter type: check boxes
	Delimiter: (a space)
	Source for Value: Value = -p,-t,-v
	Default Value: Value = -p -t






Environment:


Jenkins 1.596

Extended choice parameter plugin 0.34

Ubuntu 14.04




Project:


Jenkins



Priority:


Minor



Reporter:


David Rubio

























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







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

[JIRA] [build-timeout-plugin] (JENKINS-26491) CountDownLatch interruptable?

2015-01-19 Thread r...@initfour.nl (JIRA)















































Herman van Rink
 created  JENKINS-26491


CountDownLatch interruptable?















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


build-timeout-plugin



Created:


19/Jan/15 3:20 PM



Description:


Would this thread dump be something that could not be interrupted?


WAITING on java.util.concurrent.CountDownLatch$Sync@241036ba
	at sun.misc.Unsafe.park(Native Method)
	-  waiting on java.util.concurrent.CountDownLatch$Sync@241036ba
	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281)
	at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207)
	at org.pircbotx.Channel.getMode(Channel.java:127)
	at hudson.plugins.ircbot.v2.IRCConnection.send(IRCConnection.java:276)
	at hudson.plugins.ircbot.v2.IRCConnection.send(IRCConnection.java:268)
	at hudson.plugins.im.IMPublisher.sendNotification(IMPublisher.java:379)
	at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:585)
	at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304)
	at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1770)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)


The parent problem is described in https://issues.jenkins-ci.org/browse/JENKINS-22042




Project:


Jenkins



Priority:


Minor



Reporter:


Herman van Rink

























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







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

[JIRA] [support-core-plugin] (JENKINS-26483) Record JVM architecture

2015-01-19 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-26483


Record JVM architecture















Issue Type:


Bug



Assignee:


Steven Christou



Components:


support-core-plugin



Created:


19/Jan/15 9:12 AM



Description:


Support bundle do report JVM version but not architecture (32/64bits)




Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























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







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

[JIRA] [support-core-plugin] (JENKINS-26483) Record JVM architecture

2015-01-19 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 updated  JENKINS-26483


Record JVM architecture
















Change By:


Steven Christou
(19/Jan/15 10:33 AM)




URL:


https://github.com/jenkinsci/support-core-plugin/pull/20



























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







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

[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion















































Jakub Bochenski
 commented on  JENKINS-26472


Jenkins maven-project plugin doesnt support reactor module exclusion















I've confirmed that this is still not supported with 2.8 version of maven-project, but I don't have the time to setup jenkins nightly now.

 it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.
It is a major loss of functionality for me  this was actually the reason to upgrade to maven 3.2 for me
It might be simply that not many people are aware of the functionality, but the problem is well known and used to be solved by dupicating module declarations over profiles, c.f. https://stackoverflow.com/questions/5539348/how-to-exclude-a-module-from-a-maven-reactor-build (the old answer still has more votes)



























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







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

[JIRA] [clearcase-ucm-plugin] (JENKINS-26484) Poll sibling from named stream (case 12577)

2015-01-19 Thread m...@praqma.net (JIRA)















































Mads Nielsen
 created  JENKINS-26484


Poll sibling from named stream (case 12577)















Issue Type:


New Feature



Assignee:


Praqma Support



Components:


clearcase-ucm-plugin



Created:


19/Jan/15 11:52 AM



Project:


Jenkins



Priority:


Major



Reporter:


Mads Nielsen

























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins















































Jerry Cai
 reopened  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins
















This bug is block me , Thanks for resolving it ASAP , Thank you !

currently , I manual call the request it works well 
http://mirror.bit.edu.cn/jenkins/updates/current/update-center.json

It seems page can't trigger this api at all





Change By:


Jerry Cai
(19/Jan/15 11:52 AM)




Resolution:


NotADefect





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/d/optout.

[JIRA] [clearcase-ucm-plugin] (JENKINS-25647) LoadRules not properly added in certain situations (case 12301)















































SCM/JIRA link daemon
 commented on  JENKINS-25647


LoadRules not properly added in certain situations (case 12301)















Code changed in jenkins
User: Mads Nielsen
Path:
 pom.xml
 src/main/java/net/praqma/hudson/Util.java
 src/main/java/net/praqma/hudson/remoting/CheckoutTask.java
 src/main/java/net/praqma/hudson/remoting/deliver/StartDeliver.java
http://jenkins-ci.org/commit/clearcase-ucm-plugin/d88a0705b238606e3b4149776c92b867956962bd
Log:
  Fixed JENKINS-25647





























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







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

[JIRA] [clearcase-ucm-plugin] (JENKINS-25342) Project templates should be parsed on the executing node (case 12207)















































SCM/JIRA link daemon
 commented on  JENKINS-25342


Project templates should be parsed on the executing node (case 12207)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/net/praqma/hudson/nametemplates/BaselineTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/ClearCaseVersionNumberTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/ComponentTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/DateTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/EnvTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/FileTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/NameTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/NumberTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/ProjectTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/StreamTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/Template.java
 src/main/java/net/praqma/hudson/nametemplates/TimeTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/UserTemplate.java
 src/main/java/net/praqma/hudson/nametemplates/VersionNumberTemplate.java
 src/main/java/net/praqma/hudson/notifier/CCUCMNotifier.java
http://jenkins-ci.org/commit/clearcase-ucm-plugin/1da037b1b0ce0da167fe9e622012877502a218f7
Log:
  Fixed JENKINS-25342





























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins

2015-01-19 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins















Much more information is needed to investigate further. What happens when you do what I suggest in my earlier comment?

See also https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue



























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







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

[JIRA] [support-core-plugin] (JENKINS-26483) Record JVM architecture

2015-01-19 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 updated  JENKINS-26483


Record JVM architecture
















Change By:


Nicolas De Loof
(19/Jan/15 9:13 AM)




Issue Type:


Bug
Improvement



























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







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

[JIRA] [support-core-plugin] (JENKINS-26483) Record JVM architecture

2015-01-19 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 updated  JENKINS-26483


Record JVM architecture
















Change By:


Steven Christou
(19/Jan/15 10:32 AM)




URL:


https://github.com/jenkinsci/support-core-plugin/pull/20



























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







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

[JIRA] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label

2015-01-19 Thread bockelm...@dkrz.de (JIRA)















































hbockelmann
 commented on  JENKINS-23459


Cannot restrict a matrix build job to one node/label















I do agree that there are at least two solutions for this problem

	NodeLabel parameter plugin with only one option/slave to be chosen
	add slave axis with only one slave
but both add additional complexity for maintaining the matrix job. The advanced option "Restrict where this project can be run" should IMHO do exactly this.





























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







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

[JIRA] [multijob-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in

2015-01-19 Thread karl.th...@signavio.com (JIRA)















































Karl Theil
 commented on  JENKINS-26318


Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in















i have same issue. do you have any svn shell commands in your job? i do "svn revert . --recursive" from command line because "svn revert before update" from subversion plugin takes too long (30 mins).



























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins















































Jerry Cai
 commented on  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins















Actually , It has already running two days After I set up the instance , Meanwhile , When I click "Check Now" on Advance Tab manually , If the page is English language , It will display "Checking Updates..." and page for loading for a long time , but back to "Available" Tab , It still empty there , Do you mean it should load local metadata after backend fetching success ?



























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







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

[JIRA] [locale-plugin] (JENKINS-26437) Display problem in localization dialog













































 
Harald Albers
 edited a comment on  JENKINS-26437


Display problem in localization dialog
















see https://github.com/jenkinsci/jenkins/pull/1310



























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins













































 
Jerry Cai
 edited a comment on  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins
















Actually , It has already run two days After I set up the instance , Meanwhile , When I click "Check Now" on Advance Tab manually , If the page is English language , It will display "Checking Updates..." and page for loading for a long time , but back to "Available" Tab , It still empty there , Do you mean it should load local metadata after backend fetching success ?



























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins













































 
Jerry Cai
 edited a comment on  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins
















Actually , It has already run two days After I set up the instance , Meanwhile , When I click "Check Now" on Advance Tab manually , If the page is English language , It will display "Checking Updates..." and page is loading for a long time , but back to "Available" Tab , It still empty there , Do you mean it should load local metadata after backend fetching success ?



























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







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

[JIRA] [test-results-analyzer-plugin] (JENKINS-26342) Items in report doesn't expand if name contains some characters

2015-01-19 Thread mr.varun.me...@gmail.com (JIRA)
















































Varun Menon
 resolved  JENKINS-26342 as Fixed


Items in report doesnt expand if name contains some characters
















fixed in 0.2.0 version





Change By:


Varun Menon
(19/Jan/15 11:38 AM)




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/d/optout.

[JIRA] [subversion-plugin] (JENKINS-26443) Checkout to root directory deletes ALL files in the directory

2015-01-19 Thread david.tad...@seebyte.com (JIRA)















































Dave Taddei
 commented on  JENKINS-26443


Checkout to root directory deletes ALL files in the directory















Further update, the following combination works:

1.  Workspace cleanup plugin configured to exclude files and directories matching the pattern .svn/**
2.  Subversion plugin configured to do "svn update as much as possible" OR "svn update as much as possible with svn revert before update"

Using the fresh checkout mode deletes everything in the target directory.

Correct me if I am wrong but the mode "svn update as much as possible" still has the possibility of deleting the entire Jenkins workspace contents if the plugin decided it needed to do so.  I guess the recommended practice should be to always checkout to a specific directory within the Jenkins workspace rather than the workspace root?



























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







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

[JIRA] [support-core-plugin] (JENKINS-26483) Record JVM architecture

2015-01-19 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 started work on  JENKINS-26483


Record JVM architecture
















Change By:


Steven Christou
(19/Jan/15 10:32 AM)




Status:


Open
InProgress



























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







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

[JIRA] [core] (JENKINS-26480) The /jenkins/pluginManager/available can't list plugins

2015-01-19 Thread bochenski.kuba+jenk...@gmail.com (JIRA)













































 
Jerry Cai
 updated  JENKINS-26480


The /jenkins/pluginManager/available cant list plugins
















Hey , Guys , This is a critical bug , It can't work at all !



























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







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

[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion















































Jakub Bochenski
 updated  JENKINS-26472


Jenkins maven-project plugin doesnt support reactor module exclusion
















Change By:


Jakub Bochenski
(19/Jan/15 11:32 AM)




Environment:


Jenkinsver.1.540
maven-projectver.2.8



























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







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

[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

2015-01-19 Thread eelam.raga...@gmail.com (JIRA)















































ragavan Ambighananthan
 commented on  JENKINS-25583


Unexpected error in launching a slave. This is probably a bug in Jenkins.















thanks @darkrift



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















I just created a pull request here that provides the functionality Julien R requests: https://github.com/jenkinsci/docker-build-publish-plugin/pull/6



























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







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

[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly

2015-01-19 Thread russku...@3d-p.com (JIRA)

russ k
commented on JENKINS-24544

GIT revisions list empty while GIT tags list populated correctly

Can you try whether upgrading to 0.4.0 solves your problem or not?

I upgraded and it still gives the same error.

Otherwise would it be possible give the URL where your experience this problem.

This is a private intranet site so giving access is not possible, sorry!

Or you could checkout the git-parameter plugin, add lines like

I see the plugin crashing at `generateContents(GitParameterDefinition.java:333)` so those debugging lines would never be called. I get an error:

Caused by: hudson.plugins.git.GitException: Command "git rev-list my-project" returned status code 128:
stdout:
stderr: fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git command revision... file...'

When I go to my projects git folder and run the same command I get the exact same error. However running --all works:

my-project$ git rev-list --all
6e70eaabb2fe1d087158013ec0802ec4b4841d88
b59ea24a5bac309ad20c8853385f022857cc2da0
dc704b7aab8c707a78d972bbcf2b5eee43d58b0a
17d90081f96155946ed32dc9329aded72b900167
b98aa3a1a3e2831e48a5889d47e6cd9b49684d06
b7ef4dff66c390dc4f0047af8d240b782210f80a

my-project$ git rev-list my-project
fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree.

Now the git functionality is included by the gitclient plugin. I hesitate to touch that plugin as many others use it as well.

[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly

2015-01-19 Thread russku...@3d-p.com (JIRA)

russ k
edited a comment on JENKINS-24544

GIT revisions list empty while GIT tags list populated correctly

Can you try whether upgrading to 0.4.0 solves your problem or not?

I upgraded and it still gives the same error.

Otherwise would it be possible give the URL where your experience this problem.

This is a private intranet site so giving access is not possible, sorry!

Or you could checkout the git-parameter plugin, add lines like

I see the plugin crashing at `generateContents(GitParameterDefinition.java:333)` so those debugging lines would never be called. I get an error:

When I go to my projects git folder and run the same command I get the exact same error. However running --all works:

my-project$ git rev-list my-project
fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree.

Now the git functionality is included by the gitclient plugin. I hesitate to touch that plugin as many other plugins use it as well.

[JIRA] [multijob-plugin] (JENKINS-26492) Need Unstable option to be added to the dropdown list of Continuation condition to next phase when jobs' statuses are

2015-01-19 Thread jackyang...@gmail.com (JIRA)















































Jack Yang
 created  JENKINS-26492


Need Unstable option to be added to the dropdown list of Continuation condition to next phase  when jobs statuses are















Issue Type:


New Feature



Assignee:


Unassigned


Components:


multijob-plugin



Created:


19/Jan/15 4:42 PM



Description:


up to multijob plugin version 1.16, there are only 5 options for "Continuation condition to next phase when jobs' statuses are". I would like to request adding a new option: "unstable". It would be great to have this option when the next job is configured to be triggered only the previous job result is unstable.

One of the current options: "Stable or Unstable but not Failed" is overlapped with "Successful". I mean the "Successful" is considered as "Stable" as well.

I looked at the source v1.16: it should be a very simple solution, just adding the following piece of code to MultiJobBuilder.java, it will solve my problem.

//Begin
UNSTABLE("Unstable") {
@Override
public boolean isContinue(Result result) {
return result.equals(Result.UNSTABLE);
}
},
//End





Project:


Jenkins



Labels:


jenkins




Priority:


Major



Reporter:


Jack Yang

























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







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

[JIRA] [core] (JENKINS-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}

2015-01-19 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-23273


RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}















Tommy's point about only chown'ing files that are in the RPM seems like a bright idea to me. 

None of the files in /var/lib/jenkins are created during installation (for some reason, the plugins/ folder gets created, but nothing else).

only attempting any sort of chown if the JENKINS_USER is not "jenkins" also makes a lot of sense, and would be easier to implement.

Breaks on any system where the user used to be custom but was reset to jenkins later. I don't see any benefit either.



























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







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

[JIRA] [xcode-plugin] (JENKINS-26368) Technical Version / Marketing Version Not Updating

2015-01-19 Thread parke...@gmail.com (JIRA)













































 
James Parker
 edited a comment on  JENKINS-26368


Technical Version / Marketing Version Not Updating
















I'm trying to figure this out, but still not sure how to fix the problem. I've tried updating cocoa pods and install xcodeproj, still not getting anywhere. 



























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







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

[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED















































Torben Knerr
 commented on  JENKINS-10406


Maven Jobs with build modules in parallel always ABORTED















Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds



























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







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

[JIRA] [core] (JENKINS-10540) Maven build aborted without cause















































Torben Knerr
 commented on  JENKINS-10540


Maven build aborted without cause















Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds.

@sniglom @slash @taeric @sraf did you ever find a suitable workaround?



























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







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

[JIRA] [core] (JENKINS-10540) Maven build aborted without cause













































 
Torben Knerr
 edited a comment on  JENKINS-10540


Maven build aborted without cause
















Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds.

Adam H Bernhard Trummer Josh Berry S Raf did you ever find a suitable workaround?



























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







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

[JIRA] [ghprb-plugin] (JENKINS-26494) GhprbTrigger saves its descriptor every time it runs

2015-01-19 Thread ryan.campb...@gmail.com (JIRA)
















































recampbell
 resolved  JENKINS-26494 as Not A Defect


GhprbTrigger saves its descriptor every time it runs
















Change By:


recampbell
(19/Jan/15 7:24 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [ghprb-plugin] (JENKINS-26494) GhprbTrigger saves its descriptor every time it runs

2015-01-19 Thread ryan.campb...@gmail.com (JIRA)















































recampbell
 commented on  JENKINS-26494


GhprbTrigger saves its descriptor every time it runs















OK, I see the reason for the save(). It seems as though all pull requests are serialized by job in a giant hashtable which is stored in org.jenkinsci.plugins.ghprb.GhprbTrigger.xml. It seems unnecessary to store state which is already stored externally, but perhaps this is a design decision which is too deeply baked in.

So perhaps the fault/fix is in jobConfigHistory plugin and it's duplicate history detection.

One can work around the issue by adding GhprbTrigger to the pattern's in the jobConfigHistory's "System configuration exclude file pattern" in the Advanced area of the Job Config History plugin.

I'll close this as I suppose it's hard to argue that this is actually a defect in this 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/d/optout.

[JIRA] [core] (JENKINS-10540) Maven build aborted without cause

2015-01-19 Thread tae...@gmail.com (JIRA)















































Josh Berry
 commented on  JENKINS-10540


Maven build aborted without cause















For us, as annoying as it felt, simply giving up on the parallel option worked.  



























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







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

[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED















































Torben Knerr
 commented on  JENKINS-10406


Maven Jobs with build modules in parallel always ABORTED















Bob Tiernay did you find a workaround in the meantime?



























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







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

[JIRA] [subversion-plugin] (JENKINS-26264) NPE from SubversionSCM.checkout

2015-01-19 Thread repkov.de...@gmail.com (JIRA)















































Repkov Denis
 stopped work on  JENKINS-26264


NPE from SubversionSCM.checkout
















Change By:


Repkov Denis
(19/Jan/15 7:38 PM)




Status:


InProgress
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/d/optout.

[JIRA] [subversion-plugin] (JENKINS-26264) NPE from SubversionSCM.checkout

2015-01-19 Thread repkov.de...@gmail.com (JIRA)















































Repkov Denis
 commented on  JENKINS-26264


NPE from SubversionSCM.checkout















Pull request created, issue should be corrected now.



























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







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

[JIRA] [core] (JENKINS-24752) NodeProvisioner algorithm is suboptimal for fast one-off cloud

2015-01-19 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-24752


NodeProvisioner algorithm is suboptimal for fast one-off cloud















Is it resolved now?



























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







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

[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames

2015-01-19 Thread jared.b...@bolderthinking.com (JIRA)















































Jared Biel
 created  JENKINS-26493


Use new EC2 API endpoint hostnames















Issue Type:


Improvement



Assignee:


Francis Upton



Components:


ec2-plugin



Created:


19/Jan/15 6:00 PM



Description:


The EC2 plugin is currently throwing the following error while trying to launch a build slave:


Jan 19, 2015 5:55:48 PM hudson.plugins.ec2.EC2Cloud provision
WARNING: Failed to count the # of live instances on EC2
com.amazonaws.AmazonClientException: Unable to execute HTTP request: eu-central-1.ec2.amazonaws.com: Name or service not known


Performing a resolve directly against the SOA nameservers results in no answer:


dig eu-central-1.ec2.amazonaws.com @r1.amazonaws.com

;  DiG 9.9.2-P2  eu-central-1.ec2.amazonaws.com @r1.amazonaws.com
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 33907
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;eu-central-1.ec2.amazonaws.com.	IN	A

;; AUTHORITY SECTION:
ec2.amazonaws.com.	907	IN	NS	ns-911.amazon.com.
ec2.amazonaws.com.	907	IN	NS	ns-912.amazon.com.
ec2.amazonaws.com.	907	IN	NS	ns-921.amazon.com.
ec2.amazonaws.com.	907	IN	NS	ns-923.amazon.com.
ec2.amazonaws.com.	907	IN	NS	ns-941.amazon.com.
ec2.amazonaws.com.	907	IN	NS	ns-942.amazon.com.

;; Query time: 25 msec
;; SERVER: 205.251.192.27#53(205.251.192.27)
;; WHEN: Mon Jan 19 17:57:13 2015
;; MSG SIZE  rcvd: 192


The AWS API docs specify EC2 hostnames like the following:


...
ec2.eu-central-1.amazonaws.com
...


So, the "ec2" and "eu-central-1" portions are flipped. I recommend that the API endpoints are updated to use the hostnames that are currently outlined in the API docs.




Environment:


jenkins: 1.597

ec2-plugin: 1.24




Project:


Jenkins



Priority:


Blocker



Reporter:


Jared Biel

























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







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

[JIRA] [xcode-plugin] (JENKINS-26368) Technical Version / Marketing Version Not Updating

2015-01-19 Thread parke...@gmail.com (JIRA)















































James Parker
 commented on  JENKINS-26368


Technical Version / Marketing Version Not Updating















I'm trying to figure this out, but still not sure how to fix the problem. 



























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







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

[JIRA] [ghprb-plugin] (JENKINS-26494) GhprbTrigger saves its descriptor every time it runs

2015-01-19 Thread ryan.campb...@gmail.com (JIRA)















































recampbell
 created  JENKINS-26494


GhprbTrigger saves its descriptor every time it runs















Issue Type:


Bug



Assignee:


Honza Brázdil



Components:


ghprb-plugin



Created:


19/Jan/15 6:35 PM



Description:


The GhprbTrigger saves the descriptor every time it runs:

@Override
public void run() {
// triggers are always triggered on the cron, but we just no-op if we are using GitHub hooks.
if (getUseGitHubHooks()) {
return;
}
helper.run();
getDescriptor().save();
}

This results in the Jenkins config.xml being saved every time the trigger runs, which is especially bad if you are using the configHistory plugin.


"jenkins.util.Timer [#2]" daemon prio=10 tid=0x7f61a4002800 nid=0x2dad runnable [0x7f61d1185000]
java.lang.Thread.State: RUNNABLE
   at java.util.TimSort.sort(Unknown Source)
   at java.util.TimSort.sort(Unknown Source)
   at java.util.Arrays.sort(Unknown Source)
   at java.util.Collections.sort(Unknown Source)
   at hudson.plugins.jobConfigHistory.FileHistoryDao.hasDuplicateHistory(FileHistoryDao.java:540)
   at hudson.plugins.jobConfigHistory.FileHistoryDao.checkDuplicate(FileHistoryDao.java:560)
   at hudson.plugins.jobConfigHistory.FileHistoryDao.saveItem(FileHistoryDao.java:240)
   at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:29)
   at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:80)
   at hudson.model.Descriptor.save(Descriptor.java:760)
   - locked 0x9109dfa0 (a org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl)
   at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:182)


Looking at the serializable fields in the descriptor, I don't see any reason why this would require being saved every time the trigger runs. Even if there is a good reason, that should be fixed to avoid this sort of behavior.




Project:


Jenkins



Labels:


performance




Priority:


Major



Reporter:


recampbell

























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















There are two related StackOverflow posts:
http://stackoverflow.com/questions/21928780/create-multiple-tag-docker-image
http://stackoverflow.com/questions/22080706/how-to-create-named-and-latest-tag-in-docker



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















I think I know how to solve this now. You use build the image. Then you get a hash back. Then you tag the hash. Then you push the hash. If you push either of the tags, it only pushes that tag into the local registry.

The behavior of the local registry seems to be different to DockerHub, it doesn't seem quite so involved there.



























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







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

[JIRA] [gitlab-hook-plugin] (JENKINS-24232) Hook fails on parametrized jobs















































SCM/JIRA link daemon
 commented on  JENKINS-24232


Hook fails on parametrized jobs















Code changed in jenkins
User: Vanja Radovanović
Path:
 models/api.rb
http://jenkins-ci.org/commit/gitlab-hook-plugin/81e2725fc901863fe3ed206f3ccda82d4e83329d
Log:
  Changelog:

	logging request details nicely, including payload
	error handling fix, exceptions converted to java RuntimeException, related to JENKINS-24232
	on error displaying stack trace as well































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







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

[JIRA] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly















































SCM/JIRA link daemon
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















Code changed in jenkins
User: Shawn McCarthy
Path:
 war/src/main/webapp/scripts/sortable.js
http://jenkins-ci.org/commit/jenkins/5abb0da9233ddc76c586c9d777c6d9d85999c203
Log:
  JENKINS-19634 Fix sorting percentages. Make sure  and  percentages besides 0 and 100 get calculated correctly.





























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







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

[JIRA] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly















































SCM/JIRA link daemon
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















Code changed in jenkins
User: Daniel Beck
Path:
 war/src/main/webapp/scripts/sortable.js
http://jenkins-ci.org/commit/jenkins/6852d75bd45560e70dfc73db3b2d1ecc2564a5af
Log:
  Merge pull request #1509 from smccarthy/JENKINS-19634

FIXED JENKINS-19634 Fix sorting percentages


Compare: https://github.com/jenkinsci/jenkins/compare/a4165a04dd5b...6852d75bd455




























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







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

[JIRA] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly















































SCM/JIRA link daemon
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















Code changed in jenkins
User: Shawn McCarthy
Path:
 war/src/main/webapp/scripts/sortable.js
http://jenkins-ci.org/commit/jenkins/c02c93543ad05a9a8fd1635ac716ec707be63184
Log:
  JENKINS-19634 Fix sorting percentages. Take care of 100% and 0%.





























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







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

[JIRA] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly















































SCM/JIRA link daemon
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















Code changed in jenkins
User: Shawn McCarthy
Path:
 war/src/main/webapp/scripts/sortable.js
http://jenkins-ci.org/commit/jenkins/d65227b4ec53abe159227b3e42c792530531ac9a
Log:
  JENKINS-19634 Fix sorting percentages





























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







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

[JIRA] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly
















































SCM/JIRA link daemon
 resolved  JENKINS-19634 as Fixed


Test Statistic Grid: not sorting by percentage correctly
















Change By:


SCM/JIRA link daemon
(19/Jan/15 9:39 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/d/optout.

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















I pulled the PR request, I can't get it to work.

I think the problem is when you push to Docker hub an image automatically gets marked as latest.

But the same does not seem to happen for a local / private registry.

However if I make an image with two tags, what actually happens is I end up with two images ... and I can only push one of them.

Comments / ideas are welcome. I have left my code up for now.



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images















































Mark Butler
 commented on  JENKINS-25689


Multiple tagging of docker images















Possibly related issue on Docker-Registry: https://github.com/docker/docker-registry/issues/637



























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







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

[JIRA] [gitlab-hook-plugin] (JENKINS-24403) Cannot create jobs for branches under ldap authentication

2015-01-19 Thread javi...@gmail.com (JIRA)















































Javier Palacios
 commented on  JENKINS-24403


Cannot create jobs for branches under ldap authentication















I have actually solved the issue, by adding the impersonate method from knuttinatoll. Now our anonymous user has only project read permission, and projects can be created with no problem.



























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







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

[JIRA] [subversion-plugin] (JENKINS-26264) NPE from SubversionSCM.checkout















































SCM/JIRA link daemon
 commented on  JENKINS-26264


NPE from SubversionSCM.checkout















Code changed in jenkins
User: Steven Christou
Path:
 src/main/java/hudson/scm/subversion/UpdateUpdater.java
http://jenkins-ci.org/commit/subversion-plugin/205ef51753008e84c96f32e36005b1c79c5f3c8f
Log:
  Merge pull request #106 from tastatur/master

FIXED JENKINS-26264 UpdateUpdater perform will throw an AbortException


Compare: https://github.com/jenkinsci/subversion-plugin/compare/a20e0479e2bd...205ef5175300




























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







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

[JIRA] [subversion-plugin] (JENKINS-26264) NPE from SubversionSCM.checkout