Comments on: Paver Patterns 1: Attach git branch to version number http://goldenspud.com/rotr/index.php/2009/04/14/paver-patterns-1-attach/ Fri, 14 May 2010 16:50:56 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Kevin Dangoor http://goldenspud.com/rotr/index.php/2009/04/14/paver-patterns-1-attach/comment-page-1/#comment-41064 Kevin Dangoor Wed, 15 Apr 2009 13:10:01 +0000 http://goldenspud.com/rotr/?p=140#comment-41064 Oops... I just realized that I never went back and updated compute_version to actually return the proper version number (either options.version_base or the extended version number you provide). I'll leave that as an exercise for the reader ;) Oops… I just realized that I never went back and updated compute_version to actually return the proper version number (either options.version_base or the extended version number you provide). I’ll leave that as an exercise for the reader ;)

]]> By: Kevin Dangoor http://goldenspud.com/rotr/index.php/2009/04/14/paver-patterns-1-attach/comment-page-1/#comment-41062 Kevin Dangoor Wed, 15 Apr 2009 13:08:02 +0000 http://goldenspud.com/rotr/?p=140#comment-41062 Hey, thanks for the article! Great to see the way people are using Paver. You could potentially automate this in a "release" task. Create a DEV.txt or similar that says something like "This is unreleased development code. Good luck!". Commit that to the repository. Here is pseudocode for how you'd do the rest: <pre lang="python"> def compute_version(): if options.dev_file.exists(): try: git_head_path = path('.git/HEAD') contents = git_head_path.open('rU').readline().strip() name, value = contents.split() BRANCH = value.split('/')[-1] if BRANCH != 'master': VERSION += '-' + BRANCH except: pass VERSION += '-dev' options( version_base="1.2.3", dev_file=path('DEV.txt') ) setup( name='MyProject', version=compute_version ) @task def release(options): dev_file.copy("DEV-backup.txt") # not totally familiar with git... this command may be a little different sh("git rm %s" % dev_file) # build the distribution call_task('sdist') sh("git commit -a -m 'tagging release'") sh("git tag %s" % options.setup.version) # do tags need to be committed? beats me ;) path("DEV-backup.txt").move(dev_file) sh("git add %s" % dev_file) sh("git commit -a -m 'marking new development'") </pre> This is not necessarily the most elegant way to do it, but you get the idea. At least you don't need to manually run through these steps each time. Hey, thanks for the article! Great to see the way people are using Paver.

You could potentially automate this in a “release” task. Create a DEV.txt or similar that says something like “This is unreleased development code. Good luck!”. Commit that to the repository. Here is pseudocode for how you’d do the rest:

    def compute_version():
      if options.dev_file.exists():
          try:
              git_head_path = path('.git/HEAD')
              contents = git_head_path.open('rU').readline().strip()
              name, value = contents.split()
              BRANCH = value.split('/')[-1]
              if BRANCH != 'master':
                  VERSION += '-' + BRANCH
          except:
              pass
          VERSION += '-dev'
 
 
    options(
        version_base="1.2.3",
        dev_file=path('DEV.txt')
    )
 
    setup(
        name='MyProject',
        version=compute_version
    )
 
    @task
    def release(options):
        dev_file.copy("DEV-backup.txt")
        # not totally familiar with git... this command may be a little different
        sh("git rm %s" % dev_file)
        # build the distribution
        call_task('sdist')
        sh("git commit -a -m 'tagging release'")
        sh("git tag %s" % options.setup.version)
        # do tags need to be committed? beats me ;)
        path("DEV-backup.txt").move(dev_file)
        sh("git add %s" % dev_file)
        sh("git commit -a -m 'marking new development'")

This is not necessarily the most elegant way to do it, but you get the idea. At least you don’t need to manually run through these steps each time.

]]>