You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Hoffer <dh...@gmail.com> on 2009/06/25 17:14:36 UTC
buildnumber-maven-plugin question
I'm trying to use buildnumber-maven-plugin to get the SVN revision so I can
put it in the manifest. However I get the following error when this is run
on our build agents (TeamCity)
*09:07:00]:* *[INFO] Cannot get the revision information from the scm
repository : * *[09:07:00]:* *Exception while executing SCM command.*
*[09:07:00]:* *svn: '/home/teamcity/buildAgent2/work/317fa80dac6b46ac' is
not a working copy*
I think this is because our build agents do an export instead of a checkout
because its much faster. How can I get this plugin to work with export?
BTW, the release plugin does work this way.
-Dave
Re: buildnumber-maven-plugin question
Posted by David Hoffer <dh...@gmail.com>.
Yeah, sorry I meant to re-post. We did switch to checkout for release
plugin for this very reason...we did the same for this plugin and it works
great.
-Dave
On Thu, Jun 25, 2009 at 1:47 PM, Olivier Lamy <ol...@apache.org> wrote:
> Afaik svn export doesn't store any svn metadata.So IMHO no way to get the
> rev number.
>
> --
> Olivier
>
> 2009/6/25 David Hoffer <dh...@gmail.com>
>
> > I'm trying to use buildnumber-maven-plugin to get the SVN revision so I
> can
> > put it in the manifest. However I get the following error when this is
> run
> > on our build agents (TeamCity)
> >
> > *09:07:00]:* *[INFO] Cannot get the revision information from the scm
> > repository : * *[09:07:00]:* *Exception while executing SCM command.*
> > *[09:07:00]:* *svn: '/home/teamcity/buildAgent2/work/317fa80dac6b46ac' is
> > not a working copy*
> >
> > I think this is because our build agents do an export instead of a
> checkout
> > because its much faster. How can I get this plugin to work with export?
> > BTW, the release plugin does work this way.
> >
> > -Dave
> >
>
Re: buildnumber-maven-plugin question
Posted by Olivier Lamy <ol...@apache.org>.
Afaik svn export doesn't store any svn metadata.So IMHO no way to get the
rev number.
--
Olivier
2009/6/25 David Hoffer <dh...@gmail.com>
> I'm trying to use buildnumber-maven-plugin to get the SVN revision so I can
> put it in the manifest. However I get the following error when this is run
> on our build agents (TeamCity)
>
> *09:07:00]:* *[INFO] Cannot get the revision information from the scm
> repository : * *[09:07:00]:* *Exception while executing SCM command.*
> *[09:07:00]:* *svn: '/home/teamcity/buildAgent2/work/317fa80dac6b46ac' is
> not a working copy*
>
> I think this is because our build agents do an export instead of a checkout
> because its much faster. How can I get this plugin to work with export?
> BTW, the release plugin does work this way.
>
> -Dave
>
Re: buildnumber-maven-plugin question
Posted by Wendy Smoak <ws...@gmail.com>.
On Thu, Jun 25, 2009 at 8:14 AM, David Hoffer<dh...@gmail.com> wrote:
> I think this is because our build agents do an export instead of a checkout
> because its much faster. How can I get this plugin to work with export?
I think the buld number plugin works off the result of 'svn info' and
as the error points out, an export is not a working copy.
You would have to get it to use the full url and do a remote svn command like
svn info http://svn.apache.org/repos/asf/continuum/trunk
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org