Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Learn More Register Now

Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand

Downloads:

178,145

Downloads of v 13.9.0:

1,382

Last Update:

23 Feb 2021

Package Maintainer(s):

Software Author(s):

  • Gitlab

Tags:

admin cli foss git cross-platform build docker shell gitlab

Gitlab Runner

This is not the latest version of Gitlab Runner available.

  • 1
  • 2
  • 3

13.9.0 | Updated: 23 Feb 2021

Downloads:

178,145

Downloads of v 13.9.0:

1,382

Maintainer(s):

Software Author(s):

  • Gitlab

Gitlab Runner 13.9.0

This is not the latest version of Gitlab Runner available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Gitlab Runner, run the following command from the command line or from PowerShell:

>

To upgrade Gitlab Runner, run the following command from the command line or from PowerShell:

>

To uninstall Gitlab Runner, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade gitlab-runner -y --source="'INTERNAL REPO URL'" --version="'13.9.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade gitlab-runner -y --source="'INTERNAL REPO URL'" --version="'13.9.0'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install gitlab-runner
  win_chocolatey:
    name: gitlab-runner
    version: '13.9.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'gitlab-runner' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '13.9.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller gitlab-runner
{
    Name     = "gitlab-runner"
    Version  = "13.9.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'gitlab-runner':
  ensure   => '13.9.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 23 Feb 2021.

Description

GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.

Features

  • Allows to run:
    • multiple jobs concurrently
    • use multiple tokens with multiple server (even per-project)
    • limit number of concurrent jobs per-token
  • Jobs can be run:
    • locally
    • using Docker containers
    • using Docker containers and executing job over SSH
    • using Docker containers with autoscaling on different clouds and virtualization hypervisors
    • connecting to remote SSH server
  • Is written in Go and distributed as single binary without any other requirements
  • Supports Bash, Windows Batch and Windows PowerShell
  • Works on GNU/Linux, OS X and Windows (pretty much anywhere you can run Docker)
  • Allows to customize the job running environment
  • Automatic configuration reload without restart
  • Easy to use setup with support for Docker, Docker-SSH, Parallels or SSH running environments
  • Enables caching of Docker containers
  • Easy installation as a service for GNU/Linux, OSX and Windows
  • Embedded Prometheus metrics HTTP server

Package parameters

  • /InstallDir - Installation directory. If the Gitlab Runner is already installed, its current directory will be used. To install to a new directory, uninstall it first.
  • /Service - Install as a service. If value is not specified system account will be used. If value is specified it is in the form of Username:Password. The installer will create that user if it doesn't exist, add it to local administrators group, enable ServiceLogonRight and disable password expiration. Example: /Service:gitlab-runner:P@ssw0rd. Can't be used with Autologon parameter
  • /Autologon - Use autologon feature of Windows. Can't be used with Service parameter. Username and password must be provided. Example: /Autologon:gitlab-runner:P@ssw0rd.

Notes

  • The script register_example.ps1 is provided along the executable which can be used to quickly register runner non-interactively. If you want to use it, rename it to register.ps1 and set desired environment variables.
  • Autologon vs Service: Services do not have access to all Windows features and some scripts, particularly those that depend on GUI, are not usable.

legal\LICENSE.txt
The MIT License (MIT)

Copyright (c) 2015-2017 GitLab B.V.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
tools\register_example.ps1
<# 
    Rename this file to register.ps1 or it will get overwritten by the future updates.
    For the list of all environment vars run `gitlab-runner register --help`.
    
    After registration, config.toml is generated and subsequent configuration changes should
    be set in that file. Gitlab-Runner automatically picks up config.toml changes while executing.
#>

$Env:RUNNER_NAME                = $env:COMPUTERNAME
$Env:REGISTRATION_TOKEN         = ''
$Env:CI_SERVER_URL              = ''
$Env:RUNNER_TAG_LIST            = ''        #comma separated list of tags

$Env:CONFIG_FILE                = "$PSScriptRoot\config.toml"
$Env:REGISTER_RUN_UNTAGGED      = 'false'
$Env:REGISTER_LOCKED            = $false    #lock runner to current project 
$Env:RUNNER_EXECUTOR            = 'shell'
$Env:RUNNER_SHELL               = 'powershell'

$Env:RUNNER_REQUEST_CONCURRENCY = 1
$Env:RUNNER_BUILDS_DIR          = ''
$Env:RUNNER_CACHE_DIR           = ''


gitlab-runner register --non-interactive
tools\helpers.ps1
function Get-RunnerInstallDir() {
    $res = Get-WmiObject win32_service | ? {$_.Name -eq 'gitlab-runner'} | select -Expand PathName
    if (!$res) { 
        if (!(gcm gitlab-runner.exe -ea 0)) { return }
        $res = (gitlab-runner.exe --shimgen-help 2>&1) -match '^\s*Target:' -replace "Target:|'"
        $res = $res.Trim()
    }
    $res = $res -split '\\gitlab-runner.exe' | select -First 1
    if (Test-Path $res) { return $res }
}

function Add-ServiceLogonRight([string] $Username) {
    Write-Host "Enable ServiceLogonRight for $Username"
    
    $tmp = [System.IO.Path]::GetTempFileName()
    secedit /export /cfg "$tmp.inf" | Out-Null
    (gc -Encoding ascii "$tmp.inf") -replace '^SeServiceLogonRight .+', "`$0,$Username" | sc -Encoding ascii "$tmp.inf"
    secedit /import /cfg "$tmp.inf" /db "$tmp.sdb" | Out-Null
    secedit /configure /db "$tmp.sdb" /cfg "$tmp.inf" | Out-Null
    rm $tmp* -ea 0
}

function Add-User([string] $Username, [string] $Password ) {
    $user = Get-WmiObject win32_useraccount -Filter { LocalAccount = 'true' } | ? { $_.Name -eq $Username }
    if ($user) { Write-Host "User $Username already exists"; return } 

    Write-Host "Creating user $Username as local administrator"
    net user $Username $Password /add | Out-Null
    net localgroup Administrators $Username /add | Out-NUll
    $user = Get-WmiObject win32_useraccount -Filter { LocalAccount = 'true' } | ? { $_.Name -eq $Username }
    $user.PasswordExpires = $false
}


# Author: Miodrag Milic <[email protected]>
# Last Change: 23-Jun-2016.

<#
.SYNOPSIS
    Set Windows to automatically login as given user after restart and eventually execute a script

.DESCRIPTION
    Enable AutoLogon next time when the server reboots.
    It can trigger a specific Script to execute after the server is back online after Auto Logon.

.EXAMPLE
    Set-AutoLogon -Username "domain\user" -Password "my password"

.EXAMPLE
    Set-AutoLogon -Username "domain\user" -Password "my password" -LogonCount 3

.EXAMPLE
    Set-AutoLogon -Username "domain\user" -Password "my password" -Script "c:\test.bat"
.LINK
    https://github.com/majkinetor/posh/blob/master/MM_Admin/Set-AutoLogon.ps1
#>
function Set-AutoLogon {
    [CmdletBinding()]
    Param(
        #Provide the username that the system would use to login.
        [Parameter(Mandatory=$true)]
        [String]$Username,

        #Provide the Password for the User provided.
        [Parameter(Mandatory=$true)]
        [String]$Password,

        #Sets the number of times the system would reboot without asking for credentials, by default 100000.
        [String]$LogonCount=100000,

        #Script: Provide Full path of the script for execution after server reboot
        [String]$Script
    )

    $ErrorActionPreference = 'Stop'

    $RegPath   = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"
    $RegROPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce"

    Set-ItemProperty $RegPath "AutoAdminLogon"  -Value 1
    Set-ItemProperty $RegPath "DefaultUsername" -Value $Username
    Set-ItemProperty $RegPath "DefaultPassword" -Value $Password
    #Set-ItemProperty $RegPath "DefaultDomain" -Value $Env:USERDOMAIN

    $v = if ($LogonCount)  { $LogonCount } else { '' }
    Set-ItemProperty $RegPath "AutoLogonCount" -Value $v -Type DWord

    $v = if ($Script)  { $Script } else { '' }
    Set-ItemProperty $RegROPath "Set-Autologon" -Value $v
}
tools\gitlab-runner-windows-amd64_x64.exe
md5: 19001D75C2EF84342A270D47B0E2ABE7 | sha1: 42B586294AF7450A475B81CF390062F47DC407F0 | sha256: EFE79321FC855713868EC096A7BA3C61A1CB92C9D83DDC3D1DBE4B3523602EF4 | sha512: D5A45EB1136D64B205237B9183E35C5B1DC5CA65A011DA0698F9F249CF06F0524292A2A7EBB0D4D5847CBF0D8B2AD5CA5D3C83EB5CF3A6A9182C2A9C7FD62C9C
tools\gitlab-runner-windows-386_x32.exe
md5: 2AC88614C09A1C964DE8B69B5EE59571 | sha1: E68308243DD4754722CDF5997BF3F3AF79D2059A | sha256: B81BC81E362054E7FEA66434F0EE68932B78BD1267E75FDCF15D2454BE0EC119 | sha512: E82EDFF4BCF6C5391B7940DBD1D7E849ED93D809081F56A799F50B8DE9565241307504FD10191546D9F4846E84BBC0AD79F9F545107D5D0BA275BBF84F9D4C00
tools\chocolateyUninstall.ps1
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

if (Get-Service gitlab-runner -ea 0) {
    gitlab-runner.exe stop
    gitlab-runner.exe uninstall
}

$installDir = Get-RunnerInstallDir

Write-Warning 'If a gitlab-runner user is created during the installation, it is not removed as a safety measure'
Write-Warning '  to remove it execute: net user gitlab-runner /delete'
Write-Warning 'If Autologon parameter was used when installing, disable autolog manually'

# It might not be safe to just rm -Force -Recursive, let the user do it manually.
if ($installDir) {
    Write-Warning "Gitlab-runner remained installed in $installDir"
    Write-Warning "  to delete it execute: rm '$installDir' -Force -Recurse"
} else {
    Write-Warning "Can't find gitlab-runner installation directory, please remove it manually"
}
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

$pp = Get-PackageParameters

$current_dir = Get-RunnerInstallDir
if ($current_dir) {
    Write-Host 'Using previous gitlab-runner install path:' $current_dir
    $pp.InstallDir = $current_dir
} else {
    if (!$pp.InstallDir) { $pp.InstallDir = "c:\gitlab-runner" }
    Write-Host 'Using install directory:' $pp.InstallDir
}
$installDir = $pp.InstallDir

$is64 = (Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne 'true'
$runner_embedded = if ($is64) { Write-Host "Installing x64 bit version"; Get-Item $toolsPath\*_x64.exe } else { Write-Host "Installing x32 bit version"; Get-Item $toolsPath\*_x32.exe }

Write-Host "Stopping executing runner"
Get-Service gitlab-runner -ea 0 | Stop-Service
Get-Process gitlab-runner -ea 0 | Stop-Process
Start-Sleep 2

Write-Host "Copying files to $installDir"
New-Item -ItemType Directory $installDir -ea 0 | Out-Null
Move-Item $runner_embedded, $toolsPath\register_example.ps1 $installDir -Force
ls $toolsPath\*.exe | % { Remove-Item $_ -ea 0; if (Test-Path $_) { touch "$_.ignore" }}
Move-Item $installDir\gitlab*.exe $installDir\gitlab-runner.exe -Force

$runner_path = Join-Path $installDir 'gitlab-runner.exe'
Install-BinFile gitlab-runner $runner_path

if ($pp.Service) {
    if ($pp.Autologon) { throw 'Autologon and Service parameters are mutually exclusive' }

    if ($pp.Service -is [string]) {
        $Username, $Password = $pp.Service -split ':'
        if (!$Password) { throw 'When specifying service user, password is required' }
    }

    if (!(Get-Service gitlab-runner -ea 0)) {
        Write-Host "Installing gitlab-runner service"
        $cmd = @("install")
        if ($Username) {
            Add-User $Username $Password
            Add-ServiceLogonRight $Username
            $cmd += " --user", "$Env:COMPUTERNAME\$Username", "--password", $Password
            $cmd += " --working-directory", $installDir, "--config", "$installDir\config.toml"
        }

        $ErrorActionPreference = 'Continue'
        & $runner_path $cmd
        $ErrorActionPreference = 'Stop'
    } else { Write-Host "Service gitlab-runner already installed" }

    Write-Host "Starting service"
    Start-Service gitlab-runner
    Get-Service gitlab-runner
}

if ($pp.Autologon) {
    if ($pp.Service) { throw 'Autologon and Service parameters are mutually exclusive' }

    $Username, $Password = $pp.Autologon -split ':'
    if (!$Password) { throw 'When specifying autologon user, password is required' }

    Add-User $Username $Password

    Write-Host "Setting autologon for $Username"
    Set-AutoLogon $Username $Password

    Write-Host "Creating logon script: $installDir\autologon.bat"
    "cd ""$installDir""`n" +
    """$installDir\gitlab-runner.exe"" run" | Out-File $installDir\autologon.bat -Encoding ascii

    Write-Host "Creating scheduled task: autologon"
    [xml] $xml = gc $toolsPath\autologon.xml -Encoding Ascii
    $xml.Task.RegistrationInfo.Author       = "$Env:COMPUTERNAME\$Env:USERNAME"
    $xml.task.Triggers.LogonTrigger.UserId  = "$Env:COMPUTERNAME\$Username"
    $xml.task.Principals.Principal.UserId   = "$Env:COMPUTERNAME\$Username"
    $xml.task.Actions.Exec.Command          = "$installDir\autologon.bat"
    $xml.Save( "$toolsPath\autologon.xml" )

    schtasks.exe /Create /XML "$toolsPath\autologon.xml" /Tn autologon /F
    if ($LASTEXITCODE) { throw "Scheduled task not created ($LastExitCode)" }
}
tools\autologon.xml
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Author>DESKTOP-9Q3PK5G\majkinetor</Author>
    <URI>\autologon</URI>
  </RegistrationInfo>
  <Triggers>
    <LogonTrigger>
      <Enabled>true</Enabled>
      <UserId>DESKTOP-9Q3PK5G\gitlab-runner</UserId>
    </LogonTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>DESKTOP-9Q3PK5G\gitlab-runner</UserId>
      <LogonType>InteractiveToken</LogonType>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>C:\gitlab-runner\autologon.bat</Command>
    </Exec>
  </Actions>
</Task>
legal\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x32: https://gitlab-runner-downloads.s3.amazonaws.com/v13.9.0/binaries/gitlab-runner-windows-386.exe
   x64: https://gitlab-runner-downloads.s3.amazonaws.com/v13.9.0/binaries/gitlab-runner-windows-amd64.exe

   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: B81BC81E362054E7FEA66434F0EE68932B78BD1267E75FDCF15D2454BE0EC119
   checksum64: EFE79321FC855713868EC096A7BA3C61A1CB92C9D83DDC3D1DBE4B3523602EF4


File 'license.txt' is obtained from:
   https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/raw/master/LICENSE

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Gitlab Runner 16.6.0 765 Friday, November 17, 2023 Approved
Gitlab Runner 16.5.0 1135 Saturday, October 21, 2023 Approved
Gitlab Runner 16.4.0 1616 Tuesday, September 26, 2023 Approved
Gitlab Runner 16.3.1 1220 Tuesday, September 19, 2023 Approved
Gitlab Runner 16.2.0 3182 Saturday, July 22, 2023 Approved
Gitlab Runner 16.1.0 1219 Thursday, June 22, 2023 Approved
Gitlab Runner 16.0.2 747 Friday, June 9, 2023 Approved
Gitlab Runner 16.0.1 564 Saturday, May 27, 2023 Approved
Gitlab Runner 16.0.0 1009 Monday, May 22, 2023 Approved
Gitlab Runner 15.11.0 2722 Tuesday, April 25, 2023 Approved
Gitlab Runner 15.10.0 1357 Friday, March 24, 2023 Approved
Gitlab Runner 15.9.1 616 Wednesday, March 15, 2023 Approved
Gitlab Runner 15.8.0 3288 Thursday, February 2, 2023 Approved
Gitlab Runner 15.7.2 974 Sunday, January 15, 2023 Approved
Gitlab Runner 15.7.1 15135 Friday, December 23, 2022 Approved
Gitlab Runner 15.7.0 733 Monday, December 19, 2022 Approved
Gitlab Runner 15.6.0 2685 Tuesday, November 22, 2022 Approved
Gitlab Runner 15.5.0 44572 Sunday, October 23, 2022 Approved
Gitlab Runner 15.4.0 2070 Thursday, September 22, 2022 Approved
Gitlab Runner 15.3.0 2587 Saturday, August 20, 2022 Approved
Gitlab Runner 15.2.0 1365 Tuesday, August 9, 2022 Approved
Gitlab Runner 15.1.0 1769 Tuesday, June 21, 2022 Approved
Gitlab Runner 15.0.0 1338 Friday, May 20, 2022 Approved
Gitlab Runner 14.10.0 1609 Tuesday, April 19, 2022 Approved
Gitlab Runner 14.9.0 1397 Tuesday, March 22, 2022 Approved
Gitlab Runner 14.8.0 1149 Tuesday, February 22, 2022 Approved
Gitlab Runner 14.7.0 1093 Thursday, January 20, 2022 Approved
Gitlab Runner 14.6.0 1508 Saturday, December 18, 2021 Approved
Gitlab Runner 14.5.0 1277 Monday, November 22, 2021 Approved
Gitlab Runner 14.4.0 1049 Tuesday, October 26, 2021 Approved
Gitlab Runner 14.3.0 1353 Wednesday, September 22, 2021 Approved
Gitlab Runner 14.2.0 1150 Saturday, August 28, 2021 Approved
Gitlab Runner 14.0.0 2080 Sunday, June 20, 2021 Approved
Gitlab Runner 13.12.0 2836 Friday, May 21, 2021 Approved
Gitlab Runner 13.11.0 990 Wednesday, April 21, 2021 Approved
Gitlab Runner 13.10.0 1632 Monday, March 22, 2021 Approved
Gitlab Runner 13.9.0 1382 Tuesday, February 23, 2021 Approved
Gitlab Runner 13.8.0 1752 Thursday, January 21, 2021 Approved
Gitlab Runner 13.7.0 1393 Tuesday, December 22, 2020 Approved
Gitlab Runner 13.6.0.20201205 665 Saturday, December 5, 2020 Approved
Gitlab Runner 13.6.0 993 Sunday, November 22, 2020 Approved
Gitlab Runner 13.5.0 9136 Wednesday, October 21, 2020 Approved
Gitlab Runner 13.4.0 215 Saturday, September 19, 2020 Approved
Gitlab Runner 13.3.0 3209 Friday, August 21, 2020 Approved
Gitlab Runner 13.2.0 1627 Monday, July 20, 2020 Approved
Gitlab Runner 13.1.0 1409 Saturday, June 20, 2020 Approved
Gitlab Runner 13.0.1 1185 Monday, June 1, 2020 Approved
Gitlab Runner 13.0.0 794 Thursday, May 21, 2020 Approved
Gitlab Runner 12.10.0 2799 Wednesday, April 22, 2020 Approved
Gitlab Runner 12.9.0 707 Tuesday, April 14, 2020 Approved
Gitlab Runner 12.8.0 2452 Sunday, February 23, 2020 Approved
Gitlab Runner 12.7.1 1099 Friday, January 24, 2020 Approved
Gitlab Runner 12.7.0 264 Tuesday, January 21, 2020 Approved
Gitlab Runner 12.6.0 530 Tuesday, December 24, 2019 Approved
Gitlab Runner 12.5.0 1034 Thursday, November 21, 2019 Approved
Gitlab Runner 12.4.1 1049 Tuesday, October 29, 2019 Approved
Gitlab Runner 12.4.0 471 Tuesday, October 22, 2019 Approved
Gitlab Runner 12.3.0 2163 Saturday, September 21, 2019 Approved
Gitlab Runner 12.2.0 1222 Friday, August 23, 2019 Approved
Gitlab Runner 12.1.0 1077 Saturday, July 20, 2019 Approved
Gitlab Runner 12.0.0 1625 Saturday, June 22, 2019 Approved
Gitlab Runner 11.11.2 815 Tuesday, June 4, 2019 Approved
Gitlab Runner 11.11.0 478 Tuesday, May 21, 2019 Approved
Gitlab Runner 11.10.0 853 Saturday, April 20, 2019 Approved
Gitlab Runner 11.9.0 680 Saturday, March 23, 2019 Approved
Gitlab Runner 11.8.0 858 Saturday, February 23, 2019 Approved
Gitlab Runner 11.7.0 986 Tuesday, January 22, 2019 Approved
Gitlab Runner 11.6.0 352 Friday, January 18, 2019 Approved
Gitlab Runner 11.4.0 1451 Monday, October 22, 2018 Approved
Gitlab Runner 11.4.0-rc1 275 Thursday, October 11, 2018 Exempted
Gitlab Runner 11.3.0 816 Saturday, September 22, 2018 Approved
Gitlab Runner 11.3.0-rc1 289 Wednesday, September 12, 2018 Exempted
Gitlab Runner 11.2.0 720 Thursday, August 23, 2018 Approved
Gitlab Runner 11.2.0-rc1 273 Thursday, August 9, 2018 Approved
Gitlab Runner 11.1.0 742 Monday, July 23, 2018 Approved
Gitlab Runner 11.1.0-rc1 332 Saturday, July 14, 2018 Approved
Gitlab Runner 11.0.0 931 Saturday, June 23, 2018 Approved
Gitlab Runner 11.0.0-rc1 376 Wednesday, June 13, 2018 Approved
Gitlab Runner 10.8.0 819 Wednesday, May 23, 2018 Approved
Gitlab Runner 10.8.0-rc1 445 Friday, May 11, 2018 Approved
Gitlab Runner 10.7.0-rc1 502 Thursday, April 12, 2018 Approved
Gitlab Runner 10.6.0 1129 Friday, March 23, 2018 Approved
Gitlab Runner 10.6.0-rc1 423 Friday, March 9, 2018 Approved
Gitlab Runner 10.5.0 663 Friday, February 23, 2018 Approved
Gitlab Runner 10.5.0-rc1 440 Friday, February 9, 2018 Approved
Gitlab Runner 10.4.0 658 Monday, January 22, 2018 Approved
Gitlab Runner 10.4.0-rc1 520 Tuesday, January 9, 2018 Approved
Gitlab Runner 10.3.0 698 Saturday, December 23, 2017 Approved
Gitlab Runner 10.3.0-rc1 469 Monday, December 11, 2017 Approved
Gitlab Runner 10.2.0 798 Thursday, November 23, 2017 Approved
Gitlab Runner 10.2.0-rc1 462 Saturday, November 11, 2017 Approved
Gitlab Runner 10.1.0 928 Sunday, October 22, 2017 Approved
Gitlab Runner 10.1.0-rc1 498 Tuesday, October 10, 2017 Approved
Gitlab Runner 10.0.0-rc1 443 Tuesday, September 26, 2017 Approved
Gitlab Runner 9.5.0 1085 Wednesday, August 23, 2017 Approved
Gitlab Runner 9.4.0 722 Sunday, July 23, 2017 Approved
Gitlab Runner 9.3.0 515 Thursday, June 22, 2017 Approved
Gitlab Runner 9.2.1 401 Saturday, June 17, 2017 Approved
Gitlab Runner 9.2.0 479 Monday, May 22, 2017 Approved
Gitlab Runner 9.1.1 409 Wednesday, May 3, 2017 Approved
Gitlab Runner 9.1.0 424 Monday, April 24, 2017 Approved
Gitlab Runner 9.0.0 450 Thursday, March 30, 2017 Approved
Discussion for the Gitlab Runner Package

Ground Rules:

  • This discussion is only about Gitlab Runner and the Gitlab Runner package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Gitlab Runner, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus