Continuous integration of a large interconnected Java codebase can be very challenging. The traditional solution is to break the code up to small cohesive repositories and define semantically versioned modules in each one (e.g. using Maven or Gradle) in such a manner that won't break APIs. This leads to technical debt and stagnation. Bazel allows to discard versions aside and to work purely with source code dependencies, whether in the local repository or an external one. It can handle very large Java codebases using aggressive caching and a high degree of parallelism.

3. 1 h
1
2
3
4
5
1
2
3
4
1
2
3
1
2
7
0
1
0
1 2
5
0 7

4. 1 h-2h
1-2 m

8. mvn install -DskipTests
gradle build -x test

9. ●

11. ●
●

13. <dependency>
<groupId>com.wix.foo</groupId>
<artifactId>api</artifactId>
<version>1.3.1</version>
</dependency>
dependencies {
Implementation
'com.wix.foo:api:1.3.1'
}

14. ●

15. ●
●

16. ●
●
●

17. ●
●
●
●

18. <dependency>
<groupId>com.wix.foo</groupId>
<artifactId>api</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>

25. java_project
├── WORKSPACE
└── src
└── main
└── java
└── com
├── example
│ ├── A.java
│ ├── B.java
│ └── C.java
└── example2
├── D.java
├── E.java
└── F.java

26. java_project
├── WORKSPACE
└── src
└── main
└── java
└── com
├── example
│ ├── A.java
│ ├── B.java
│ ├── BUILD
│ └── C.java
└── example2
├── D.java
├── E.java
└── F.java

27. f(A,B,C)f( )
Source files
env’ variables
dependencies
A
B
C
wix

28. f(A,B,C)f( )
A
B
C

29. java_project
├── WORKSPACE
└── src
├── main
│ └── java
│ └── com
│ └── example
│ ├── A.java
│ ├── B.java
│ ├── BUILD FILE
│ ├── C.java
│ └── Example.java
└── test
A.java + :c -> java_library -> a.jar
java_library(
name="a",
srcs=[
"A.java",
],
deps = [":c"])
$ bazel build :a

30. f(A,B,C)f( )
A
B
C

31. f(A,B,C)
f( )
A
B
C
f(A,B,C)
f( )
A
B
C

34. Compilation Test RunPending

35. ✔ ✔ ✔
✔ ✔ ✔
✔ ✔ ✔ ✔
$ bazel build //...

37. ✔ ✔ ✔
✔ ✔ ✔
✔ ✔ ✔ ✔

43. *Tech debt

52. ✔
✔ ✔ ✔