travis build stages

[UziTech]

Marked version: 76d75e1

Description

Adds build stages to travis-ci to make it easier to see what failed.

Contributor

• Test(s) exist to ensure functionality and minimize regresstion (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• Draft GitHub release notes have been updated.
• CI is green (no forced merge required).
• Merge PR

[joshbruce]

I really like, and am assuming here, that lint comes last; so, we get the really really important sorted first, yeah?

[styfle]

It looks like this ran properly but why is the first node_js line missing the - hyphen prefix?

[UziTech]

that is the same as json:

[
      {
        "stage": "spec tests 👩🏽‍💻",
        "node_js": "v0.10"
      },
      {
        "node_js": "v4"
      }
]

the hyphen is the start of an array item.

[UziTech]

@joshbruce The jobs in each stage run in parallel but each stage runs in series so it will only run Lint if all Test jobs pass.

I was thinking it would be good to add stages for unit and integration tests after they are added.

We could also do a minify stage that would minify and commit after every master branch commit

[joshbruce]

We could also do a minify stage that would minify and commit after every master branch commit

Could be a good thing. If we do that, we should make a note to update the RELEASING docs.

[joshbruce]

#1119

[joshbruce]

::sad trombone:: https://travis-ci.org/markedjs/marked/builds/365594264?utm_source=email&utm_medium=notification

[joshbruce]

@UziTech ^^

[UziTech]

this ☝️ should be on #1132