Build failed in Jenkins: Aurora #305

See Changes: [maxim] Preserving sandbox deleted task history (part 2: state machine). -- [...truncated 4020 lines...] PASSED src/test/python/apache/aurora/client/commands/test_restart.py:162: TestRestartC

Jenkins build is back to normal : Aurora #306

See

[DISCUSS] Use $(git describe) output to bake version instead of .auroraversion

Hi all, Summarizing an IRC discussion with Bhuvan Arumugam I'm convinced we should use git-describe(1) to generate the embedded version string instead of .auroraversion. This will require 2 changes. The first is to use git-descr

Re: [DISCUSS] Use $(git describe) output to bake version instead of .auroraversion

Plucking from the man page: NAME git-describe - Show the most recent tag that is reachable from a commit Does this proposal fall apart if/when we start using tags for other purposes? -=Bill On Mon, Apr 7, 2014 at 8:05 PM, Kevin Sweeney wrote: > Hi all, > > Summarizing an IRC discussio

Re: [DISCUSS] Use $(git describe) output to bake version instead of .auroraversion

Since we create release and rc (and currently dev) tags on a terminal branch they don't show in the history for master. Similarly rc and release tags will always resolve to themselves. On Monday, April 7, 2014, Bill Farner wrote: > Plucking from the man page: > > NAME >git-describe - Sho

Re: [DISCUSS] Use $(git describe) output to bake version instead of .auroraversion

On Mon, Apr 7, 2014 at 8:35 PM, Bill Farner wrote: > Plucking from the man page: > > NAME >git-describe - Show the most recent tag that is reachable from a > commit We don't fall apart from this purpose. By default git-describe honor annotated tags unless --tags option is specified. As l