npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

verzasca

v1.0.7

Published

Add some friction if teamcity builds are red

Downloads

179

Readme

verzasca

CLI tool to check teamcity builds add friction if you've got broken builds

npm Build Coveralls License

Installing

Install globally npm install -g verzasca

When would I use this?

Add this as a git pre-hook as part of your git push then you can avoid putting more commits on top of a broken build.

An example pre-push might look a little like this

#!/bin/bash
#allow interactive shell commands
exec < /dev/tty

# check for broken builds
verzasca --url http://teamcity --auth ABCDEFGHIG --builds Build1,Build2 || exit

Usage + Example

Usage: index [options]

Options:

  -h, --help            output usage information
  -V, --version         output the version number
  --url <url>           Set teamcity url
  --builds <builds...>  The builds to check the status of (comma separated)
  --auth <auth>         Basic auth token for teamcity

This is an example command which will result in output like below

verzasca --url http://teamcity --auth ABCDEFGHIG --builds Build1,Build2
================== TEAMCITY STATUS ==================

Build Name: Build1
Status:     SUCCESS
Url:        http://teamcity/viewLog.html?buildId=123&buildTypeId=Build1

Build Name: Build2
Status:     FAILURE
Url:        http://teamcity/viewLog.html?buildId=124&buildTypeId=Build2

=====================================================
There are broken builds, do you want to continue?
=====================================================
 (Use arrow keys)
❯ Stop
  Continue

Selecting Stop will exit with code 1, selecting Continue will exit with code 0