[JIRA] [promoted-builds-plugin] (JENKINS-31901) Promoted builds now clean workspace before running.

2015-12-04 Thread jbeeck...@compliancesystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Beeckman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31901 
 
 
 
  Promoted builds now clean workspace before running.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 04/Dec/15 2:08 PM 
 
 
 

Environment:
 

 Jenkins 1.639  Promoted Builds Plugin 2.24 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Jay Beeckman 
 
 
 
 
 
 
 
 
 
 
In 2.23.1, and as far back as I can think, the workspace was never cleaned during a promotion. Starting with 2.24, when a promotion is run, it looks like it does the subversion clean before running the promotion scripts. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
   

[JIRA] [powershell-plugin] (JENKINS-31069) Error after 1.3 Powershell Plugin Update

2015-10-20 Thread jbeeck...@compliancesystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Beeckman updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31069 
 
 
 
  Error after 1.3 Powershell Plugin Update  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jay Beeckman 
 
 
 
 
 
 
 
 
 
 [XInstaller] $ powershell.exe -NonInteractive -ExecutionPolicy ByPass "& 'C:\Users\Builder\AppData\Local\Temp\hudson506960763024489469.ps1'"Missing _expression_ after unary operator '-'.At line:1 char:2+ -E  xecutionPolicy ByPass & 'x\hudson506960763024489469.ps1'Reverted to the 1.2 plugin and it works fine. Also should note...  The script ran fine before the update, it has not changed, and for giggles, I ran it manually on the server and it was ok.  I don't think there is anything in the script that could be causing the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [powershell-plugin] (JENKINS-31069) Error after 1.3 Powershell Plugin Update

2015-10-20 Thread jbeeck...@compliancesystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Beeckman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31069 
 
 
 
  Error after 1.3 Powershell Plugin Update  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 powershell-plugin 
 
 
 

Created:
 

 20/Oct/15 6:50 PM 
 
 
 

Environment:
 

 Jenkins 1.6.3.4 on Windows Server, various versions. 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Jay Beeckman 
 
 
 
 
 
 
 
 
 
 
[XInstaller] $ powershell.exe -NonInteractive -ExecutionPolicy ByPass "& 'C:\Users\Builder\AppData\Local\Temp\hudson506960763024489469.ps1'" Missing _expression_ after unary operator '-'. At line:1 char:2 + -E  xecutionPolicy ByPass & 'x\hudson50 6960763024489469.ps1' 
Reverted to the 1.2 plugin and it works fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

[JIRA] [core] (JENKINS-30899) Build History order not sorted properly

2015-10-19 Thread jbeeck...@compliancesystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Beeckman commented on  JENKINS-30899 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build History order not sorted properly  
 
 
 
 
 
 
 
 
 
 
This fix has worked for us. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-environment-plugin] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

2015-10-12 Thread jbeeck...@compliancesystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Beeckman commented on  JENKINS-22088 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder  
 
 
 
 
 
 
 
 
 
 
Same here on 1.627 on Windows 2008 R2 64 Bit. I'm going to manually clear it out, but this should be fixed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page

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














































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
 commented 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.  



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account

2014-08-28 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 commented on  JENKINS-14847


Apply button not taken into account















Any update on this?  I'd even settle for a 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] [scm-sync-configuration] (JENKINS-22573) SCM Sync Stops working

2014-04-10 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 created  JENKINS-22573


SCM Sync Stops working















Issue Type:


Bug



Affects Versions:


current



Assignee:


Frédéric Camblor



Components:


scm-sync-configuration



Created:


10/Apr/14 5:21 PM



Description:


I think it's related to JENKINS-22199, but the SCM Sync stopped working.  Says ERROR and when you click details, it gives the following stack trace:

Passing user name builder and password you entered
FAILED: svn: E175002: OPTIONS x failed
org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/QA/Jenkins failed
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)
	at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:2285)
	at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:2230)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at com.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja

[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion

2014-03-14 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 commented on  JENKINS-22199


Jenkins throwing errors in SCM Polling and Updates with Subversion















Current versions are:
Jenkins: v1.554
Subversion Plugin:  2.2, upgraded from 2.0 I think.

Not sure of the previous version of Jenkins, we keep it pretty up to date though.  I'd say it never is more than a month back on updates.  Not sure if it helps, but the credential stuff may be a factor as well, that is:
Credentials Plugin:  1.10



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion

2014-03-14 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 created  JENKINS-22199


Jenkins throwing errors in SCM Polling and Updates with Subversion















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


14/Mar/14 4:24 PM



Description:


After an update maybe 2-4 weeks ago, we get the following error in the polling and when a job runs and it goes to get the code from SVN.  Most of the time, if you manually force the job to run, it works.

Here is the stack of the error:

hudson.util.IOException2: revision check failed on https://csqaw2k832.compliancesystems.com/svn/QA/Release/PXDev/SimplicityHELOCWorkflow.FXL
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189)
	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132)
	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:738)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:899)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
	at hudson.model.Run.execute(Run.java:1676)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/QA/!svn/bc/32712/Release/PXDev/SimplicityHELOCWorkflow.FXL failed
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:324)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:995)
	at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1035)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872)
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177)
	... 11 more
Caused by: svn: E175002: REPORT /svn/QA/!svn/bc/32712/Release/PXDev/SimplicityHELOCWorkflow.FXL failed
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
	... 27 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -8
	at java.lang.String.substring(Unknown Source)
	at java.lang.String.substring(Unknown Source)
	at hudson.scm.DirAwareSVNXMLLogHandler.handleLogEntry(DirAwareSVNXMLLogHandler.java:90)
	at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:167)
	at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:164)
	at org.tmatesoft.svn.core.wc2.SvnReceivingOperation.receive(SvnReceivingOperation.java:78)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.handleLogEntry(SvnRemoteLog.java:199)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository$1.handleLogEntry(DAVRepository.java:950)

[JIRA] (JENKINS-13790) Subversion externals fail

2012-06-29 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 commented on  JENKINS-13790


Subversion externals fail















Can we get an update on this?  It has twice caused me to load the plugin, upgrade my workspaces, and have to revert them back because it doesn't work properly.



























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






[JIRA] (JENKINS-13771) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.

2012-06-27 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 reopened  JENKINS-13771


Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.
















This is still not working correctly with File Externals.  Can you please test with the triggering with both folder externals to a remote repository and file externals within the same repository.





Change By:


Jay Beeckman
(27/Jun/12 12:38 PM)




Resolution:


Fixed





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






[JIRA] (JENKINS-13790) Subversion externals fail

2012-06-20 Thread jbeeck...@compliancesystems.com (JIRA)














































Jay Beeckman
 commented on  JENKINS-13790


Subversion externals fail















It is also not triggering a build when an external changes.



























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






[JIRA] (JENKINS-13771) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.

2012-05-14 Thread jbeeck...@compliancesystems.com (JIRA)
Jay Beeckman created JENKINS-13771:
--

 Summary: Jenkins not being triggered on a change to an external 
with new 1.4 SVN plugin.
 Key: JENKINS-13771
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13771
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Windows Server 2008, 32 bit.
Reporter: Jay Beeckman
Priority: Blocker


Previously, external commits would trigger a build.  This is no longer working 
after the 1.4 update to the Subversion Plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

2012-04-18 Thread jbeeck...@compliancesystems.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161739#comment-161739
 ] 

Jay Beeckman commented on JENKINS-11381:


Jan, I have considered trying to get the fix in myself.  If I wasn't so busy 
right now I would.  This is holding up a big integration we have done with our 
delivery process, so it's killing me, but not something I could do right away.  
I do like your suggestion of voting, more voices the better :-)

Jay

> Subversion Plugin does not support Subversion 1.7
> -
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
>  Issue Type: Improvement
>  Components: subversion
>Reporter: soundworker
>Priority: Blocker
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

2012-04-09 Thread jbeeck...@compliancesystems.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161388#comment-161388
 ] 

Jay Beeckman commented on JENKINS-11381:


This is according to SVNKit's web page (http://svnkit.com/download.php):

"Lastest stable version of SVNKit (1.3.7) is not compatible with Subversion 1.7 
working copy format. However, SVNKit 1.7 is under development now and we plan 
to release it in 12th of April 2012. We plan to publish first Release Candidate 
build till the end of February 2012."

This is in three days, when could we reasonably expect this to be rolled into 
the plugin if they do indeed release on the 12th?

> Subversion Plugin does not support Subversion 1.7
> -
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
>  Issue Type: Improvement
>  Components: subversion
>Reporter: soundworker
>Priority: Blocker
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

2012-04-03 Thread jbeeck...@compliancesystems.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161188#comment-161188
 ] 

Jay Beeckman commented on JENKINS-11381:


Any update on this?  It appears that SVNKIT has updated their stuff?  An ETA 
would be great.

> Subversion Plugin does not support Subversion 1.7
> -
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
>  Issue Type: Improvement
>  Components: subversion
>Reporter: soundworker
>Priority: Blocker
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira