Re: OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

Thanks, issue created… https://github.com/openshift/jenkins-client-plugin/issues/96 For now the work-around gets me out of the hole. Cheers. Alan. > On 19 Dec 2017, at 14:26, Justin Pierce wrote: > > The plugin tries to simplify

Re: OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

The plugin tries to simplify namespace handling for the majority of cases. In your particular case, that attempt to help is detrimental. An issue would probably be appreciated. I've copied Gabe, the active maintainer. On Tue, Dec 19, 2017 at 9:20 AM, Alan Christie < achris...@informaticsmatters.c

Re: OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

Thanks Justin, Is it of interest that the plugin’s create() behaves differently to the command-line? It just doesn't _feel_ right. I could create an issue in the client plugin GitHub project if the consensus is that the behaviour is wrong. After all, why does create() care? Its command-line-cou

Re: OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

Alan - This might be a use case for the openshift.raw API [1]. It will simply pass through any arguments you give it. Best Regards, Justin [1] https://github.com/openshift/jenkins-client-plugin#i-need-more On Tue, Dec 19, 2017 at 6:57 AM, Alan Christie < achris...@informaticsmatters.com> wrote:

Re: OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

I appear to be able to work-around the problem by iterating through the objects created by the call to process() and conditionally setting the namespace, i.e. by doing this… def objs = openshift.process('—filename=’) for (obj in objs) { if (obj.metadata.namespace

OpenShift Jenkins Pipeline (DSL) Plugin : erroneous 'incorrect namespace' error from create()?

Hi guys, I have a template that can be successfully processed and the objects created using oc from the command-line. The template is supposed to run in one namespace (let’s call it Y) but it creates secrets that are placed in another namespace/project (let’s call that X). The namespaces are ma