You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Lars Kotthoff (JIRA)" <ji...@apache.org> on 2008/08/08 07:58:46 UTC
[jira] Created: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Hudson builds do not have the SVN revision because svnversion is not available
------------------------------------------------------------------------------
Key: SOLR-684
URL: https://issues.apache.org/jira/browse/SOLR-684
Project: Solr
Issue Type: Task
Affects Versions: 1.3
Reporter: Lars Kotthoff
Priority: Trivial
The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627059#action_12627059 ]
Hoss Man commented on SOLR-684:
-------------------------------
r690357 should help us solve this problem ... i've made the corrisponding changes to the Hudson Solr-trunk config and manually kicked off a build.
if it works, i'll merge to the 1.3 branch.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627108#action_12627108 ]
Hoss Man commented on SOLR-684:
-------------------------------
bq. When you get something like 690356:690357M it's highly unlikely that this will help you to uniquely identify the "revision" as a whole or recreate it, which I think is the point of including it in the manifest.
True: but it will tell you that you *can't* recreate it purely from the repository. having the svnversion info is just an added bit of security blanket for people who later want a starting point to understand where the release came from -- when it's a single number, you have a good starting point. when it's mixed you have an ambiguous starting point, and when it's got an "M" all bets are off.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man reassigned SOLR-684:
-----------------------------
Assignee: Hoss Man
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627080#action_12627080 ]
Lars Kotthoff commented on SOLR-684:
------------------------------------
Looks good :)
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Mike Klaas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627090#action_12627090 ]
Mike Klaas commented on SOLR-684:
---------------------------------
In case this ever needs to be done with pure "svn":
$ svn info | grep 'Revision' | awk '{print $2}'
15171
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627067#action_12627067 ]
Lars Kotthoff commented on SOLR-684:
------------------------------------
Hmmm, doesn't look like it :(
[exec] Execute failed: java.io.IOException: /opt/subversion-1.4.5/bin/svnversion: not found
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627077#action_12627077 ]
Hoss Man commented on SOLR-684:
-------------------------------
yeah ... i forgot the solr hudson builds are actually run on the Lucene zone machine (which has a slightly different setup then the hudson zone) ... let's see how build#551 goes
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627099#action_12627099 ]
Lars Kotthoff commented on SOLR-684:
------------------------------------
...but then again it's probably no big deal if the svn version number is incorrect as it's only used in the jar/war manifests. When you get something like 690356:690357M it's highly unlikely that this will help you to uniquely identify the "revision" as a whole or recreate it, which I think is the point of including it in the manifest.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-684.
---------------------------
Resolution: Fixed
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627097#action_12627097 ]
Hoss Man commented on SOLR-684:
-------------------------------
bq. In case this ever needs to be done with pure "svn":
I strongly recommend people don't do that ... or at least, don't assume it's equivalent.
svnversion is automatically recursive, and aware of both mixed version trees and local modifications, so you can get output like this...
{code}
hossman@coaster:~/lucene/solr$ svnversion
690356:690357M
{code}
...when the revs of your files vary between 690356 and 690357 and some files deep in your tree are locally modified.
attempting to get the same information out of "pure svn" would require shell scripting the likes of which would likely drive you insane.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Mike Klaas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627106#action_12627106 ]
Mike Klaas commented on SOLR-684:
---------------------------------
Good point, Hoss.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-684) Hudson builds do not have the SVN
revision because svnversion is not available
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-684:
--------------------------
Fix Version/s: 1.3
I've merged to 1.3 in r690384 and made the appropriate Hudson config changes for Grant's shiny new Hudson "Solr Release Candidate" setup, so 1.3-RC2 and on should be golden.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to include the revision number. This fails in Hudson however as the svnversion executable is not available.
> This could be addressed by installing svnversion on the build machine or using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.