Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
How to get a list of edition names ?
eddie1
I want to have a list of all currently available editions in a combo box in the start up form of my deployment workflow. This would enable the user to specify exactly which editions to compare when the Open Deploy task happens.
Any ideas on how to get a list of currently available editions for the branch ??
Find more posts tagged with
Comments
Adam Stoller
Take a look at the
iwlist
CLT. Example usage:
%
iwlist /default/main/devnet/EDITION
INITIAL ed_0001 ed_0002
--fish
(Interwoven, Curriculum Development)
SOAPResponse2.pcap.zip
Migrateduser
It is not clear to me why you would want the user to select an edition, and it may not be clear to the user what effect the selection will have. You may have your reasons.
Have you considered using a filelist deployment instead of an edition based deployment?
Brinko Kobrin
Interwoven Staff Engineer
eddie1
The user will only be selecting the baseline edition which will always be compared to the latest edition to deploy the 'delta' of the two.
The baseline edition is the last known 'Good' edition in the branch which is also currenly in the target server. The user is willing to keep the track of this baseline edition. By being able to specify this baseline edition, the user can be sure that all changes since the last 'good' ( bug free ) deployment have been deployed as there could be a number of 'bad' editions in between.
Yes the same thing can be achived thru a filelist deployment from the last edition, but the point where the user initiates the deployment is the start of another WorkFlow (becuase the user has to go thru some offline process to authorize deployment to production boxes ) so i dont have anyway to get the list of files that have been updated/added since the last deployment in the second workflow.
Migrateduser
That is fine if this is the process that you really want. I wouldn't expect most users to know on which edition the last deployment was based. And if the wrong edition is selected, you could end up with a very strange result. But you know your users better than I do.
You could consider having the workflow (or a DNR in the deployment configuration) record the edition in a file outside of the branch being deployed. That value could then be used as the default for the edition selection.
Brinko Kobrin
Interwoven Staff Engineer