atomist-attic/travis-rugs

Atomist Rug handlers for Travis CI

Atomist 'travis-rugs'

A set of Rugs that that integrate with Travis CI.

Read more about automating software development at Automating Our Development Flow With Atomist. Detailed documentation is available in the Atomist Documentation.

Support

General support questions should be discussed in the #support channel on our community Slack team at atomist-community.slack.com.

If you find a problem, please create an issue.

Contributing

If you are interested in contributing to the Atomist open source projects, please see our contributing guidelines and our code of conduct.

Developing

You can build, test, and install the project locally with the Rug CLI, Node.js, and Yarn.

$ cd .atomist
$ yarn
$ yarn test

To clean up cached files and update TypeScript dependencies, run this command.

$ ( cd .atomist && find editors generators handlers tests -name '*.js' -print0 | xargs -0 rm; rm -rf node_modules; yarn && rug clean )

To create a new release of the project, simply push a tag of the form M.N.P where M, N, and P are integers that form the next appropriate semantic version for release. For example:

$ git tag -a 1.2.3

The Travis CI build (see badge at the top of this page) will upload the needed artifacts.

---

Created by Atomist. Need Help? Join our Slack team.

travis-rugs's Issues

Handle non-github-owners for Travis build enablement

Reported by @jessitron:

Enabling Travis builds is very impressive in our demos. Spinning up CI is a big pain point in new service creation IRL.

However, it only works if you're an owner on the GitHub repo. That is not the case for most developers.

Currently the error I get is that it was unable to run the rug. Completely opaque. in Logz.io I find "500 Server Error" from Travis, so it's not giving us any help in identifying the problem.
Let's handle this!

• notice that the person is not an owner; ask them to have an owner enable the repo for builds. (Can we list the people who are owners?)
• skip the Enable Build travis call when it is not necessary (it's already enabled). Then people can proceed.

... later we can think about ways to let orgs let devs enable builds without being a github owner.

Tag builds are not reported

We report on Push and PR builds, but not tag builds.

Restart build handler should send "org" parameter based on visibility of the repo

@tanya-coding commented on Tue Mar 07 2017

Currently build handler doesn't pre-populate "org" parameter so bot ends up using default ".org" which is not correct for all organizations. Handler should instead use repo information and populate the parameter. This will likely require changes in model as well.

cc: @cdupuis @whostolebenfrog

---

@whostolebenfrog commented on Tue Mar 07 2017

This will likely require changes in model as well

To be specific this information isn't currently recorded on a repo. Also need to take into account that repos might move between public and private.

An alternative is that we do currently have build_url available on the build itself which would work right now with no model changes.

---

@kipz commented on Wed Mar 22 2017

Shouldn't this be another MappedParameter @tanya-coding ?

---

@tanya-coding commented on Tue Apr 11 2017

@kipz bot doesn't really know if it should use ".org" or ".com" for a given repo, seems like handler should be able to make that determination based on model it loads.

Remove duplication of common TS stuff with github-handlers

Common.ts and SlackTemplates.ts is in both.

Should probably go in some common node module - maybe @johnsonr is working on one of these?

atomist-attic/github-rugs#15

Add enable/disable repo command handlers

We should have simple command handlers to enable and disable a repo from the bot.

Typo in PR event handler

https://github.com/atomist-rugs/travis-handlers/blob/master/.atomist/handlers/event/Build.ts#L119

There is a typo on build.triggerdBy().

I'm also wondering if this should be build.triggeredByPr() anyway?

Error on npm install

When running npm install I got the following error:

npm install

> @atomist/[email protected] postinstall /Users/ben/workspace/travis-handlers/.atomist/node_modules/@atomist/rugs
> tslint **/*.ts

sh: tslint: command not found
npm WARN .atomist No description
npm WARN .atomist No repository field.
npm WARN .atomist No license field.
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.9.0
npm ERR! npm  v4.2.0
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! @atomist/[email protected] postinstall: `tslint **/*.ts`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @atomist/[email protected] postinstall script 'tslint **/*.ts'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @atomist/rugs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tslint **/*.ts
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @atomist/rugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @atomist/rugs
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/ben/.npm/_logs/2017-04-28T10_02_25_819Z-debug.log

I had to run npm install typescript tslint to fix.

Could this be added to the install script somehow? The error is actually a little hard to spot in the output.

@ddgenome Any thoughts on this?

Travis restart button has disappeared

Looks like atomist-attic/rug-functions-travis#11 might be bigger than rug-functions-travis.

The restart button has disappeared from the build failure messages.

Build event handler on PR has an incorrect path expression

The path expression for PR build events starts wiith /Build() when it should be /Build.

Build failure DMs are not working

The build event handler has code to DM the person who made the last Commit on the Push that triggered the Build, but they do not work.

Update rugs to use new single parameter class decorators

e.g.

@CommandHandler("description")