juliangruber / travis-watch Goto Github PK

Github orgs and repos sometimes aren't strictly lower case, however you can git clone them in any case you want. This results in a local git config pointing to say level/leveldown whereas the real repo is as Level/leveldown. Travis handles repo names in a case sensitive way, and so resolution currently fails.

As mentioned in #35, we should add an additional step to resolve the canonical repository name in case fetching the build from travis fails.

For example for PHP projects.

one step toward #15

so you can require('travis-watch')

Hi,

sorry for this issue having nothing to do whatsoever with this project (which looks pretty cool btw!). I'm just curious about something I spotted in your package.json and haven't seen elsewhere before. I'm sure there's a reason, I'm just curious why something like this is necessary. Thanks 😊

"devDependencies": {
    "prettier-standard-formatter": "^0.222222222222222.333333333333333"
},

I was just trying out travis-watch in my project's master branch and it appeared to get "stuck" in loading build. (I hadn't pushed recently, but was curious what happened regardless)

Poked into the code and it looks like it's just in the getBuild callback repeatedly.
Perhaps I'm holding it wrong :)

Excited to use this.. thanks!

We don't want to cause unnecessary load for travis, so better subscribe to updates instead of polling

https://docs.travis-ci.com/api#external-apis

in the output as well, not just through the exit code

Node version: v4.4.3

Error:

let diff = differ()
^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/Users/m/.nvm/versions/node/v4.4.3/lib/node_modules/travis-watch/index.js:10:16)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

Looks like strict mode isn't enabled in travis-watch/lib/render.js.

I'll submit a PR to fix shortly.

This looks like a great tool we could use in my team, but it doesn't seem to work with private repositories. Happy to help code a solution, but wanted to put an issue in to see if that is something you would like to support or not.

like how long it has been running for

https://travis-ci.org/rails/rails/builds/214406069

Hi

This project looks super cool & i'm really keen to try it but i'm getting errors. Here's what I did (as per readme):

npm i -g travis-watch

cd /path/to/proj
travis watch .

And i get an error:

travis-watch
⠸ Loading jobs/usr/local/lib/node_modules/travis-watch/node_modules/semver/semver.js:293
    throw new TypeError('Invalid Version: ' + version);
    ^

TypeError: Invalid Version: node.0.0
    at new SemVer (/usr/local/lib/node_modules/travis-watch/node_modules/semver/semver.js:293:11)
    at SemVer.compare (/usr/local/lib/node_modules/travis-watch/node_modules/semver/semver.js:342:13)
    at Function.compare (/usr/local/lib/node_modules/travis-watch/node_modules/semver/semver.js:566:31)
    at Object.keys.sort (/usr/local/lib/node_modules/travis-watch/index.js:68:21)
    at Array.sort (native)
    at Object.keys.forEach.os (/usr/local/lib/node_modules/travis-watch/index.js:67:47)
    at Array.forEach (native)
    at render (/usr/local/lib/node_modules/travis-watch/index.js:66:24)
    at check (/usr/local/lib/node_modules/travis-watch/index.js:135:11)
    at travis.jobs.get (/usr/local/lib/node_modules/travis-watch/index.js:55:5)

The project in question is Stayck which i'm working on at the moment.

I assume TW is trying to read version from package.json - this is present in my package.json:

{
  "name": "statyck",
  "version": "1.2.0",
  "description": "A super simple, markdown-based, static blog generator",
  "main": "dist/bin.js",
  "bin": {
    "statyck": "dist/bin.js"
  },
  "config": {
    "force": true
  },
  "ava": {
    "require": [
      "babel-register"
    ],
    "babel": "inherit"
  },
  "scripts": {
...

My apologies if i am doing something stupid - I just can't see what :-).

More than happy to test/investigate/send a PR - is this something you can shortcut at all for me please?

Cheers

@juliangruber Can u tell me, please?

using both travis-watch and appveyor-watch as libs, and render-ci-matrix for output

https://github.com/semantic-release/semantic-release

Uses your npmjs and GitHub tokens to make travis trigger npm publish for every* master build. Requires some standards on commit messages though...

-* every release that has fix and feat commits.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Just tried this out on abstract-leveldown but I can't seem to get any output.

Output:

lms@x240 ~/src/level/abstract-leveldown (TEST)
$ travis-watch 
⠹ Loading build
It is taking unusually long to fetch your build.
Have you pushed your commits yet?

Please please pretty please

we're getting ETIMEDOUTs sometimes

Version 5.5.0 of semver was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

What are thoughts on a command that opens the current travis build? Similar to hub's browse command

https://github.com/github/hub

osx clocks seem to live in the future, showing values like -12394s

either add to this or create a new tool.

This would stream travis log output from your selected build to the terminal.

less clutter

• https://www.appveyor.com/docs/api/
• https://github.com/rhyolight/appveyor-js-client
• https://github.com/finnp/node-appveyor
• https://github.com/kevinoid/appveyor-status