Team Projects determine which objects are controlled by Team Coding. If you are a Team Coding Administrator (meaning that you have the TC_ADMIN_ROLE) you can create one or more Team Projects to group the controlled objects into logical work units, based on your organization's workflow requirements. To use Team Coding there must be at least one Team Project.
When a version control system (VCS) is being used in Team Coding, you can link a Team Project to a project in the VCS. This linking determines where the object source revisions of the Team Project are managed in the VCS.
SQL Navigator enables you to create one or more sub-directories in a VCS project at the same time that you create a Team Project. This feature is helpful if, for example:
Use Team Projects page of Team Coding Administration to administer your Team Projects. Only a Team Coding Administrator can administer Team Projects.
To Create a Team Project
See Setup Team Projects.
To change a Team Project
Under the Team Project that you want to change, do one of the following:
To delete a Team Project
To freeze a Team Project
Note: In the Team Projects list, the project is now marked (Frozen) rather than (Active). Click to unfreeze the project.
To work with revisions
The Team Coding Administrator can perform the following actions for a project:
(Disabled if a VCS is not being used)
Synchronize differences between the version in the database and the version in the VCS. Select the objects that you want to synchronize.
Synchronize resolves the following issues:
(Disabled if a VCS is not being used)
|Create New Revision in the VCS
Create a new revision in the VCS for all controlled objects. This action loads all of the objects for a Team Project into the Synchronize window. Select the ones for which you want to make a new revision.
|Compile PL/SQL Objects in DB
Compile the selected object in the database.
The Team Coding Administrator must create at least one Team Project before users begin to use Team Coding. A Team Project is linked to specific controlled objects and a version control system (VCS), if one is being used with Team Coding.
Team Coding must be installed and set up before Team Projects can be created. For more information, see Install Team Coding.
To create a Team Project
Specify a nested sub-project for SQL Navigator to create under the selected VCS project.
Store each object type in a separate sub-directory under the VCS directory that you created in the previous steps:
Clear the check box for any object type in this schema that you do not want to control with Team Coding.
For tables, you can control how tables and their associated objects are checked out:
Double-click to create filters that control which objects of each object type are controlled. You can add one or more filters. Use standard Oracle filtering such as string% or string_.
Use Filter to specify the objects that you want to control with this project.
Use Exclude to exclude objects from being controlled by this project.
Note: By default, a Team Project is marked as active when it is created. A status of (Active) means that the objects in the project are controlled through Team Coding.
Team Coding only has one defined role, that of the Team Coding Administrator: TC_ADMIN_ROLE. This role is automatically granted to the user who creates the Team Coding objects. This user can set up or remove Team Coding, set up global rules for the Team Coding environment, and set up Team Projects.
If necessary, you can grant the TC_ADMIN_ROLE to additional users. Be sure to select the Default checkbox when you grant the role to additional users.
You do not need to assign a role to other Team Coding users. By default, all users in the database can:
Use the Configure Team Coding Options page to configure the following local settings that are unique to your local SQL Navigator installation:
To set local Team Coding options
From the Main Menu, click Team Coding | Configure.
Select a version control system to use with Team Coding. Select None to use Team Coding without a VCS.
Configure connection settings to the selected VCS.
(Not required for Microsoft Visual Source Safe.)
Prompt for check-in comment
Prompt for check-out comment
Force users to enter comments when checking controlled objects in or out.
If the Force check-in comments or Force check-out comments option is set globally by the Team Coding Administrator, that option is read only on this page.
|Prompt for check-in all on exit
|Prompt users to check in their work when they close SQL Navigator.
|Prompt for changes to VCS server config
|Prompt to alert you of changes made to the VCS configuration.
|Check-out object on opening
|Automatically check out a controlled object when it is opened in SQL Navigator.
|Check-in object on closing
|Automatically check in a controlled object when it is closed in SQL Navigator.
|Force new revision on check-in
|Force a new VCS revision when a controlled object is checked in, even if no changes are made. Not all VCS systems support this feature.
|Show VCS command output window
|Display Team Coding VCS commands and responses in the Output Window.
|Enable VCS debug logging
|Save VCS commands and responses to the VCS debug log. To view this log, click Open log file.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center