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

publishToCrates - publish to crates.io (rust artifacts) #155

Closed
1 task done
Tracked by #2505
gaiksaya opened this issue Mar 1, 2023 · 2 comments · Fixed by #194
Closed
1 task done
Tracked by #2505

publishToCrates - publish to crates.io (rust artifacts) #155

gaiksaya opened this issue Mar 1, 2023 · 2 comments · Fixed by #194
Assignees

Comments

@gaiksaya
Copy link
Member

gaiksaya commented Mar 1, 2023

Add a jenkins library to allow artifacts to be able to published to crates https://crates.io/

Acceptance Criteria

- [ ] Artifacts should be signed before publishing

  • Artifacts should be published in an automated manner without any human intervention
@gaiksaya gaiksaya transferred this issue from opensearch-project/opensearch-build Mar 1, 2023
@gaiksaya gaiksaya removed the untriaged label Mar 2, 2023
@gaiksaya
Copy link
Member Author

gaiksaya commented Mar 2, 2023

[Triage] We will be working on this in next few weeks.

@gaiksaya
Copy link
Member Author

From opensearch-project/opensearch-build#3247 (comment)

Did some research around publishing the rust clients to crates.io.

Here are few findings:

  1. There is no mechanism to sign crates (yet!) See Security model / TUF rust-lang/crates.io#75 for details
  2. We need to have rust toolchain installed to run crago commands. (Adding cargo installation on docker image used for release)
  3. CI systems you can use the CARGO_REGISTRY_TOKEN environment variable to publish programmatically or just use --token. https://doc.rust-lang.org/cargo/commands/cargo-publish.html
cargo publish --token <token>

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

Successfully merging a pull request may close this issue.

1 participant