Code Life Cycle Flashcards
Where does Dev 1 create code for the first time by itself?
Local 1
What if code breaks in Local?
Create new local
How many codes are there in a Local?
Each local contains code only for individual component
When is the first time code gets uploaded to a shared space?
When it gets uploaded to Branch
What is source?
Source is current code in production, that has been tested and validated
What is the benefit of using a branch?
If anything goes wrong, we can just get rid of branch code and go back to source code
What happens if code breaks in branch
Start over with new local
Who approves a pull request?
Senior Dev, and sometimes Senior QA
What happens after pull request is approved?
Branch code can now be merged with source code
What is a repository?
It is where code can be saved and shared among teams
What happens if code breaks in Pull Request?
Start over with new local
Who moves code from Source to Dev environment?
DevOps
What is a build?
A build is a compilation of multiple code bases into one single file
When is a build changed?
Whenever new code is introduced
Explain the numbers in hypothetical Build 1.23.45
- 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 is it possible for source to break after merging with new code if PR was approved?
New code has never interacted with other devs’ codes before
What should be done if source breaks after merging code
Deactivate broken version and reactivate previous build version that was stable
Perform root cause analysis
Why are we putting a build number in the source repo?
To keep records, and it helps with accountability because we record who is responsible for each build
