Today we release GitLab CE, GitLab EE and GitLab CI 7.9.2.
This release only affects GitLab CI. If you do not use GitLab CI, you do not need to upgrade to GitLab 7.9.2.
Versions affected: GitLab CI 7.9.1
Versions fixed: GitLab CI 7.9.2
In 7.9.1 (previous release) we added a project setting option "Allow shared runners".
After upgrading to this version all existing CI projects have this option enabled, so that all projects can be served by shared runners (runners which added by admin).
This introduced an issue: shared runners do not remove projects from the temporary directory because of performance reason. This means that by creating a special job script it is possible to get access to the repository of any project which has been ran on the shared runner.
This fix disables the option "Allow shared runners" in project settings for those projects that have at least one specific runner.
For installations from source we advise you to upgrade GitLab CI using traditional method.
Upgrading GitLab CI from 7.9.1 to 7.9.2 contains database migrations. Downtime is not required but it is recommended as existing records are updated.
Upgrading GitLab CE or EE from 7.9.1 requires no downtime as this release contains no changes related to GitLab.
Omnibus-gitlab packages for GitLab 7.9.2 are now available.
To upgrade a GitLab installation from source please use the upgrader or the patch update guide.
To upgrade a GitLab CI installation from source, please use the upgrade guide.
Omnibus packages for GitLab Enterprise Edition 7.9.2 are available for subscribers here. For installations from source, use this guide.
Interested in GitLab Enterprise Edition? For an overview of feature exclusive to GitLab Enterprise Edition please have a look at the features exclusive to GitLab EE.
Access to GitLab Enterprise Edition is included with a subscription. No time to upgrade GitLab yourself? A subscription also entitles to our upgrade and installation services.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.Share your feedback