[Buildbot-commits] [Buildbot] #2066: Fix new source steps' URL handling

[Buildbot]

#2066: Fix new source steps' URL handling
------------------------+--------------------
Reporter:  in3xes       |       Owner:
    Type:  enhancement  |      Status:  new
Priority:  minor        |   Milestone:  0.8.7
 Version:  0.8.4p2      |  Resolution:
Keywords:  simple       |
------------------------+--------------------

Comment (by sa1):

 There is no simple way to handle subversion urls by just the baseURL, as
 there are no guarantees of patterns in how branches are stored in the svn
 file system.

 For projects with no convention, repourl is the only way that is
 acceptable. e.g branches/dev/branch and branches/for-upstream may be the
 locations of two "branches". "branch" here simply means a folder that is
 buildable.

 For projects that do have a convention as to how branches are stored, the
 documentation states that the baseURL and branch are simply concatenated
 together to derive the repoURL to use for the checkout. This is
 inadequate.

 But the code contains a simpler way of specifying a convention for the
 branches by adding a branch_placeholder. If %%BRANCH%% is specified in the
 baseURL, it is replaced by branch in the generated repourl. This addresses
 a lot of simple branch conventions and is in my opinion the simplest way
 of adding flexibility for the user. This pattern of baseURL is also
 perhaps not compatible with the url in the source stamp. But I believe
 that this is the best way to handle the situation.

 The configuration for specifying how branches are stored can be be made
 more complex for complicated setups if we want to have the required
 flexibility. To have an all-encompassing configuration does not seem to be
 possible. There is a sample BDF(branch description format) specified here
 http://article.gmane.org/gmane.comp.version-control.git/192801
 which can be used to specify the location of branches but the scope of the
 description is too expansive for our purpose and only serves to indicate
 the complexity in such a task.

 Other simple url patterns can be added later if they are in widespread use
 by some project.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2066#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation