Skip to content

zenoss/pynetsnmp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

pynetsnmp

This repo defines the pynetsnamp artifact

Building

To buid a dev artifact for testing locally, use

  • git checkout develop
  • git pull origin devlop
  • make clean build

The result should be a file named something like pynetsnmp-0.40.5-dev.linux-x86_64.tar.gz artifact in the dist subdirectory. If you need to make changes, create a feature branch like you would for any other kind of change, modify the requirements definition as necessary, use make clean build to build a new tar file and then test it as necessary.

Once you have finished your local testing, commit your changes, push them, and create a pull-request as you would normally. A Jenkins PR build will be started to verify that your changes will build in a Jenkins environment.

Releasing

Use git flow to release a version to the master branch.

The artifact version number is defined in the makefile.

For Zenoss employees, the details on using git-flow to release a new version is documented on the Zenoss Engineering web site here. After the git flow release process is complete, a jenkins job must be triggered manually to build and publish the artifact.