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

travis-ping

v1.0.2

Published

manually trigger travis builds

Downloads

12

Readme

travis-ping

manually ping travis-ci to restart the last build.

Useful if an external dependency (like a plugin/module, server, or service) was down when the test originally ran, or if your testing target changes over time (like a▸ web scraper).

requirements

  • A repo that has testing enabled and at least one test previously ran
  • Github credentials for an account with access to the travis repo

Use it as a node module

  var travisPing = require('travis-ping');
  travisPing.ping(
    {username: 'patrickkettner', password: 'mYr33lP4$5w0rd101jk'}, // Credentials
    'patrickkettner/travis-ping',                                  // Repository
    {branch: 'master'},                                            // Filter
    function(travisResponse) {                                     // Callback
      console.log(travisResponse)
    }
  )

or as a command line tool

  travis-ping patrickkettner/travis-ping [options]

Credentials

When run from the commandline, you are asked for your username and credentials.

Alternatively you may supply a GitHub personal access token with --token [token] or the GITHUB_TOKEN environment variable and use the tool without interaction. When using as a module set {github_token: token} instead of the username and password.

To connect to the Pro API (travis-ci.com), use the --pro option. As module, add pro: true to the credentials.

Filter

You can filter on a branch using --branch [branch] to restart the last build of a specific branch. As module, use {branch: branch} as filter.

Use --push to restart a build for a push event, excluding builds for pull requests. The --pull-request option will do the oposite. As module, set {eventType: 'push'} or {eventType: 'pull_request'} as filter.