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

jenkins-client

v2.0.0

Published

a small client for jenkins

Downloads

6

Readme

jenkins-client

a simple NodeJS client for jenkins

Build StatusCode Coverage 100%ISC LicenseNodeJS

JavaScript Style Guide

API

jenkins-client(uri, user, pwd, jobName, [, socketOptions])

  • uri string, the URI for your jenkins server
  • user string, the user to access jenkins
  • pwd string, the password for the user
  • jobName string, the job name we want
  • socketOptions a js object, right now only accepts the timeout property (default to 10 seconds)

jenkins-client#info(callback(err, statusCode, payload))

returns the info about the job

  • callback
    • err an error object
    • statusCode an integer, the returning status code
    • payload a JSON, the job info

jenkins-client#build([parameters,] callback(err, statusCode))

runs a new build for that job

  • parameters should be an array, not required
    • here goes the parameters needed for the job to run if is the case
  • callback
    • err an error object
    • statusCode an integer, the returning status code

jenkins-client#buildResult(jobNumber, callback(err, statusCode, payload))

returns the output from the build

  • jobNumber should be an integer, required
  • callback
    • err an error object
    • statusCode an integer, the returning status code
    • payload a string but ... depends of the the job output

buildResult can return a stream and allows you to pipe the data from the request, the best option

var st = Client(URI, user, pwd, jobName).buildResult(1)
st.on('end', end)
st.on('error', error)

st.pipe(process.stdout)

// or using the event `data`
st.on('data', data)
example
var JenkinsClient = require('jenkins-client')


var jobX = JenkinsClient(uri, user, pwd, jobName[, socketOptions])

jobX.info(getInfo)

function getInfo (err, statusCode, payload) {
    // err - something went wrong
    // statusCode - the http returning status code
    // the JSON payload from your jenkins server
}

ISC License