date:20141210















































Jesse Glick
 started work on  JENKINS-25898


Create acceptance tests based on tutorial
















Change By:


Jesse Glick
(10/Dec/14 4:29 PM)




Status:


Open
In Progress



























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







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

[JIRA] [matrix-auth-plugin] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used

2014-12-10 Thread emil.dr...@gmail.com (JIRA)















































Emil Dragu
 commented on  JENKINS-17764


'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used















I had the same problem, to workaround I used this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Token+Root+Plugin. Hope it helps.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master

2014-12-10 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-18088


Build flow execute on slave but write file on master















http://javadoc.jenkins-ci.org/hudson/FilePath.html



























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







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

[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build

2014-12-10 Thread wink...@dresearch-fe.de (JIRA)















































Peter Winkler
 commented on  JENKINS-25340


lost trend history after skipping build















Thanks for the information.
I've made an interesting detection. It seems that the complete history trend information is still there.
To be found at //lastCompletedBuild/testReport/history/countGraph/png?start=0&end=100".
(There I can see a history of 100 items although there was gaps in the history due to deleted builds.)
For the moment I can put this url in a img-html statement in the job description and have back the old trend graph.
That would means that the history graph shown by junit plugin isn't the same as before and it would be enough to change something in the junit plugin only.
Is that right?



























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







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

[JIRA] [maven-plugin] (JENKINS-19352) Maven logs no errors

2014-12-10 Thread eric-w...@rizzoweb.com (JIRA)















































Eric Rizzo
 commented on  JENKINS-19352


Maven logs no errors















Sorry if the answer is buried in all the comments and metadata (I've read through everything twice), but I can't determine if this fix is in any release of Jenkins other than the LTS 1.532.1 and later. Can anyone confirm precisely which releases I can get that include this fix?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-25340) lost trend history after skipping build















































Jesse Glick
 commented on  JENKINS-25340


lost trend history after skipping build















Of course the issue is in the JUnit 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] [chromedriver-plugin] (JENKINS-25911) ChromeDriver plugin 1.1 throws NPE since Jenkins 1.591 when polling SCM

2014-12-10 Thread chris.ra...@blueacorn.com (JIRA)















































Chris Rasys
 commented on  JENKINS-25911


ChromeDriver plugin 1.1 throws NPE since Jenkins 1.591 when polling SCM















Getting same issue in Jenkins 1.593. Disabling the chromedriver plugin does seem to be a viable workaround though.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [email-ext-plugin] (JENKINS-26005) "Run condition trigger" does not retain "Send To" information on Save/Apply

2014-12-10 Thread sl...@ganz.com (JIRA)















































slav dok
 created  JENKINS-26005


"Run condition trigger" does not retain "Send To" information on Save/Apply















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext-plugin



Created:


10/Dec/14 6:33 PM



Description:



	Create new "Freestyle Project"
	Choose "Editable Email Notification" from "Post-build Actions"
	Click "Advanced Settings..."
	Click "Add Trigger"
	Select "Run condition trigger"
	Click "Add" for "Send To" of "Run condition trigger"
	Choose "Recipient List" (or any other)
	Click "Advanced..." of "Run condition trigger"
	Select "Run Condition" (can leave at "Always")
	Click Jenkins "Save" or "Apply"
	Leave the page, and return to the same configuration



Expected result: 

	All configuration was saved, "send to" has a list of selected recipients.



Actual result:

	Most configuration was saved, "send to" list has been cleared.



Please note this only happens for "Run condition trigger". Other triggers save correctly




Environment:


Jenkins ver: 1.565.3	

Email Extension Plugin: 2.39




Project:


Jenkins



Labels:


plugin
email-ext




Priority:


Minor



Reporter:


slav dok

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [xfpanel-plugin] (JENKINS-26006) Can't change background color

2014-12-10 Thread bteixe...@rocket-internet.pt (JIRA)















































Bruno Teixeira
 created  JENKINS-26006


Can't change background color















Issue Type:


Bug



Assignee:


Julien RENAUT



Attachments:


gHA5P.jpg, iSMHS.jpg



Components:


xfpanel-plugin



Created:


10/Dec/14 6:34 PM



Description:


I use the extreme feedback panel for some time now, and all time time i was able to change background colors for all kind of builds.

After the last update all colors were reset and i'm not able to do that anymore, also other configurations don't work anymore. 




Project:


Jenkins



Priority:


Minor



Reporter:


Bruno Teixeira

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-26007) Job dependent on SSH Plugin does not fail when the plugin is not installed

2014-12-10 Thread nmalino...@gmail.com (JIRA)















































Nathan Malinoski
 created  JENKINS-26007


Job dependent on SSH Plugin does not fail when the plugin is not installed















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 6:36 PM



Description:


I have a job that utilizes the SSH and SSH Credentials plugins. The job is configured to use "Execute shell script on remote host using ssh", with "Pre build script" configured execute a backup script. These jobs had been running successfully from at least mid-July.

At some point at the beginning of November (I only caught this today; a month later), the SSH plugin was uninstalled from this Jenkins instance; however, these scheduled backup jobs continued to run, reporting as successful. The console output had an SSH Agent connect, then disconnect, and the job was marked as successful. No errors, no warnings, no notifications.

I'm not sure how feasible it is, but I believe Jenkins should [at least have the option to] check each job before running to ensure that it has all of the required Jenkins plugins, and, if it doesn't, fail the build, thus sending notification emails so responsible parties can fix it.



Plugins: Active Directory Plugin 1.38, Credentials Plugin 1.18, Deploy to container Plugin 1.10, Javadoc Plugin 1.2, JUnit Plugin 1.2-beta-3, Mailer 1.11, MapDB API Plugin 1.0.6.0, Matrix Authorization Strategy Plugin 1.2, Matrix Project Plugin 1.4, Maven Project Plugin 2.7.1, OWASP Markup Formatter Plugin 1.3, PAM Authentication plugin 1.2, Parameterized Trigger plugin 2.25, SCM API Plugin 0.2, SSH Agent Plugin 1.5, SSH Credentials Plugin 1.10, SSH plugin 2.4, SSH Slaves plugin 1.9, Subversion Plugin 2.4.4, Translation Assistance plugin 1.12, Windows Slaves Plugin 1.0




Environment:


Jenkins 1.588 (Standalone from pkg.jenkinsci.org repo)

Red Hat Enterprise Linux 6.6




Project:


Jenkins



Priority:


Major



Reporter:


Nathan Malinoski

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state

2014-12-10 Thread tianyuyang...@yahoo.com (JIRA)













































  
Tony Yang
 edited a comment on  JENKINS-25742


Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
















Hi Daniel,

We reproduced this in the latest weekly release Jenkins ver. 1.590

Here is the thread deadlock stack trace we captured through jConsole for the pair of threads that got into deadlock




Name: Handling POST /jenkins/view/deadlock1/configSubmit from 10.72.120.119 : qtp1955915048-52
State: BLOCKED on hudson.model.Hudson@7e3b42ad owned by: Handling POST /jenkins/job/aaa_test2/doRename from 10.73.211.174 : qtp1955915048-45
Total blocked: 1  Total waited: 14

Stack trace: 
jenkins.model.Jenkins.save(Jenkins.java:2756)
hudson.model.View.save(View.java:333)
hudson.model.View.doConfigSubmit(View.java:959)

	locked hudson.model.ListView@1a6186c3
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:483)
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
org.kohsuke.stapler.Stapler.service(Stapler.java:238)
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:114)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
org.eclipse.jetty.servlet.ServletHand

[JIRA] [email-ext-plugin] (JENKINS-26005) "Run condition trigger" does not retain "Send To" information on Save/Apply

2014-12-10 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26005


"Run condition trigger" does not retain "Send To" information on Save/Apply















The "run condition trigger" is not part of the email-ext plugin. It is part of the run-condition-extras 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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state

2014-12-10 Thread tianyuyang...@yahoo.com (JIRA)













































  
Tony Yang
 edited a comment on  JENKINS-25742


Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
















Hi Daniel,

We reproduced this in the latest weekly release Jenkins ver. 1.590

Here is the thread deadlock stack trace we captured through jConsole for the pair of threads that got into deadlock


Name: Handling POST /jenkins/view/deadlock1/configSubmit from 10.72.120.119 : qtp1955915048-52
State: BLOCKED on hudson.model.Hudson@7e3b42ad owned by: Handling POST /jenkins/job/aaa_test2/doRename from 10.73.211.174 : qtp1955915048-45
Total blocked: 1  Total waited: 14

Stack trace: 
jenkins.model.Jenkins.save(Jenkins.java:2756)
hudson.model.View.save(View.java:333)
hudson.model.View.doConfigSubmit(View.java:959)
   - locked hudson.model.ListView@1a6186c3
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:483)
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
org.kohsuke.stapler.Stapler.service(Stapler.java:238)
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:114)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
org.eclipse.jetty.servlet.ServletHan

[JIRA] [run-condition-extras-plugin] (JENKINS-26005) "Run condition trigger" does not retain "Send To" information on Save/Apply

2014-12-10 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 updated  JENKINS-26005


"Run condition trigger" does not retain "Send To" information on Save/Apply
















Change By:


Alex Earl
(10/Dec/14 6:45 PM)




Assignee:


Alex Earl
Oleg Nenashev





Component/s:


run-condition-extras-plugin





Component/s:


email-ext-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-26008) Use of compression during copying of artifacts cut throughput by a factor of 3

2014-12-10 Thread ca...@clearcore.com (JIRA)

Carl George
created JENKINS-26008

Use of compression during copying of artifacts cut throughput by a factor of 3

Issue Type:

Improvement

Assignee:

Unassigned

Components:

core

Created:

10/Dec/14 7:26 PM

Description:

We have 19GB of tarballs and isos that are built on a Linux slave. The pulling of artifacts to the master takes 33 minutes over a local network. I modified the Jenkins source to not use compression and reran the job; the job took 9 minutes. This mirrors what happens if you use tar and ssh from the command line with the same machines.

My method of test was to have a job in Jenkins that only archived the artifacts. I pre-populated the workspace with the data that I wanted archived.

To turn of compression I modified the function copyRecursiveTo in FilePath.java (core/src/main/hudson). I change the 4 lines in that function that referenced TarCompression.GZIP to TarCompression.NONE for my test.

I don't suggest just simply changing the TarCompression to NONE but to make it configurable. It should be configurable due to slaves running over the internet, remotely, or in the cloud, etc where compression may be desirable.

As a note if I tar up the same data with compression and pipe it to ssh and untar it on the destination it takes 19 minutes. Doing the same thing without compression it takes 5 minutes.

Environment:

Jenkins 1.565

jdk-1.7.0_67 (master and slave)

Custom Linux running 3.10.59 64 bit (master and slave)

Project:

Jenkins

Labels:

slave
linux
performance
artifacts
archiving

Priority:

Minor

Reporter:

Carl George

[JIRA] [parameterized-trigger-plugin] (JENKINS-26009) Triggering Workflow using parameterized-trigger-plugin

2014-12-10 Thread a...@rbauction.com (JIRA)















































Andrew Lin
 created  JENKINS-26009


Triggering Workflow using parameterized-trigger-plugin















Issue Type:


Bug



Assignee:


huybrechts



Components:


parameterized-trigger-plugin



Created:


10/Dec/14 7:29 PM



Description:


Can not trigger workflow from  Parameterized Trigger plugin

Error:
"X is not buildable"




Environment:


Jenkins: 1.591

Parameterized Trigger plugin: 2.25




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Lin

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot

2014-12-10 Thread oldel...@java.net (JIRA)















































Richard Mortimer
 commented on  JENKINS-24155


Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot















Relevant bits from the thread dump.

NioChannelHub (and a few other things not included for compactness) are waiting on Channel@2323a3cd


NioChannelHub keys=4 gen=5352736: Computer.threadPoolForRemoting [#2]
 
"NioChannelHub keys=4 gen=5352736: Computer.threadPoolForRemoting [#2]" Id=144 Group=main BLOCKED on hudson.remoting.Channel@2d23a3cd owned by "Finalizer" Id=3
at hudson.remoting.Channel.terminate(Channel.java:804)
-  blocked on hudson.remoting.Channel@2d23a3cd
at hudson.remoting.Channel$2.terminate(Channel.java:491)
at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72)
at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:211)
at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:631)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
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)
 
Number of locked synchronizers = 1
- java.util.concurrent.ThreadPoolExecutor$Worker@1b9eef5


this is held by the Finalizer that is waiting on FifoBuffer@782372ec


Finalizer
 
"Finalizer" Id=3 Group=system WAITING on org.jenkinsci.remoting.nio.FifoBuffer@782372ec
at java.lang.Object.wait(Native Method)
-  waiting on org.jenkinsci.remoting.nio.FifoBuffer@782372ec
at java.lang.Object.wait(Object.java:503)
at org.jenkinsci.remoting.nio.FifoBuffer.write(FifoBuffer.java:336)
at org.jenkinsci.remoting.nio.FifoBuffer.write(FifoBuffer.java:324)
at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.writeBlock(NioChannelHub.java:222)
at hudson.remoting.AbstractByteArrayCommandTransport.write(AbstractByteArrayCommandTransport.java:83)
at hudson.remoting.Channel.send(Channel.java:553)
-  locked hudson.remoting.Channel@2d23a3cd
at hudson.remoting.RemoteInvocationHandler.finalize(RemoteInvocationHandler.java:240)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
at java.lang.ref.Finalizer.access$100(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)


It looks like the Finalizer is trying to write to a channel to cleanup an object with remote state and has effectively locked things up because nothing can come along and force the FifoBuffer write to terminate.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [delivery-pipeline-plugin] (JENKINS-25744) Change delivery-pipeline job property from using section to an optionalBlock
















































Patrik Boström
 closed  JENKINS-25744 as Fixed


Change delivery-pipeline job property from using section to an optionalBlock
















Released in 0.8.8





Change By:


Patrik Boström
(10/Dec/14 7:57 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-21291) Loading animation for first load of the view
















































Patrik Boström
 resolved  JENKINS-21291 as Fixed


Loading animation for first load of the view
















Change By:


Patrik Boström
(10/Dec/14 7:57 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-21291) Loading animation for first load of the view
















































Patrik Boström
 closed  JENKINS-21291 as Fixed


Loading animation for first load of the view
















Released in 0.8.8





Change By:


Patrik Boström
(10/Dec/14 7:57 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
















































Patrik Boström
 closed  JENKINS-25457 as Fixed


Server error when viewing pipeline with NOT_BUILT result job.
















Released in 0.8.8





Change By:


Patrik Boström
(10/Dec/14 7:56 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [workflow-plugin] (JENKINS-25898) Create acceptance tests based on tutorial
















































Jesse Glick
 resolved  JENKINS-25898 as Fixed


Create acceptance tests based on tutorial
















Change By:


Jesse Glick
(10/Dec/14 8:00 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [parameterized-trigger-plugin] (JENKINS-26009) Triggering Workflow using parameterized-trigger-plugin

2014-12-10 Thread a...@rbauction.com (JIRA)















































Andrew Lin
 updated  JENKINS-26009


Triggering Workflow using parameterized-trigger-plugin
















Change By:


Andrew Lin
(10/Dec/14 8:15 PM)




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] [github-plugin] (JENKINS-23995) Adding commit status context in github-plugin

2014-12-10 Thread crazy...@gmail.com (JIRA)















































Nelson Chen
 commented on  JENKINS-23995


Adding commit status context in github-plugin















Which is kinda weird since their examples feature a jenkins context.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20217) Too many PingThread's

2014-12-10 Thread sridharan.go...@libertymutual.com (JIRA)















































Jesse Glick
 commented on  JENKINS-20217


Too many PingThread's















-Dhudson.slaves.ChannelPinger.pingInterval=0 seems to be the 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] [hp-application-automation-tools-plugin] (JENKINS-25478) HTTPS to HP ALM PC















































Sridharan Gopal
 commented on  JENKINS-25478


HTTPS to HP ALM PC















I see this issue is categorized as a Minor issue. Is there a workaround for this? I am hoping the workaround isnt "Use HTTP".



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-3002) TFS Support to get labels

2014-12-10 Thread nelm...@gmail.com (JIRA)















































nelson jordan
 commented on  JENKINS-3002


TFS Support to get labels















Hi,  I've downloaded the 3.1.2-SNAPSHOT in an effort to pull in a specific label.  I've used VERSION_SPEC and CHECKOUT_INFO as parameters, but the plugin keeps pulling in the latest code.  Did anyone have any success with pulling code from a specific label.



























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







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

[JIRA] [google-login-plugin] (JENKINS-25994) Unable to log in via google login plugin

2014-12-10 Thread dzuc...@dlc-solutions.com (JIRA)















































Devin Zuczek
 commented on  JENKINS-25994


Unable to log in via google login plugin















I get this too, using a Google apps account. I'm using the same API credentials with Gitlab's OAuth so I know the setup on Google side is correct.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [google-login-plugin] (JENKINS-25994) Unable to log in via google login plugin

2014-12-10 Thread bubenk...@gmail.com (JIRA)
















































Anatoly Bubenkov
 resolved  JENKINS-25994 as Fixed


Unable to log in via google login plugin
















Actually i've found that it was because of the wrong configuration - i've put improper secret





Change By:


Anatoly Bubenkov
(10/Dec/14 10:03 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] [extensible-choice-parameter-plugin] (JENKINS-24274) New DB-based choice provider

2014-12-10 Thread m...@peopledesigned.com (JIRA)















































Mark Chance
 commented on  JENKINS-24274


New DB-based choice provider















Is this available anywhere?  I don't see such a fork on GitHub...
I'm trying to do a very similar thing, but even less ambitious - have my Groovy script read from a database (hard-coded table, column, etc.).  But it is not working due to class loader issues – i have a jar file with the sqlite driver in it, but I sure can't get it to be recognized by the Groovy...
import groovy.sql.Sql
//def jc = jenkins.getPluginManager().uberClassLoader;
def jc = this.getClass().getClassLoader()
def furl = new File("/vagrant/lib/sqlite-jdbc-3.8.7.jar").toURL()
jc.addURL(furl)
def cc = Class.forName('org.sqlite.JDBC', true, jc)
java.sql.DriverManager.registerDriver(cc.newInstance())
def props = new java.util.Properties()
def sql = new Sql(java.sql.DriverManager.getConnection('jdbc:sqlite:databasefile.sqlite', props))

Results in:
Failed to execute script
java.sql.SQLException: No suitable driver found for jdbc:sqlite:databasefile.sqlite
	at java.sql.DriverManager.getConnection(DriverManager.java:596)
	at java.sql.DriverManager.getConnection(DriverManager.java:187)
	at java_sql_DriverManager$getConnection.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
	at Script1.run(Script1.groovy:9)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extensible-choice-parameter-plugin] (JENKINS-24274) New DB-based choice provider

2014-12-10 Thread m...@peopledesigned.com (JIRA)













































  
Mark Chance
 edited a comment on  JENKINS-24274


New DB-based choice provider
















Is this available anywhere?  I don't see such a fork on GitHub...
I'm trying to do a very similar thing, but even less ambitious - have my Groovy script read from a database (hard-coded table, column, etc.).  But it is not working due to class loader issues – i have a jar file with the sqlite driver in it, but I sure can't get it to be recognized by the Groovy...
import groovy.sql.Sql
//def jc = jenkins.getPluginManager().uberClassLoader;
def jc = this.getClass().getClassLoader()
def furl = new File("/vagrant/lib/sqlite-jdbc-3.8.7.jar").toURL()
jc.addURL(furl)
def cc = Class.forName('org.sqlite.JDBC', true, jc)
java.sql.DriverManager.registerDriver(cc.newInstance())
def props = new java.util.Properties()
def sql = new Sql(java.sql.DriverManager.getConnection('jdbc:sqlite:databasefile.sqlite', props))

Results in:
Failed to execute script
java.sql.SQLException: No suitable driver found for jdbc:sqlite:databasefile.sqlite
	at java.sql.DriverManager.getConnection(DriverManager.java:596)
	at java.sql.DriverManager.getConnection(DriverManager.java:187)
	at java_sql_DriverManager$getConnection.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
	at Script1.run(Script1.groovy:9)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)

btw - you see in the commented out code, i tried using the class loader of the jenkins - unfortunately it wasn't a WebappClassLoader or NetworkClassLoader, so there didn't seem to be a way to add the jar file to it.



























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







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

[JIRA] [core] (JENKINS-25986) Cannot save jenkins job after updating it

2014-12-10 Thread de...@ikedam.jp (JIRA)















































ikedam
 updated  JENKINS-25986


Cannot save jenkins job after updating it
















Change By:


ikedam
(11/Dec/14 12:05 AM)




Assignee:


huybrechts





Component/s:


core





Component/s:


parameterized-trigger-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] [git-plugin] (JENKINS-25913) Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files

2014-12-10 Thread stu...@somepointinthefuture.co.nz (JIRA)















































Stuart Whelan
 commented on  JENKINS-25913


Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files















Also the ability to do a git clean -dff, and clean away sub-repos.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [svnmerge-plugin] (JENKINS-25769) "Rebase" build action cannot be triggered from Promoted Builds

2014-12-10 Thread hugues.cha...@gmail.com (JIRA)















































Hugues Chabot
 commented on  JENKINS-25769


"Rebase" build action cannot be triggered from Promoted Builds















Applying the fix for JENKINS-14725 (https://github.com/jenkinsci/svnmerge-plugin/pull/24) should fix 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] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
















































Oleg Nenashev
 resolved  JENKINS-25732 as Fixed


NPE Thrown when using the parameterize build with a 'Run Parameter'
















1.3.31 should resolve the issue.
// SCM Link bot seems to be dead





Change By:


Oleg Nenashev
(11/Dec/14 2:54 AM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names if ClientNameFormat substitution fails
















































Oleg Nenashev
 resolved  JENKINS-25559 as Fixed


Missing hash in client names if ClientNameFormat substitution fails
















1.3.31 should resolve the issue.
// SCM Link bot seems to be dead





Change By:


Oleg Nenashev
(11/Dec/14 2:55 AM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [perforce-plugin] (JENKINS-24401) Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
















































Oleg Nenashev
 resolved  JENKINS-24401 as Fixed


Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
















1.3.31 should resolve the issue.
// SCM Link bot seems to be dead





Change By:


Oleg Nenashev
(11/Dec/14 2:58 AM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [perforce-plugin] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration