public class MergeWithGitSCMExtension extends GitSCMExtension
PreBuildMerge, but for use from SCMSource implementations that need to specify the exact
base branch hash. The hash is specified so that we are not subject to a race condition between the baseHash
we think we are merging with and a possibly newer one that was just pushed.
IMPORTANT This extension is intended for programmatic use only. It must be the last extension in the list of extensions or else some other extension may turn on shallow cloning.
| Constructor and Description |
|---|
MergeWithGitSCMExtension(String baseName,
String baseHash) |
| Modifier and Type | Method and Description |
|---|---|
void |
decorateCloneCommand(GitSCM scm,
Run<?,?> build,
org.jenkinsci.plugins.gitclient.GitClient git,
TaskListener listener,
org.jenkinsci.plugins.gitclient.CloneCommand cmd)
Called before a
CloneCommand is executed to allow extensions to alter its behaviour. |
void |
decorateFetchCommand(GitSCM scm,
org.jenkinsci.plugins.gitclient.GitClient git,
TaskListener listener,
org.jenkinsci.plugins.gitclient.FetchCommand cmd)
Deprecated.
|
hudson.plugins.git.Revision |
decorateRevisionToBuild(GitSCM scm,
Run<?,?> build,
org.jenkinsci.plugins.gitclient.GitClient git,
TaskListener listener,
hudson.plugins.git.Revision marked,
hudson.plugins.git.Revision rev)
Called after
BuildChooser selects the revision to pick for this build, but before |
String |
getBaseHash() |
String |
getBaseName() |
beforeCheckout, beforeCheckout, decorate, decorateCheckoutCommand, decorateCheckoutCommand, decorateCloneCommand, decorateFetchCommand, decorateMergeCommand, decorateMergeCommand, decorateRevisionToBuild, determineSupportForJGit, enableMultipleRevisionDetection, getDescriptor, getRequiredClient, getWorkingDirectory, getWorkingDirectory, isRevExcluded, onCheckoutCompleted, onCheckoutCompleted, onClean, populateEnvironmentVariables, requiresWorkspaceForPolling@NonNull public String getBaseName()
public String getBaseHash()
public void decorateCloneCommand(GitSCM scm, Run<?,?> build, org.jenkinsci.plugins.gitclient.GitClient git, TaskListener listener, org.jenkinsci.plugins.gitclient.CloneCommand cmd) throws IOException, InterruptedException, hudson.plugins.git.GitException
GitSCMExtensionCloneCommand is executed to allow extensions to alter its behaviour.decorateCloneCommand in class GitSCMExtensionscm - GitSCM objectbuild - run contextgit - GitClientlistener - build logcmd - clone command to be decoratedIOException - on input or output errorInterruptedException - when interruptedhudson.plugins.git.GitException - on git error@Deprecated public void decorateFetchCommand(GitSCM scm, org.jenkinsci.plugins.gitclient.GitClient git, TaskListener listener, org.jenkinsci.plugins.gitclient.FetchCommand cmd) throws IOException, InterruptedException, hudson.plugins.git.GitException
GitSCMExtensionFetchCommand is executed to allow extensions to alter its behaviour.decorateFetchCommand in class GitSCMExtensionscm - GitSCM objectgit - GitClientlistener - build logcmd - fetch command to be decoratedIOException - on input or output errorInterruptedException - when interruptedhudson.plugins.git.GitException - on git errorpublic hudson.plugins.git.Revision decorateRevisionToBuild(GitSCM scm, Run<?,?> build, org.jenkinsci.plugins.gitclient.GitClient git, TaskListener listener, hudson.plugins.git.Revision marked, hudson.plugins.git.Revision rev) throws IOException, InterruptedException, hudson.plugins.git.GitException
GitSCMExtensionBuildChooser selects the revision to pick for this build, but before
This allows extensions to select a derived revision (for example by merging another branch into the chosen revision and returning it) or manipulate the state of the working tree (such as running git-clean.)
GitSCMExtension.decorateRevisionToBuild(GitSCM, Run, GitClient, TaskListener, Revision, Revision) vs BuildChooser
BuildChooser and this method are similar in the sense that they both participate in the process
of determining what commits to build. So when a plugin wants to control the commit to be built, you have
a choice of these two approaches. The rule of the thumb is to ask yourself if your process takes
another commit as an input.
BuildChooser is suitable when you do not take any commit as a parameter, and need to precisely
control what commit to build. For example the gerrit-trigger plugin looks at
a specific build parameter, then retrieves that commit from Gerrit and builds that.
GitSCMExtension.decorateRevisionToBuild(GitSCM, Run, GitClient, TaskListener, Revision, Revision) is suitable
when you accept arbitrary revision as an input and then create some derivative commits and then build that
result. The primary example is for speculative merge with another branch (people use this to answer
the question of "what happens if I were to integrate this feature branch back to the master branch?")
decorateRevisionToBuild in class GitSCMExtensionscm - GitSCM objectbuild - run contextgit - GitClient objectlistener - build logmarked - The revision that started this build. (e.g. pre-merge)rev - The revision selected for this build.rev, return the value
given in the rev parameter.IOException - on input or output errorInterruptedException - when interruptedhudson.plugins.git.GitException - on git errorCopyright © 2007–2021. All rights reserved.