Build
Facts about the process serving this page.
| Service | task-03-app |
|---|---|
| Version | 1.0.0 |
| Release | 20260905-121541 |
| Java version | 17.0.20 |
| Java vendor | Ubuntu |
| Operating system | Linux |
| Architecture | amd64 |
| Processors | 2 |
| Maximum heap | 512 MB |
| Heap in use | 31 MB |
| Host | ip-172-31-37-95 |
| Listening on | port 8080 |
| Started | 2026-09-05 07:15:42 UTC |
| Uptime | 1h 48m |
Why the build pins its own Java version
The Gradle build declares a Java 17 toolchain, so the compiler used is fixed by the project rather than by whatever happens to be installed on the machine running the build. The same sources therefore produce the same bytecode on a laptop, on this server, and on a CI runner.
Two runtimes, on purpose
Jenkins itself needs Java 21 and this service runs on Java 17. Both are installed, and each process is pointed at the one it needs. Separating the tool from the thing it builds is what makes that possible.