jira-importer commented on issue #927:
URL: https://github.com/apache/maven-scm/issues/927#issuecomment-2964633397

   **[Chris 
Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)**
 commented
   
   Here is an extract of a successful run of the release:prepare:
   
   [INFO] Executing: cmd.exe /X /C "scm create workspace --repository-uri 
https://rtc:9444/jazz --username Deb --password ***** GPDB-1.0.46 --snapshot 
GPDB-1.0.46"
   [INFO] Working directory: C:\Documents and Settings\admin\workspace\GPDB
   [INFO] Executing: cmd.exe /X /C "scm deliver --repository-uri 
https://rtc:9444/jazz --username Deb --password ***** --source GPDB-1.0.46 
--target GPDBStream"
   [INFO] Working directory: C:\Documents and Settings\admin\workspace\GPDB
   [INFO] Executing: cmd.exe /X /C "scm snapshot promote --repository-uri 
https://rtc:9444/jazz --username Deb --password ***** GPDBStream GPDB-1.0.46"
   [INFO] Working directory: C:\Documents and Settings\admin\workspace\GPDB
   
   and to follow up:
   
   we perform a scm status to see/verify that we do indeed have a flow target:
   
   C:\Documents and Settings\admin\workspace\GPDB>scm status
   Workspace: (1156) "GPDBWorkspace" <-> (1157) "GPDBStream"
   Component: (1158) "GPDB"
   Baseline: (2292) 44 "GPDB-1.0.46"
   
   So, we should flow into GPDBStream, so let's list the snapshots of that 
stream:
   
   C:\Documents and Settings\admin\workspace\GPDB>scm list snapshots --username 
Deb --password Deb --repository-uri https://rtc:9444/jazz --maximum 1000 
GPDBStream
   (2291) "GPDB-1.0.46" Apr 23, 2015 8:21 PM
   (2284) "GPDB-1.0.42" Nov 27, 2012 5:21 PM
   (2275) "GPDB-1.0.41" Nov 27, 2012 4:28 PM
   (2258) "GPDB-1.0.40" Jun 2, 2012 3:51 PM
   (2249) "GPDB-1.0.39" Jun 2, 2012 3:06 PM
   (2240) "GPDB-1.0.38" Jun 2, 2012 1:49 PM
   (2231) "GPDB-1.0.37" Jun 2, 2012 1:39 PM
   (2221) "GPDB-1.0.36" Jun 2, 2012 1:09 PM
   (2211) "GPDB-1.0.35" May 15, 2012 10:29 PM
   (2201) "GPDB-1.0.34" May 15, 2012 10:09 PM
   (2190) "GPDB-1.0.33" May 15, 2012 8:39 PM
   (2180) "GPDB-1.0.32" May 15, 2012 8:18 PM
   (2170) "GPDB-1.0.31" May 15, 2012 8:00 PM
   (2159) "GPDB-1.0.30" May 15, 2012 4:20 PM
   (2146) "GPDB-1.0.29" May 8, 2012 11:20 PM
   (2078) "GPDB-1.0.28" Mar 30, 2012 4:21 PM
   (1850) "GPDB-1.0.27" Mar 21, 2012 5:52 PM
   (1806) "GPDB-1.0.26" Mar 20, 2012 6:18 PM
   (1717) "GPDB-1.0.25" Feb 29, 2012 3:30 PM
   (1707) "GPDB-1.0.24" Feb 29, 2012 3:06 PM
   (1697) "GPDB-1.0.23" Feb 29, 2012 1:37 PM
   (1686) "GPDB-1.0.22" Feb 29, 2012 1:26 PM
   (2297) "GPDB-1.0.21" Feb 25, 2012 10:13 PM
   (2298) "GPDB-1.0.20" Feb 24, 2012 11:03 PM
   (2299) "GPDB-TEST" Feb 22, 2012 9:39 PM
   (2300) "GPDB-1.0.19" Feb 22, 2012 4:16 PM
   (2301) "GPDB-1.0.18" Feb 22, 2012 11:02 AM
   (2302) "GPDB-1.0.17" Feb 22, 2012 9:04 AM
   (2303) "GPDB-1.0.16" Feb 22, 2012 12:10 AM
   (2304) "GPDB-1.0.15" Feb 21, 2012 11:48 PM
   (2305) "GPDB-1.0.14" Feb 21, 2012 11:28 PM
   (2306) "GPDB-1.0.13" Feb 21, 2012 11:22 PM
   (2307) "GPDB-1.0.12" Feb 21, 2012 11:15 PM
   (2308) "GPDB-1.0.11" Feb 21, 2012 5:03 PM
   (2309) "GPDB-1.0.10" Feb 21, 2012 4:48 PM
   (2311) "GPDB-1.0.9" Feb 21, 2012 4:35 PM
   (2312) "GPDB-1.0.7" Feb 21, 2012 1:18 PM
   (2313) "GPDB-1.0.6" Feb 20, 2012 4:35 PM
   
   So that works as expected.
   
   I'm happy to close this issue if I do not receive some feedback soon, as Not 
a Bug.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to