GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Scheduled maintenance will be performed on GitLab September 12th between 19:00-23:00

GitLab will be upgraded to version 17 on September 12th. If you own a GitLab Runner, and your Runner is not created recently, please verify that the token is up to date or else the Runner will stop working after the upgrade. This message is only meant for GitLab Runner owners and users of frequent users of CI/CD. Guide for upgrading the Runner to work on GitLab 17 or to verify if your token is still valid: https://dsn.pages.sintef.no/help/8_gitlab/gitlab_runner/

Admin message

Admin message

Admin message

energy_code_colloquium