Custom Query (159 matches)
Results (34 - 36 of 159)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#35 | fixed | First build with pb doesn't create the correct tree | ||
Description |
When using pb for the first time on a system without previous pb, the checkout done use the version passed in param. However, you may want to refer to the whole tree instead in pburl. Which may create a problem. pb should detect that and propose the right thing. Checking out svn+ssh://svn.project-builder.org/mondo/svn/pb to /home/pb/pb//0.9.4 ... Executing svn co svn+ssh://svn.project-builder.org/mondo/svn/pb /home/pb/pb//0.9.4 Where pburl is pburl pb = svn+ssh://bryang@svn.project-builder.org/mondo/svn/pb In that case the co creates twice a 0.9.4 dir in which it exports the content. |
|||
#36 | fixed | distinction for cms2 vs using sandbox as is | ||
Description |
When doing the cms2 commands, I would have expected the operation to grab the specified version from cms, rather than using my current sandbox of a project. In fact the way it behaves now, it much more implements a sandbox2 or local2 functionality (which itself is useful). However, I'd like both modes to be available, and certainly the cms2 modes to actually refresh what gets built/packaged to match what the specified CMS repository has. And the new sandbox2 or local2 operation to rely on what you have in place (modified or not) to be the source (which is really useful for local and/or offline testing). |
|||
#37 | worksforme | cms anonymous access | ||
Description |
It appears that I can't correctly specify anonymous access for CVS (and I suspect for svn) for the project to be packaged itself (eg. for pburl) . This is a must to have, since I can't be expected to have authenticated access to a project's CMS at the early stages. This is also likely true for the pbconfurl as well, so that once the necessary configurations are established, packages could be build by automated means. Hence the same defect and requirement here. |