Deployment - pdt-eg/Core-Plugin GitHub Wiki
The pdt-extensions are built and deployed via our Jenkins instance.
Continuous Delivery
When pushing into one of these repositories, the pdt-extensions p2 repository will be automatically built and new artifacts are published to amazon s3:
Deploying manually
Simply start the Deploy Trigger
job in jenkins, which will trigger the Deployment build-pipeline:
- external-mirror (aggregates our own repo and other useful p2 repos)
- pex-p2-repository (creates a composite p2 repo)
- p2-dev.pdt-extensions.org (updates the pdt-extensions.org website and flushes the cdn caches)
This can take up to 15 minutes, so you'll need to wait some time to test the updated artifacts.
Adding a new plugin
- Add a jenkins build with your plugin
- Add your feature to https://github.com/pdt-eg/external-mirror/blob/master/org.pex.p2-mirror.repo/category.xml
- Add your feature to https://github.com/pdt-eg/external-mirror/blob/master/org.pex.p2-mirror.mirror/category.xml