Packaging Of A Maven Project
Step 24: Same steps to be followed as done in build phase only difference is that under goals and option we write the command “package” and
- Under post-build actions choose: “File to archive”—>**/target/*.jar (write this where the bundled file will be stored in this location)
- After configuration build the package phase.
Step 25: Enter the value as “package” in the Goals and Options section.
Step 26: Under post-build action choose “Files to archive” then write the location where the package file will be stored.
Step 27: The console output of the package job will be as following screenshot.
Docker – Continuous Integration
Continuous Integration ( CI ) with Docker improves the productivity of software development. Docker make the applications portable and independent of the system making its environment uniform. Development of the pipelines can be improved with CI technology tools like Jenkins which automates building, testing and packing the applications. In this article, we will see how to make Continuous Integration using Jenkins and how to create an application using docker. You can practice the below implementation with any preferred language of your application. For this post, we will be making a continuous integration pipeline for a Java project.
Table of Content
- What Is Continuous Integration?
- How And Why You Need To Use Docker In CI?
- Step By Step Implementation Of Continuous Integration Pipeline
- Building Of A Maven Project
- Testing Of A Maven Project
- Packaging Of A Maven Project
- Integration Of “Build-Test-Package” Job Of A Maven Project
- Conclusion
- Continuous Integration With Docker – FAQs