Vous êtes sur la page 1sur 3

ADE Workflow

A developer would follow these steps to make changes and commit their work
1. Obtain Kerberos ticket
2. Create a new view (or re-use existing)
3. Refresh to particular label
4. Begin a transaction
5. Make changes (co/ci)
6. Build and test
7. Send code for review (optional)
8. Submit mergereq (optional)
9. Commit changes to codeline branch (merge transaction)




ADE Commands

Listing labels and series
ade showseries [-prod <product name>]
ade showlabels series <series name>

Create View
ade createview label <label_name> <view_name>
ade refreshview {label <label name> | -latest}

Begin a Transaction
ade begintrans <txn_name>
ade begintrans bug <bug #>

Make Changes to Objects & Check in Changes
ade co [c <comment>] <file name>
ade describetrans
ade ci [-c <comment>] <file name>



Build and Test
Transaction Approval : Submit transaction for OraReview /
Submit mergereq

Merge Transaction
ade beginmerge
ade mergetrans
ade endmerge

ADE commands for working with groups
ade desc somefile.c
ade chgrp -newgrp FUSION_CODE_ACCESS
somefile.c
ade lsvtree chenv.cshrc

Vous aimerez peut-être aussi