Downloads:

244,238

Downloads of v 0.5.0-rc6:

379

Last Update:

13 May 2017

Package Maintainer(s):

Software Author(s):

  • The Bazel Authors

Tags:

bazel build automation

bazel (Install)

This is a prerelease version of bazel (Install).

  • 1
  • 2
  • 3

0.5.0-rc6 | Updated: 13 May 2017

Downloads:

244,238

Downloads of v 0.5.0-rc6:

379

Maintainer(s):

Software Author(s):

  • The Bazel Authors

  • 1
  • 2
  • 3
bazel (Install) 0.5.0-rc6

This is a prerelease version of bazel (Install).

  • 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

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

(this should look similar to https://community.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: 0.5.0-rc6
    source: STEP 3 URL

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


chocolatey_package 'bazel' do
  action    :install
  version  '0.5.0-rc6'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller bazel
{
   Name     = 'bazel'
   Ensure   = 'Present'
   Version  = '0.5.0-rc6'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install bazel version="0.5.0-rc6" 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 15 May 2017.

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
$paramsText = get-content "$($toolsDir)\params.txt"
write-host "Content of $($toolsDir)\params.txt:"
write-host $paramsText
write-host "url:  $($paramsText[0])"
write-host "hash: $($paramsText[1])"
write-host "Type: $($paramsText.GetType())"

$packageDir = Split-Path -parent $toolsDir


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

write-host "Ensure that msys2 dll is present in PATH to allow bazel to be run from non-msys2 shells"
$pp = Get-PackageParameters $env:chocolateyPackageParameters
$msys2Path = ($pp.msys2Path, "c:\tools\msys64" -ne $null)[0]
Install-ChocolateyPath -PathToInstall "$($msys2Path)\usr\bin" -PathType "Machine"

$addToMsysPath = ($packageDir -replace '^([a-zA-Z]):\\(.*)','/$1/$2') -replace '\\','/'
write-host @"
bazel installed to $packageDir

To use it in powershell or cmd, you should ensure your PATH environment variable contains
  $($msys2Path)\usr\bin
BEFORE both
  c:\windows\system32 (because bash-on-windows' bash.exe will be found here, if it's installed)
  any references to msysgit (like c:\program files (x86)\git\bin or c:\program files (x86)\git\cmd) (because git's vendored version of msys2 will interfere with the real msys2)

To use it in msys2, you should add that to your msys2 PATH:
  export PATH=$($addToMsysPath):`$PATH

You also need, in your msys2 environment (adjust paths for your system):
  export JAVA_HOME="`$(ls -d C:/Program\ Files/Java/jdk* | sort | tail -n 1)`"
  export BAZEL_SH=c:/tools/msys64/usr/bin/bash.exe
  export BAZEL_PYTHON=c:/tools/python2/python.exe

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

tools\chocolateyuninstall.ps1
write-host @"
bazel is being uninstalled.

You should now:
* Remove "<msys>/usr/bin" from your PATH

Sorry this isn't automatic; there are no helper functions available within chocolatey (as of v0.10.0) to do these steps as part of the uninstall. See:
* https://github.com/chocolatey/choco/issues/310
* https://github.com/chocolatey/package-validator/issues/148
"@
tools\LICENSE
 
tools\params.txt
https://storage.googleapis.com/bazel/0.5.0/rc6/bazel-0.5.0rc6-windows-x86_64.zip
a6f300be831ac5a149d876b17a2f57e8536292930ea392426703571c4dacad45
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) 4.2.0 422 Monday, August 23, 2021 Approved
bazel (Install) 4.1.0 4416 Friday, May 21, 2021 Approved
bazel (Install) 4.0.0 17206 Thursday, January 21, 2021 Approved
bazel (Install) 3.7.2 1901 Sunday, December 20, 2020 Approved
bazel (Install) 3.7.1 21428 Wednesday, November 25, 2020 Approved
bazel (Install) 3.7.0 2058 Monday, October 26, 2020 Approved
bazel (Install) 3.6.0 373 Sunday, October 18, 2020 Approved
bazel (Install) 3.5.1 41 Sunday, October 18, 2020 Approved
bazel (Install) 3.5.0 14470 Monday, September 7, 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