Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create publishToNpm jenkins library #2637

Closed
Tracked by #2505
gaiksaya opened this issue Sep 16, 2022 · 1 comment · Fixed by opensearch-project/opensearch-build-libraries#21
Closed
Tracked by #2505

Create publishToNpm jenkins library #2637

gaiksaya opened this issue Sep 16, 2022 · 1 comment · Fixed by opensearch-project/opensearch-build-libraries#21
Assignees

Comments

@gaiksaya
Copy link
Member

gaiksaya commented Sep 16, 2022

Node JS clients will be published on NPM under @opensearch-project namespace. Component that can be used for this library testing is JS client: https://github.com/opensearch-project/opensearch-js

Acceptance Criteria:

  • The library needs to be generic enough to accept any JS artifact
  • Publish to NPM without manual intervention
@gaiksaya gaiksaya changed the title publishToNpm: Node JS clients will be published on NPM Create publishToNpm jenkins library Sep 16, 2022
@gaiksaya
Copy link
Member Author

gaiksaya commented Oct 19, 2022

Putting some research details out:

NPM packages can be easily published using npm automation tokens specifically designed for CI/CD systems. More details: https://docs.npmjs.com/creating-and-viewing-access-tokens#creating-tokens-on-the-website
The package should allow auto publishing via tokens. Good article read

We need to create a new automation token (one time effort) and then use it in our CI/CD to publish the packages. The project needs to have a .npmrc file with below details:

//registry.npmjs.org/:_authToken=${NPM_TOKEN}

source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant