> From: Les Mikesell <lesmikesell_at_gmail.com>
> To: BRM <bm_witness_at_yahoo.com>
> Cc: "users_at_subversion.apache.org" <users_at_subversion.apache.org>
> Sent: Wednesday, February 27, 2013 5:30 PM
> Subject: Re: Tagging svn:externals
>
> On Wed, Feb 27, 2013 at 4:14 PM, BRM <bm_witness_at_yahoo.com> wrote:
>>>
>>> But that's not what I want. I want the externals in tags to point to
>>> previously tagged component versions. Without forcing that to be
>>> committed to the trunk or encouraging copying to tags from a workspace
>>> that doesn't match any trunk commit.
>> From that description, it'll have to be a manual process that you run
> from within your working copy.
>> Just update the svn:externals appropriately and then do an "svn
> update".
>> You can test whatever you like without committing.
> Everything is built by jenkins and has to come from the repository.
> Things in uncommitted workspaces aren't necessarily repeatable.
,,,
>> Let me propose this:
>>
>> For QA, let them do a simple modified working copy to get the svn:externals
> where you want them; but then they are not allowed to commit or make other
> changes.
>
> Won't work - it has to be committed somewhere or it won't be built.
Perhaps then you need a different tool.
For example, git-svn[1] is might be what you want.
When something is ready for QA it is pushed to a git repository for Jenkins to pick up.
How you change the externals in the process I'm not sure; but it would at least give you
a trackable repository that would mimick a modified working copy.
Otherwise I think you're out of luck if you don't want to (i) commit to trunk, or (ii) create a branch,
but still want to track it in the repository somehow.
Ben
[1] https://www.kernel.org/pub/software/scm/git/docs/git-svn.html
Received on 2013-02-27 23:44:47 CET