Downloads:

2,399

Downloads of v 1.11.2.1123:

1,019

Last Update:

14 May 2016

Package Maintainer(s):

Software Author(s):

  • Stefan Kueng

Tags:

subversion svn monitor

CommitMonitor

1.11.2.1123 | Updated: 14 May 2016

Downloads:

2,399

Downloads of v 1.11.2.1123:

1,019

Maintainer(s):

Software Author(s):

  • Stefan Kueng

Tags:

subversion svn monitor

CommitMonitor 1.11.2.1123

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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

>

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

>

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

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


Chocolatey::Ensure-Package
(
    Name: commitmonitor,
    Version: 1.11.2.1123,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller commitmonitor
{
   Name     = 'commitmonitor'
   Ensure   = 'Present'
   Version  = '1.11.2.1123'
   Source   = 'STEP 3 URL'
}

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


package { 'commitmonitor':
  provider => 'chocolatey',
  ensure   => '1.11.2.1123',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install commitmonitor version="1.11.2.1123" 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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 05 Jul 2020.

Description

CommitMonitor is a small tool to monitor Apache™ Subversion® repositories for new commits. It has a very small memory footprint and resides in the system tray.

In case you have multiple repositories under an SVNParentPath with the SVNListParentPath directive activated in Apache, CommitMonitor can monitor these URLs too, as you can see in the screenshot above: the "Private Projects" is shown as a folder, which means this is an URL to an SVNParentPath URL.

The new commits are shown on the top right of the main dialog, while the commit log message is shown at the bottom right.

A double click on any revision in the top right view will fetch the diff for that revision as a unified diff so you can further inspect the commit. If you have TortoiseSVN installed, CommitMonitor automatically uses TortoiseSVN to do the diff.

Of course, you can configure the time interval CommitMonitor should check your repositories for new commits.

Just make sure in case you want to monitor a public open source repository to set the check interval not too small - you don't want to hammer those repositories!

You can also put an svnrobots.txt file on your repository server to set a minimum time interval. See the svnrobots documentation for more details about this.

Once CommitMonitor has found new commits to one or more of the repositories you monitor, it shows a notification popup, and the system tray icon changes the "eyes" from black to red. And if you have the system tray animation enabled in the Options dialog, the eyes will also move around until you open CommitMonitor's main dialog (by double-clicking on the system tray icon) and read the commits.

If you have Snarl installed, CommitMonitor automatically uses Snarl to show its popups.

CommitMonitor also registers itself with Snarl which will allow you to configure the popups in more detail.

As already mentioned, CommitMonitor resides in your system tray (if so required). Tools which do that should use as less resources as possible, and that's what CommitMonitor tries to do. As you can see in the screenshot below, when the program is idle (i.e., not currently connecting to a repository and downloading information) it only uses about 1MB of RAM. Of course, it uses more (about 15MB RAM) while it accesses the repositories.

Source Code

tools\chocolateyInstall.ps1 
# MetaPackage
tools\chocolateyUninstall.ps1 
# powershell v2 compatibility
$psVer = $PSVersionTable.PSVersion.Major
if ($psver -ge 3) {
  function Get-ChildItemDir {Get-ChildItem -Directory $args}
} else {
  function Get-ChildItemDir {Get-ChildItem $args}
}
$warningPreference = "Continue"
$chocoLib = Join-Path $env:ChocolateyInstall "lib"
if (Test-Path -PathType Container (Join-Path $chocoLib 'commitmonitor.*')) {
  Write-Warning "Uninstall NOT complete."
  Write-Host 
@"
  This package is a metapackage; a chocolatey feature not yet fully implemented.
  To retain future compatibility this package does not uninstall the dependent
  package it points to as designated with *.install or *.portable.`n
"@
  Write-Warning "To finish removing the program installed by package commitmonitor, please also run the command:"
  $text += " `n`tchoco uninstall "
  $list = (Get-ChildItemDir $chocoLib\commitmonitor.*).Name
  foreach ($i in $list) {
    $text += "$i "
  }
  $text += "-y`n"
  Write-Host $text
}

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
CommitMonitor 1.11.2.1123 1019 Saturday, May 14, 2016 Approved
CommitMonitor 1.11.1.1099 344 Saturday, October 31, 2015 Approved
CommitMonitor 1.11.0.1073 253 Saturday, August 22, 2015 Approved
CommitMonitor 1.10.2.1025 384 Wednesday, April 1, 2015 Approved
CommitMonitor 1.8.7.831 305 Wednesday, April 1, 2015 Approved
Discussion for the CommitMonitor Package

Ground Rules:

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