open-nomad/website/content/docs/commands/version.mdx
Daniel Bennett 39e3a1ac3e
build/cli: Add BuildDate (#16216)
* build: add BuildDate to version info

will be used in enterprise to compare to license expiration time

* cli: multi-line version output, add BuildDate

before:
$ nomad version
Nomad v1.4.3 (coolfakecommithashomgoshsuchacoolonewoww)

after:
$ nomad version
Nomad v1.5.0-dev
BuildDate 2023-02-17T19:29:26Z
Revision coolfakecommithashomgoshsuchacoolonewoww

compare consul:
$ consul version
Consul v1.14.4
Revision dae670fe
Build Date 2023-01-26T15:47:10Z
Protocol 2 spoken by default, blah blah blah...

and vault:
$ vault version
Vault v1.12.3 (209b3dd99fe8ca320340d08c70cff5f620261f9b), built 2023-02-02T09:07:27Z

* docs: update version command output
2023-02-27 11:27:40 -06:00

36 lines
807 B
Plaintext

---
layout: docs
page_title: 'Commands: version'
description: |
Display the version and build data of Nomad
---
# Command: version
The `version` command displays build information about the running binary,
including the release version, build date, and the exact revision.
## Usage
```plaintext
nomad version
```
## Output
This command prints the version number and info about the git commit that was
used to build the binary. `BuildDate` is when the commit was made,
and `Revision` is the exact commit SHA.
The SHA may also have the string `+CHANGES` appended to the end,
indicating that local, uncommitted changes were detected at build time.
## Examples
```shell-session
$ nomad version
Nomad v1.5.0
BuildDate 2023-02-17T19:29:26Z
Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
```