C_CPE_2409 · Question #65
How do you run a Cl/CD build manually without pushing changes to Git?
The correct answer is D. Select 'Trigger a Build' in the CI/CD job's context menu. Option D is correct because most CI/CD platforms (Jenkins, GitLab, GitHub Actions, etc.) expose a "Trigger a Build" or equivalent option directly in the job/pipeline's context menu, allowing you to kick off a pipeline run on demand without committing or pushing any code. A is…
Question
How do you run a Cl/CD build manually without pushing changes to Git?
Options
- ASubmit Changes via Sync & Share action
- BCreate and run "Build task" in Task Explorer
- CSelect Deploy from the project's context menu in the Project Explorer
- DSelect 'Trigger a Build' in the CI/CD job's context menu
How the community answered
(24 responses)- B4% (1)
- C4% (1)
- D92% (22)
Explanation
Option D is correct because most CI/CD platforms (Jenkins, GitLab, GitHub Actions, etc.) expose a "Trigger a Build" or equivalent option directly in the job/pipeline's context menu, allowing you to kick off a pipeline run on demand without committing or pushing any code.
- A is wrong - "Sync & Share" is a version control action (typically in IDEs like IntelliJ) for pushing/syncing code, not triggering a build pipeline.
- B is wrong - "Build task" in Task Explorer refers to running a local build task (e.g., a Gradle or Maven task inside the IDE), not a remote CI/CD pipeline job.
- C is wrong - "Deploy" from the Project Explorer context menu initiates a deployment, not a CI/CD build run, and conflates two distinct pipeline stages.
Memory tip: Think of it this way - you want to trigger something that already exists (the CI/CD job), so you look in that job's context menu for a trigger action. The other options all involve either local tasks or code-sharing workflows, neither of which is the CI/CD control plane.
Topics
Community Discussion
No community discussion yet for this question.