[#QB-2789] There is an issue with Repository Checkout

QuickBuild

There is an issue with Repository Checkout

Created: 19/Aug/16 02:20 PM Updated: 25/Aug/16 10:32 PM

Component/s:

None

Affects Version/s:

6.1.14

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

Hi Support Team,

I are using Perforce for our SCM and found there is an issue when using the plugin Checkout. We have 'ConfigurationA' and 'ConfigurationB', they are at the same level. Each of them has repository named 'Source'. They have the same name, but have different view settings. These configurations use the Repository->Checkout of built-in plugin to check the source from Perforce. The issue that if we do a promotion from ConfigurationA to ConfigurationB, the ConfigurationB doesn't checkout the source properly and vice versa. Please look into this issue as your earliest chance.

Thanks,
ptrinh

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [19/Aug/16 11:25 PM]

This is by design, repository of the same name across promotions are treated as same repository. If you want to handle them differently, please make sure to use different names.

[ Permlink | « Hide ]

Dennis Marks [25/Aug/16 03:29 AM]

Robin,

The issue is not the repository of the same name. what we had was different repositories, if we promoted to a different configuration, we found it either did not sync the files correctly from perforce, or totally missed the files correctly and did not sync the right files at all. Triggering over promotion works, but then you cannot follow the promotion pipeline from the current process.

Root
   Product1
         Process1
                Compile1 - Trigger/Promote GetData1 - Repository Source
                GetData1- Trigger/Promote BuildInstall1 - Repository Data
                BuildInstall1 - Repository Install
         Process2
                Compile2 Trigger/Promote GetData2 - Repository Source2

                GetData2 Trigger/Promote BuildInstall2 - Repository Data2
                BuildInstall2 - Repository Install2
        Trigger or promote if all is successful to Product2 process -Repository name reference to product2 process.

There should be a way to promote without carrying the repository information to be able promote to some other configuration and only carry variables like a trigger step does.

Thanks
Dennis

[ Permlink | « Hide ]

Dennis Marks [25/Aug/16 03:31 AM]

Please contact myself or Phong on this issue

[ Permlink | « Hide ]

Robin Shen [25/Aug/16 10:32 PM]

This is not clear to me, please demonstrate the issue with a sample database and send the database backup and reproducing steps to [robin AT pmease DOT com]. Thanks!