Running Commands with Contexts
Learn how to push code changes to the remote Git repository.
We'll cover the following...
Overview
The final step your Go CI has to perform is pushing code changes to the remote Git repository. For this step, you’ll use some concepts from the Git Version Control System, such as commits, local and remote repositories, branches, and pushing commits to remote repositories.
If you need more information about these concepts, take a look at Git’s official documentation. And if you want to try this tool locally, you’ll also need Git installed on your machine.
To push code, you’ll add another step to your pipeline to execute the command
git with the appropriate options. For now, let’s simplify it and assume that
we’re pushing code to the remote repo identified by origin using the branch
master. The complete command is git push origin master.
We could implement this feature by adding another step using the existing
step type with the necessary options. But in this case, this command will try
to push the code to a remote repository over the network—and potentially
over the internet. If there’s a network issue, it could cause the command to
hang, which would cause the goci tool to hang. If we’re executing the goci
tool manually, it’s not too bad, as we can cancel its execution after a while, but if we’re running it as part of an automation process or script, this is an
undesirable situation.
As a rule of thumb, when running external commands that can potentially
take a long time to complete, it’s a good idea to set a timeout, which upon
expiration, stops the command execution. In Go, we accomplish this by using
the context package. We’ll put this into practice by extending the step type into
a new type named timeoutStep. This new type shares the same ...