-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Increase timeout for crates publishing job #12934
Increase timeout for crates publishing job #12934
Conversation
necessary when lots of crates need to be published, as demonstrated by https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2158667
@@ -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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
bot merge |
necessary when lots of crates need to be published, as demonstrated by https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2158667
necessary when lots of crates need to be published, as demonstrated by https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2158667
Necessary when lots of crates need to be published, as demonstrated by https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2158667