Add CI Integration about speedtracker HOT 7 CLOSED

@eduardoboucas looking for feedback here when you get around to it. I'm not sure how much of this system you want to open up. but keys can be encrypted using the travis CLI tool.

from speedtracker.

I'd love to see this happening! +1 for Travis.

from speedtracker.

Awesome. Here's an example Travis file to model from for an existing Jekyll site:

https://github.com/jhabdas/habd.as/blob/master/.travis.yml

It's using a Rakefile, though that's not necessary for regular Jekyll builds to GH. That particular site is hosted on an S3 bucket behind CloudFront for HTTPS/2.

Please let me know how I can help.

from speedtracker.

Here's what I do every time I release a new version of the dashboard:

• Update the version in package.json
• Update the version in the README file
• Create a new GitHub tag/release

How much (if any) of this do you think could be automated by the CI tool?

from speedtracker.

How much (if any) of this do you think could be automated by the CI tool?

Everything except the version in the README, which could be replaced with a CHANGELOG.md and automatically generated with standardization of commit messages.

If you want that level of automation it's not difficult. There are a few different ways to go about it, two of which I have experience with:

Semantic Release

• Designed for packages.
• Highly opinionated.
• Batteries not included.
• Extreme automation.
• CHANGELOG kept in GitHub versions page.
• Requires published package (sets 0.0.0-dev version in repo, always)

Example implementation (see manifest and click versions to view changelog):
https://github.com/jhabdas/fetch-inject/

Personal thoughts:
Carries so much automation you may find yourself up late at night trying to figure out how to back of something which went wrong. Viewing CHANGELOG requires an internet connection.

Standard Version

• Designed for just about anything.
• Not as opinionated.
• Easy to use.
• Good enough automation.
• CHANGELOG kept in source code (necessitating version bump commits, automated).
• Does not require published NPM package (modifies manifest when generating changelog)

Example implementation:
https://github.com/comfusion/after-dark

Personal thoughts:
If Goldilocks were here she'd probably say this porridge was just about the right temperature.

from speedtracker.

Adding to more options, neither of which require conventional commits AFAIK:

https://github.com/zeit/release or https://github.com/egoist/changelog.md

@egoist is the creator of hackcss

from speedtracker.

Sorry I dropped the ball on this! I may loop back after I finish moving my creative work off GH as SpeedTracker is still the best free way I've seen to monitor metrics.

from speedtracker.