-
Notifications
You must be signed in to change notification settings - Fork 504
Jenkins pipeline not configured when importing from existing GIT repository #6605
Comments
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? |
@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) |
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. |
@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 |
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. |
Not sure if stackpoint have upgraded yet but I wonder if this is related to fabric8io/fabric8-forge#755 |
The PR from @christian-posta is here |
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. |
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. |
Still facing this issue on version 2.4.24. Any solution/workaround/fix for this? |
Figured it's not the same issue as original, created #6835 . |
Steps to reproduce:
At this point the pipeline script config is empty.
The text was updated successfully, but these errors were encountered: