We’re happy to announce the immediate availability of GForge 23.0. This release is primarily a bug-fix release with a fair number of new features included!
Key Highlights in 23.0
SSO – Many improvements to our Single Sign-On support.
Security – Fixed a number of security vulnerabilities found in an audit.
Angular 14 Migration – While this doesn’t impact our customers in any obvious way, this is a large undertaking to pay some technical debt.
Releases – We’ve made a number of improvements to the visibility of releases, particularly in the case where you want to prevent a release from being accessible but want to keep all its associations to tickets, etc intact.
We’re happy to announce the immediate availability of GForge 22.2. This release is primarily a bug-fix release with a fair number of new features included!
Key Highlights in 22.2
HTTP/2 Support added – To learn more about the benefits of HTTP/2 here.
Tickets can now be filtered based on whether or not they have attachments.
Tickets can also be filtered based on they have a parent and/or child ticket.
Users can now react (thumbs up/down) on comments.
File Uploads – Fixed the issue where file uploads would die after 20MB regardless of the configured value.
REST API – Updated missing and incomplete documentation.
Site Admin – Searching projects by name has been improved.
Browse Projects – Users could only search for projects they knew about in prior GForge versions. This version allows users to browse all projects they have access to.
Looking Ahead to 23.0
We want to point out some important changes coming in GForge 23.0 (spring 2023). This version will add support for Kubernetes and it is going to have a new ticket editor. We’d love to get some feedback on the new editor before it is released so if you would like a sneak peak you can register a test project or you can send us an email and we can shoot over some screenshots. Additionally, for you users interested in Kubernetes, if you have any specific questions or would like to beta test this in your environment we’d love to hear form you. Just contact us at feedback@gforgegroup.com.
GForge v22.1 is primarily a bug fix release with a fair number of new features included!
GForge Now Supports Windows
Over the years we have been asked numerous times if GForge can run under windows. The complexities of GForge’s collaboration features had tied us completely to Linux. When we released our first version of GForgeNext under Docker we saw a future that might eventually include Windows. Today is that day.
You’re probably wondering why now when Docker has been out for years. The key lies in GForge’s interactions with the host filesystem and now with WSL (Windows Subsystem in Linux) those final hurdles have been dealt with.
GForge Includes Podman Support
We’re not here to ding Docker, it’s served us well for many years. That said, their approach to virtualization has caught the eye of many in the security world and because of that Podman was born. Podman was built to do everything Docker does but addressing many of the security concerns in Docker. With all that in mind, GForge now support Podman in addition to Docker. As important, your choice of Podman vs Docker is independent of your choice of Linux vs Window+WSL.
Other Key Highlights in v22.1
Tickets
Tickets can now be filtered based on whether or not they have attachments.
Tickets can also be filtered based on they have a parent and/or child ticket.
Users can now react (thumbs up/down) on comments.
Chat – We have added a few useful macros. For example you can search StackOverflow, Microsoft, and Wikipedia. You can also send private messages to a specific user. To see all of the supported macros just type “/help”.
Markdown – Anywhere GForge supports markdown now includes support for tables.
Version Control – All the repository homepages now include a link to a GForge-specific FAQ addressing common issues our customers have using Git, SVN and CVS
GForge v22.0 is primarily a feature release with a fair number of bug fixes included
Introducing Planning Boards
You already know GForge allows you to plan, distribute and track your work. With GForge you are already able to plan a release, break the release down into manageable sprints and assign work to your team. Planning Boards gives our existing kanban features a big shot in the arm by allowing you to create boards and quickly begin moving work around. The image below gives an example of moving tickets in a release into sprints and assigning the work out.
We’ll be sharing a deeper dive covering Planning Boards on here and on our YouTube Channel.
Other Key Highlights in v22.0
Project Navigation – We’ve made a big improvement to the project navigation bar. The new version now groups related project features and adds labels. The prior version assumed you knew the icon for each feature).
Tickets
There are cases where you want to have tickets in one project reference commits made in other projects. The commits tab in the ticket editor will now show the commit data.
There is a printable version of a ticket.
Documents – You can now add tags to documents.
Version Control – There’s been a number of improvements:
For Git repositories we’ve replaced the “master” branch with the name “main” (this only applies to new projects)
We’ve added a script to convert CVS repositories to Git
Some minor bug fixes (see ChangeLog below for more information)
Admin:
We now have the ability to share a software bill of materials (SBOM) listing all the libraries and packages GForge uses in each release. You can request the SBOM by email feedback@gforgegroup.com
Projects can now to exported from one GForge instance and imported into another GForge instance assuming both instances are running the same version of GForge.
GForge v21.2 is primarily a bug fix release. You will notice that there aren’t that many tickets in this release because we continued to focus on core technologies (libraries, etc) that needed to be upgraded. Specifically, a lot of energy was focused on upgrading to Angular 1.6.
Highlights in GForge 21.2
OIDC Support – GForge now supports OIDC and works with SSO systems like Okta.
Site Search – When inside a project, the navbar search now allows a way for you to search outside the current project (i.e. across all your projects and their artifacts)
Reports – There’s a couple of new reports for Site Administrators including a Cron History and Audit Log Reports.
Site Administration – We’ve added data retention settings for purging cron history and activity log data.
Kanban – The user interface has been completely revamped when working with tickets in Kanban view.
SVN – There’s been a number of improvements. The most notable is we’ve improved the speed of SVN operations (especially repositories with a lot of files). Also for repositories using SSH we fixed an ACL issue.
Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.
Check back soon as we’ll be sharing our plans for the rest of 2022!
Hello and welcome to another GForge How-To. In this series, we teach you tips and tricks to help you maximize your experience with GForge. This time, we’re talking about the Project Admin SCM page, and the settings available there.
The settings on this page are as follows:
Access Method toggles between accessing your SCM over SSH or HTTPS; SSH is the default.
Git LFS support enables and disables Git LFS support.
Code search indexes the code in your promotion model branches for searching. Code tagging indexes the project’s code to tag related tracker items and user commits.
Enable Anonymous Read allows SCM to be read by anyone, including anonymous users.
Associate Tracker Items has three choices: you can keep commits unattached to tickets, attach them when you want, or require that every commit associates to a ticket.
Restrict Tracker Item Associations requires commit ticket IDs to reference a ticket in the project.
Commit Notifications sends an email to everyone monitoring the SCM repo when someone commits.
Validate Committers ensures that each commit is pushed by an authenticated user.
Validate Assignment automatically assigns a specified ticket to a committer.
Access Text shows any text you type in on the main SCM repo page.
Browse Text shows the text you type on the SCM Browse page.
As you can see, the SCM settings available to project admins can help in customizing and correcting GForge to fit any project’s needs. If you have any questions or feedback about the Project Admin SCM page, you can send us a message here. Make sure to check your inbox for more GForge How-To’s in the future!
Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.
Check back soon as we’ll be sharing our plans for the rest of 2021!
We’re happy to announce the immediate availability of GForge 20.2. This is largely a bug fix release with a handful of new features.
Highlights in GForge 20.2
Large File Uploads – GForge now implements chunked uploading which allows you to upload files in up to gigabytes in size, if desired. This has been implemented anywhere file uploads are allowed but specifically for Docs, attachments to tickets, releases and for importing SVN dump files. (Note: there are a few settings you must set to achieve this).
Docs – You can now upload and an extract a zip. This is great for moving a large number of files.
French Translation – 20.2 now support French in addition to English and Spanish.
Organizations – There have been a large number of improvements to organizations. Key changes include:
Organization homepage gets a facelift which includes showing all the projects in the org and GForge shows how many users in your organization and the disk usage across all projects.
You can create a project from the organization homepage which ensures the project is properly related to the org.
WYSIWYG – Now uses local storage to help prevent loss of edits.
PostgreSQL 13 – GForge now support PostgreSQL 13. The upgrade process will give you the option of making the switch or staying with PostgreSQL 9.
DevOps – A number of important improvements to the GForge environment have been made to improve overall availability. These changes will be transparent to you but if you contact us we’d be happy to share them.
Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we have officially dropped support as of October of 2020. We will still answer any support questions about older releases but we will not be providing any future code updates or patches. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.
Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.
We’re happy to announce the immediate availability of GForge 2020 (aka 20.0). This is a large feature release and also includes a number of bug fixes.
Highlights in GForge 2020
Zoom Integration – You can now create Zoom meetings and invite project team members to the meeting right from GForge (SaaS only).
oAuth Support – You can now log-in to GForge using your Google account (additional oAuth providers will be coming).
Auto Tagging – When users push commits, GForge will now automatically tag the user, project and ticket with any technologies identified in the commit (e.g. Java, XML, JavaScript).
Code Search – GForge now indexes Git and SVN repositories allowing you to search your codebase right from GForge.
Git LFS – GForge now supports Large File Storage (LFS) for Git repositories.
DKIM Support – For on-premises customers, GForge now supports DomainKeys Identified Mail (DKIM) which adds additional email security and SPAM protection.
Just a reminder for customers still running GForge Advanced Server (v6.4.5 and prior) we are planning on officially dropping support in October of 2020. Please feel free to reach out to us for a free consultation on the planning and upgrade paths.
