Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

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

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

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

Webinar from
Wednesday, 17 January 2024

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!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
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

Downloads:

216,879

Downloads of v 10.1.0:

943

Last Update:

22 Oct 2017

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

10.1.0 | Updated: 22 Oct 2017

Downloads:

216,879

Downloads of v 10.1.0:

943

Maintainer(s):

Software Author(s):

  • Gitlab

Gitlab Runner 10.1.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="'10.1.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="'10.1.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: '10.1.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  '10.1.0'
end

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


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

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


package { 'gitlab-runner':
  ensure   => '10.1.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.

WARNING

There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved as a trusted package on 22 Oct 2017.

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.
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/v10.1.0/binaries/gitlab-runner-windows-386.exe
   x64: https://gitlab-runner-downloads.s3.amazonaws.com/v10.1.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: 23ED40119D85B2E2B198DDF2835B633FF6042D927D0EAF811C71D4A74E5F58FB
   checksum64: 4C894F128DFC4E75869FFC6F9080A3FA03B13F7A3A155C7DFA4B2E0469AEC07B


File 'license.txt' is obtained from:
   https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/raw/master/LICENSE
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>
tools\chocolateyBeforeModify.ps1
Get-Service gitlab-runner -ea 0 | Stop-Service
ps gitlab-runner -ea 0 | kill
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"; gi $toolsPath\*_x64.exe } else { Write-Host "Installing x32 bit version"; gi $toolsPath\*_x32.exe }

mkdir $installDir -ea 0 | Out-Null
mv $runner_embedded, $toolsPath\register_example.ps1 $installDir -force
ls $toolsPath\*.exe | % { rm $_ -ea 0; if (Test-Path $_) { touch "$_.ignore" }}
mv $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' } 
    }

    Write-Host "Installing gitlab-runner service"
    $cmd = "$runner_path install"
    if ($Username) {
        Add-User $Username $Password
        Add-ServiceLogonRight $Username
        $cmd += " --user $Env:COMPUTERNAME\$Username --password $Password" 
    }
    iex $cmd

    Write-Host "Starting service"
    iex "$runner_path start"
}

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 -Script "$installDir\autologon.bat"

    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\chocolateyUninstall.ps1
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

if (gsv 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\gitlab-runner-windows-386_x32.exe
md5: 07C85AB873B106FA9C83082683CE7E8B | sha1: 1CAD3662FB6FD9EE7E4BB7115A1F9C731ABD563E | sha256: 23ED40119D85B2E2B198DDF2835B633FF6042D927D0EAF811C71D4A74E5F58FB | sha512: 0DCB26F0F1E5CFB8D2A985C70E18AF2264BEE49335CCD11AEB0AEAF94292474D51B9ED25AD1DAEBC5F43B3C57F9CEA701440D664F2E6D665E243B6754ABD43ED
tools\gitlab-runner-windows-amd64_x64.exe
md5: FD91E6EDAF680A62B4A508FFC6EA3036 | sha1: B69BDC49A96EA15BB9A291B637C6CACEC64A88D4 | sha256: 4C894F128DFC4E75869FFC6F9080A3FA03B13F7A3A155C7DFA4B2E0469AEC07B | sha512: 24B7E5F146B886387B8631E04B22A012A3C499FC48F20F977E399830C5CAF8DA9DC03EEDB08EC923A74B037797F2115D63305A6942B4301737256B3A50C3D06C
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\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`
    Running runners should automatically pick up config.toml changes.
#>

$Env:RUNNER_NAME                = ''
$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

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.11.0 5 Friday, April 19, 2024 Ready
Gitlab Runner 16.9.1 1782 Thursday, February 29, 2024 Approved
Gitlab Runner 16.9.0 1417 Friday, February 16, 2024 Approved
Gitlab Runner 16.8.0 2627 Saturday, January 20, 2024 Approved
Gitlab Runner 16.7.0 2665 Friday, December 22, 2023 Approved
Gitlab Runner 16.6.1 1648 Sunday, November 26, 2023 Approved
Gitlab Runner 16.6.0 1216 Friday, November 17, 2023 Approved
Gitlab Runner 16.5.0 1294 Saturday, October 21, 2023 Approved
Gitlab Runner 16.4.0 1669 Tuesday, September 26, 2023 Approved
Gitlab Runner 16.3.1 1333 Tuesday, September 19, 2023 Approved
Gitlab Runner 16.2.0 3248 Saturday, July 22, 2023 Approved
Gitlab Runner 16.1.0 1292 Thursday, June 22, 2023 Approved
Gitlab Runner 16.0.2 1504 Friday, June 9, 2023 Approved
Gitlab Runner 16.0.1 571 Saturday, May 27, 2023 Approved
Gitlab Runner 16.0.0 1016 Monday, May 22, 2023 Approved
Gitlab Runner 15.11.0 6918 Tuesday, April 25, 2023 Approved
Gitlab Runner 15.10.0 1378 Friday, March 24, 2023 Approved
Gitlab Runner 15.9.1 624 Wednesday, March 15, 2023 Approved
Gitlab Runner 15.8.0 3319 Thursday, February 2, 2023 Approved
Gitlab Runner 15.7.2 983 Sunday, January 15, 2023 Approved
Gitlab Runner 15.7.1 15419 Friday, December 23, 2022 Approved
Gitlab Runner 15.7.0 742 Monday, December 19, 2022 Approved
Gitlab Runner 15.6.0 2692 Tuesday, November 22, 2022 Approved
Gitlab Runner 15.5.0 64019 Sunday, October 23, 2022 Approved
Gitlab Runner 15.4.0 2085 Thursday, September 22, 2022 Approved
Gitlab Runner 15.3.0 2593 Saturday, August 20, 2022 Approved
Gitlab Runner 15.2.0 1372 Tuesday, August 9, 2022 Approved
Gitlab Runner 15.1.0 1775 Tuesday, June 21, 2022 Approved
Gitlab Runner 15.0.0 1349 Friday, May 20, 2022 Approved
Gitlab Runner 14.10.0 1620 Tuesday, April 19, 2022 Approved
Gitlab Runner 14.9.0 1406 Tuesday, March 22, 2022 Approved
Gitlab Runner 14.8.0 1159 Tuesday, February 22, 2022 Approved
Gitlab Runner 14.7.0 1099 Thursday, January 20, 2022 Approved
Gitlab Runner 14.6.0 1568 Saturday, December 18, 2021 Approved
Gitlab Runner 14.5.0 1283 Monday, November 22, 2021 Approved
Gitlab Runner 14.4.0 1059 Tuesday, October 26, 2021 Approved
Gitlab Runner 14.3.0 1357 Wednesday, September 22, 2021 Approved
Gitlab Runner 14.2.0 1157 Saturday, August 28, 2021 Approved
Gitlab Runner 14.0.0 2086 Sunday, June 20, 2021 Approved
Gitlab Runner 13.12.0 2843 Friday, May 21, 2021 Approved
Gitlab Runner 13.11.0 1001 Wednesday, April 21, 2021 Approved
Gitlab Runner 13.10.0 1637 Monday, March 22, 2021 Approved
Gitlab Runner 13.9.0 1434 Tuesday, February 23, 2021 Approved
Gitlab Runner 13.8.0 1761 Thursday, January 21, 2021 Approved
Gitlab Runner 13.7.0 1399 Tuesday, December 22, 2020 Approved
Gitlab Runner 13.6.0.20201205 677 Saturday, December 5, 2020 Approved
Gitlab Runner 13.6.0 1013 Sunday, November 22, 2020 Approved
Gitlab Runner 13.5.0 9145 Wednesday, October 21, 2020 Approved
Gitlab Runner 13.4.0 225 Saturday, September 19, 2020 Approved
Gitlab Runner 13.3.0 3220 Friday, August 21, 2020 Approved
Gitlab Runner 13.2.0 1635 Monday, July 20, 2020 Approved
Gitlab Runner 13.1.0 1418 Saturday, June 20, 2020 Approved
Gitlab Runner 13.0.1 1193 Monday, June 1, 2020 Approved
Gitlab Runner 13.0.0 802 Thursday, May 21, 2020 Approved
Gitlab Runner 12.10.0 2807 Wednesday, April 22, 2020 Approved
Gitlab Runner 12.9.0 721 Tuesday, April 14, 2020 Approved
Gitlab Runner 12.8.0 2459 Sunday, February 23, 2020 Approved
Gitlab Runner 12.7.1 1162 Friday, January 24, 2020 Approved
Gitlab Runner 12.7.0 275 Tuesday, January 21, 2020 Approved
Gitlab Runner 12.6.0 543 Tuesday, December 24, 2019 Approved
Gitlab Runner 12.5.0 1044 Thursday, November 21, 2019 Approved
Gitlab Runner 12.4.1 1057 Tuesday, October 29, 2019 Approved
Gitlab Runner 12.4.0 478 Tuesday, October 22, 2019 Approved
Gitlab Runner 12.3.0 2176 Saturday, September 21, 2019 Approved
Gitlab Runner 12.2.0 1235 Friday, August 23, 2019 Approved
Gitlab Runner 12.1.0 1090 Saturday, July 20, 2019 Approved
Gitlab Runner 12.0.0 1638 Saturday, June 22, 2019 Approved
Gitlab Runner 11.11.2 821 Tuesday, June 4, 2019 Approved
Gitlab Runner 11.11.0 493 Tuesday, May 21, 2019 Approved
Gitlab Runner 11.10.0 862 Saturday, April 20, 2019 Approved
Gitlab Runner 11.9.0 692 Saturday, March 23, 2019 Approved
Gitlab Runner 11.8.0 887 Saturday, February 23, 2019 Approved
Gitlab Runner 11.7.0 1000 Tuesday, January 22, 2019 Approved
Gitlab Runner 11.6.0 357 Friday, January 18, 2019 Approved
Gitlab Runner 11.4.0 1467 Monday, October 22, 2018 Approved
Gitlab Runner 11.4.0-rc1 284 Thursday, October 11, 2018 Exempted
Gitlab Runner 11.3.0 825 Saturday, September 22, 2018 Approved
Gitlab Runner 11.3.0-rc1 303 Wednesday, September 12, 2018 Exempted
Gitlab Runner 11.2.0 727 Thursday, August 23, 2018 Approved
Gitlab Runner 11.2.0-rc1 286 Thursday, August 9, 2018 Approved
Gitlab Runner 11.1.0 752 Monday, July 23, 2018 Approved
Gitlab Runner 11.1.0-rc1 338 Saturday, July 14, 2018 Approved
Gitlab Runner 11.0.0 943 Saturday, June 23, 2018 Approved
Gitlab Runner 11.0.0-rc1 386 Wednesday, June 13, 2018 Approved
Gitlab Runner 10.8.0 831 Wednesday, May 23, 2018 Approved
Gitlab Runner 10.8.0-rc1 451 Friday, May 11, 2018 Approved
Gitlab Runner 10.7.0-rc1 513 Thursday, April 12, 2018 Approved
Gitlab Runner 10.6.0 1137 Friday, March 23, 2018 Approved
Gitlab Runner 10.6.0-rc1 430 Friday, March 9, 2018 Approved
Gitlab Runner 10.5.0 672 Friday, February 23, 2018 Approved
Gitlab Runner 10.5.0-rc1 447 Friday, February 9, 2018 Approved
Gitlab Runner 10.4.0 667 Monday, January 22, 2018 Approved
Gitlab Runner 10.4.0-rc1 537 Tuesday, January 9, 2018 Approved
Gitlab Runner 10.3.0 706 Saturday, December 23, 2017 Approved
Gitlab Runner 10.3.0-rc1 479 Monday, December 11, 2017 Approved
Gitlab Runner 10.2.0 808 Thursday, November 23, 2017 Approved
Gitlab Runner 10.2.0-rc1 472 Saturday, November 11, 2017 Approved
Gitlab Runner 10.1.0 943 Sunday, October 22, 2017 Approved
Gitlab Runner 10.1.0-rc1 508 Tuesday, October 10, 2017 Approved
Gitlab Runner 10.0.0-rc1 453 Tuesday, September 26, 2017 Approved
Gitlab Runner 9.5.0 1091 Wednesday, August 23, 2017 Approved
Gitlab Runner 9.4.0 735 Sunday, July 23, 2017 Approved
Gitlab Runner 9.3.0 524 Thursday, June 22, 2017 Approved
Gitlab Runner 9.2.1 411 Saturday, June 17, 2017 Approved
Gitlab Runner 9.2.0 492 Monday, May 22, 2017 Approved
Gitlab Runner 9.1.1 418 Wednesday, May 3, 2017 Approved
Gitlab Runner 9.1.0 435 Monday, April 24, 2017 Approved
Gitlab Runner 9.0.0 460 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