for some old version of git-commit-id-plugin, for example, `


there is a Auth Fail error, when the plugin is in execution.

Turns out there was a bug (should be fixed in latest version), which uses JGitDataProvider, and requesting for



mark the plugin as office…



Turns out when spring boot construct the configuration bean, it’s using the setter method to map the values.

So for IgniteConfiguration, for example, even though the variable for peer ClassLoading is

private boolean p2pEnabled =DFLT_P2P_ENABLED;

however, the values below won’t work

instead, it should be

peerClassLoadingEnabled: true

as the setter to set the p2pEnabled is actually called

public IgniteConfiguration setPeerClassLoadingEnabled(boolean p2pEnabled) { this.p2pEnabled = p2pEnabled; return this; }


Originally published at https://lwpro2.wordpress.com on March 3, 2022.



there are many options for continuous deployment. one possible approach is to leverage on ansible and couple it with gitlab.

so in .gitlab-ci.yml

add a deploy stage

ansible will try to remove the old container and start the newly built docker image from previous steps.


Originally published at https://lwpro2.wordpress.com



I was not able to generate the git.properties at the beginning. somehow turns out it was due to a missing version for the plugin.

<plugin> <groupId>pl.project13.maven</groupId> <artifactId>git-commit-id-plugin</artifactId> <version>4.0.5</version> <!--need to add the specific version--> <executions> <execution> <goals> <goal>revision</goal> </goals> </execution> </executions> </plugin>

with that, at packaging, it could generate the…