Add support for "Delete OpenShift Resource(s)" about jenkins-plugin HOT 13 CLOSED

@bparees FYI

from jenkins-plugin.

Up. Necessary functionality. And I say more, we need that after environments launching we should be able stop/destroy the environment or components of the environment (builds, images, pods etc.).

from jenkins-plugin.

• preferably as build steps

from jenkins-plugin.

@bdeneuter and @livelace : I've got a question related to your potential preferences on how to capture what to delete. Would you say prefer:
a) to specify the same json/yaml content you provided to the create resources command, or
b) to specify a simple list of api object type:api object key pairings, or
c) to have both input methods, or
d) some other form I'm not thinking of

from jenkins-plugin.

Hello.

a) It's needed, I think.
b) I not sure what that means. Can you add examples ?
d) I think, if I can just type DC (other object name) for deletion - it' will be great.

from jenkins-plugin.

@livelace for b) something like "ImageStream:frontend,BuildConfig:frontend,DeploymentConfig:frontend,DeploymentConfig:frontend-prod"

for d) do you mean simply type in "DeploymentConfig", and we would delete all the DeploymentConfigs in the project?

from jenkins-plugin.

Your "b" - it's what I mean in my "d". Conclusion:

a) to specify the same json/yaml content you provided to the create resources command, or
b) to specify a simple list of api object type:api object key pairings ("ImageStream:frontend,BuildConfig:frontend,DeploymentConfig:frontend,DeploymentConfig:frontend-prod")

I think that it will be sufficient for us.

from jenkins-plugin.

Seems like we should just have the resource-type/resource-name pairings, not sure what benefit users would get from providing the entire resource definition yaml?

from jenkins-plugin.

not sure what benefit users would get from providing the entire resource definition yaml?

Hm, I thought about this situation and I think that will be useful for conveniences. With json/yaml (which may be huge with a lot of elements) I don't must review all objects inside and I can just put its content into Jenkins job.

from jenkins-plugin.

@livelace ok. i guess i can see the argument for it as a secondary capability.

@gabemontero another thing to consider is allowing users to provide a label to match for deletions, like you can do on the CLI. That makes it easier to delete everything a template instantiated, for example.

from jenkins-plugin.

OK, I've built a pre-release version that is stored here

It is based off of b77af1c

Don't know the precise schedule yet of when we'll start updating the OpenShift Jenkins image again with new versions of the plugin, but my best guess would be in the later May or June timeframe.

from jenkins-plugin.

@gabemontero we can do a new centos image anytime you're confident in the plugin :)

from jenkins-plugin.

On Tue, Apr 26, 2016 at 2:53 PM, Ben Parees [email protected]
wrote:

@gabemontero https://github.com/gabemontero we can do a new centos
image anytime you're confident in the plugin :)

Cool - thx for the go ahead @bparees .... I'll review the post v1.0.9
commits and come up with a regression
plan for me to try. Also, there are a couple of plugin cards which should
be eligible for inclusion in the next
sprint. If they go in, they will also trigger new image generation.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#24 (comment)

from jenkins-plugin.