Build Step - Eclipse Update Site

This Build Step Dialog allows you to edit the general properties of this step, as well as the details for the Eclipse Update Site that will be created by this step.

Field Definitions

• ID This is a read-only field that displays the ID for this Build Step which is unique throughout the system.
• Name This is the name of your build step and is displayed in the Build Editor Build Steps table, as well as in the Build History view.
• Type This is a read-only field that displays what type of Build Step this is.
• Execute On Server This field allows you to set up Remote Execution of build steps. It will default to the current server, but if you have more than one Build Server defined, you may pick from any server to choose where this Build Step will run.
• Timeout This is the amount of time (in Minutes) that this step will be allowed to run. If this Step does not complete in the given amount of time, it will be canceled and the Step will be marked as Failed.
• Execute Step in Parallel This indicates whether this Step will be Run in Parallel with the subsequent step. If so, this step will be run on a separate thread from the subsequent step.
• Stop Build if Step Fails This indicates whether a failure of this Step should halt the entire Build.
• Working Dir This is the Directory in which this Build Step will execute. You may use the value ${WORKDIR} to pick up the Build's Working Directory, or specify a different one as required.
• Create if Missing This is a flag that tells the build execution engine to create this Step Working Directory if it is missing. If the directory does not exist and this flag is not set, then this Step will fail.
• Erase Before Build This is a flag that tells the build execution engine to completely erase any files or folders that it finds inside the working directory prior to starting this Step. If this flag is not checked then any contents inside your working directory will be left as-is when the Step starts.
• Feature Name This is the name of your Eclipse feature.
• Feature Category This is the name of your Feature Category and will be added to your site.xml file.
• Description This describes your Feature Category and will be added to your site.xml file.
• Update Site Root This is the full path to your eclipse update site. You may use build replacement variables for this setting.
• Create If Missing If the path defined by the Update Site Root field is missing, the Zed server will attempt to create it.
• Delete Update Site Contents Before Deploying If you are not sharing your update site folder with other projects, this can be a good way of ensuring that only the latest compiles are published to the update site.
• Site Description This is the overall description of your Eclipse update site. It will be set in the site.xml file.
• Error if Include Plugins Missing This allows you to trigger a build step error if any of the plugins defined by your Feature are missing. Sometimes you don't want this, and want to allow your Feature to be published even if some of the included features are missing.
• Error if Included Features Missing Eclipse Features can reference other Features. When this happens, a dependency chain is built up for each referenced feature. This option allows you to cause the build step to fail if anything in the dependency chain is missing. Sometimes you want to allow for missing features, though, and this option gives you that capability.
• Extra Files to Copy Sometimes you have files or plugins that you would also like to have copied over to the update site. This area gives you a free-form list of items that you would also like to have included in the copy process to build your update site.