Comments (7)
hey @xiuwang - responded in the commit as well, but I'll repeat here:
hey @xiuwang - perhaps I should change it to :
"if a namespace is specified in the json/yaml provided for any of the resources, that namespace will take precedence over the namespace specified in the "The name of the project to create ..."
Does that make it more understandable?
from jenkins-plugin.
@gabemontero In my remember, if we
create resource(json is not include namespace , for example: https://raw.githubusercontent.com/openshift/origin/master/examples/hello-openshift/hello-pod.json) in test1 , the resource should be in test1, if we add namespace in json/yaml , I don't think it's convenient.
my understand of "if a namespace is specified in the json/yaml provided for any of the resources, that namespace will take precedence over the namespace specified in the "The name of the project to create ..." is that a namespace is not specified in json, the resource is created in project which is setting in "The name of the project to create ..."
from jenkins-plugin.
but now using hello-pod.json to create resources in test1, but actually created resouces in test which has jenkins
from jenkins-plugin.
Hey @wewang58 - I realize that I should have provided some more information to you.
- the README at http://github.com/openshift/jenkins-plugin reflects the functionality of the very latest code, which can be later than the version of the plugin installed in the openshift jenkins images for rhel (and occasionally for centos though usually that is up to date).
As such, the piece around the namespace used while creating resources is based off of this commit: 895c47b
That change came between the 1.0.20 and 1.0.21 releases.
Do you know which release of the plugin you were running with? If you were not at v1.0.21 of the plugin, I'd like for you to retry with that version installed, and tell me the results.
If you want to get an officially released version of the plugin that has the fix associated with 895c47b, I suggest you download the latest released version, install it into a running jenkins server, restart the jenkins server, and give it a try.
- for documentation and code associated with the latest official release of the plugin, go to https://github.com/jenkinsci/openshift-pipeline-plugin
In the interim, I am going to open a documentation PR to add the clarification I previously posted in this issue. I'll tag you so you can provide feedback.
thanks,
gabe
from jenkins-plugin.
@wewang58 - hey, any chance you'll be able to get back to this next week (Aug 1 - Aug 5), using the latest version of the plugin (where if you are using the rhel image, you might have to download and install the latest plugin) ?
If not I'm going to close this, as the multiple namespace stuff is working for me.
I've merge the README update.
from jenkins-plugin.
@gabemontero now tested plugin 1.0.21 ,when created resource in test1, pod is in test1 now ,thanks
from jenkins-plugin.
Cool - thanks for confirming @wewang58
from jenkins-plugin.
Related Issues (20)
- Patch / Update resources HOT 9
- jenkins template using spec.clusterIP instead of spec.portalIP HOT 2
- Build output sometimes not shown in jenkins console output HOT 2
- Deployments don't work HOT 3
- Environment Variables don't respect Parameterised Builds HOT 6
- Timeout of builds HOT 3
- Unable to do openshiftTag() in pipeline HOT 1
- FR: Support of variables inside Openshift Exec HOT 9
- BUG: "Test connection" always returns "Connections successful" HOT 11
- BUG: OpenshiftExec ignores timeout HOT 12
- Confusing print statement if openshiftVerifyDeployment fails HOT 1
- okhttp binary changes break plugin when others installed HOT 11
- Externalize the CERT_FILE = "/run/secrets/kubernetes.io/serviceaccount/ca.crt"; HOT 7
- Issue with Jenkin's Verify Build OpenShift plug-in functionality HOT 9
- Declarative pipeline support? HOT 4
- openshift-client-plugin really still a "tech preview" ? HOT 3
- Jenkins throws an error when using the openhiftBuild with the buildConfig parameter HOT 3
- Resulting GDSL is Broken HOT 2
- openshiftBuild should support binary build type. HOT 10
- Add deprecation warning and link to new plugin as first thing in repo
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jenkins-plugin.