Add a publish-build-info command for reporting build results to crates.io #5099
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
Like #3627 looks great to me! I think we can mege whenever crates.io is ready |
|
☔ The latest upstream changes (presumably #5152) made this pull request unmergeable. Please resolve the merge conflicts. |
|
I'm gonna close this for now as it's pretty out of date at this point, but it can of course be resubmitted! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're working on reviving this old thing :) The associated crates.io PR should go in first.
This goes with rust-lang/crates.io#764. @shepmaster worked on these too :)
This PR adds a cargo command,
publish-build-info, which allows crate owners to report crate version, rust version, target, and pass/fail to crates.io.The purpose is to enable crate authors to automatically report to potential crate users on the Rust version and platform compatibility of each version of the crate.
The idea is that this command would be added to CI, and an example of configuration for Travis is in the documentation we added. We haven't actually tested that configuration out yet; we wanted to get these PRs in for feedback before we set up crates.io instances that weren't local but that we could publish to :) We want to add Appveyor too, but we want to test the travis configuration first.
We also thought about, but didn't implement:
AnOverwriting is now the default behavior.--overwriteflag to allow editing of an already-reported-on crate version+rust version+target combination, to allow for correcting errors if reporting manually--targetsince there was already support for that flag :)