Deployment Overview
Last updated
Last updated
If you're working on a new feature, create a new branch in your local repository. Ensure that the branch is named descriptively, reflecting the feature's purpose.
Implement the new feature within this branch, making necessary code changes and additions.
Regularly commit your changes as you make progress.
Once the PR is reviewed and approved, merge it into the "master" branch.
Goto Jenkins and trigger tag creation job to generate the latest tag.
Once a job is completed latest tag will be available in GitHub tag.
Access the GitHub repository.
Navigate to the "Tags" section of the repository.
Identify the latest build tag associated with the most recent release.
This tag typically represents a specific version or build of the project.
The latest tag will be available here
Initiate a build job in Jenkins and provide the latest tag as a parameter.
The build job compiles the code, runs tests, and prepares the artefacts for deployment.
After the build job successfully completes, an automatic deployment job may be triggered.
This deployment job takes the compiled code and deploys it to the desired environment.
If the automatic deployment job is not triggered automatically, you can manually initiate the deployment job in Jenkins.
This ensures that the latest version of the code is deployed.
Depending on the environment you're working in (development, testing, production, etc.), the paths to these jobs may vary.
Adjust the job paths according to your specific environment.
