Downloads:

308,300

Downloads of v 5.1.0:

11,008

Last Update:

29 Apr 2022

Package Maintainer(s):

Software Author(s):

  • The Bazel Authors

Tags:

bazel build automation

bazel (Install)

  • 1
  • 2
  • 3

5.1.0 | Updated: 29 Apr 2022

Downloads:

308,300

Downloads of v 5.1.0:

11,008

Maintainer(s):

Software Author(s):

  • The Bazel Authors

  • 1
  • 2
  • 3
bazel (Install) 5.1.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install bazel (Install), run the following command from the command line or from PowerShell:

>

To upgrade bazel (Install), run the following command from the command line or from PowerShell:

>

To uninstall bazel (Install), 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 bazel -y --source="'INTERNAL REPO URL'" [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 bazel -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install bazel
  win_chocolatey:
    name: bazel
    version: '5.1.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'bazel' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '5.1.0'
end

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


cChocoPackageInstaller bazel
{
    Name     = "bazel"
    Version  = "5.1.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'bazel':
  ensure   => '5.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.

This package was approved as a trusted package on 29 Apr 2022.

Description

Build software of any size, quickly and reliably, just as engineers do at Google.

Bazel is Google's own build tool, now publicly available in Beta.

Bazel has built-in support for building both client and server software, including client applications for both Android and iOS platforms. It also provides an extensible framework that you can use to develop your own build rules.

Package parameters

Supply like --params="/option:'value' ..." (see docs for --params)

  • msys2Path (optional, defaults to c:\tools\msys64) - override this if msys2 is installed elsewhere.

tools\chocolateybeforemodify.ps1
write-host "Attempting to stop any running bazel processes, to allow upgrade"
try
{
  $running = get-process bazel
}
catch
{
  write-host "No running bazel processes to stop"
  $running = @()
}

if ($running)
{
  write-host "Stopping bazel processes"
  foreach($p in $running)
  {
    stop-process $p
    write-verbose "Stopped $($p.ProcessName) $($p.Id)"
  }
}
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'bazel'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$raw = get-content "$($toolsDir)\params.txt" | out-string
write-host "Content of $($toolsDir)\params.txt:"
write-host $raw
$params = $raw -split "`n"
write-host "url:  $($params[0].Trim())"
write-host "hash: $($params[1].Trim())"

$packageDir = Split-Path -parent $toolsDir

Install-ChocolateyZipPackage -PackageName "$packageName" `
  -Url64bit "$($params[0].Trim())" `
  -Checksum64 "$($params[1].Trim())" `
  -ChecksumType64 "sha256" `
  -UnzipLocation "$packageDir"

write-host @"
bazel installed to $packageDir

See also https://bazel.build/docs/windows.html
"@

tools\LICENSE
 
tools\params.txt
https://github.com/bazelbuild/bazel/releases/download/5.1.0/bazel-5.1.0-windows-x86_64.zip
ac2309f165d4ea4811f5710b182e3640c7eee09af21c79eb0c438dcad8ea8560
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Download the zip file from github releases
Take its sha256
If it matches what is in package's chocolateyinstall.ps1, it's authentic.

Example:

```
invoke-webrequest https://github.com/bazelbuild/bazel/releases/0.3.1/bazel_0.3.1_windows_x86_64.zip -outfile bazel_0.3.1_windows_x86_64.zip
get-filehash bazel_0.3.1_windows_x86_64.zip -algorithm sha256
# compare that to what's in <package>/tools/chocolateyinstall.ps1
```

See also package build script `<repo>/scripts/packages/chocolatey/buildAndInstall.ps1`.

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
bazel (Install) 5.0.0 6228 Wednesday, January 19, 2022 Approved
bazel (Install) 4.2.2 3134 Sunday, December 5, 2021 Approved
bazel (Install) 4.2.1 19888 Monday, August 30, 2021 Approved
bazel (Install) 4.2.0 502 Monday, August 23, 2021 Approved
bazel (Install) 4.1.0 7364 Friday, May 21, 2021 Approved
bazel (Install) 4.0.0 18690 Thursday, January 21, 2021 Approved
bazel (Install) 3.7.2 2107 Sunday, December 20, 2020 Approved
bazel (Install) 3.7.1 21632 Wednesday, November 25, 2020 Approved
bazel (Install) 3.7.0 2200 Monday, October 26, 2020 Approved

Discussion for the bazel (Install) Package

Ground Rules:

  • This discussion is only about bazel (Install) and the bazel (Install) 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 bazel (Install), 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