Release to Production

[Former Member]

Hi,

In a track with DEV/TEST/PROD systems configured, and transports happening regularly into TEST system, the component is assembled each time and waits in the Approval tab to go into production.

Can anyone tell me if its enough to move the latest assembled component into Production while go-live or should all the assembled components be transported into Prod one by one (starting from oldest to latest)?

When I created another track to transport the developments to a training system with Transport as connection type, I observed that, say, out of the 10 approved assembled components, few of them (8) were regarded as obsolete and only the latest few assembled components were imported.

Does it happen similarly while transporting into Production?

If so, on what criteria does the Transport system treats (some of) them as obsolete or not?

Any help is greatly appreciated.

Regards,

Rajit Srinivas

[sid-desh · Accepted solution]

Hi Rajit,

What i have found is that the components which are delivered i.e. the SCA file are always complete deliverables. What i am trying to say that it doesnt happen with every patch only the delta (changes) are sent. So if you have an SCA file (SCA1) and a patch for it (SCA1P) it is not required that you install SCA1 first and then SCA1P. SCA1P is complete in all respects.

Hence in your case even if your transport the latest assembled components that should work fine.

I dont know the criteria by which CMS determines whether component is obsolete but can guess that it may be date time and if a newer component is available. I know this is a long shot.

I hope some other member will also shed more light on this topic.

Regards

Sidharth

[Former Member · Accepted solution]

If you select all assemblies and choose Import, you will see that only the last release will get the Import Finished status. The rest will be marked outdated.