Closed Bug 1602985 Opened 5 years ago Closed 5 years ago

`yarn release` fails to publish clients

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bstack, Assigned: dustin)

References

Details

yarn publish failed in the way seen below. Afaict I had all of my env vars and such set up correctly. It is interesting that error code 66 from release.sh is for detected changes in the repo but as can be seen from my prompt, the repo had nothing in staging. I'll try to debug this further.

taskcluster|master ⇒ yarn release
yarn run v1.21.0
$ node infrastructure/tooling/src/main.js release
... 16 completed tasks
✖ Publish clients/client to npm (Error: npm exited with code 1)
✖ Publish clients/client-web to npm (Error: npm exited with code 1)
✖ Publish clients/client-py to pypi (Error: release.sh exited with code 66)
95% finished
Error: release.sh exited with code 66
    at ChildProcess.<anonymous> (/home/bstack/Projects/taskcluster/infrastructure/tooling/src/utils/pypi.js:41:26)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:210:5)
    at Pipe.<anonymous> (net.js:659:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hm, thanks. We really should restore the create-a-logfile functionality so we can debug these things when they go wrong.

It looks like you followed up with the releases manually -- thanks for that.

Summary: `yarn publish` fails to publish clients → `yarn release` fails to publish clients

https://github.com/taskcluster/taskcluster/pull/2172 won't actually fix the issue, but should help debug it.

Blocks: 1598649
npm ERR! code E401
npm ERR! 401 Unauthorized - PUT https://registry.yarnpkg.com/taskcluster-client - You must be logged in to publish packages.

..which was probably because i was using my own token (which requires MFA).

and from pypi:

There are changes in the local tree.  This probably means
you'll do something unintentional.  For safety's sake, please
revert or stash them!
Assignee: nobody → dustin

Oh, I got the filename wrong, too:

✖ Publish clients/client-py to pypi (Error: release.sh exited with code 66; see /tmp/taskcluster-builder-build/npm-publish-client-py.log for details)

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.