Downloads:

1,453

Downloads of v 1.2.2:

151

Last Update:

06 Jul 2018

Package Maintainer(s):

Software Author(s):

  • Dennis Doomen

Tags:

teamcity build-monitoring delcom ci continuous integration

Beacon

This is not the latest version of Beacon available.

1.2.2 | Updated: 06 Jul 2018

Downloads:

1,453

Downloads of v 1.2.2:

151

Maintainer(s):

Software Author(s):

  • Dennis Doomen

Beacon 1.2.2

This is not the latest version of Beacon available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall Beacon, 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 beacon -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 beacon -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 beacon installed
  win_chocolatey:
    name: beacon
    state: present
    version: 1.2.2
    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 'beacon' do
  action    :install
  version  '1.2.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: beacon,
    Version: 1.2.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller beacon
{
   Name     = 'beacon'
   Ensure   = 'Present'
   Version  = '1.2.2'
   Source   = 'STEP 3 URL'
}

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


package { 'beacon':
  provider => 'chocolatey',
  ensure   => '1.2.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install beacon version="1.2.2" 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 by moderator gep13 on 17 Jul 2018.

Description

Beacon is a little command-line tool that lets you connect a Delcom USB RGB LED light to a set of TeamCity builds and use that to get an irrefutable indication on whether those builds succeeded, failed or are under investigation.

To get started just run the following command-line:

beacon --url=http://yourteamcity.com --username=username --password=password --builds=build_id_1 build_id_2 etc

or, alternatively using TeamCity guest access and running only once with verbose logging:

beacon --url=http://yourteamcity.com --guestaccess --runonce --verbose --builds=build_id_1 build_id_2 etc


tools\Beacon.Core.dll
md5: 3DC1A95964CF2AC8304D02E9CBC75854 | sha1: C961C7A05BDF67C456013AC69C2D0F5F47BF39A0 | sha256: 89F67F77B59F0FAB671A249F97A4A6E4329764A0E89AE343821703989EC7A3C1 | sha512: 048E2871EA52CD31E2D5A0289FC0BD16B5203B5D35237B5F57D5FA3BD92301E6EEBE88A80519B77534971526FD56F99EDE27CB6B074E5A5D62D48D0AC177BF76
tools\Beacon.Core.pdb
 
tools\Beacon.exe
md5: F5C867BA08C43F4B62D0554621547434 | sha1: F625F4AF787BF1A0E0206C45521C0637856A9349 | sha256: 7B9654EB6BA73CF560FF04DD595807D9AE98F7D7A5CB0269CA5B542BB31105F0 | sha512: 9E528C67C378929E74B5131735642678FB5EF7A5B6F430F7E0A49B9A7C9463BA41B9773AD67E50124C87ECAB16B04F1339FC861AE78D16489028CF8CE35555ED
tools\Beacon.exe.config
<?xml version="1.0" encoding="utf-8"?>

<configuration>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
</configuration>
tools\Beacon.Lights.dll
md5: E2AB77AF7F77D22564F001158BEF6129 | sha1: 1B9E5C59AC5C2BA87A73945CE0E59E7621B1879D | sha256: 0F1DD169CD0B7CC89958C3D212FB10C2669E4A97AA83983919799B4570446E3B | sha512: DCB2B1F600CBFBB055BC680200CBEEA43215D8A981C1F0B668AB6CD66F5AEBC651A14125C7CC0FFD89D636A81376F8A6012D95E33DAB5411C43A753CE892B746
tools\Beacon.Lights.pdb
 
tools\Beacon.pdb
 
tools\CommandLine.dll
md5: 412350D8CB73963992FE5A1F1A393446 | sha1: D0DA7B533B7A46811E343E14A07A5AABC4FA3964 | sha256: C1FBB1989141F69D90C46A73D6E3BBD7895F5FC4D267A830C7D5CE0D0FB8D6B2 | sha512: 25B033AC931FD25394370A84AAFB36441D6A6E1D3A57CC8C5B629AC0941AF4EFD66691AA14C69E79EBA9AD4E166B6BC3FA5D1594A22E392881F50C644B2A9749
tools\DelcomDLL.dll
md5: 87386F771C7F79B90E7CAC6495152287 | sha1: 2A846A395FF363B6A720967664BF5B41F79D7B5F | sha256: 63C75524B8941C387694DF59C0BE5EBF7E7A0B437BECB884758799964B2940C8 | sha512: FDB924E454BF8A76BC508DCCDDB4AC6A2ABD5E9F8E346C0E3B46638FA1FE46C70520F2B7B9AD91BF8C14BC1D9079B98264131AEC51096828D4302E255C3025CC
tools\LICENSE
 
tools\README.md
<!-- markdownlint-disable MD041 -->
[![Build status](https://ci.appveyor.com/api/projects/status/sm9eoe5qd48b44ay?svg=true)](https://ci.appveyor.com/project/dennisdoomen/beacon)

# Beacon

A TeamCity monitoring tool that uses a Delcom USB LED light to notify your teams

![Chocolate](./Images/Screenshot.png)

## Backlog

* Support for configuring the RGB values, flash mode and power level of the LED.
* Support for including all TeamCity projects under a certain project node, including more advanced filtering rules.
* Deployment as a Windows Service.

## How to install

The easiest deployment mechanism is to install [Chocolatey](https://chocolatey.org/) and run the following command-line to install the [Chocolate package](https://chocolatey.org/packages/beacon):

    choco install beacon

Then run `beacon` and observe the command-line arguments.

## Example usage

Using a named TeamCity account and running continuously:

    beacon --url=http://yourteamcity.com --username=username --password=password --builds=build_id_1 build_id_2 etc

Or, alternatively using TeamCity guest access, running only once and with verbose logging:

    beacon --url=http://yourteamcity.com --guestaccess --runonce --verbose --builds=build_id_1 build_id_2 etc

## Why another

My original idea was triggered by [TeamFlash](https://github.com/Readify/TeamFlash), a prototype implementation made by Readify. Unfortunately, the quality of that code was way below anything I can work with, so I planned to contribute a big list of improvements as well as more configuration options. However, it took me several emails, tweets and DMs and a month of patience just to get a [single pull request](https://github.com/Readify/TeamFlash/pull/16) accepted. So I see no point in working with a fork. Instead, I decided to take their code as a starting point and revive the product.
tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
This package is published by the Beacon project itself. Any binaries will be 
identical to the ones published by the AppVeyor build mentioned on the GitHub 
project page.

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
Beacon 1.2.2 151 Friday, July 6, 2018 Approved
Beacon 1.1.1 374 Friday, April 21, 2017 Approved
Beacon 1.0.1 423 Tuesday, February 24, 2015 Approved

This first version is still a bit rudimentary, but keep an eye on the project site to see some of the things being worked on.


This package has no dependencies.

Discussion for the Beacon Package

Ground Rules:

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