Code Life Cycle Flashcards

1
Q

Where does Dev 1 create code for the first time by itself?

A

Local 1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What if code breaks in Local?

A

Create new local

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How many codes are there in a Local?

A

Each local contains code only for individual component

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When is the first time code gets uploaded to a shared space?

A

When it gets uploaded to Branch

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is source?

A

Source is current code in production, that has been tested and validated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the benefit of using a branch?

A

If anything goes wrong, we can just get rid of branch code and go back to source code

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What happens if code breaks in branch

A

Start over with new local

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Who approves a pull request?

A

Senior Dev, and sometimes Senior QA

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What happens after pull request is approved?

A

Branch code can now be merged with source code

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a repository?

A

It is where code can be saved and shared among teams

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What happens if code breaks in Pull Request?

A

Start over with new local

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Who moves code from Source to Dev environment?

A

DevOps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is a build?

A

A build is a compilation of multiple code bases into one single file

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When is a build changed?

A

Whenever new code is introduced

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Explain the numbers in hypothetical Build 1.23.45

A
  • 1 - Version Number
  • 23 - Major Version Number
    Not a redesign, but many new features were introduced
    Number of times SDLC was deployed
  • 45 - Minor Version Number
    Every time a branch gets merged with source
    Every new individual component
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How is it possible for source to break after merging with new code if PR was approved?

A

New code has never interacted with other devs’ codes before

17
Q

What should be done if source breaks after merging code

A

Deactivate broken version and reactivate previous build version that was stable

Perform root cause analysis

18
Q

Why are we putting a build number in the source repo?

A

To keep records, and it helps with accountability because we record who is responsible for each build