Skip to content

Commit 293092c

Browse files
authored
mage: run mage update steps in parallel (#6871)
From the looks of it, none of the update steps interact with each other, so I don't see a reason to run them serially. As an example, making a single line change in the otel components file results in the following timings: parallel mage update 9.19s user 1.92s system 366% cpu 3.027 total serial mage update 20.20s user 2.93s system 181% cpu 12.748 total
1 parent 633272c commit 293092c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

magefile.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -651,7 +651,7 @@ func commitID() string {
651651

652652
// Update is an alias for executing control protocol, configs, and specs.
653653
func Update() {
654-
mg.SerialDeps(Config, BuildPGP, BuildFleetCfg, Otel.Readme)
654+
mg.Deps(Config, BuildPGP, BuildFleetCfg, Otel.Readme)
655655
}
656656

657657
func EnsureCrossBuildOutputDir() error {

0 commit comments

Comments
 (0)