Downloads:

103,275

Downloads of v 2.1.0:

294

Last Update:

09 Feb 2020

Package Maintainer(s):

Software Author(s):

  • The Bazel Authors

Tags:

bazel build automation

bazel (Install)

2.1.0 | Updated: 09 Feb 2020

Downloads:

103,275

Downloads of v 2.1.0:

294

Maintainer(s):

Software Author(s):

  • The Bazel Authors

bazel (Install) 2.1.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade bazel -y --source="'STEP 3 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="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure bazel installed
  win_chocolatey:
    name: bazel
    state: present
    version: 2.1.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'bazel' do
  action    :install
  version  '2.1.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: bazel,
    Version: 2.1.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller bazel
{
   Name     = 'bazel'
   Ensure   = 'Present'
   Version  = '2.1.0'
   Source   = 'STEP 3 URL'
}

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


package { 'bazel':
  provider => 'chocolatey',
  ensure   => '2.1.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install bazel version="2.1.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 09 Feb 2020.

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/2.1.0/bazel-2.1.0-windows-x86_64.zip
0c8492b49310f73cdfbc4df9173b5f2cd2aa547d8dfbe46b47b93f3d712e5864
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.

Version Downloads Last Updated Status
bazel (Install) 2.0.0 1774 Tuesday, January 7, 2020 Approved
bazel (Install) 1.2.1 1594 Wednesday, November 27, 2019 Approved
bazel (Install) 1.2.0 350 Wednesday, November 27, 2019 Approved
bazel (Install) 1.1.0 82 Wednesday, November 27, 2019 Approved
bazel (Install) 1.0.0 9394 Saturday, October 12, 2019 Approved
bazel (Install) 1.0.0-rc5 36 Friday, October 4, 2019 Approved
bazel (Install) 1.0.0-rc4 25 Friday, October 4, 2019 Approved
bazel (Install) 1.0.0-rc3 53 Wednesday, September 18, 2019 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