43 docs tagged with "ctf_20.2"

When a user asks for access to an unmanaged SCM server, an administrator must approve or reject the request.

Create associations between code commits and other Digital.ai TeamForge items, such as tracker artifacts or documents, to help define relationships, track dependencies, and enforce workflow rules.

You can connect tracker artifacts with other Digital.ai TeamForge items such as documents or topics. Creating associations between items enables you to define relationships, track dependencies, and enforce work flow rules.

To control who can access your project, consider the purpose of your project and the appropriate type of user.

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.

When you delete a repository, a request is submitted to the administrator for approval.

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

You can enable caching for TeamForge Baselines in case you have a large number of binary (Nexus) repositories. Caching Nexus repositories enables fast loading of Nexus repositories when you try to create or modify the binary filter criteria for baselines or baseline definitions.

TeamForge enables user authentication both against its internal database and against other external authentication services such as LDAP, OAuth, and SAML. This section provides information on how to set up TeamForge for authenticating its users against these services.

These are some of the frequently asked questions on the installation, upgrade, and site admin related activities in TeamForge.

The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings.

Memcached caches Subversion (SVN) authentication and authorization information and serves the mod_authnz_ctf module's authentication and authorization requests thereby reducing the number of SOAP calls, which in turn results in less load on the TeamForge Application Server.

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

Install Review Board on your site before you can make it available as an integrated application to project managers on your TeamForge site.

Distributed setup with TeamForge, Database (including Datamart), Review Board, SCM (Subversion and Git), Code Search and Baseline installed on separate servers.

You can install TeamForge with its database installed separately on an external PostgreSQL server such as AWS RDS/Aurora.

Distributed setup with TeamForge and Oracle Database (including Datamart) installed on separate servers.

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

As a project group administrator, you know that the key to any user's access to the project group and the projects belonging to the group, is in the role you assign to the user. You can do almost all the role-related activities with project groups that you could do with individual projects.

To facilitate troubleshooting, keep an eye on key data about your Digital.ai TeamForge site.

Plan your installation or upgrade setup, hardware and software requirements and so on before you begin.

The restore-data.py script restores the compressed data from the named source directory and deletes any existing data. By default, the TeamForge and the reporting database are backed up to the destination directory. If reporting is disabled, only the TeamForge database is backed up.

TeamForge provides a unified code review experience as it supports both Pull Request and Gerrit single-commit reviews.

On sites distributed across multiple geographic locations, Git Replica Servers are local and remote mirror servers that can provide up-to-date copies of the central repositories. If set up, Git Replica Servers can address load balancing and fetch performance issues. You can set up one or more Git Replica Servers (also referred to as slave or mirror servers) with TeamForge 8.1 and later.

The Planning Board is an important tool for your TeamForge project's agile planning activities. It enables you to plan and monitor the features that are required in each sprint (or iteration), and assign them from the product backlog to specific sprints.

If SELinux is active on the server that runs your TeamForge site, configure it to allow the services that TeamForge requires.

Webhooks can be configured both at a project level or for select repositories. Once set up, SCM events such as commit and merge are published to the Webhooks for other applications to consume.

Change log of site-options.conf tokens.

These are some of the frequently asked questions on SCM related activities in TeamForge.

Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code.

What is a Baseline Definition?

Installing TeamForge in a Load Balancing setup ensures distribution of processing load between multiple servers. The HAProxy Server hosts the HAProxy services that are required for the load balancing function.

System administrators can use logs to debug problems and ensure that the application is performing to expectations.

TeamForge ETL jobs can extract transform and load the TeamForge tracker association data to the datamart for reporting purposes.

TeamForge supports integration with Git, a distributed version control tool powered by Gerrit.

Use these instructions to upgrade Review Board to a latest build.

You can upgrade TeamForge on new hardware in a distributed multi-host setup.

You can upgrade TeamForge on new hardware with all services on a single server.

You can upgrade TeamForge on the same hardware with all services on a single server.

You can upgrade TeamForge on the same hardware in a distributed multi-host setup.

Distributed setup with TeamForge, Oracle Database (including Datamart) and EventQ installed on separate servers.

By setting up the SAML+LDAP IdP, TeamForge users can reap the benefits of both SAML and LDAP authentication mechanisms in a unified manner. With SAML+LDAP authentication, while SAML enables TeamForge users to access web applications, the LDAP authentication supports user authentication required for CLI applications. For example, if a user performs a source code commit in Git/SVN repository, the user can get authenticated via LDAP.

TeamForge supports integration with LDAP. Once integrated with LDAP servers, TeamForge can use LDAP credentials for user authentication.