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

ci-jira

v0.0.7

Published

Node package to add CI features for simple JIRA transactions

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jovermarsjovermars

Keywords

Readme

Build Status Coverage Status

ci-jira

Package to add CI features for simple JIRA and BitBucket Cloud transactions

Installation

npm install @jovermars/ci-jira

Usage

Atlassian

To be able to connect to Atlassian JIRA or BitBucket the following parameters need to be specified. By default https will be selected as protocol, but this can be overwritten if necessary.

Options

  • username: Atlassian JIRA or BitBucket username
  • password: Password for the username

fix-version

Assigns the issues to the specified vrsion in the JIRA project. Return the number of issues that have been updated with the fixVersion

Remarks

If the version of the JIRA project of the tickets does not exist yet it will be created in the project. If tickets from multiple projects are specified then fixversion creates the version in each project.

All issues will be added to the version if it has not been assigned to the version yet. Other versions in the fixversion value of the issue will be respected.

Example

grunt fix-version --versionName=1.0.Test --issues=DM-1,DM-2 --username=john.doe --password=secret --host=test.jira.com

Options

  • host: Hostname of JIRA instance (e.g. company.jira.com)
  • versionName: Name of the version to be created in the related JIRA project
  • issues: Comma separated list of JIRA issues to be updated

merged-between

Returns all JIRA issues numbers between two commits by connecting to the BitBucket cloud API and analysing all commit messages in between

Example

grunt merged-between --owner=company_name --slug=test_repository --hashFrom=f42ed1ffd1ddbf83fa66ebc1ddb380a0401ed3b1 --hashTo=6a49aab7fcae427b77631b13cb0c58e924151196 [email protected]=secret --branch=master

Options

  • owner: Name of the owner of the repository. This value can be found in the url of the repository in BitBucket
  • slug: Name of the repository
  • toFrom: The newest SHA1 of the commit on the branch in the repository
  • hashFrom: The oldest SHA1 of the commit on the branch in the repository
  • branch (optional): Default master. Name of the branch to analyse

merged-since

Returns all JIRA issues numbers until and including the specified commit by connecting to the BitBucket cloud API and analysing all commit messages

Example

grunt merged-till--owner=company_name --slug=test_repository --hashTo=6a49aab7fcae427b77631b13cb0c58e924151196 [email protected]=secret --branch=master

Options

  • see merged-between

Tests

npm test