dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Get latest version on branch includes versions for trunk

( SVNSCC , PB 9.0.3, 1.3.1.5, WIN 2000/XP  )
Type: Public Status:Closed Created: 30 Aug 06 08:00 Updated: 31 Oct 06 10:00
You value our support on this issue as "ok, with some efforts from me problem is solved". Click here to resubmit your opinion.
--> Igor Pushkov (admin)  at 31 Oct 06 10:00 writes

Unfortunately I do believe that it is not possible to work with branches in
the same workspace because PB reuse the same folder for temporary
extracting source files from pbl to make possible integration with SCC.
So, the only one right way to work with branches is to have several
workspaces.
--> Ben DE PAUW (user)  at 30 Aug 06 08:00 writes

Hello,

we just made our first branch on the trunk version and after a "Tortoise
checkout" (no update) and add the new target in PB, we get the following
effect:

A GLV (get latest version) in PB gives an object list that includes not
only the objects of the branch, but also the same objects of the trunk.
However, in SVN the trunk and branch are 2 separate locations. (see
PB_GetLatestVersion.jpg).
When all items are selected (branch + trunk) pushOK lists that all have
been updated afterwards, even if the trunk target is not set in PB.

FYI: I've attached some screenshots of our configuration (repository,
pb_settings + GLV object list, XYZ)
As you can see, we have a general access point for our pb sources at
http://revbase.sofico.be/svn/miles/generic/client/pb that is linked to the
local Q:\GUISource, under which both trunk and branches are located.

The branch that was just made is
http://revbase.sofico.be/svn/miles/generic/client/pb/branches/release_151p1
as a copy of http://revbase.sofico.be/svn/miles/generic/client/pb/trunk
(see screenshot Tortoise_making_branch.jpg)

We've noticed that when we make a separate workspace for just that 1
branch, the GLV does not suggest to include the trunk version. (see
screenshots branch_workspace_*.jpg)

How can we avoid this problem? We would still like to work with 1 Workspace
with separate targets for trunk and branches. We do not want to make a
workspace for each separate branch.

Another general question: can you advise us whether we could improve our
setup for branches & workspace etc.. (we currently do most of our SCC
operations from within PB, so the "SCC RW monitor" is not active).

Thanks for a quick response.



Screenshots 
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9536329 visitor since 20 Jan 2003.
887 visitors today and 2 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com