The following pages are tagged with
Title | Excerpt |
---|---|
Activity Sources and Associations | EventQ provides a mechanism, allowing you to add relevant project tools to the TeamForge project context. This is accomplished through "sources", which repre... |
Approve or Reject Repository Delete Requests | SCM system maintenance requests (such as a repository delete request) must be approved (or rejected) by an administrator. |
backup-rb-data.py | The backup-rb-data.py script is used to back up the Review Board application data. |
Back up and Restore TeamForge | Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site. |
Change the scmviewer Password | It is recommended to change the scmviewer password after installing TeamForge. |
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. |
Customize TeamForge | You can redesign some aspects of your site to suit your organization's needs and preferences. |
db.py | The db.py script can be used to dump and restore a PostgreSQL database. |
domain_change_db.py | The domain_change_db.py script handles all the steps required to change the domain name in the site database. It does not change anything in the file system. |
domain_change_webr.py | The domain_change_webr.py script is used to change the domain name or host name of the subscriber in the TeamForge Webhooks-based Event Broker database. |
Edit SCM Integration Details | You can move or reconfigure a source control server without having to reintegrate the server into TeamForge. |
etl-client.py | The etl-client.py script allows you to access the Extract, Transform and Load (ETL) scheduler and check the status of the jobs configured. The script also su... |
EventQ End of Life | EventQ is no longer supported and is completely removed from TeamForge starting from TeamForge 20.0. If you have been using EventQ on your site, you must con... |
Generate SSL certificates | To use HTTPS for web traffic, you will need to obtain a valid Apache SSL certificate. |
Install the TeamForge Webhooks-based Event Broker | This page walks you through the installation procedure for TeamForge Webhooks-based Event Broker (WEBR). |
Install Nexus | TeamForge supports only Nexus 3 integration. This page walks you through the installation procedure for Nexus 3 and upgrade procedure from Nexus 2 to Nexus 3. |
Install or Upgrade the TeamForge—Nexus Integration Plugin | Once you have your Nexus server set up, install the TeamForge-Nexus integration plugin. |
FAQs on Install/Upgrade/Administration | These are some of the frequently asked questions on the installation, upgrade, and site admin related activities in TeamForge. |
Integrate an Unmanaged CVS Repository with TeamForge | Here's how you can integrate an unmanaged CVS repository with TeamForge. |
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... |
TeamForge Load Balancing Setup | Installing TeamForge in a Load Balancing setup ensures distribution of processing load between multiple servers. The HAProxy Server hosts the HAProxy service... |
login-config.xml | This is the sample application-policy block that you can copy into your login-config.xml file to support LDAP authentication. |
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 ... |
Create a Single Cluster for Both Database and Datamart | The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server has been deprecated in TeamForge 17.11. |
Upgrade TeamForge on New Hardware in a Distributed Multi-host Setup | You can upgrade TeamForge on new hardware in a distributed multi-host setup. |
Upgrade TeamForge on New Hardware with All Services on a Single Server | You can upgrade TeamForge on new hardware with all services on a single server. |
pebble-app.xml | The pebble-app.xml file, also known as the Pebble application configuration file, contains the text that the Pebble application displays in the TeamForge use... |
pebble-dep.xml | The pebble-dep.xml file, also known as the Pebble deployment configuration file, contains the data that Pebble needs to interact with the TeamForge site. |
Plan Your Installation / Upgrade | Plan your installation or upgrade setup, hardware and software requirements and so on before you begin. |
Project Templates - Install, Update, Enable and Disable | Provide sample projects to help users get started quickly. TeamForge comes with a sample template useful for agile development projects. Site administrators ... |
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... |
Schedule Data Extraction for Reporting | Set the interval at which you want yourTeamForge site's data extracted to the datamart from which reports are generated. |
Installation Requirements | Here's what it takes to install and run TeamForge and other integrations supported by TeamForge. |
restore-data.py | 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 repo... |
restore-rb-data.py | The restore-rb-data.py script is used to restore the Review Board application data from the backup directory. |
Upgrade TeamForge on the Same Hardware in a Distributed Multi-host Setup | You can upgrade TeamForge on the same hardware in a distributed multi-host setup. |
Upgrade TeamForge on Same Hardware with All Services on a Single Server | You can upgrade TeamForge on the same hardware with all services on a single server. |
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... |
SearchReindex.py | The SearchReindex.py script allows you to reindex the entire TeamForge data. |
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 Networking for TeamForge | After installing the operating system, prepare the networking connections and configuration for your TeamForge site. |
Set up SELinux | If SELinux is active on the server that runs your TeamForge site, configure it to allow the services that TeamForge requires. |
Create a Site-wide Broadcast | To say something to everyone who uses your site, post a site-wide broadcast message. |
Create a Site-wide Broadcast | To say something to everyone who uses your site, post a site-wide broadcast message. |
TeamForge Services and Domain Configuration Tokens | 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 s... |
Site Options Change Log | Change log of site-options.conf tokens. |
TeamForge site-options.conf Tokens | Here's a list of TeamForge `site-options.conf` tokens and configuration information. |
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. |
task-data-export.py | Tasks, as a component, is no longer supported and was completely removed from TeamForge 20.1 and later. The task-data-export.py script is used to back up the... |
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... |
The teamforge.py Script | Use the teamforge.py script to deploy and undeploy services, start and stop services, verify the status of services, verify the application environment, boot... |
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... |
update_artifact_textflex_carriage_return.py | If you have been updating your tracker artifacts both via the UI and CLI/SOAP, you may optionally run the `update_artifact_textflex_carriage_return.py` scrip... |
Upgrade Review Board | Use these instructions to upgrade Review Board to a latest build. |
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. |
[]:
[]: