Comments (13)
@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.
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.