This repository has been archived on 2020-03-24. You can view files and clone it, but cannot push or open issues or pull requests.
quay/static/js/directives/ui/manage-trigger-custom-git/manage-trigger-custom-git.component.html
Charlton Austin faa6b0c3a6 fix(custom git trigger): fixed init
correctly added in default parameters for config

[TESTING -> locally with docker]

Issue: https://www.pivotaltracker.com/story/show/145071887

- [ ] It works!
- [ ] Comments provide sufficient explanations for the next contributor
- [ ] Tests cover changes and corner cases
- [ ] Follows Quay syntax patterns and format
2017-05-15 13:37:00 -05:00

64 lines
3.2 KiB
HTML

<div class="manage-trigger-custom-git-element manage-trigger-control">
<linear-workflow
done-title="Create Trigger"
(on-workflow-complete)="$ctrl.activateTrigger.emit({config: $ctrl.config})">
<!-- Section: Repository -->
<linear-workflow-section class="row"
section-id="repo"
section-title="Git Repository"
section-valid="$ctrl.config.build_source !== undefined">
<div class="col-lg-7 col-md-7 col-sm-12 main-col">
<h3>Enter repository</h3>
<strong>Please enter the HTTP or SSH style URL used to clone your git repository:</strong>
<input class="form-control" type="text" placeholder="git@example.com:namespace/repository.git"
ng-model="$ctrl.config.build_source"
ng-pattern="/(((http|https):\/\/)(.+)|\w+@(.+):(.+))/">
</div>
<div class="col-lg-5 col-md-5 hidden-sm hidden-xs help-col">
<p>Custom git triggers support any externally accessible git repository, via either the normal git protocol or HTTP.</p>
<p><b>It is the responsibility of the git repository to invoke a webhook to tell <span class="registry-name" short="true"></span> that a commit has been added.</b></p>
</div>
</linear-workflow-section><!-- /Section: Repository -->
<!-- Section: Build context -->
<linear-workflow-section class="row"
section-id="dockerfile"
section-title="Build context"
section-valid="$ctrl.config.context">
<div class="col-lg-7 col-md-7 col-sm-12 main-col">
<h3>Select build context directory</h3>
<strong>Please select the build context directory under the git repository:</strong>
<input class="form-control" type="text"
ng-model="$ctrl.config.context"
ng-pattern="/^($|\/|\/.+)/">
</div>
<div class="col-lg-5 col-md-5 hidden-sm hidden-xs help-col">
<p>The build context directory is the path of the directory containing the Dockerfile and any other files to be made available when the build is triggered.</p>
<p>If the Dockerfile is located at the root of the git repository, enter <code>/</code> as the build context directory.</p>
</div>
</linear-workflow-section><!-- /Section: Build context -->
<!-- Section: Dockerfile Location -->
<linear-workflow-section class="row"
section-id="dockerfilelocation"
section-title="Select Dockerfile"
section-valid="$ctrl.config.dockerfile_path">
<div class="col-lg-7 col-md-7 col-sm-12 main-col">
<h3>Select dockerfile path</h3>
<strong>Please select the build context directory under the git repository:</strong>
<input class="form-control" type="text"
ng-model="$ctrl.config.dockerfile_path"
ng-pattern="/^($|\/|\/.+)/">
</div>
<div class="col-lg-5 col-md-5 hidden-sm hidden-xs help-col">
<p>The dockerfile path stars with the context and ends with the path to the dockefile that you would like to build</p>
<p>If the Dockerfile is located at the root of the git repository and named Dockerfile, enter <code>/Dockerfile</code> as the dockerfile path.</p>
</div>
</linear-workflow-section><!-- /Section: Dockerfile Location -->
</linear-workflow>
</div>