Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E134 Exam - Topic 1 Question 61 Discussion

Which practice should be used to push a code fix to make it into the current release candidate?
D) Cherry-pick the fix commit into the release candidate.
A) Make the fix in CRX where the current release candidate is currently deployed.
B) Create a new release candidate from the master branch.
C) Make the fix locally and upload the package to where the release candidate is deployed.

Adobe AD0-E134 Exam - Topic 1 Question 61 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 61
Topic #: 1
[All AD0-E134 Questions]

Which practice should be used to push a code fix to make it into the current release candidate?

Show Suggested Answer Hide Answer
Suggested Answer: D

To push a code fix into the current release candidate, the best practice is to cherry-pick the fix commit into the release candidate branch. Cherry-picking allows you to apply specific changes from one branch to another, ensuring that only the necessary fixes are included without introducing unrelated changes.

Here's how to cherry-pick a commit:

Identify the Commit: Locate the commit hash of the fix you need to apply. This can be found in your version control system (e.g., Git).

Checkout the Release Candidate Branch:

git checkout release-candidate-branch

Cherry-pick the Commit:

git cherry-pick <commit-hash>

Resolve Conflicts (if any): If there are conflicts, resolve them manually and then continue the cherry-pick process:

git add <resolved-files>

git cherry-pick --continue

Test the Changes: Ensure that the changes are tested thoroughly in the release candidate environment to confirm the fix works as expected.

Push the Changes:

git push origin release-candidate-branch

Cherry-picking ensures that only the required changes are applied to the release candidate, maintaining the stability and integrity of the codebase.


Git Cherry-pick Documentation

Contribute your Thoughts:

0/2000 characters
Carlota
4 days ago
I prefer option B. It ensures everything is stable before release.
upvoted 0 times
...
Theron
9 days ago
Option D is efficient. Quick fixes should be easy to integrate.
upvoted 0 times
...
Quinn
14 days ago
I feel like option C is too manual. Automation is key.
upvoted 0 times
...
Callie
20 days ago
Option A seems risky. What if it breaks something?
upvoted 0 times
...
Fletcher
25 days ago
I agree, but option B could be safer for bigger changes.
upvoted 0 times
...
Solange
30 days ago
I think option D is the best. Cherry-picking keeps the history clean.
upvoted 0 times
...
Lauran
1 month ago
I think C could work, but it feels risky.
upvoted 0 times
...
Nohemi
1 month ago
Wait, can we really push fixes directly to CRX?
upvoted 0 times
...
Gary
2 months ago
Cherry-picking can lead to merge conflicts later.
upvoted 0 times
...
Herman
2 months ago
I disagree, B is safer for stability.
upvoted 0 times
...
Ming
2 months ago
Option D is the best choice for a clean fix.
upvoted 0 times
...
Tegan
2 months ago
I think option C could work, but I’m not confident about uploading packages directly. We discussed the importance of testing before deployment, right?
upvoted 0 times
...
Laurel
4 months ago
I feel like creating a new release candidate from the master branch, option B, might be overkill for just a small fix. But then again, it could ensure everything is stable.
upvoted 0 times
...
Tu
4 months ago
I'm not entirely sure, but I remember something about making fixes directly in CRX. Is that option A? It feels risky to change things directly in production.
upvoted 0 times
...
Josefa
4 months ago
I think option D sounds familiar, like we practiced cherry-picking in our last session. It seems like a safe way to get the fix into the release candidate.
upvoted 0 times
...

Save Cancel