To use buckminster you need to configure at least one Buckminster installation. This is done in the Jenkins configuration. The easiest way to do this, is to use the 'Install automatically' feature. Enter a name for the Buckminster installation, select a version from the dropdown box and buckminster will be installed as needed when you run a buckminster build step. The installed buckminster will contain every feature from the respective headless update-site on eclipse.org as well as the 'subclipse' feature from cloudsmith.com.
If you activate the 'update automatically' checkbox, a check for updates will be performed before a build gets executed. If features have been updated or new features get available, they will automatically provisioned into the buckminster installation.
Those screenshot show the setup for the Buckminster Hello XML World Example. Running it will produce the following result:
The Target Platform Publisher can be used to share a definition of an eclipse target platform between different projects that build eclipse plugins with buckminster. To make use of these capabilities you need to create a new job that creates a target platform first. This can be done for example with one or more MSPECs (detailed information on when and how to use MSPECs can be found in the Buckminster Book), or simply by downloading/copying an update-site or eclipse package to the workspace.
This will also introduce the project that creates the target platform as an upstream project of the job that depends on the target platform:
Skip to end of metadata Go to start of metadata