Project

General

Profile

Adding a new plugin to AutoFOCUS3

  1. if not present already, add a pom.xml in your plugin
  2. add the plugin to org.fortiss.af3.phoenix.product.feature/feature.xml at the end of the "require" section
  3. in the same file, add the plugin at the end of the list of plugins
  4. in the META-INF of your plugin, set the version to 2.x.0.qualifier (x to be replaced to match the current version of AF3), the name of the plugin to your plugin name, and the name of the vendor to "fortiss GmbH"
  5. give jenkins the right to access your plugin(s) (respectively ask someone who has the right to do it) -- in most cases there is actually nothing to do
Continuous build:
  1. if not already present in your workspace, checkout the "jenkins" folder of the SVN repository; check the "ignore externals" option! otherwise it will take ages to checkout for some null benefit
  2. add the plugin to /jenkins/af3/phoenix/continous/00_source/svn.externals, at the end of the list of plugins;
    if the plugin is a *.ui plugin, add it at the end of the list of other *.ui plugins
  3. set the "svn:externals" property of /jenkins/af3/phoenix/continous/00_source/ to the contents
    of the complete text of /jenkins/af3/phoenix/continous/00_source/svn.externals (which you just modified):
    1. copy the content of svn.externals
    2. rightclick on the folder and select Team -> Show properties
    3. in the view which just opened, double-click on the svn:external property
    4. Replace the complete text with the content of svn.externals
  4. add your plugin(s) at the end of /jenkins/af3/phoenix/continous/01_compile/pom.xml
  5. add your plugin(s) at the end of /jenkins/af3/phoenix/continous/02_p2site/org.fortiss.af3.phoenix.latest.feature/feature.xml
  6. add your plugin(s) at the end of /jenkins/af3/phoenix/continous/02_p2site/pom.xml
  7. add your plugin(s) at the end of /jenkins/af3/phoenix/continous/02_test/pom.xml
  8. add your plugin(s) at the end of /jenkins-af3/af3/phoenix/continuous/03_rawrelease/org.fortiss.af3.phoenix.product.release.feature/feature.xml
Nightly build:
  1. add the plugin to /jenkins/af3/phoenix/nightly/00_source/svn.externals, at the end of the list of plugins;
    if the plugin is a *.ui plugin, add it at the end of the list of other *.ui plugins
  2. set the "svn:externals" property of /jenkins/af3/phoenix/nightly/00_source/ to the contents
    of the complete text of /jenkins/af3/phoenix/nightly/00_source/svn.externals (which you just modified):
    1. copy the content of svn.externals
    2. rightclick on the folder and select Team -> Show properties
    3. in the view which just opened, double-click on the svn:external property
    4. Replace the complete text with the content of svn.externals
  3. add your plugin(s) at the end of /jenkins/af3/phoenix/nightly/01_compile/pom.xml
  4. add your plugin(s) at the end of /jenkins/af3/phoenix/nightly/02_p2site/org.fortiss.af3.phoenix.nightly.feature/feature.xml
  5. add your plugin(s) at the end of /jenkins/af3/phoenix/nightly/02_p2site/pom.xml
  6. add your plugin(s) at the end of /jenkins-af3/af3/phoenix/nightly/03_rawproduct/org.fortiss.af3.phoenix.product.nightly.feature/feature.xml
Developer install:
  1. give world the right to access your plugin(s)
  2. Iff there is no dependency of other plugins to your newly added plugin: create a dependency on your plugin (probably the *.ui plugin) in org.fortiss.af3.rcp.application, such that your plugin will be also checked out during the buckminster materialization of the developer workspace.
  3. send an email to everybody informing that they should update their workspace