forked from junoyoon/simpleupdatesiterepo
-
Notifications
You must be signed in to change notification settings - Fork 21
Home
Merkushev Kirill edited this page Jul 14, 2015
·
4 revisions
When you write your first custom jenkins plugin for internal purposes, its easily to deploy it into one, or maximum two jenkins instances. You can save it on your desktop and simply upload hpi
via update center when you need. Its easy to do it five or maybe ten releases. But when your experience grows, grows the number of plugins and number of their releases. And your local plugins folder became garbage dump where unreal to find new version of any plugin. And if you have lot of jenkins instances, updating all your plugins may cause lot of pain.
To avoid such situation you need to setup your own update center to serve private plugins from hpi files.