58 docs tagged with "upgrade"

SCM system maintenance requests (such as a repository delete request) must be approved (or rejected) by an administrator.

Save a copy of your TeamForge site's data to a location from where you can quickly retrieve it to your TeamForge site.

The backup-rb-data.py script is used to back up the Review Board application data.

It is recommended to change the scmviewer password after installing TeamForge.

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.

The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server has been deprecated in TeamForge 17.11.

To say something to everyone who uses your site, post a site-wide broadcast message.

This script creates an event, a publisher (with the Webhook URL), and a subscriber in TeamForge Webhooks-based Event Broker for a specified application.

You can redesign some aspects of your site to suit your organization's needs and preferences.

The db.py script can be used to dump and restore a PostgreSQL database.

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.

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.

You can move or reconfigure a source control server without having to reintegrate the server into TeamForge.

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 supports triggering jobs manually.

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 consider a few things when you upgrade to TeamForge 20.0 or later.

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

To use HTTPS for web traffic, you will need to obtain a valid Apache SSL certificate.

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.

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

This page walks you through the installation procedure for TeamForge Webhooks-based Event Broker (WEBR).

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

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 a separate server.

This is the sample application-policy block that you can copy into your login-config.xml file to support LDAP authentication.

A replica server in TeamForge is a Subversion Edge server that replicates the content of an existing core SCM integration server.

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 project into the other one.

The pebble-app.xml file, also known as the Pebble application configuration file, contains the text that the Pebble application displays in the TeamForge user interface.

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 or upgrade setup, hardware and software requirements and so on before you begin.

Provide sample projects to help users get started quickly. TeamForge comes with a sample template useful for agile development projects. Site administrators and project managers can use this template to jumpstart a project without a lot of manual setup steps.

Queue type events are provided within the TeamForge Webhooks-based Event Broker to support client server processing and http based load balancing. It provides a robust mechanism for invoking jobs asynchronously and receiving the response through callbacks.

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.

The restore-rb-data.py script is used to restore the Review Board application data from the backup directory.

Set the interval at which you want yourTeamForge site's data extracted to the datamart from which reports are generated.

The TeamForge Webhooks-based Event Broker v4 engine provides powerful scripting using JavaScript and custom JSON filtering capabilities that provide customization capability to products through webhooks.

The SearchReindex.py script allows you to reindex the entire TeamForge data.

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.

After installing the operating system, prepare the networking connections and configuration for your TeamForge site.

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

Change log of site-options.conf tokens.

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 event type.

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

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 Tasks data.

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.

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 Webhooks-based Event Broker is a webhook driven integration broker, delivered as a free technical microservice along with TeamForge. It is a replacement for the event brokering aspects of the now deprecated EventQ product.

The TeamForge Webhooks-based Event Broker related settings are discussed in this page.

TeamForge Webhooks-based Event Broker supports TeamForge—Jenkins integration. Jenkins integration plugin is used to integrate TeamForge with Jenkins using TeamForge 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 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 TeamForge—Testlink integration is no longer supported.

Use the teamforge.py script to deploy and undeploy services, start and stop services, verify the status of services, verify the application environment, bootstrap or migrate data, back up and restore data and do much more.

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 delivered to all the subscription endpoints.

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` script to fix the inconsistent CRLF characters that were found to exist in the text flex field data.

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.