Remove CI to build rustdocs on each release

[JoshOrndorff]

Substrate's CI is supposed to build the rustdocs and publish them to https://github.com/substrate-developer-hub/rustdocs . You can see this has worked for other alphas except for alpha.4 which was cancelled/interrupted.

It did not happen for alpha.6 which is holding up the devhub team from publishing updated tutorials. Who can help daignose this? maybe @gnunicorn or @gabreal

[JoshOrndorff]

In case this isn't solvable, I've started building to docs locally so I can publish manually, but I get lots of filename collision warnings like this. How bad is this? Does it happen in CI?

warning: output filename collision.
The lib target `ansi_term` in package `ansi_term v0.12.1` has the same output filename as the lib target `ansi_term` in package `ansi_term v0.11.0`.
Colliding filename is: /home/joshy/ProgrammingProjects/substrate/target/doc/ansi_term/index.html
The targets should have unique names.
This is a known bug where multiple crates with the same name use
the same path; see <https://github.com/rust-lang/cargo/issues/6313>.

[gnunicorn]

This is an old CI task from when we didn't release on crates.io . Now that we do we can (and should) just use docs.rs: https://docs.rs/sp-io/2.0.0-alpha.6/sp_io/ That seems to have build fine

…

On Wed, 15 Apr 2020, 21:56 Joshy Orndorff, ***@***.***> wrote: In case this isn't solvable, I've started building to docs locally so I can publish manually, but I get lots of filename collision warnings like this. How bad is this? Does it happen in CI? warning: output filename collision. The lib target `ansi_term` in package `ansi_term v0.12.1` has the same output filename as the lib target `ansi_term` in package `ansi_term v0.11.0`. Colliding filename is: /home/joshy/ProgrammingProjects/substrate/target/doc/ansi_term/index.html The targets should have unique names. This is a known bug where multiple crates with the same name use the same path; see <rust-lang/cargo#6313>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5652 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJ4MHTNR76P72OGDJWV6TRMYGNHANCNFSM4MI3MB3A> .

-- Wichtige Mitteilung Diese Mitteilung wurde von Parity Technologies Deutschland GmbH kommuniziert, eine im Handelsregister des Amtsgerichtes Charlottenburg unter HRB 190583 B registrierte Gesellschaft mit beschränkter Haftung (GmbH). Die Geschäftsführerin der GmbH ist Frau Dr. Jutta Steiner. Der registrierte Geschäftssitz ist Glogauer Straße 6 in 10999 Berlin, Deutschland.  Diese Mitteilung enthält Informationen welche vertraulich sind und welche eventuell die Vertraulichkeit der Rechtsberatung ("Anwaltsgeheimnis") berühren. Sie ist ausschließlich für den/die vorgesehenen Empfänger bestimmt. Wenn Sie nicht der/die beabsichtigte(n) Empfänger sind, benachrichtigen Sie bitte admin@parity.io <mailto:admin@parity.io> und löschen Sie diese Nachricht sofort. Unsere Datenschutzrichtlinie, einschließlich die Art und den Umfang von personenbezogenen Daten, die wir erfassen, wie wir diese Daten erfassen und verarbeiten, an wen wir sie in Bezug auf die von uns angebotenen Dienste weitergeben dürfen, sowie bestimmte Rechte und Optionen, die Sie in dieser Hinsicht haben, finden Sie unter: https://www.parity.io/privacy/ <https://www.parity.io/privacy/>

[gabreal]

sounds great. if the substrate-developer-hub/rustdocs repo is not needed anymore i will remove the ci job publish-gh-doc

[gnunicorn]

it failed to compile because of a change in process: we publish under ci-release-*-tags now, and only tag the release post-merge (to have the commit in master after squash-merging). However, this currently means cargo unleash check doesn't find any unpublished packages and interrupts. this leads to the other tasks not being run:

https://gitlab.parity.io/parity/substrate/pipelines/87894

We could just skip unleash on v*-tags and be good, everything should go back as before. That said, us publishing the docs was always a band-aid solution because we didn't publish on crates.rs (yet). I can see the point of still publishing master (after every merge probably?!?), but we should really fade out publishing releases locally, too.

If the reason for that is, that links need updating, we should sed-replace them with the new docs.rs and change the current http-moved to docs.rs .

[gabreal]

building it on master only would make sense imo 👍 eventually releasing it but not sure what the use would be for that.

[JoshOrndorff]

I agree building them for master still makes sense for people who are following master in their own development. I would be in favour of publishing the master docs at crates.parity.io as we do now (I believe).

[JoshOrndorff]

Okay, I've made an attempt at this in #5657#5675 but I don't know gitlab very well, and I'm unsure where the job that published master-branch docs is. So I'd like someone to confirm that I haven't accidentally deleted it.