![]() Required if using the authenticated API with org and repo. The key within the token secret containing the actual secret. The Kubernetes secret containing the SCM provider API token. Not needed if using, , or BitBucket Cloud ![]() The SCM provider’s base URL for use with the authenticated API. Github, gitlab, gitea, bitbucketcloud, bitbucketserver ![]() The default git repository URL to use for anonymous cloning if none is specified. Note: a global maximum timeout of 1 minute is currently enforced on all resolution requests. The maximum time any single git clone resolution may take. The default git revision to use if none is specified config/resolvers/git-resolver-config.yamlįor the name, namespace and defaults that the resolver ships with. This resolver uses a ConfigMap for its settings. Tekton-pipelines-resolvers namespace set to true. The enable-git-resolver feature flag in the resolvers-feature-flags ConfigMap in the.The built-in remote resolvers installed.A cluster running Tekton Pipeline v0.41.0 or later.Defaults to empty, meaning it will try to use the configuration from the global configmap.Īn optional key in the token secret name in the PipelineRun namespace to fetch the token from. Default can be set in configuration.Īn optional secret name in the PipelineRun namespace to fetch the token from. The organization to find the repository in. Either url, or repo (with org) must be specified, but not both. URL of the repo to fetch and clone anonymously. Migrating from v1alpha1.Run to v1beta1.CustomRun.Tekton Controller Performance Configuration.Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels. This you can create pipelines for single repositories and complete namespaces in Jenkins, trigger builds for branches, tags and pull requestsĪre you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features! Though this is no direct part of SCM-Manager, we want to point to our Jenkins Plugin. The new communication is way more simple and we removed a theoratical vulnerability on the way. Last but not least we changed the way mercurial hooks are processed in SCM-Manager. We deem branches as "stale", when the latest commit of this branch is 30 days behind the latest commit When you open the branches overview, you will notice that there are two tables: First there are the "Active Branches" below you To create a new tag, you can use the little "Create Tag" button on the top Or press "Delete tag" in the detail page for a tag. To delete a tag, you can press the bin icon in the overview Like for branches, you now can create and delete tags in SCM-Manager. With the mail plugin you will get a mail. Landingpage plugin you will see the result in the "Latest activities", Finally you just have to name the repository. If this repository is not public, you can enter Mercurial) and then you can enter a repository URL (for example from GitHub). Here you can select the type (for now git or "Add Repository" and then select "Import repository" on the top right of the page. When you create new repositories you can now choose to import other repositories (for now git and mercurial). Separated into "active" and "stale" branches. The creation and deletion of tags after our changes to the branch views in the last release. Two big features are the import of git and mercurial repositories from URLs and Today we released version 2.11.0 of SCM-Manager.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |