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

hubot-github-tfs

v0.9.4

Published

A Hubot script to integrate GitHub and Microsoft Team Foundation Server (TFS)

Downloads

28

Readme

Build Status

hubot-github-tfs

A Hubot script to integrate GitHub and Microsoft Team Foundation Server (TFS). You can now automatically trigger a TFS build following a push on a pull request and get the build result back.

Installation

  • In hubot project repo, run:

npm install hubot-github-tfs --save

  • Then add hubot-github-tfs to your external-scripts.json:
[
  "hubot-github-tfs"
]
  • Set the following environment variables in the shell where Hubot is running

| Variable | Required/Optional | Comments | |----------|---------|----------| |HUBOT_TFS_SERVER|required|Ip or DNS name of the TFS server| |HUBOT_TFS_USERNAME|required|TFS username| |HUBOT_TFS_PASSWORD|required|Password of the TFS user| |HUBOT_TFS_GITHUB_PAT|optional|Personal Access Token of the GitHub user with repo:status permission. This will be used to update the pull request status.| |HUBOT_TFS_PROTOCOL|optional|default to https| |HUBOT_TFS_PORT|optional|default to 80 for http and 443 for https| |HUBOT_TFS_URL_PREFIX|optional|default to /| |HUBOT_TFS_DEFAULT_COLLECTION|optional|default to defaultcollection|

  • Create a webhook on your GitHub repo for the Push event with the following URL :
http://<hubot_server>/hubot/github-tfs/build/<room>
  • Create a webhook on TFS with the following URL so Hubot can receive the notification back
http://<hubot_server>/hubot/github-tfs/build-result/<room>
  • Make sure the IIS server running TFS as basic authentication enabled.

Sample Interactions

Get some help

**user1**>> hubot tfs-build help
**hubot**>>Here's what I can do with TFS builds :
tfs-build list builds for <project>
tfs-build list builds for <project> from <collection>
tfs-build queue <project> with def=<definition id>
tfs-build queue <project> from <collection> with def=<definition id> branch=<branch name>
tfs-build list definitions for <project>
tfs-build list definitions for <project> from <collection>
tfs-build rem all
tfs-build rem about <org>/<repo>
tfs-build forget about <org>/<repo>
tfs-build rem <org>/<repo> builds with <project>/<definition id>
tfs-build rem <org>/<repo> builds with <project>/<definition id> from <collection>

List builds

**user1**>> hubot tfs-build list builds for SpidersFromMars
**hubot**>>
----------------------------------------------------------------------------------------
| Build       | Status   | Result  | Branch             | Definition                   |
----------------------------------------------------------------------------------------
|20160407.2   |completed |succeeded|master              |SpidersFromMars on github.com |
|20160407.1   |completed |failed   |master              |SpidersFromMars on github.com |
|20160331.19  |completed |succeeded|master              |SpidersFromMars on Octodemo   |
|20160331.18  |completed |failed   |master              |SpidersFromMars on Octodemo   |
|20160331.17  |completed |succeeded|syntaxerror         |SpidersFromMars on Octodemo   |
|20160331.16  |completed |failed   |synataxerror        |SpidersFromMars on Octodemo   |
----------------------------------------------------------------------------------------

List build definitions for a project

**user1**>> hubot tfs-build list definitions for SpidersFromMars
**hubot**>> Found 1 results for SpidersFromMars in
**hubot**>>
--------------------------------------
| ID  | Name                         |
--------------------------------------
|1    |SpidersFromMars on Octodemo   |
--------------------------------------

Remind me which build definition is used to automatically trigger the build of a repository

**user1**>> hubot tfs-build rem about OctoCheese/SpidersFromMars
**hubot**>> OctoCheese/SpidersFromMars builds with defaultcollection/SpidersFromMars/1

Automatically build in TFS following a push in GitHub

**user1**>> hubot tfs-build rem OctoCheese/SpidersFromMars builds with SpidersFromMars/1
**hubot**>> Saved build setting for SpidersFromMars. Now building with defaultcollection/SpidersFromMars/1

Note : The build definition id 1 was retrieved with the list definitions command

Whenever a push happens on this repo, Hubot will comment in the room specified in the webhook URL and trigger the registered build.

**hubot**>> @helaili just pushed code on OctoCheese/SpidersFromMars/testTFS. Requesting a TFS build with defaultcollection/SpidersFromMars/1