Engineering Lifecycle Management Wiki - Deployment
Deployment Web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
E
dit
A
ttach
P
rintable
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RTCSystemZPerformanceTesting
>
RTCEEConcBuildTests
Revision 5 - 2015-07-02 - 03:44:03 - Main.rucielulu
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! RTCEE Performance Testing: Concurrent Builds Scenario %DKGRAY% Authors: [[Main.JorgeAlbertoDiaz][Jorge Diaz]] <br> Build basis: RTC 4.x 5.x 6.x %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> %STARTSECTION{"Intro"}% The scenario targets the concurrent execution builds. To accomplish that, team builds and personal builds are executed concurrently in different steps of the scenario.<br/> %ENDSECTION{"Intro"}% ---++ Scenario Detailed Description Following the detail of the different steps that are performed for testing this scenario on both z/OS and IBMi: <table class="gray-table"> <tbody> <tr> <th align="center">Test Steps of RTCz</th> <th align="center">Description</th> </tr> <tr> <td>1. Perform two(2) enterprise dependency builds concurrently with Mortgageapplicationx250</br>2. Change a COBOL file in each repository workspace</br>3. Request five(5) personal builds concurrently</td> <td>After a first complete build of all the programs ran in two team builds concurrently, <br/>different sets of changes and personal builds are performed. </td> </tr> </tbody> </table> <table class="gray-table"> <tbody> <tr> <th align="center">Test Steps of RTCi</th> <th align="center">Description</th> </tr> <tr> <td>1. Perform two(2) enterprise dependency builds concurrently with Maillist X250</br>2. Change one RPG file in each repository workspace</br>3. Request five(5) personal builds concurrently</td> <td>After a first complete build of all the programs ran in two team builds concurrently, <br/>different sets of changes and personal builds are performed. </td> </tr> </tbody> </table> ---++ Test Topologies The following topologies are being used for the execution of this scenario in order to test the performance and gather relevant data. %INCLUDE{"RTCEETestingTopologies" section="SingleTierZ"}% %INCLUDE{"RTCEETestingTopologies" section="SingleTierI"}% ---++ Test Reports Please refer to the link below for test report related to current scenario. <br/> * Below report compares the concurrent build performance of RTC for z/OS. <br/> [[RTCEEConcurrentBuildComparisonBetweenReleases][Rational Team Concert For z/OS Concurrent Build Performance]]<br/> * Below report compares the concurrent build performance of RTC for IBMi.<br/> [[RTCEEConcurrentBuildComparisonBetweenReleasesForIBMi][Rational Team Concert For IBMi Concurrent Build Performance]]<br/> ---+++++!! Related topics: ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: [[Main.LuLu][Lu Lu]] <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
M
ore topic actions
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.