Merge branch 'main' into pr/bom-modules-cs-project

com-lihaoyi · Dec 27, 2024 · 1ca26c7 · 1ca26c7
2 parents f9d1a06 + 2ff4923
commit 1ca26c7
Show file tree

Hide file tree

Showing 112 changed files with 4,017 additions and 208 deletions.
diff --git a/.github/workflows/pre-build.yml b/.github/workflows/pre-build.yml
@@ -38,7 +38,7 @@ jobs:
       - run: ./mill -i -k selective.prepare ${{ inputs.prepareargs }}
         if: ${{ github.event_name == 'pull_request' && !contains(github.event.pull_request.labels.*.name, 'run-all-tests') }}
 
-      - uses: actions/upload-artifact@v4.4.3
+      - uses: actions/upload-artifact@v4.5.0
         with:
           path: out/mill-selective-execution.json
           name: ${{ inputs.os }}-selective-execution-artifact
@@ -50,7 +50,7 @@ jobs:
 
       - run: ./mill -i -k ${{ inputs.compileargs }}
 
-      - uses: actions/upload-artifact@v4.4.3
+      - uses: actions/upload-artifact@v4.5.0
         with:
           path: .
           name: ${{ inputs.os }}-artifact

diff --git a/.github/workflows/publish-artifacts.yml b/.github/workflows/publish-artifacts.yml
@@ -40,7 +40,7 @@ jobs:
 
       - run: ./mill -i __.publishArtifacts
 
-      - uses: actions/upload-artifact@v4.4.3
+      - uses: actions/upload-artifact@v4.5.0
         with:
           path: .
           include-hidden-files: true

diff --git a/blog/antora.yml b/blog/antora.yml
@@ -1,5 +1,5 @@
 name: blog
-title: Mill Blog
+title: The Mill Build Engineering Blog
 version: ~
 nav:
   - modules/ROOT/nav.adoc

diff --git a/blog/modules/ROOT/nav.adoc b/blog/modules/ROOT/nav.adoc
@@ -1,3 +1,4 @@
 
+* xref:3-selective-testing.adoc[]
 * xref:2-monorepo-build-tool.adoc[]
 * xref:1-java-compile.adoc[]
diff --git a/blog/modules/ROOT/pages/1-java-compile.adoc b/blog/modules/ROOT/pages/1-java-compile.adoc
@@ -15,6 +15,9 @@ not match today's reality. Nowadays the Java compiler can compile "typical" Java
 should take more than 10s to compile in a single-threaded fashion, and should be even
 faster in the presence of parallelism
 
+// end::header[]
+
+
 Doing some ad-hoc benchmarks, we find that although the compiler is blazing fast, all
 build tools add significant overhead over compiling Java directly:
 
@@ -31,8 +34,6 @@ all build tools fall short of how fast compiling Java _should_ be. This post exp
 these numbers were arrived at, and what that means in un-tapped potential for Java build
 tooling to become truly great.
 
-// end::header[]
-
 ## Mockito Core
 
 To begin to understand the problem, lets consider the codebase of the popular Mockito project:

diff --git a/blog/modules/ROOT/pages/2-monorepo-build-tool.adoc b/blog/modules/ROOT/pages/2-monorepo-build-tool.adoc
@@ -22,7 +22,10 @@ Software build tools mostly fall into two categories:
 One question that comes up constantly is why do people use Monorepo build tools? Tools
 like Bazel are orders of magnitude more complicated and hard to use than tools
 like Poetry or Cargo, so why do people use them at all?
-https://knowyourmeme.com/memes/is-he-stupid-is-she-smart-are-they-stupid[Are they stupid?]
+
+// end::header[]
+
+
 
 It turns out that Monorepo build tools like Bazel or Mill do a lot of non-obvious things that
 other build tools don't, that become important in larger codebases (100-10,000 active developers).
@@ -32,7 +35,6 @@ features become critical. We'll explore some of the core features of "Monorepo B
 below, from the perspective of Bazel (which I am familiar with) and Mill (which this
 technical blog is about).
 
-// end::header[]
 
 ## Support for Multiple Languages