Add Wercker and more

[honzajavorek]

Summer cleanup 😎

• Preparing for CircleCI 2.0 support in Dredd's dredd init
• Adding Wercker
• Using simpler naming for several files
• Being more explicit in the README about where all the files are, to which service they belong, etc.
• Adding Jenkins to the README even though it's not live-tested
• Swagger is dead, long live the OpenAPI 2 (preparing for OpenAPI 3 support in Dredd and elsewhere)

[honzajavorek]

@nadade @kylef Call for help 🙋‍♂️

I'm trying to make Wercker to npm install --no-optional, but the no optional flag seems to be ignored - it still installs protagonist:

...
export WERCKER_NPM_INSTALL_OPTIONS="--no-optional"
source "/pipeline/npm-install-83ebc85d-4d44-47f3-a21f-75237025acae/run.sh" < /dev/null
Using wercker cache
Creating $WERCKER_CACHE_DIR/wercker/npm
Configuring npm to use wercker cache
Starting npm install, try: 1
npm WARN deprecated json-schema-faker@0.5.0-rc13: Broken not support
npm WARN deprecated nomnom@1.5.2: Package no longer supported. Contact support@npmjs.com for more info.

> protagonist@1.6.8 install /pipeline/source/node_modules/protagonist
> node-gyp rebuild
...

Even if I tried to create my own step, it was still ignored and Wercker just installed the project as without --no-optional, compiling protagonist. Any ideas?

[kylef]

@honzajavorek I think this may be NPM bug: https://npm.community/t/npm-install-no-optional-not-actually-filtering-optionals-in-cli-6-0-1-or-6-1-0/257 / https://github.com/npm/npm/issues/17633#issuecomment-403938408

Perhaps you can work around the issue with having a package-lock.json generated without protagonist. Probably something you should do regardless due to transient dependency licensing approval.

[honzajavorek]

Oh, package-lock.json is a different can of worms I'll need to resolve later. Thanks for looking into it, I think I'm fine with Wercker installing protagonist now.