Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve guidance when there are no pipelines to show #953

Merged
merged 1 commit into from
Nov 30, 2016

Conversation

jwforres
Copy link
Member

Fixes #932

@jwforres
Copy link
Member Author

no-pipelines

@jwforres
Copy link
Member Author

@danmcp @spadgett PTAL

@jwforres
Copy link
Member Author

the deploy button shows up if we are able to find the sample pipeline template, which is configurable through our extension Constants. It goes straight to the template deploying page for the sample.

@jwforres
Copy link
Member Author

Tweaked the spacing within the paragraph

no-pipeline-updated

@danmcp
Copy link

danmcp commented Nov 29, 2016

Awesome!

Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two small comments, otherwise LGTM.

Thanks for adding this.

var sampleNamespace = Constants.SAMPLE_PIPELINE_TEMPLATE.namespace;
DataService.get("templates", sampleName, {namespace: sampleNamespace}, {errorNotification: false}).then(
function() {
$scope.deploySampleURL = "project/" + $scope.projectName + "/create/fromtemplate?name=" + encodeURIComponent(sampleName) + "&namespace=" + encodeURIComponent(sampleNamespace);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use Navigate.fromTemplateURL. Then this won't need to change when the parameter names change in #884

Add to Project
<p ng-if="(project.metadata.name | canIAddToProject) && deploySampleURL">
<a ng-href="{{deploySampleURL}}" class="btn btn-lg btn-primary">
Deploy Sample Pipeline
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "Create Sample Pipeline" better?

@jwforres
Copy link
Member Author

updated based on feedback [merge]

@openshift-bot
Copy link

Evaluated for origin web console merge up to 482ae3a

@openshift-bot
Copy link

openshift-bot commented Nov 30, 2016

Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_web_console/777/) (Base Commit: 14fe437)

@openshift-bot openshift-bot merged commit 3e75b27 into openshift:master Nov 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants