Skip to content
This repository has been archived by the owner on Oct 5, 2022. It is now read-only.

Jenkins pipeline not configured when importing from existing GIT repository #6605

Open
oogmy opened this issue Nov 30, 2016 · 11 comments
Open

Comments

@oogmy
Copy link

oogmy commented Nov 30, 2016

Steps to reproduce:

  1. Create new app and choose import from git
  2. Enter git repository
  3. Made new ssh credential
  4. Pipeline correctly identified that there's already a Jenkins file and even offered the "edit' option
  5. Click save
  6. Go to Jenkins and see pipeline created matching the app name

At this point the pipeline script config is empty.

@davsclaus
Copy link
Member

Can you tell a bit more about what you mean with "pipeline script config"? Is it in the fabric8.yaml file or is the Jenkinsfile empty or something else? Maybe paste a screenshot or something?

@jstrachan
Copy link
Contributor

@oogmy you're using a recent release right? I thought @christian-posta had a go at fixing this issue (of importing a project with a Jenkinsfile and auto-creating the job in jenkins)

@oogmy
Copy link
Author

oogmy commented Dec 2, 2016

This is the "latest" from Stackpoint.

This is importing an existing project. fabric8.yaml gets updated and Jenkinsfile is already present. But when you go to the actual pipelines project inside Jenkins, nothing is configured.

@jstrachan
Copy link
Contributor

@oogmy ah we're waiting for the stackpoint folks to upgrade to a newer fabric8. Does it work OK in the separate namespace you deployed the fabric8-team YAML?

@oogmy
Copy link
Author

oogmy commented Dec 2, 2016

I haven't tried that yet - it was a 2 minute job setting up jenkins anyway so that's what I did. I will come back to it later after I get an end-to-end pipeline build + testing + environment promotion.

@rawlingsj
Copy link
Contributor

Not sure if stackpoint have upgraded yet but I wonder if this is related to fabric8io/fabric8-forge#755

@davsclaus
Copy link
Member

The PR from @christian-posta is here
#6556

@christian-posta
Copy link
Member

christian-posta commented Dec 2, 2016

Yah, give it a try @oogmy on the latest f8 and let me know if that works!

[edited]

Ah, looks like the PR is still opened.

@oogmy
Copy link
Author

oogmy commented Dec 5, 2016

Hi - just tried it on the latest (http://central.maven.org/maven2/io/fabric8/platform/packages/fabric8-team/2.4.6/).

The pipeline is now imported but not the credentials. I am importing from an exiting GIT repository and the associated credential config did not make it into Jenkins.

@romanlytvyn
Copy link

Still facing this issue on version 2.4.24.
After importing from git repository pipeline fails because Git URL looks like: http://gogs/...
It's impossible to change it on Core tab - gets reset back to gogs.
Interesting thing though - "Sources" section displays sources fetched from external repo using correct secrets.

Any solution/workaround/fix for this?

@romanlytvyn
Copy link

Figured it's not the same issue as original, created #6835 .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants