Jenkins: Essentials

Question 1

The intent of the continuous workflow

Answer 1

To have a code that is stable and valid all the time

Question 2

Continuous

Answer 2

implements Agile and Devops philosophies with tools that standardize the steps in the process and thoroughly test each code modification before it is integrated into the official source.

Question 3

Continuous Integration (CI)

Answer 3

frequent, automatic integration of code. All new and modified code is automatically tested with the master code.

Question 4

Continuous Delivery (CD)

Answer 4

the natural extension of CI. It ensures that the code is always ready to be deployed, although manual approval is required to actually deploy the software to production.

Question 5

Continuous Deployment

Answer 5

automatically deploys all validated changes to production. Frequent feedback enables issues to be found and fixed quickly.

Question 6

Elements of the Delivery Pipelines

Answer 6

1. Version control
2. Build
3. Unit test
4. Deploy
5. Auto test
6. Deploy to production
7. Measure and validate

Question 7

Steps in the software delivery process

Answer 7

1. Code
2. Build
3. Integrate
4. Test
5. Release
6. Deploy
7. Operate

Question 8

Source code management systems (SCMs) / version control systems (VCSs),

Answer 8

software systems that record all changes for a set of files over time. This allows you to share those changes and provide merging and tracking history of the recorded changes.

Question 9

Using a modern SCM enables

Answer 9

1. Collaborate efficiently on a single codebase.
2. Track every change. SCM is considered the Single Source of Truth. (rollback)

Question 10

The workflow to modify code that is stored in an SCM

Answer 10

1. Clone (copy) the repo to your local computer.
2. Create a branch for the change you want to make. A branch should represent a small, discrete change, which is typically the amount of work you can do in a few hours or less.
3. Modify your local codebase and test your changes locally.
4. Create a commit that contains the modified codebase.
5. Push your commit to the remote, official repository.

Question 11

commit

Answer 11

1. a set of diffs that have been explicitly validated.
2. A commit is actually a new version of the codebase. It can exist only locally or remotely. The latest commit on the history is the Head.

Question 12

branch

Answer 12

a pointer to a single commit.

Question 13

Head

Answer 13

the “latest” branch, also known as the master branch. To integrate a branch, you must merge it:

Question 14

A Pull Request (PR)

Answer 14

contains the commits you want to add to the official code. It is pushed to the central server, where it can be reviewed and modified before it is merged to the destination branch. A pull request ends by being closed or merged.