After clone on dev instance, update sets are all retrieved again in quality instance

vanessaheux
Tera Contributor

Hello

I’ve just cloned my dev instance with production one.

Today I created a new update set in dev that I want to import in quality.

When I “retrieved Complete update sets” in quality instance, I did not get only the new complete update set but also many other update sets that were already imported in quality and production instance.

Did I miss something ?

I used to clone instances before and never had that problem.

And what can I do not to retrieve them again in quality instance except the new one ? Can I put them all except one in “ignore” status ? is it the good way to work ?

Regards

Vanessa Heux

 

1 ACCEPTED SOLUTION

Sebastian R_
Kilo Sage

You probably didn´t ignore the completed update sets on your production instance. Therefore if you clone the instance the update sets will be retrieved again.

 

Following the best practice:

"Set completed Update Sets on the production instance to ignore. This state ensures the Update Set is not reapplied when cloning the instance."

Source

 

View solution in original post

2 REPLIES 2

Goutham sai
Tera Expert

Hi,

 

If you want to import specific update set, please follow the below procedure:

1) Login Dev Instance => Type ' Local update set' in left navigation and click on 'Local Update Sets' => Open the corresponding Update set => Change the state to complete and save => Click on 'Export to XML' link under Related links.

2) Login to Test instance =>Type 'retrieved update set' in left navigation and click on 'Retrieved update sets' => Click on 'Import Update Set from XML' link => choose the XML file which was downloaded in step1.

 

Please mark my answer correct/helpful if it helped you solve your issue.

 

Thanks,

Sebastian R_
Kilo Sage

You probably didn´t ignore the completed update sets on your production instance. Therefore if you clone the instance the update sets will be retrieved again.

 

Following the best practice:

"Set completed Update Sets on the production instance to ignore. This state ensures the Update Set is not reapplied when cloning the instance."

Source