Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Increase timeout for crates publishing job #12934

Merged
merged 1 commit into from
Dec 15, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion scripts/ci/gitlab/pipeline/publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ update-node-template:
# taking into account the 202 (as of Dec 07, 2022) publishable Substrate crates, that would equate
# to roughly 202 minutes of delay, or 3h and 22 minutes. As such, the job needs to have a much
# higher timeout than average.
timeout: 5h
timeout: 9h
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to publish crates in parallel? Because if the job is going to run at night the runner might not get the latest cache for rusty-cachier

Copy link
Contributor Author

@joao-paulo-parity joao-paulo-parity Dec 15, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to publish crates in parallel

Currently no. To publish a crate you need to publish all of its dependencies first, so it's a serial processing operation which happens in the context of a single job. I couldn't find a nice way to parallelize that so far.

if the job is going to run at night the runner might not get the latest cache for rusty-cachier

Caching is not used for publishing to crates.io at the moment. It might be possible to use it in the future.

# A custom publishing environment is used for us to be able to set up protected secrets
# specifically for it
environment: publish-crates
Expand Down