www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4925) Freebsd1 svn client is 1.7, but Jenkins uses an earlier version of SVN to check out workspaces
Date Mon, 18 Jun 2012 17:13:42 GMT

    [ https://issues.apache.org/jira/browse/INFRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396043#comment-13396043
] 

Sebb commented on INFRA-4925:
-----------------------------

Ran JMeter adhoc on freebsd1. [1]
This worked OK, but it did not update the workspace and did not exercise the Jenkins SVN client
code.

So I deleted the workspace and re-ran the job.
The workspace was checked out OK, but the svnCheck task failed as before [2]

[1] https://builds.apache.org/view/G-L/view/JMeter/job/JMeter%20adhoc/16/console
[2] https://builds.apache.org/view/G-L/view/JMeter/job/JMeter%20adhoc/17/console

===

BTW, the client on ubuntu2 is

+ svn --version
svn, version 1.6.6 (r40053)
   compiled Jun  5 2011, 14:51:47

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
                
> Freebsd1 svn client is 1.7, but Jenkins uses an earlier version of SVN to check out workspaces
> ----------------------------------------------------------------------------------------------
>
>                 Key: INFRA-4925
>                 URL: https://issues.apache.org/jira/browse/INFRA-4925
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jenkins
>            Reporter: Sebb
>
> Jenkins on freebsd1 uses what appears to be SVN 1.5 to check out workspaces.
> However, the installed SVN client which is found on the default PATH is SVN 1.7.
> This causes problems when Ant or Maven needs to access SVN versions

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

        

Mime
View raw message