Use the repository after publishing multiple versions of the same artifact
What feature or behavior is this required for?
Successful long-term usage of the repo
How could we solve this issue? (Not knowing is okay!)
By uncovering the root cause
Anything else?
Reproducible steps:
Start the repo locally: docker build -t nexus-repository-cargo . then docker run --rm -p 8081:8081 --name nexus-repository-cargo nexus-repository-cargo
Do the initial setup (admin password; configure crate realm; create a repo of type cargo - say, named, crates-snapshot and obtain a token for publishing - by calling /repository/crates-snapshot/token endpoint)
Obtain a Rust crate to publish
cargo publish the crate into local repo
modify the version of the crate to be version + 1 patch
attempt to clone the index git clone http://localhost:8081/repository/crates-snapshot/index
repeat steps 4 to 6 until step 6 fails with 500 server error and the attached stacktrace.log shows up in the Nexus logs
Use the repository after publishing multiple versions of the same artifact
Successful long-term usage of the repo
By uncovering the root cause
Reproducible steps:
docker build -t nexus-repository-cargo .thendocker run --rm -p 8081:8081 --name nexus-repository-cargo nexus-repository-cargocargo- say, named,crates-snapshotand obtain a token for publishing - by calling/repository/crates-snapshot/tokenendpoint)cargo publishthe crate into local repogit clone http://localhost:8081/repository/crates-snapshot/index