Skip to content

fix semantic-release setup to follow latest rules#23

Merged
alexkli merged 1 commit intomasterfrom
semantic-release
Jul 21, 2020
Merged

fix semantic-release setup to follow latest rules#23
alexkli merged 1 commit intomasterfrom
semantic-release

Conversation

@alexkli
Copy link
Copy Markdown
Contributor

@alexkli alexkli commented Jul 21, 2020

Semantic-release was setup for this repo but it was not working and not following our latest setup with BUGFIX-RELEASE: etc. prefixes.

@codecov
Copy link
Copy Markdown

codecov bot commented Jul 21, 2020

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##            master       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines           70        61    -9     
  Branches        12         0   -12     
=========================================
- Hits            70        61    -9     
Impacted Files Coverage Δ
lib/cpu.js 100.00% <0.00%> (ø)
lib/utils.js 100.00% <0.00%> (ø)
lib/memory.js 100.00% <0.00%> (ø)
lib/metrics.js 100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5c6bb5e...2ce76f2. Read the comment docs.

@alexkli alexkli mentioned this pull request Jul 21, 2020
8 tasks
@alexkli alexkli merged commit 3a8cd52 into master Jul 21, 2020
@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 21, 2020

Let's see if it works :)

@alexkli alexkli deleted the semantic-release branch July 21, 2020 23:28
@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 21, 2020

Unfortunately, semantic release did not work: https://travis-ci.com/github/adobe/node-cgroup-metrics/jobs/363544630

Not quite sure what the issue is, but I see these discrepancies:

  1. it ran the release stage on Windows (why?), but we say condition: $TRAVIS_OS_NAME == linux so it skipped it, doing no release
  2. it run npm run report-coverage which failed as it did not run npm test before (we don't need to report coverage here)

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 21, 2020

Ok, possible answers:

  1. the .travis.yml here listed windows before linux, maybe that tells Travis what OS to use for the release/deploy stage

  2. this seems to happen everywhere, but get ignored. see here, expand the npm run report-coverage part in the logs and see it fails too: https://travis-ci.com/github/adobe/aio-cli-plugin-asset-compute/jobs/363148121

@tmathern
Copy link
Copy Markdown
Member

Drop the other OS from travis.yml: https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L12
This will be a start. Also drop https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L17, we already test 10.15 and 10.19 (should reduce wait times too).

And there seems to be a syntax issue: https://github.com/adobe/node-cgroup-metrics/blob/master/.travis.yml#L39, there should only be one = for the test, according to documentation (https://docs.travis-ci.com/user/deployment-v2/conditional)

@tmathern
Copy link
Copy Markdown
Member

#24

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 22, 2020

See #25.

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 22, 2020

#25 mostly worked, and semantic-release was triggered, but now it failed with This operation requires a one-time password from your authenticator. because likely the NPM token set in travis is old and needs a new one. Will try to update it.

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 22, 2020

Latest try in #27.

@adobe-bot
Copy link
Copy Markdown

🎉 This PR is included in version 3.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 22, 2020

Worked!

@alexkli
Copy link
Copy Markdown
Contributor Author

alexkli commented Jul 22, 2020

Regarding 2. from above: after_script did not help, it also runs on the release stage, see https://travis-ci.com/github/adobe/node-cgroup-metrics/jobs/363568375

But it doesn't fail it either, so we can just keep ignoring it. Suggest we stick to after_success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants