What marks the beginning of the Continuous Delivery Pipeline?
29 comments · newest first
ST
Stefan
6 months ago
I feel A is the best choice. It’s the first step in CI/CD.
MA
Malinda
6 months ago
B) A committed Feature could also work, but it comes later.
KI
King
7 months ago
C) An idea is too vague. We need something concrete.
SH
Sherron
7 months ago
I lean towards D) A committed user story. It feels more structured.
RY
Ryann
7 months ago
I agree, A makes sense. It triggers the whole process.
LA
Lawanda
7 months ago
I think it's A) A checked-in change. That's where it all starts.
PE
Pearly
8 months ago
I agree, it’s all about that first change!
LE
Leonor
8 months ago
Really? A checked-in change? Seems too simple.
FE
Felicia
8 months ago
Definitely an idea, right?
WI
Wilda
8 months ago
I thought it was a committed user story?
AL
Alesia
8 months ago
A checked-in change is the start!
DA
Dahlia
9 months ago
Haha, an idea? Might as well start the pipeline with a dream and a prayer!
JO
Joni
9 months ago
An idea? Really? That's not even close to the beginning of the pipeline!
JE
Jennifer
9 months ago
A checked-in change is the correct answer. That's where the pipeline starts!
CA
Carlee
9 months ago
I’m leaning towards a committed feature, but I could be mixing it up with another concept we covered.
FI
Filiberto
9 months ago
Isn't it possible that it could start with just an idea? I feel like that was mentioned in one of our readings.
LE
Lewis
10 months ago
I remember practicing a question like this, and I think it was about the importance of a committed user story.
JU
Junita
10 months ago
I think the Continuous Delivery Pipeline starts with a checked-in change, but I'm not entirely sure.
MI
Michael
10 months ago
I think the beginning is when an idea is conceived. That's the true starting point, even if the technical pipeline kicks off with a code commit. Gotta start with that initial idea.
NO
Noel
10 months ago
I'm not entirely sure about this one. Is it really just a checked-in change, or does it have to be a committed feature or user story? I'll need to review my notes to be confident.
MI
Micaela
10 months ago
Okay, I've got this. The beginning of the pipeline is when a checked-in change triggers the automated build and deployment process. That's the key event that kicks everything off.
VI
Viola
11 months ago
I always get confused between a committed feature and a committed user story. Glad the right answer is clear here.
BE
Berry
11 months ago
I'm a bit confused on this one. Is it when the feature is committed or when the user story is committed? I'll have to think this through carefully.
KE
Kenia
11 months ago
Hmm, I think the beginning of the Continuous Delivery Pipeline is when a change is checked in. That seems like the logical starting point.
OR
Ora
6 months ago
Yeah, without that initial change, nothing moves forward.
SH
Sharan
6 months ago
A committed feature could also be a start, but I lean towards the checked-in change.
FR
Francoise
6 months ago
Definitely! It’s where everything starts.
JO
Joesph
6 months ago
I agree, a checked-in change makes sense.
HA
Hana
11 months ago
Exactly! It’s the first step in the pipeline.