17 docs tagged with "ctf_19.2"

You can compare two Baselines created at two different points in time to know the differences. You can also compare the Baseline Definitions of two Baselines.

Use the Configure Application tool to define your site level TeamForge settings.

Each project can have one or more source code repositories. Before you can create a source code repository, a site administrator must first add one or more SCM servers to the Digital.ai TeamForge environment.

Create a Baseline when you accomplish specific milestones in your project or when you release or deliver a product. You can create a Baseline from either a Baseline Definition or from the ground up.

You can create a tracker artifact whenever you need to report and track a bug, feature request, support request, or other type of issue. You can also create a tracker artifact without logging into TeamForge just by sending an email to the tracker.

Updating the information in tracker artifacts is one important way that project members can work together effectively.

You can publish the output of your project to selected audiences as packages and releases.

You can generate a downloadable package of physical project artifacts such as Tracker Artifacts, Documents, Source Code Repositories (only Git and Subversion are supported), File Releases, and Binaries (only Nexus binaries are supported) from an approved Baseline or a Project Baseline and share the package with your stakeholders.

External public Git repositories can now be imported into TeamForge from the Code Browser UI.

Once you have your Nexus server set up, install the TeamForge-Nexus integration plugin.

Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.

With TeamForge—Nexus integration enabled, you can create one or more binary repositories and link them to your project.

The Digital.ai TeamForge Maven Deploy Plugin can be configured to post binary artifact deployment information to TeamForge via the Webhooks-based Event Broker (WEBR) for end-to-end traceability.

Use the host:SERVICES and the host:PUBLIC_FQDN tokens to define the services and domain names of your TeamForge site respectively. You can also have unique service-specific FQDNs for services such as Subversion, Git, mail, Codesearch and so on.

Here's a list of TeamForge `site-options.conf` tokens and configuration information.

TeamForge's native Webhooks-based Event Broker replaces EventQ as the default event broker to support TeamForge integration with TestLink. EventQ-based TeamForge—Testlink integration is no longer supported.

For Subversion and Git repositories, you have the option to use the TeamForge code browser which is turned on by default while integrating the source code server.