Notices: This section not yet converted to new layout. Download stats are rolling back out.

Jenkins CI

2.60.3

Package test results are passing.

This package was approved as a trusted package on 9/13/2017.

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:

  1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
  2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

To install Jenkins CI, run the following command from the command line or from PowerShell:

C:\> choco install jenkins

To upgrade Jenkins CI, run the following command from the command line or from PowerShell:

C:\> choco upgrade jenkins

Files

Hide
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop'; # stop on all errors
    
    $packageName= 'jenkins' # arbitrary name for the package, used in messages
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    
    $url = 'http://mirrors.jenkins-ci.org/windows-stable/jenkins-2.60.3.zip'
    $checkSum = 'f971db1a4a78f535a4e2e7bc31453d1c6306a22d482f89aede26ddaa3fa616b8'
    $checkSumMsi = 'be0dca1871d2b99d9a40ad4095b9b36b8122988dda7d8b22fdb11d8956cfd3f7'
    
    $filename = Join-Path $toolsDir ($url.Substring($url.LastIndexOf("/") + 1))
    
    Get-ChocolateyWebFile -PackageName $packageName -FileFullPath $filename -Url $url -Checksum $checkSum -ChecksumType 'sha256'
    Get-ChocolateyUnzip -FileFullPath $fileName -Destination $toolsDir -PackageName $packageName
    
    $msiPath = Join-Path $toolsDir 'jenkins.msi'
    
    $packageArgs = @{
      packageName   = $packageName
      unzipLocation = $toolsDir
      fileType      = 'msi'
      url           = $msiPath
    
      softwareName  = 'jenkins*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
    
      checksum      = $checkSumMsi
      checksumType  = 'sha256' #default is md5, can also be sha1, sha256 or sha512
    
      silentArgs    = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`"" # ALLUSERS=1 DISABLEDESKTOPSHORTCUT=1 ADDDESKTOPICON=0 ADDSTARTMENU=0
      validExitCodes= @(0, 3010, 1641)
    }
    
    Install-ChocolateyPackage @packageArgs # https://chocolatey.org/docs/helpers-install-chocolatey-package
    
    
    
  • tools\chocolateyuninstall.ps1 Show
    # IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
    #   $f='c:\path\to\thisFile.ps1'
    #   gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f
    
    ## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements), you may 
    ## not need this file due to AutoUninstaller. See https://chocolatey.org/docs/commands-uninstall
    
    ## If this is an MSI, cleaning up comments is all you need.
    ## If this is an exe, change installerType and silentArgs
    ## Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9).
    ## - https://chocolatey.org/docs/helpers-uninstall-chocolatey-package
    
    $ErrorActionPreference = 'Stop'; # stop on all errors
    
    $packageName = 'jenkins'
    $softwareName = 'jenkins*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
    $installerType = 'MSI' 
    #$installerType = 'EXE' 
    
    $silentArgs = '/qn /norestart'
    # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
    $validExitCodes = @(0, 3010, 1605, 1614, 1641)
    if ($installerType -ne 'MSI') {
      # The below is somewhat naive and built for EXE installers
      # Uncomment matching EXE type (sorted by most to least common)
      #$silentArgs = '/S'           # NSIS
      #$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup
      #$silentArgs = '/s'           # InstallShield
      #$silentArgs = '/s /v"/qn"' # InstallShield with MSI
      #$silentArgs = '/s'           # Wise InstallMaster
      #$silentArgs = '-s'           # Squirrel
      #$silentArgs = '-q'           # Install4j
      #$silentArgs = '-s -u'        # Ghost
      # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence.
      #$silentArgs = ''             # none; make silent with input macro script like AutoHotKey (AHK)
                                    #       https://chocolatey.org/packages/autohotkey.portable
      $validExitCodes = @(0)
    }
    
    $uninstalled = $false
    # Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below,
    # take a dependency on "chocolatey-uninstall.extension" in your nuspec file.
    # This is only a fuzzy search if $softwareName includes '*'. Otherwise it is 
    # exact. In the case of versions in key names, we recommend removing the version
    # and using '*'.
    [array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName
    
    if ($key.Count -eq 1) {
      $key | % { 
        $file = "$($_.UninstallString)"
    
        if ($installerType -eq 'MSI') {
          # The Product Code GUID is all that should be passed for MSI, and very 
          # FIRST, because it comes directly after /x, which is already set in the 
          # Uninstall-ChocolateyPackage msiargs (facepalm).
          $silentArgs = "$($_.PSChildName) $silentArgs"
    
          # Don't pass anything for file, it is ignored for msi (facepalm number 2) 
          # Alternatively if you need to pass a path to an msi, determine that and 
          # use it instead of the above in silentArgs, still very first
          $file = ''
        }
    
        Uninstall-ChocolateyPackage -PackageName $packageName `
                                    -FileType $installerType `
                                    -SilentArgs "$silentArgs" `
                                    -ValidExitCodes $validExitCodes `
                                    -File "$file"
      }
    } elseif ($key.Count -eq 0) {
      Write-Warning "$packageName has already been uninstalled by other means."
    } elseif ($key.Count -gt 1) {
      Write-Warning "$key.Count matches found!"
      Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
      Write-Warning "Please alert package maintainer the following keys were matched:"
      $key | % {Write-Warning "- $_.DisplayName"}
    }
    
    
    ## OTHER HELPERS
    ## https://chocolatey.org/docs/helpers-reference
    #Uninstall-ChocolateyZipPackage $packageName # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
    #Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable 
    #Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
    ## Remove any shortcuts you added
    
    

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Maintainer(s)

Software Author(s)

  • The Jenkins Team

Tags

Release Notes

http://jenkins-ci.org/changelog

Version History

Version Downloads Last updated Status
Jenkins CI 2.46.3 2047 Friday, May 26, 2017 approved
Jenkins CI 2.46.1 815 Saturday, April 8, 2017 approved
Jenkins CI 2.32.3 1953 Friday, March 10, 2017 approved
Jenkins CI 2.32.2 759 Friday, February 3, 2017 approved
Jenkins CI 2.32.1 653 Friday, January 6, 2017 approved
Jenkins CI 2.19.4 1069 Friday, December 2, 2016 approved
Jenkins CI 2.19.3 260 Monday, November 21, 2016 approved
Jenkins CI 2.19.2 171 Monday, November 14, 2016 approved
Jenkins CI 2.16.0.0 3296 Tuesday, August 2, 2016 approved
Show More

Discussion for the Jenkins CI Package

Ground rules:

  • This discussion is only about Jenkins CI and the Jenkins CI 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 Jenkins CI, 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