MENU
Which is NOT a continuous integration best practice?
Suggested Answer: C
Get Premium CJE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
RE
Ressie
11 months ago
I thought self-testing builds were standard now.
CH
Christoper
11 months ago
A single source repository is a must!
LO
Louvenia
11 months ago
Wait, are people really still doing things manually?
JE
Jerry
11 months ago
Totally agree, manual processes slow everything down!
BO
Boris
11 months ago
B is definitely not a best practice.
BE
Bernardine
12 months ago
I have a vague memory that making the build self-testing is important too, so maybe B is the answer?
VA
Van
12 months ago
I practiced a question similar to this, and I think building every commit is definitely a best practice.
OD
Odette
12 months ago
I'm not entirely sure, but "doing everything manually" seems off. I feel like automation is key in CI.
LA
Lavera
1 year ago
I remember that maintaining a single source repository is crucial for CI, so I think that's a best practice.
LE
Lenna
1 year ago
I got this! Doing everything manually with great care is definitely not a continuous integration best practice.
HA
Harrison
1 year ago
Hmm, I'm not sure about this one. I'll have to think it through carefully.
FR
France
1 year ago
This question seems pretty straightforward. I'm pretty confident I know the answer.
ME
Melina
1 year ago
Okay, let me see. I think the key is to identify the best practices and then choose the one that isn't one.
AR
Arthur
1 year ago
Okay, let me think this through. If the goal is to send conflicts to the conflicts feed, then the LastWriterWins policy might not be sufficient. I'd want to explore the other conflict resolution options, like custom conflict resolution procedures, to make sure I meet all the requirements.
GI
Giuseppe
1 year ago
This seems like a straightforward question about using resource planning software to manage SME scheduling conflicts. I'd focus on analyzing the dashboard reports to identify scheduling issues and make adjustments accordingly.
KE
Keshia
1 year ago
Hmm, I'm a bit confused by the wording here. I'll have to re-read the question a few times to make sure I understand what it's asking.
KI
Kiera
1 year ago
B) Do everything manually? What is this, the stone age? I thought we were past the days of using carrier pigeons to deploy code.
JA
Jade
1 year ago
D) Make the build self-testing is a must. How else are you going to catch those pesky bugs early on?
AR
Ardella
1 year ago
D) Make the build self-testing.
BR
Brice
1 year ago
C) Build every commit.
MA
Marva
1 year ago
A) Maintain a single source repository.
DE
Devora
1 year ago
C) Build every commit is the way to go. Waiting for a full manual build? Who has time for that?
MA
Man
1 year ago
Haha, I guess 'do everything manually' is the 'with great care' part of the question. Sounds like a recipe for a never-ending build process.
AN
Annmarie
1 year ago
D) Make the build self-testing.
SO
Sol
1 year ago
C) Build every commit.
WA
Wai
1 year ago
A) Maintain a single source repository.
GE
German
1 year ago
B) Do everything manually with great care? Are you kidding me? That's the opposite of continuous integration!
EU
Eun
1 year ago
D) Make the build self-testing.
LO
Lottie
1 year ago
C) Build every commit.
RI
Rima
1 year ago
A) Maintain a single source repository.
TE
Tennie
2 years ago
I disagree. I think the answer is C) Build every commit. That's not always practical in every situation.
CH
Cherelle
2 years ago
I agree with Cammy. Doing everything manually goes against the idea of continuous integration.
CA
Cammy
2 years ago
I think the answer is B) Do everything manually with great care.