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 Exam AD0-E134 Topic 5 Question 32 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 32
Topic #: 5
[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:

Adela
17 hours ago
I prefer making the fix locally and uploading the package. It's more controlled.
upvoted 0 times
...
Hoa
3 days ago
I think we should cherry-pick the fix commit into the release candidate. It's quicker.
upvoted 0 times
...
William
12 days ago
B. Creating a new release candidate from the master branch is the safest option to ensure the fix is properly integrated.
upvoted 0 times
Janine
4 days ago
A) Make the fix in CRX where the current release candidate is currently deployed.
upvoted 0 times
...
...
Nobuko
16 days ago
I agree with Oretha. It's safer to create a new release candidate.
upvoted 0 times
...
Oretha
21 days ago
I think we should create a new release candidate from the master branch.
upvoted 0 times
...
Elliott
26 days ago
D. Cherry-pick the fix commit into the release candidate seems like the most straightforward approach here.
upvoted 0 times
Penney
17 hours ago
D) Cherry-pick the fix commit into the release candidate.
upvoted 0 times
...
Keneth
7 days ago
C) Make the fix locally and upload the package to where the release candidate is deployed.
upvoted 0 times
...
Amos
14 days ago
B) Create a new release candidate from the master branch.
upvoted 0 times
...
Peter
18 days ago
A) Make the fix in CRX where the current release candidate is currently deployed.
upvoted 0 times
...
...

Save Cancel