Preferences

I disagree that a timestamp is a “build number”. Additionally, injecting dates/times into builds is bad juju from a reproducibility perspective.

Preferably you'd have a build server where you can use the build number. I use this to build my macOS application in GitHub Actions.

    [[ $GITHUB_REF_TYPE = "tag" ]] && MARKETING_VERSION=$GITHUB_REF_NAME || MARKETING_VERSION=$(git rev-parse --short HEAD)
    echo "Building $MARKETING_VERSION ($GITHUB_RUN_NUMBER)"
    agvtool new-version -all $GITHUB_RUN_NUMBER
    agvtool new-marketing-version $MARKETING_VERSION
Non-tagged build gives me "Building a3d4743 (54)", tagged build gives me "Building 0.3.1 (55)".
Agreed, CI-managed build numbers are a good way of handling this. I've done the same thing at my past handful of jobs.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal