Argument was classified as an image, image~source, or loaded template reference but should be git repo about jenkins-client-plugin HOT 7 CLOSED

Can you give some more details, eg code snippets, on what you are doing and what fails?
Sounds like you are doing st. related to "oc new-app" command!?

from jenkins-client-plugin.

openshift.newApp( 'https://stash.tre.se/scm/itopstools/alerta-oc.git', '--source-secret=repo-at-bitbucket' )
This is the step that's failing in jenkins, and what I understand is that it triggers a oc new-app command in the cluster..

And what we get is this:

ERROR: new-app returned an error;
{err=error: unable to load template file "https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc": error parsing https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc: error converting YAML to JSON: yaml: line 16: did not find expected <document start>
error: git ls-remote failed with: fatal: https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc/info/refs not valid: is this a git repository?;  local file access failed with: stat https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc: no such file or directory
error: unable to locate any images in image streams, templates loaded in accessible projects, template files, local docker images with name "https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc"

Argument 'https://stash.tre.se/projects/ITOPSTOOLS/repos/alerta-oc' was classified as an image, image~source, or loaded template reference.

So it seems this is not recognized as a git repo by oc. So can we in the openshift.newApp command specify that this is actually a git repo? We know connection works between our cluster and this git repo atleast. The repo is BitBucket.

from jenkins-client-plugin.

Try to get the new-app cmd working on the cmdline first, to fix the error(s).
Use oc new-app https://stash.tre.se/scm/itopstools/alerta-oc.git --source-secret=repo-at-bitbucket and see what that gives you.

On OCP v4.8 (and on all previous versions iirc), oc new-app will connect to the specified git repo and then tries to figure out which type of project is kept inside the repo (Java, NodeJS, ... ), to determine the Source2Image builder-image to use in the BuildConfig.
Unfortunately new-app does not use the credentials given in the secret, but prompts for interactive authentication. So - that way it wont work from Jenkins pipeline. (Note, the source-secret is only used inside the generated Buildconfig!)

But you can override new-app's behaviour by forcing it to use a S2I builder image using the tilde-syntax:
eg: use the httpd builder image from Openshift:
oc new-app httpd~https://stash.tre.se/scm/itopstools/alerta-oc.git --source-secret=repo-at-bitbucket
This should give you a few K8s/OCP manifests: Imagestream, BuildConfig, Deployment, Service

Personally, I would not use new-app inside a Jenkins pipeline. I would generate all required YAML manifests once and put them into Git. In my pipeline I would checkout that repo, then apply these YAMLs ... but in the end that's your decision, and ymmv.

Regards
Thomas

from jenkins-client-plugin.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from jenkins-client-plugin.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from jenkins-client-plugin.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

from jenkins-client-plugin.

@openshift-bot: Closing this issue.

from jenkins-client-plugin.