I would envision that in the job you would pass the plugin, the JSON file 
you want to use for the deployment, the image name, and the environment you 
want to deploy to.

The main Jenkins dashboard would allow you to set your Docker repository 
location, and URLs for your various environments that you may want to 
deploy to.

I did this with a couple of lines of shell script in a free for job, but 
I'd like something that hides the implementation details from most 
developers.

Also, is there anything else you can think of that this type of plugin 
should have in order to be most useful?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b1897b62-ac24-4813-9183-92a5d96c1f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to