How to check out a Snaphot/Baseline version of a component?
Hi All.
I am surprised (to say the least, shocked is more like it) that we are unable to check out/copy/load a specific snapshot/baseline/tag of a component!
If we are unable to so this, then what is the point of being able to create it???
One workaround, from what I can see is to create a new repository workspace of the components' baseline/snapshot and then check it out.
However, I can not work out how to do this from the scm command line.
This is what was used to create the snapshot to start with.
So could any kind soul suggest as to how I can sue the scm command line to effectively check out (load in jazz scm terms) snapshot "BogusTestJazz-3.0.0.15" of the code in the BogusRepositoryWorkspace?
Thanks!
-Chris
I am surprised (to say the least, shocked is more like it) that we are unable to check out/copy/load a specific snapshot/baseline/tag of a component!
If we are unable to so this, then what is the point of being able to create it???
One workaround, from what I can see is to create a new repository workspace of the components' baseline/snapshot and then check it out.
However, I can not work out how to do this from the scm command line.
This is what was used to create the snapshot to start with.
scm create snapshot --repository-uri https://rtc:9444/jazz --username Deb --password Deb --name BogusTestJazz-3.0.0.15 --description "[maven-release-plugin] copy for tag BogusTestJazz-3.0.0.15" BogusRepositoryWorkspace
So could any kind soul suggest as to how I can sue the scm command line to effectively check out (load in jazz scm terms) snapshot "BogusTestJazz-3.0.0.15" of the code in the BogusRepositoryWorkspace?
Thanks!
-Chris
2 answers
With some help from one of our friendly SCM's, thanks Chris (not me!), we get:
which, when executed, returned:
:-)
So, then we can execute this to check out the newly created Repository Workspace "BogusTestJazz-3.0.0.15":
And, when executed, shows:
The only problem here, and it's not strictly, a jazz issue (ClearCase has the same issue) is that maven will expect the pom.xml file the /tmp/maven dir (given the above example), not the /tmp/maven/BogusTest dir.
So, we're getting there.
-Chris
scm create workspace BogusTestJazz-3.0.0.15 --repository-uri https://rtc:9444/jazz --username Deb --password Deb --snapshot BogusTestJazz-3.0.0.15
which, when executed, returned:
C:\>scm create workspace BogusTestJazz-3.0.0.15 --repository-uri https://rtc:9444/jazz --username Deb --password Deb --snapshot BogusTestJazz-3.0.0.15
Workspace (1034) "BogusTestJazz-3.0.0.15" successfully created
:-)
So, then we can execute this to check out the newly created Repository Workspace "BogusTestJazz-3.0.0.15":
scm load --repository-uri https://rtc:9444/jazz --username Deb --password Deb --force --dir C:\tmp\maven BogusTestJazz-3.0.0.15
And, when executed, shows:
C:\>scm load --repository-uri https://rtc:9444/jazz --username Deb --password Deb --force --dir C:\tmp\maven BogusTestJazz-3.0.0.15
Downloading /BogusTest/.settings/org.eclipse.jdt.core.prefs (629 B)
Downloading /BogusTest/zip-for-release-no-deps.xml (427 B)
Downloading /BogusTest/.classpath (320 B)
Downloading /BogusTest/.project (385 B)
Downloading /BogusTest/test.txt (12 B)
Downloading /BogusTest/.jazzignore (733 B)
Downloading /BogusTest/src/main/java/Blah.java (219 B)
Downloading /BogusTest/pom.xml (4.2 KB)
C:\>
The only problem here, and it's not strictly, a jazz issue (ClearCase has the same issue) is that maven will expect the pom.xml file the /tmp/maven dir (given the above example), not the /tmp/maven/BogusTest dir.
So, we're getting there.
-Chris
Hi All.
I am surprised (to say the least, shocked is more like it) that we are unable to check out/copy/load a specific snapshot/baseline/tag of a component!
If we are unable to so this, then what is the point of being able to create it???
One workaround, from what I can see is to create a new repository workspace of the components' baseline/snapshot and then check it out.
However, I can not work out how to do this from the scm command line.
This is what was used to create the snapshot to start with.
scm create snapshot --repository-uri https://rtc:9444/jazz --username Deb --password Deb --name BogusTestJazz-3.0.0.15 --description "[maven-release-plugin] copy for tag BogusTestJazz-3.0.0.15" BogusRepositoryWorkspace
So could any kind soul suggest as to how I can sue the scm command line to effectively check out (load in jazz scm terms) snapshot "BogusTestJazz-3.0.0.15" of the code in the BogusRepositoryWorkspace?
Thanks!
-Chris
In 3.0.1.1, it is:
scm create workspace --snapshot <snapshot>
scm load <workspace-name.
The reason you are asked to create a workspace first is that this tells
RTC to create the metadata so that it can efficiently update your loaded
files in subsequent load requests.
Cheers,
Geoff
On 1/4/2012 10:08 PM, chrisgwarp wrote:
scm create workspace --snapshot <snapshot>
scm load <workspace-name.
The reason you are asked to create a workspace first is that this tells
RTC to create the metadata so that it can efficiently update your loaded
files in subsequent load requests.
Cheers,
Geoff
On 1/4/2012 10:08 PM, chrisgwarp wrote:
Hi All.
I am surprised (to say the least, shocked is more like it) that we are
unable to check out/copy/load a specific snapshot/baseline/tag of a
component!
If we are unable to so this, then what is the point of being able to
create it???
One workaround, from what I can see is to create a new repository
workspace of the components' baseline/snapshot and then check it
out.
However, I can not work out how to do this from the scm command line.
This is what was used to create the snapshot to start with.
scm create snapshot --repository-uri
https://rtc:9444/jazz --username Deb --password Deb --name
BogusTestJazz-3.0.0.15 --description
" copy for tag
BogusTestJazz-3.0.0.15" BogusRepositoryWorkspace
So could any kind soul suggest as to how I can sue the scm command
line to effectively check out (load in jazz scm terms) snapshot
"BogusTestJazz-3.0.0.15" of the code in the
BogusRepositoryWorkspace?
Thanks!
-Chris