Jx: Tekton: error: No Pipeline found for name PIPELINE_NAME in values:

[shahnewazrifat]

Summary

I'm getting a
error: No Pipeline found for name trilogy-group/angular7-example-app/master in values:
When running:
jx get build logs PIPELINE_NAME
Although I can see the pipeline present when I run
jx get pipelines
And even I can see it in deck

Steps to reproduce the behavior

jx import --url SOME_GIT_URL

Expected behavior

shows the build logs

Actual behavior

Shows error error: No Pipeline found for name PIPELINE_NAME_HERE in values:

Jx version

2.0.191
The output of jx version is:

jx                 2.0.191                                                                                                                                                                                                                    jenkins x platform 2.0.330                                                                                                                                                                                                                    Kubernetes cluster v1.12.6-eks-d69f1b                                                                                                                                                                                                         kubectl            v1.14.2                                                                                                                                                                                                                    helm client        Client: v2.14.0+g05811b8    

Jenkins type

• [x] Next Generation (Tekton + Prow)
• [ ] Classic Jenkins
• [ ] Serverless Jenkins (JenkinsFileRunner + Prow)

Kubernetes cluster

EKS. Created using jx create cluster eks

Operating system / Environment

Ubuntu 18.04

[abayer]

Verified that this is the case - but the approach used with classic Jenkins here doesn't really apply to Prow/Tekton/etc very well, so we need to think about what the solution is.

For now, you can use filters, though - so jx get build logs --repo=angular7-example-app --owner=trilogy-group --branch=master will get you basically the same results you're expecting.

[shahnewazrifat]

Thanks for confirming @abayer !
It's confusing as after the jx import that's the suggested command shown in output terminal.

[shahnewazrifat]

Verified that this is the case - but the approach used with classic Jenkins here doesn't really apply to Prow/Tekton/etc very well, so we need to think about what the solution is.

For now, you can use filters, though - so jx get build logs --repo=angular7-example-app --owner=trilogy-group --branch=master will get you basically the same results you're expecting.

jx get build logs --repo=angular7-example-app --owner=trilogy-group --branch=master
Yields the same error though.

[hferentschik]

@abayer, @shahnewazrifat - I just tried jx get build logs <pipeline-name> and it seems to work. I think this issue is really out of date. WDYT?

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.