- Released on: April 30, 2019
- GA Version: 19.1.272
Here’s the list of what’s new with the TeamForge Baseline feature.
Save a Draft of Baselines
You can now save a draft of the baseline that’s being created. Use the Save as Draft button in the Create Baseline and Create Project Baseline pages to save a draft of the baselines that are being created.
Once saved, you can edit or delete draft baselines at a later point in time.
You can view the list of draft baselines by selecting Draft from the left navigation menu. The total number of draft baselines is shown next to the Draft option within parenthesis
Import Source Code and Binary Repositories from Project Baselines
Source code and Binary repositories, included in a Project Baseline, can now be imported into projects that are created from the Project Baseline.
When you create a new project from a Project Baseline that include source code/binary repositories, the Create New Project page has the following options:
Include Source code: This option shows up if the Project Baseline includes source code repositories.
Include Binaries: This option shows up if the Project Baseline includes binary repositories.
Include External Baselines in Baseline Packages
External Baselines, included in a Baseline or a Project Baseline, are now included as part of the Baseline/Project Baseline package. Such External Baselines, if included, are available as TAR files in the baseline package.
Group Baselines Awaiting Review
You can now go to the Pending Review Baselines page to view a list of baselines awaiting review. The number of baselines awaiting review is shown next to the Pending Review link within paranthesis
index.pdf File in Baseline Package
index.pdf file (created when you generate a baseline package) replaces the
index.html file to better handle large volume of data associated with baselines that have a large number of objects.
References to External Baselines in Projects Created from Project Baselines
A new tracker, External Baselines, is created automatically on all the projects that are created from Project Baselines that include one or more external baselines. The External Baselines tracker consists of as many artifacts as the external baselines that were included in the Project Baseline.
The description of these artifacts include a link (in the format “baseline id:baseline name”) to the External Baseline.
Click this link to view the External Baseline from within its native project.
Auto Refresh Baselines and Packages Lists
The baselines list page is automatically refreshed every minute if baselines (with the status Creation In Progress) are being created in the background.
Similarly, the packages list (Packages tab of the View Baseline and View Project Baseline pages) is automatically refreshed every minute if packages are being created in the background.
You can continue to use the Click to refresh link to manually refresh the list of baselines and packages.
Group Binary Repositories by Nexus Version
The Nexus binary repositories are now grouped by the Nexus version (Nexus 2 or Nexus 3) on the Create Baseline, Create Definition, and Project Baseline Definition pages to help you quickly identify and select the required repositories.
Here’s the list of Tracker enhancements.
Drag and Drop Files to the Add Attachments Dialog box
In addition to the Status/Comments tab of the View Artifact page, you can now drag and drop one or more files to the Add Attachments dialog box of the Attachments tab to attach files to an artifact.
Mandatory Fields Without Default Value
Unlike in the past, you can mark user defined Text Entry and Select User(s) flex fields as “Required” without having to select a default value. Such flex fields are left blank for users to provide a value while creating or updating an artifact (on the Create Artifact and the View Artifact pages).
View the Progress of File Uploads
When you attach files to an artifact, a file upload progress indicator shows up on the Create Artifact and View Artifact (including the Add Attachments dialog box) pages.
GitAgile™—Enterprise Version Control
TeamForge-Git Integration 19.1.6-2.15.13 is based on Gerrit version v2.15. Read more to know what’s new.
Mass Configuration of Repository Policies Within a Project
You may often want to apply a specific set of policies to more than one repository. You can now select multiple repositories within a project and apply your policies in one go.
For more information, see Mass Configuration of Repository Policies.
Quality Gates for Protected Branches
Quality gates can now be enabled for protected branches in a TeamForge project. Just create a change detail filter and set the branch pattern to annotation “@protectedBranches” in the
rules.pl file. This filter reads all the protected branches and enforces the configured submit rule to these branches. For example, you can simply create the following rule to block any submission to protected branches.
Tree View of Git Tags
A new tab, Tree View, has been added to the Tags tab to display the tags of a given Git repository in a tree structure. Select a tag from the new tree view to view its details on the right side of the tree view. Tags are slash-delimited in breadcrumbs. In the following example, tag
220.127.116.11 can be found by expanding the
Bug Fixes in TeamForge-Git Integration 19.1.6-2.15.13
- Sorting the repository list was limited to the current page in cases where the list of repositories spans multiple pages, which is now fixed.
- Fixed an issue that prevented anonymous users of public projects from viewing/accessing source code repositories.
Also see: Bug Fixes in Gerrit 2.15.13.