a20d10e3d5
This adds an optional date field to the prefix passed by automatic_version_prefix. An example of specifying the field is as follows: 10.<date:%Y> And the fields progress like: 10.2018.0 10.2018.1 10.2018.2 10.2019.0 The date format creates a new "current date" string using valid date directives passed into g_date_time_format(). If there is a problem reading the given date format, an error is given and the next version is returned as NULL. If no <date:...> tag is detected in the auto version prefix, the same behavior as before (appending .1 and incrementing) occurs. This may be helpful to avoid writing glue code to auto-update the version if a date string in the commit version is desired. Otherwise, --add-metadata-string=version= is an alternative for complete customization. Fixes: #1712 Closes: #1721 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose-tests | ||
| composedata | ||
| ex-container-tests | ||
| gpghome | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose | ||
| ex-container | ||
| README.md | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.To use them, you might do a
make && sudo make installinside a Docker container.Then invoke
./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.Note: This is intentionally not a
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.