Maven For Java

by Anil Jalela | Oct 23, 2022 | DevOps

Maven is a tool that can now be used for building and managing any Java-based project. We hope that we have created something that will make the day-to-day work of Java developers easier and generally help with the comprehension of any Java-based project.

Maven’s Objectives:-
Maven’s primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time. In order to attain this goal, Maven deals with several areas of concern:-
Making the build process easy.
Providing a uniform build system.
Providing quality project information.
Encouraging better development practices.
Making the build process easy.

While using Maven doesn’t eliminate the need to know about the underlying mechanisms, Maven does shield developers from many details.

Providing a uniform build system:-
Maven builds a project using its project object model (POM) and a set of plugins. Once you familiarize yourself with one Maven project, you know how all Maven projects build. This saves time when navigating many projects.

Providing quality project information:-
Maven provides useful project information that is in part taken from your POM and in part generated from your project’s sources. For example, Maven can provide:
Change log created directly from source control.
Cross-referenced sources.
Mailing lists are managed by the project.
Dependencies used by the project.
Unit test reports including coverage.

Third-party code analysis products also provide Maven plugins that add their reports to the standard information given by Maven.

Providing guidelines for best practices development:-
Maven aims to gather current principles for best practices development and make it easy to guide a project in that direction. For example, specification, execution, and reporting of unit tests are part of the normal build cycle using Maven. Current unit testing best practices were used as guidelines:

Keeping test source code in a separate, but parallel source tree. Using test case naming conventions to locate and execute tests. Having test cases set up their environment instead of customizing the build for test preparation.

Maven also assists in project workflows such as release and issue management.

Maven also suggests some guidelines on how to lay out your project’s directory structure. Once you learn the layout, you can easily navigate other projects that use Maven.

While Maven takes an opinionated approach to project layout, some projects may not fit with this structure for historical reasons. While Maven is designed to be flexible to the needs of different projects, it cannot cater to every situation without compromising its objectives. If your project has an unusual build structure that cannot be reorganized, you may have to forgo some features or the use of Maven altogether.

What is Maven Not?

You might have heard some of the following things about Maven:-

Maven is a site and documentation tool.
Maven extends Ant to let you download dependencies.
Maven is a set of reusable Ant scriptlets.

While Maven does these things, as you can read above in the What is Maven? section, these are not the only features Maven has, and its objectives are quite different.

Ci Tool Jenkins

by Anil Jalela | Oct 21, 2022 | DevOps

Jenkins:-

→ Jenkins is an Open-Source project Written in Java that runs on Windows, macOS, and Other Unix-like Operating Systems. It is free, Community Supported, and might be your first-choice tool for CI.

→ Jenkins automates the entire Software development life Cycle

→ Jenkins was Originally developed by Sun Microsystem in 2004 under the name Hudson.

→ The project was later named Jenkins when Oracle bought Microsystems.

→ It Can run on any major platform without any Compatibilities issues.

→ Whenever developers Write Code, we integrate all that Code of all developers at that point in time and we build, test, and deliver/Deploy to the client. This process is called CI/CD ..

→ Jenkins helps us to achieve fast development.

→ Because of CI, Now bugs will be reported fast and get rectified fast So the entire Software development happens fast.

Workflow of Jenkins:-

→ We Can attach git, Maven, Selenium, Sonarqube, and Artifactory plugins to Jenkins.

→ Once developers put Code in GitHub, – Jenkins pulls that Code & sends to Maven for build

→ Once the build is done Jenkins pulls that Code and sends it to Selenium for testing.

→ Once testing is done, then Jenkins will pull that Code and Send it to artifactory (archive) as per requirement and so on.

→ We Can also deploy codes with Jenkins.

Build means=( compile, code review, unit testing, Integration testing, packaging[tar,jar,exe] )

Advantages of Jenkins: –

 → It has lots of plug-ins available

 → You Can Write your own plug-in.

 → You Can use Community Plug-in.

 → Jenkins is not just a tool. It is a framework i.e.: – You Can do whatever you want All you need is plug-ins.

 → We Can attach Slaves (nodes) to Jenkins master. It instructs others (slaves) to do Job. If slaves are not available Jenkins itself does the job.

 → Jenkins also behaves as a crone Server Replacement. i.e.: – Can do the scheduled task.
 → It Can Create Labels

what needs to learn in Jenkins?

‌Introduction to Jenkins 
‌      Introduction to Continuous Integration 
‌      Continuous Integration vs Continuous Delivery 
‌      Jenkins Overview 
‌      Characteristics and features 
‌      Architecture 
‌      Concepts and Terms 
‌      Benefits and Limitations 
‌Installation and Configuration 
‌      Jenkins Installation and Configuration 
‌      Plug-ins Overview 
‌      Integration with Git 
‌      Integration with Maven 
‌      Integration with Java 
‌      Installing plugins 
‌Setting up Build Jobs 
‌      Jenkins Dashboard 
‌      Create the first job 
‌      Running the first job 
‌      Manage jobs – failing, disable, update and delete 
‌      Pipeline with Jenkinsfile 
‌      Freestyle Project Configuration 
‌      Git Hooks and Other Build Triggers 
‌      Workspace Environment Variables 
‌      Parameterized Projects 
‌      UpstreamDownstream Projects and the Parameterized Trigger Plugin 
‌      Build a Java application with Maven using Jenkins 
‌Continuous Delivery Pipeline 
‌      Publishing Build Artifacts 
‌      Deployment Plug-in setup and configuration 
‌      Auto Deployment of build artifacts into the target server 
‌      Deploy a Java application with Maven using Jenkins 
‌      Executing selenium Functional Testing with deployment 
‌Management, Security and Best Practices 
‌      Managing and Monitoring Jenkins Server 
‌      Scaling Jenkins 
‌      Securing Jenkins 
‌      Adding Linux Node and executing job on it 
‌      Adding windows node and executing job on it 
‌      Configuring access control on Jenkins 
‌      Configuring role-based access control 
‌      Jenkins logs 
‌      Management 
‌      Credentials in Jenkins 
‌      Best Practices 
‌Jenkins Pipeline 
‌      Writing Jenkins Pipeline file for java application build and deployment 
‌      Storing Jenkins in git and configuring webhook 
‌      Difference between declarative and scripted pipeline 
‌      Specify an agent in the pipeline 
‌      Parameters in Pipeline 
‌      Schedule build in the pipeline 
‌      Webhook in pipeline 
‌      Approval in pipeline 
‌      Approval with timeout in the pipeline 
‌      Variables in pipeline 
‌      Email notification in the pipeline 
‌      Post-build action in the pipeline 
‌      Parallel stages in the pipeline 
‌      Condition in pipeline 
‌      Selenium Functional Testing in the pipeline