{"id":238009,"date":"2022-02-11T06:27:00","date_gmt":"2022-02-11T11:27:00","guid":{"rendered":"https:\/\/wordpress-756359-3782526.cloudwaysapps.com\/?p=238009"},"modified":"2025-05-30T07:30:31","modified_gmt":"2025-05-30T07:30:31","slug":"2022-02-11-springboot","status":"publish","type":"post","link":"https:\/\/www.travis-ci.com\/blog\/2022-02-11-springboot\/","title":{"rendered":"Travis and Spring Boot"},"content":{"rendered":"\n

In this series of tech blog Friday by Montana Mendy, we will learn how to run maven build goals, perform test coverage validation whether this be Coveralls, SonarCloud or Docker. Are you ready? I\u2019m ready. Let\u2019s jump in.<\/p>\n\n\n\n

Getting started<\/h2>\n\n\n\n

There\u2019s choices and choices. In this example I\u2019ll be using Maven, but you can obviously use Gradle as well. Next, you\u2019ll want to create a SpringBoot project<\/a> either using http:\/\/start.spring.io or alternatively use your IDE.<\/p>\n\n\n\n

Create your .travis.yml<\/code> file<\/h2>\n\n\n\n

We have to enable your .travis.yml<\/code> file and the way we do that is by the following:<\/p>\n\n\n\n

language: java\njdk: oraclejdk8<\/code><\/pre>\n\n\n\n
Now this just invokes Travis into your project, this is sufficient enough for Travis to see that there\u2019s a build that needs to be triggered, how Travis is architected Travis will run mvn test -B<\/code> for building the project. If Travis finds mvnw wrapper<\/code> then it will be used like .\/mvnw test -B.<\/code> as you can see it\u2019s a bit recursive. You can instruct Travis to run different commands in your script:<\/code> hook in your .travis.yml<\/code>.<\/p>\n\n\n\n
Adding Coverage Checks for Travis<\/h2>\n\n\n\n
Add the Maven specific JaCoCo plugin to pom.xml<\/code> with flags that define what is the desired code coverage percentage, classes, etc:<\/p>\n\n\n\n
<Plugin>\n    <GroupId>org.jacoco<\/GroupId>\n    <ArtifactId>jacoco-maven-plugin<\/ArtifactId>\n    <Version>0.7.9<\/Version>\n    <Configuration>\n        <Excludes>\n            <Exclude>in\/sivalabs\/freelancerkit\/entities\/*<\/Exclude>\n            <Exclude>in\/sivalabs\/freelancerkit\/*Application<\/Exclude>\n        <\/Excludes>\n    <\/Configuration>\n    <Executions>\n        <Execution>\n            <Id>default-prepare-agent<\/Id>\n            <Goals>\n                <Goal>prepare-agent<\/Goal>\n            <\/Goals>\n        <\/Execution>\n        <Execution>\n            <Id>default-prepare-agent-integration<\/Id>\n            <Goals>\n                <Goal>prepare-agent-integration<\/Goal>\n            <\/Goals>\n        <\/Execution>\n        <Execution>\n            <Id>default-report<\/Id>\n            <Phase>verify<\/Phase>\n            <Goals>\n                <Goal>report<\/Goal>\n            <\/Goals>\n        <\/Execution>\n        <Execution>\n            <Id>default-report-integration<\/Id>\n            <Goals>\n                <Goal>report-integration<\/Goal>\n            <\/Goals>\n        <\/Execution>\n        <Execution>\n            <Id>default-check<\/Id>\n            <Goals>\n                <Goal>check<\/Goal>\n            <\/Goals>\n            <Configuration>\n                <Rules>\n                 <Rule Implementation=\"Org.Jacoco.Maven.RuleConfiguration\">\n                        <Element>BUNDLE<\/Element>\n                        <Limits>\n                            <Limit Implementation=\"Org.Jacoco.Report.Check.Limit\">\n                                <Counter>COMPLEXITY<\/Counter>\n                                <Value>COVEREDRATIO<\/Value>\n                                <Minimum>0.60<\/Minimum>\n                            <\/Limit>\n                        <\/Limits>\n                    <\/Rule>\n                <\/Rules>\n            <\/Configuration>\n        <\/Execution>\n    <\/Executions>\n<\/Plugin><\/code><\/pre>\n\n\n\n
Classifiers<\/h2>\n\n\n\n
To fix the classifier issue, the workaround is to add the classifier configuration to spring-boot-maven-plugin<\/code> as follows:<\/p>\n\n\n\n
<Plugin>\n    <GroupId>org.springframework.boot<\/GroupId>\n    <ArtifactId>spring-boot-maven-plugin<\/ArtifactId>\n    <Configuration>\n        <Classifier>exec<\/Classifier>\n    <\/Configuration>\n<\/Plugin><\/code><\/pre>\n\n\n\n
Now let\u2019s take a look at our travis.yml<\/code> file, and be on the lookout for the script:<\/code> hook:<\/p>\n\n\n\n
language: java\njdk: oraclejdk8\n  \nscript:\n- .\/mvnw clean install -B<\/code><\/pre>\n\n\n\n
You can see in our script:<\/code> hook we\u2019ve added .\/mvnw vlean install -B<\/code> and that\u2019s going to be key. Now let\u2019s get a .travis.yml<\/code> that has SonarCloud. Now remember to set your environment variables<\/code> you grabbed from SonarCloud and also add them to Travis, here\u2019s a .travis.yml<\/code> demonstrating this:<\/p>\n\n\n\n
language: java\njdk: oraclejdk8\n  \nenv:\n  global:\n  - secure: (ENV_VARS_HERE)\n  \naddons:\n  sonarcloud:\n    organization: \"montanamendy-from-travis\"\n    token:\n      secure: $SONAR_TOKEN\n  \nscript:\n- .\/mvnw clean install -B\n- .\/mvnw clean org.jacoco:jacoco-maven-plugin:prepare-agent package sonar:sonar\n<\/code><\/pre>\n\n\n\n
Now let\u2019s build a Dockerfile that mirrors essentially that .travis.yml<\/code>:<\/p>\n\n\n\n
ROM frolvlad\/alpine-oraclejdk8:slim\nVOLUME \/tmp\nADD target\/freelancer-kit-0.0.1-SNAPSHOT.jar app.jar\nRUN sh -c 'touch \/app.jar'\nENV JAVA_OPTS=\"-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=8787,suspend=n\"\nEXPOSE 8080 8787\nENTRYPOINT [ \"sh\", \"-c\", \"java $JAVA_OPTS -Djava.security.egd=file:\/dev\/.\/urandom -Dspring.profiles.active=docker -jar \/app.jar\" ]<\/code><\/pre>\n\n\n\n
That Dockerfile is going to grab alpine-oraclejdk8:slim<\/code> the slim<\/code> flag is making sure it\u2019s grabbinb the slim version.<\/p>\n\n\n\n
Deploying<\/h2>\n\n\n\n
Now let\u2019s say you\u2019re using Heroku for deployment, you\u2019ll need to grab all those credentials as well and add them to your deploy:<\/code> hook. We can add your Heroku key and secrets by running the following command in the CLI:<\/p>\n\n\n\n
travis encrypt HEROKU_API_KEY=\u201dHEROKU_KEY\"<\/code><\/pre>\n\n\n\n
You\u2019ll now want to add the following to your .travis.yml<\/code>:<\/p>\n\n\n\n
deploy:\n  provider: heroku\n  api_key: $HEROKU_API_KEY\n  app: montana<\/code><\/pre>\n\n\n\n
Now that you\u2019ve added your Heroku secrets, it\u2019s time to see the final .travis.yml<\/code>:<\/p>\n\n\n\n
sudo: required\nlanguage: java\njdk: oraclejdk8\n  \nservices:\n- docker\n  \nenv:\n  global:\n  - secure: \"encrypted-sonar-token\"\n  - secure: \"encrypted-dockerhub-username\"\n  - secure: \"encrypted-dockerhub-password\"\n  - secure: \"encrypted-heroku-api-key\"\n  - COMMIT=${TRAVIS_COMMIT::7}\n  \naddons:\n  sonarcloud:\n    organization: \"montanamendy-travis\"\n    token:\n      secure: $SONAR_TOKEN\n  \nscript:\n- .\/mvnw clean install -B\n- .\/mvnw clean org.jacoco:jacoco-maven-plugin:prepare-agent package sonar:sonar\n  \nafter_success:\n- docker login -u $DOCKER_USER -p $DOCKER_PASS\n- export TAG=`if [ \"$TRAVIS_BRANCH\" == \"master\" ]; then echo \"latest\"; else echo $TRAVIS_BRANCH&amp;amp;amp;amp;amp;amp;lt;span data-mce-type=\"bookmark\" style=\"display: inline-block; width: 0px; overflow: hidden; line-height: 0;\" class=\"mce_SELRES_start\"&amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;lt;\/span&amp;amp;amp;amp;amp;amp;gt;; fi`\n- export IMAGE_NAME=sivaprasadreddy\/freelancer-kit\n- docker build -t $IMAGE_NAME:$COMMIT .\n- docker tag $IMAGE_NAME:$COMMIT $IMAGE_NAME:$TAG\n- docker push $IMAGE_NAME\n  \ndeploy:\n  provider: heroku\n  api_key: $HEROKU_API_KEY\n  app: montanamendy-from-travis<\/code><\/pre>\n\n\n\n
If all is successful, you should see this in your Travis build log:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
There you go, we just used unit testing, Spring Boot and Travis CI into our project. The integration was kind of easy wasn\u2019t it?<\/p>\n\n\n\n
As always if you have any questions, any questions at all, please email me at montana@travis-ci.org<\/a>.<\/p>\n\n\n\n
Happy building!<\/p>\n","protected":false},"excerpt":{"rendered":"
In this series of tech blog Friday by Montana Mendy, we will learn how to run maven build goals, perform test coverage validation whether this be Coveralls, SonarCloud or Docker. Are you ready? I\u2019m ready. Let\u2019s jump in. Getting started There\u2019s choices and choices. In this example I\u2019ll be using Maven, but you can obviously […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_breakdance_hide_in_design_set":false,"_breakdance_tags":"","footnotes":""},"categories":[16],"tags":[7,19,20,5],"class_list":["post-238009","post","type-post","status-publish","format-standard","hentry","category-news","tag-community","tag-feature","tag-infrastructure","tag-news"],"_links":{"self":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/238009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/comments?post=238009"}],"version-history":[{"count":2,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/238009\/revisions"}],"predecessor-version":[{"id":242759,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/238009\/revisions\/242759"}],"wp:attachment":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/media?parent=238009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/categories?post=238009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/tags?post=238009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}