This setting applies only to the repo specified in this Git Clone step. You could also use expressions to match the pipeline's codebase branch or tag so that, for example, the pipeline and the Git Clone step both pull code from the same environment, such as production when a production build runs or development when a development build runs. For example, you can enter for the branch or tag name to supply a branch or tag name at runtime. You can use fixed values, runtime input, or variable expressions for the branch and tag names. Based on your selection, specify a Branch Name or Tag Name. Build Type, Branch Name, and Tag Name įor Build Type, select Git Branch if you want the step to clone code from a specific branch within the repo, or select Git Tag if you want the step to clone code from a specific commit tag. If the connector's URL Type is Account, then you must specify the name of the code repo that you want to clone into the pipeline workspace. If the connector's URL Type is Repository, then Repository Name is automatically populated based on the repository defined in the connector's configuration. GitLab: GitLab Connector Settings Reference.GitHub: GitHub connector settings reference.Bitbucket: Bitbucket connector settings reference.The following topics provide more information about creating code repo connectors: Select a connector for the source control provider hosting the code repo that you want the step to clone. The Description is an optional text string. Harness automatically assigns an Id ( Entity Identifier Reference) based on the Name. Name, Id, and Description Įnter a Name summarizing the step's purpose. Depending on the stage's build infrastructure, some settings might be unavailable. The Git Clone step has the following settings. Then, you can use a Build and Push step to build and push an image using files from both repos. ![]() You can use a Git Clone or Run step to clone the second repo into the workspace. You can use a Git Clone or Run step to clone an additional repo into a pipeline's workspace.įor example, assume the default codebase is a repo that contains app code files, and the Dockerfile necessary to build the app image is in a different repo. The codebase declared in a pipeline's first stage becomes the pipeline's default codebase, and this repo is cloned into the workspace automatically when the pipeline runs.įor more information about creating pipelines, configuring the Build stage, and specifying the default codebase, go to CI pipeline creation overview, Create and configure a codebase, and CI Build stage settings. When you add a Build stage to a CI pipeline, you specify the Git account or repository where your code is stored. If you need to clone LFS-enabled repositories or run git lfs commands (such as git lfs clone), go to Git Large File Storage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |