#BUILD INTIME HOW TO#
#BUILD INTIME ZIP FILE#
#BUILD INTIME PLUS#

In case you don’t have git installed, you can just download a zip file from the web page. The following prerequisites are required in this tutorial:įinally, clone the git repo below to your local computer.

Architecture, event based snapshot creation- image by author 2.1 Prerequisites

#BUILD INTIME PLUS#

If you need something more powerful, look at Spring Actuator or Spring Admin, which can provide the build metadata functionality plus a lot more.2. In Spring boot application, you can easily obtain the info by altering the Spring Boot Maven/Gradle plugin configuration to generate the build.properties file and then accessing it through BuildProperties object.įor simple scenarios, this is an easy and quick solution and should work for you. Having access to version and build information at runtime can be quite useful. Spring Boot Admin is a community project, which provides a nice user interface on top of Spring Actuator endpoints, so the app is more comfortable to manage through a nice admin GUI. In fact, it can easily be configured to use build information provided by BuildProperties and provide them through one of its endpoints. Spring Boot Actuator is a sub-project of Spring Boot, which adds some production-grade monitoring and management tools exposed as REST and JMX endpoints. While this approach gives you basic build and version info, sometimes you may need a more powerful tool. What's more, since you already have environment object, you can obtain any environmental properties by calling environment.getProperty('property.name'). To detect the current profiles, you need just to inject Environment object and then you can simply obtain them by calling private Environment environment It is useful to be able to determine current profiles as sometimes the app can be run with different profiles than expected. Depending on the profile, the correct environmental configuration can be loaded such as DB connection and more.

Typical usage is, for example, having a separate profile for each environment (DEV, UAT, PROD. Often Spring applications use various profiles, which can significantly change the behavior. It is no doubt useful to know which version of your artifact is deployed and when it was built. You just need to add the following (resources = '$ Detecting Spring profiles If you are using Spring Boot, your pom.xml should already contain spring-boot-maven-plugin. In Spring Boot, it is fortunately quite easy.

#BUILD INTIME HOW TO#

In any case, having build information can be handy and it is useful to know how to obtain it at runtime. Maybe the issue reported is already fixed in a newer version or maybe the bug still occurs because the new version is implemented, but not deployed yet. In such cases, it is vital to know what build exactly is currently running when testing and submitting bug reports. This can be especially important in non-production environments, where the app is frequently deployed or even with continuous deployment in production. It can be useful because you can quickly determine what version of the app is currently deployed. For example, imagine a scenario, where you expose a REST endpoint, which can tell the client what your current version of the application is, when was it built and so on. Having such information at runtime can be useful. Sure, most of this information is already in your pom.xml file, but it can be tricky to retrieve these when the application is running. It can often be useful to obtain information about artifact, version, build time and other at runtime. Monitor and manage your application in production with Spring Boot Actuator 2.x.

Build intime