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

bitbucket-build-status

v1.2.0

Published

Creates Bitbucket Build Statuses via REST

Downloads

200

Readme

Bitbucket Build Status

A small tool for POSTing build statuses to Bitbucket.

Installation

$ npm install -g bitbucket-build-status

Usage

$ bbuild --help

Usage: bbuild [options]

Options:

-h, --help                       output usage information
-e, --server <url>               the Bitbucket Server Base URL to POST the build status to (omit if targeting bitbucket.org)
-c, --commit <commit>            the commit to lodge the build status against
-r, --repo <repo>                the repository slug containing the commit
-o, --owner <owner>              user or team that owns the repository (defaults to username if omitted)
-s, --state <state>              INPROGRESS, SUCCESSFUL or FAILED
-k, --key <key>                  the build key
-n, --name <name>                the build name
-l, --url <url>                  the build url
-d, --description <description>  the build description
-u, --username <username>        the user to authenticate as
-p, --password <password>        the user's password
-f, --file <file>                JSON file containing the state, key, name, url and description. Values can be overridden with other commandline options

Example

$ bbuild -c <commit> -r <repository> -u <username> -p <passowrd>

Testing

Currently, changes can only be tested locally.
* In Bitbucket:
    - You can use one of your repository or create a new one. (Make sure, you have setup pipelines and run at least 1 build).
    - You need to create an app password to authenticate to Bitbuvket API.
* In your terminal:
    - Run
     $ node index.js -c <commit> -r <repository> -u <username>  -p <app password>
    - You should get:
     $ Created https://api.bitbucket.org/2.0/repositories/<username>/<repository>/commit/<commit>/statuses/build/BBS