This information is specific to the 2020.3.1 Flow Enterprise Server release.
In this article
- This upgrade requires Postgres 12 and utilizes KOTS, which is an embedded Kubernetes stack.
Note: Google Cloud SQL is currently in beta for Postgres 12, and will be supported in a future release.
- You must upgrade to Flow Enterprise 2020.2.2 before upgrading to 2020.3.1. Flow Enterprise 2020.2.2 is the first release requiring Kubernetes. If you're a current Flow Enterprise customer and need to migrate to 2020.2.2, please reach out to your Pluralsight contact or email Pluralsight Support (opens email form) to discuss upgrading to 2020.2.2. At this time, customers cannot upgrade to 2020.2.2 without assistance from the installation team.
Important: When Flow starts after the upgrade, your commit-based reports will be missing commits for a period of time. This will resolve itself as the commit preprocessor completes its first run. The preprocessor runs every two hours, so you should have your data back within three hours. This missing commit data is a one-time process. Check out more information on troubleshooting the preprocessor.
- If you intend to use SSO, please ensure you have a fully-formed URL for an entity ID. This is a requirement with the upgraded version of the underlying pip install pySAML dependency.
- Before you begin the installation, make sure to gather all required information and read our system requirements carefully.
- This release introduces additional data structures for storing your commit data. These require an incremental increase to your database storage. We do not expect this to be material—likely between four and ten percent of your scm_commit tables—but this is a good time to verify your database has plenty of space. The initial load of these tables uses TEMP table space heavily, so it's also important to verify you have adequate space there.
Features and major changes
- We've added a process to better prepare your commit data for reporting. This will increase the load speed of Code Fundamentals, Project Timeline, Snapshot, Daily Update, and Retrospective. More information has been added to the Repo settings page to show you the status of this process.
- Now pair programming lets you give credit for group work. You can split the work between contributors or give each contributor full credit.
- You can disable industry benchmarks by default for your organization for each of the Fundamentals reports. Read more about report preferences.
- Download a CSV of your team import results. You can also get a CSV download of your current team structure and upload a team CSV via our API.
- Now you can use the Vendor URL page to configure, review, and modify your Vendor URLs if your self-hosted git host didn't provide the correct URL to Flow. Check out our article on managing integrations to learn more.
- The Alias column of the User List now shows you a list of email addresses associated with a user to help you identify your users when they've used more than one email address.
- Username/password authentication has been removed as an option for GitHub and GitHub Enterprise integrations, since GitHub will discontinue password authentication on November 13, 2020. Existing integrations authenticated via password will continue to work, but will need to be updated before GitHub’s deprecation date. Read more about the deprecation and how to update your integrations here.
- Import teams from your GitHub Enterprise account.
- Now you can bulk auto-import all repo groups for an integration. Both existing repo groups and any newly imported repo groups will be set to auto-import.
- Flow used to have a Manage users and teams permission, That permission has been split into three more specific permissions: Manage user invites, Manage user permissions, and Manage users and teams. This change lets people manage their users and teams without requiring them to have full administrative access. Existing users and roles that had the Manage users and teamsmpermission will automatically receive Manage user invites and Manage user permissions,with this update. Learn more about administrative permissions.
Patch release updates
- 2020.3.1-1: Removed reporting of 500 errors as a result of initial commit preprocessor running. These errors occurred during the first two hours after upgrade.
- 2020.3.1-2: Fixed data migration handling issue for upgrades, fixed log rotation, and added settings to configure session timeout.
- 2020.3.1-3: Fixed settings load error.
- Enhancements to SSO sign-in page
- Exposed and defaulted web server configurations to help resolve consistent 502 errors when accessing the app
- Added a configuration to restrict data ingestion to the last three years
- Enabled TLS on the prometheus, alertmanager, and grafana endpoints
- Updated email reports to include the Flow logo
- General system availability improvements.
- Combined head/tail process for improvements to performance of ingestion for large organizations
- Marked PR projects as tail complete when there are no PRs to process
- Improved performance for BitBucket Server
- Removed automatic/periodic tail tracking reset
- Improved repo space handling to reduce amount of repo storage needed
- Performance improvements to User Merge API
- Allowed users to edit profile name when login is disabled
- Changed PR/Tickets processing method to reduce load on JVM memory consumption
- Miscellaneous fixes to Admin Alerts email
- Enhancements to thread management in PR and Ticket workers
- Improvements to exception handling in many Java pods to reduce pod restarts
- Improvement to memory management of large files inside of the Advanced Outlier detection pod
- Updates to PR processing to properly set the Closed at date for some PR vendors
- Resolved issue with the commits.agg endpoint
- Change to allow for log file rotation based on maxsize in addition to daily. This reduces the ability of the application log file to grow too large.
- Updates for new embedded databases
- Fixed a PR processing issue by properly handling deleted repos
Resolved issues and miscellaneous updates
- Fixed an issue with user unmerging and errors when trying to merge users
- Regular expression tester with pull requests to exclude not displaying pull requests
- Calendar date picker showing Last year by default
- Repository picker not showing when a tag is selected
Miscellaneous updates and fixes
- Improved experience for error pages
- Emails from Flow come from an updated Pluralsight email address
- Alias auto-merging is now case-insensitive
If you need help, please contact Pluralsight Support.