Forge Bundle Updates

Community users of the NA Inventory product will use AdapterTool's –crate switch to create a suitable zip file to post on the Forge. The owner of that ZipForge module must keep their own plugin up-to-date.

AlterPoint certified content on the forge is generated directly from our source code in CVS.

The status of all current builds can be viewed at http://build.ziptie.org. Builds will run within four minutes of your CVS checkin. You can immediately grab the adapter or tools zip from the build artifacts after the build is complete or you can wait until the artifacts are published to the Forge, which happens every morning at 12:30AM CST.

In addition, you should also subscribe to the NAI Builds email list. By subscribing to this list you will receive an email notification each time you or someone else updates an adapter or tools project that is used on the forge.

1. Checkin your project to CVS. In Eclipse you can do this by right-click –> Team –> Share
2. Update the CVSROOT/modules file. The forge module must have your new module listed in it for the build process to recognize it as a forge project.
3. Go to the Forge and add your new project

1. Make sure your project is checked into CVS
2. Login to the Forge with your username and password
3. Select “Add New…” link from left navigation
4. Select the type of content you want to add. Certified adapters/tools are based on CVS projects. Community adapters/tools are based on uploaded crates.
5. Enter name for your adapter or tool. We are using the Vendor Name + OS/Model + Adapter/Tool as a naming schema. For example, the IOS adapter for Cisco devices is called “Cisco IOS Adapter” on the Forge.
6. Select the Existing CVS Project from the drop-down list. This is a list of all of the current projects in the HEAD of the NAI CVS repository. By selecting a project, you automatically correlate this Forge instance with the selected CVS project.
7. Select the Device Make from the drop-down list. If the specific vendor is not on the list, select “Other.”
8. Select the Vendor Logo. If the appropriate vendor is not available, select the top, blank option.
9. Give your content a rating. Start with five stars for certified content.
10. For Adapters, enter a description of the adapter and what models are supported by this adapter.
11. For Tools, enter a description and what commands are used and select what adapter this tools requires to run.
12. Click “Submit” to save the new content to the Forge.
13. Note: if you post an adapter to the Forge, you MUST check in an adapter test as well. http://docs.inventory.alterpoint.com/doku.php?id=dev:adapters_testing

1. Login to the Forge with your username and password
2. Navigate to the content you want to edit
3. Click the edit tab
4. Make changes and click “Submit” button at the bottom of the form

1. Simply check in your updates to the project via CVS

Adapter or Tool updates should usually be checked into the CVS HEAD so that they are saved for future product versions.

If you want to update an adapter for a current product release of NetworkAuthority Automation or NetworkAuthority Inventory you need to merge your changes to the branch associated with that release. Here is a table of the branch that matches a release.

The build process will use the plugin version number, e.g. “2008.10.0” coupled with a timestamp of the last file updated for that project in that CVS branch. So a final name of an adapter plugin might be ziptie.adapters.cisco.ios_2008.10.0.v200810301235. Since the timestamp will be generated based on your last checkin, it will be enough for the NAA sosgi or NAI servers to recognize the new plugin.

You should never update the major version of the plugin manually, i.e. leave the MANIFEST.MF file alone.

Don't forget to add a test for any new adapters