The following pages are tagged with
| Title | Excerpt |
|---|---|
| Approve or Reject an Unmanaged SCM Server Access Request | When a user asks for access to an unmanaged SCM server, an administrator must approve or reject the request. |
| Approve or Reject a Source Control Repository Request | When a user requests a source code repository on a source control server for which you have required approval, a TeamForge administrator must approve the req... |
| Approve or Reject Repository Delete Requests | SCM system maintenance requests (such as a repository delete request) must be approved (or rejected) by an administrator. |
| Authenticate your Integrated Application with TeamForge | To help third party developers write integrated applications, CollabNet provides an SDK. |
| Change the scmviewer Password | It is recommended to change the scmviewer password after installing TeamForge. |
| Control Your Code Review Policy | You can control all Gerrit Code Review features directly from TeamForge by specifying a code review policy. |
| Connect to a Subversion Edge Console | When a Subversion Edge server has been converted to a SCM Integration server in TeamForge, you can log into its management console from within TeamForge. |
| create_webhook_event.py | This script creates an event, a publisher (with the Webhook URL), and a subscriber in TeamForge Webhooks-based Event Broker for a specified application. |
| Edit SCM Integration Details | You can move or reconfigure a source control server without having to reintegrate the server into TeamForge. |
| Integrate or Link External Applications | If your site's users need access to an application or web site that is not part of TeamForge, you can make it available by linking or integrating from within... |
| Integrate or Link External Applications to Projects | You can make it easy for project members to use a wide variety of applications and sites from within TeamForge. |
| TeamForge-Git Integration | TeamForge supports integration with Git, a distributed version control tool powered by Gerrit. |
| TeamForge-Git Integration Reference | This topic discusses the mappings between TeamForge and Gerrit, Gerrit access rights, directory structure, connectivity, logs and configuration properties, a... |
| History Protection | History protection archives rewritten changes and keeps backups of deleted branches. If history changes occur, an immutable backup `ref` is created in the re... |
| Add Binaries to TeamForge Projects | When TeamForge Site Administrator has made the Binaries application available, Project Administrators can add it as one of their project tools. |
| Add Review Board to TeamForge Projects | When TeamForge Site Administrator has made the Review Board application available, Project Administrators can add it as one of their project tools. |
| Install the TeamForge Webhooks-based Event Broker | This page walks you through the installation procedure for TeamForge Webhooks-based Event Broker (WEBR). |
| Install or Upgrade the TeamForge—Nexus Integration Plugin | Once you have your Nexus server set up, install the TeamForge-Nexus integration plugin. |
| Integrate a Source Code Server | A site must have one or more servers to handle source code repositories and users. The source code server can be the same server as the application server or... |
| Integrated Application References | Here is some stuff you may need to know to work with integrated applications. |
| Integrate Tools Using Post-submit Webhooks | Post-submit webhooks lets you integrate TeamForge with other heterogeneous applications. Speaking of TeamForge trackers, post-submit webhooks are meant for p... |
| TeamForge Binary Integration Overview | An important aspect of the end-to-end development lifecycle is the creation and storage of software packages that are often binary artifacts. In the Java wor... |
| Manage Replicas | A replica server in TeamForge is a Subversion Edge server that replicates the content of an existing core SCM integration server. |
| Move a Source Code Repository | When the existing code base for an application may need to be managed by a different team or project, you can move the source code repository from the first ... |
| QUEUE Event Type | Queue type events are provided within the TeamForge Webhooks-based Event Broker to support client server processing and http based load balancing. It provide... |
| Installation Requirements | Here's what it takes to install and run TeamForge and other integrations supported by TeamForge. |
| Scripts and Filters in the TeamForge Webhooks-based Event Broker | The TeamForge Webhooks-based Event Broker v4 engine provides powerful scripting using JavaScript and custom JSON filtering capabilities that provide customiz... |
| Set up Git Replica Servers | 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 ... |
| Set up LFS | Git Large File Storage (LFS) is a Git extension for versioning large files. Git LFS replaces large files such as audio samples, videos, datasets, and graphic... |
| SYNC Event Type | A SYNC event type within the TeamForge Webhooks-based Event Broker is called as a Pre-Submit event in TeamForge. Only one subscription is allowed for this ev... |
| Synchronize TeamForge Source Control Integrations | Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code. |
| TeamForge—Jenkins Integration Using the Webhooks-based Event Broker | TeamForge Webhooks-based Event Broker supports TeamForge—Jenkins integration. A new Jenkins integration plugin v2.0.6 is used to integrate TeamForge with Jen... |
| TeamForge—JIRA Integration Using the Webhooks-based Event Broker | TeamForge Webhooks-based Event Broker supports TeamForge-JIRA integration. A new JIRA integration plugin version 1.1 is used to integrate TeamForge with JIRA... |
| TeamForge—TestLink Integration Using the TeamForge Webhooks-based Event Broker | TeamForge's native Webhooks-based Event Broker replaces EventQ as the default event broker to support TeamForge integration with TestLink. EventQ-based TeamF... |
| TOPIC Event Type | A TOPIC event type within the TeamForge Webhooks-based Event Broker is called as a Post-Submit event in TeamForge. The message of this event type is delivere... |
| TeamForge WebConnect UIs | TeamForge 20.3 brings you intuitive UIs for TeamForge WebConnect (also known as TeamForge WEBR). You can now use the UIs to accomplish tasks such as creating... |
| TeamForge Webhooks-based Event Broker Overview | TeamForge Webhooks-based Event Broker is a webhook driven integration broker, delivered as a free technical microservice along with TeamForge. It is a replac... |
| TeamForge Webhooks-based Event Broker Settings | The TeamForge Webhooks-based Event Broker related settings are discussed in this page. |
| Integrate Tools Using WEBR Orchestration Scripts | WEBR Orchestration is a webhook integration capability that lets you integrate tools using orchestration scripts. |