Continuous Integration

Continuous Integration 

Continuous Integration (CI) is the process of automating the build and testing of code every time a team member commits changes to version control. ... CI emerged as a best practice because software developers often work in isolation, and then they need to integrate their changes with the rest of the team's code base.

CI is devops software development practice where developers regularly merge their code changes in central repository after which automated builds and tests are run.

 

Advantage of CI
improve quality
early bug finding
reduce time to validate n release app updates
fast feedback on changes

 

Tools used for CI

TFS, Jenkin, Azure

 

Team Foundation Server aka TFS is a Microsoft product which is serves as a SCM tool like Git. It also has features like reporting, project management, automated builds, testing and release management capabilities. It covers entire lifecycle, and enables DevOps capabilities. TFS can be used with numerous IDE including Visual Studio and Eclipse on all platforms.

It also provides the features of implementing both CI and CD. It has the feature of Build Management which includes build process management and automating build triggering. It supports good number of automated build triggers such as scheduled build, Continuous Integration trigger, trigger, etc

Bamboo

Bamboo is a continuous integration (CI) server that can be used to automate the release management for a software application, creating a continuous delivery pipeline.

Jenkins 
Jenkins is an open source automation tool written in Java with plugins built for Continuous Integration purpose. Jenkins is used to build and test your software projects continuously making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build

Team City

TeamCity is a Java-based build management and continuous integration server from JetBrains. It was first released on October 2, 2006.TeamCity is commercial software and licensed under a proprietary license. A Freemium license for up to 100 build configurations and 3 free Build Agent licenses is available.

Difference between Jenkins and TeamCity

Both Jenkins and TeamCity are continuous integration tools that serve many of the same purposes. Jenkins is an open source tool, while TeamCity is a proprietary offering from JetBrains.

The big difference between Bamboo vs Jenkins is that Jenkins is Open Source – it's free. Integration with JIRA and Bitbucket is limited. ... There are only 100 Bamboo plug-ins in the Atlassian environment compared to Jenkins which has over 1000.

note:  All references taken from google.  

Jira user story workflow

Hey folks,

In Jira, we have to work on user story for testing. Here, I try to write some basic flow about it. This can be vary as per your project needs.

When story is assigned-it will be in NEW stage.
After discussions, when story is accepted it will be inPENDING ASSIGNMENT stage.
When story is discussed among team it is ASSIGNED to development team.
When story is developing ,it is in FIX IN PROGRESS.
Once developed, it is in READY FOR QA DEPLOYMENT
Once deployed,it is in READY FOR TESTING
Once testing is in progress,it is in QA IN PROGRESS
If everything working fine on SIT, story assigned to UAT for testing and take change to PASS. If something fails, then defect needs to raise and follow defect life cycle and stage is FAILED RETEST.
Once the story is passed, stage change to CLOSE

Regards,
Trupti

Git Hub basics- Source control tool

Hey Folks,

Few updates on Source Control tool, which I recently learn, would like to share with you.

GitHub (originally known as Logical Awesome LLC)^[3] is a web-based hosting service for version control using git. It is mostly used for computer code. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project (Reference taken from Wikipedia)

Repository-A repository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets – anything your project needs. You can create public and private repository

Branch-
Branching is the way to work on different versions of a repository at one time.
By default your repository has one branch named master which is considered to be the definitive branch. We use branches to experiment and make edits before committing them to master.

Basic Git Commands

1. git init- create new local repository
2. git status-List the files you've changed and those you still need to add or commit
3. git push origin master- Send changes to the master branch of your remote repository
4. git commit -m "Commit message"-Commit changes to head (but not yet to the remote repository):
5. git commit -a- Commit any files you've added with git add, and also commit any files you've changed since then

Steps

1. Login through git url

2. Start Project 

3. Create project and follow link

4. Install git on local machine

5. Create folder on c:

6. Type cmd on url and write git command

7. Change environment variable to your account and path %git_home%\bin

8. Again go to c: folder and write command cmd and git

9. Clone the project to url with ‘ git clone https://githubprojectpath/hit Project.git”

10. Enter username and password

11. Copy your local code to clone folder and follow git basic commands

Regards,
Trupti