Create hotfix packages, as an iteration on the previous package.
When doing hotfixes, and try to automate versioning, we can envounter a couple of problems.
The hotfix needs to fit in between 2 existing versions. This is required, because production could be running on version 1.0.0 while test is allready running on version 1.0.123.
A hotfix should be merged back into the main branch, but not cause any disturbance of The automatic version system. What can happen is that we are doing a hotfix on 1.0.0, while HEAD has allready received a tag for version 1.0.123. If we add a hotfix tag and merge it on top of 1.0.123, we could reset the version counter.
For this reason hotfixes are never tagged. We simply release a package as an iteration on a previous package and release it without tagging the repository. The reasoning behind this strategy is, that when the hotfix is merged back onto HEAD, it will get tagged and release through the main branch anyway and it makes no sense at all to have multiple tags for the same feature. (Enforcing this is a main feature of vdt.version).
Usage
The hotfix plugin will look up the latest tag in your current branch and get it’s version. If we started a branch from a tag somewhere in the middle of our version history, that would work out fine:
> version --plugin=hotfix --iteration=11 --maintainer=lars@permanentmarkers.nl -e -t deb setup.py Skipping installation of /var/folders/46/j79zq70n21n5m54j30f1rwrh0000gp/T/package-python-staging20140618-19649-432fe4/usr/lib/python2.7/dist-packages/vdt/__init__.py (namespace package) Skipping installation of /var/folders/46/j79zq70n21n5m54j30f1rwrh0000gp/T/package-python-staging20140618-19649-432fe4/usr/lib/python2.7/dist-packages/vdt/versionplugin/__init__.py (namespace package) > ls python-vdt.versionplugin.hotfix_0.0.1-11_all.deb
The hotfix plugin can not create new versions and thus tags for you:
> version --plugin=hotfix --minor --iteration=11 --maintainer=lars@permanentmarkers.nl -e -t deb setup.py Skipping installation of /var/folders/46/j79zq70n21n5m54j30f1rwrh0000gp/T/package-python-staging20140618-19819-l5ti7o/usr/lib/python2.7/dist-packages/vdt/__init__.py (namespace package) Skipping installation of /var/folders/46/j79zq70n21n5m54j30f1rwrh0000gp/T/package-python-staging20140618-19819-l5ti7o/usr/lib/python2.7/dist-packages/vdt/versionplugin/__init__.py (namespace package) > ls python-vdt.versionplugin.hotfix_0.0.1-11_all.deb
You can see, that while we requested the minor version number to be incremented, that didn’t happen.
These hotfix packages can be pushed to a separate ‘hotfix’ repository and because they received a higher iteration number as the package it is based on, it will be installed on any environment running on that base version.
Newer packages will have a higher version number and surpass the iteration.
Plugin Arguments
--iteration The iteration number for the hotfix -s Fpm input type, one of 'dir', 'rpm', 'gem', 'python', 'empty', 'tar', 'deb'. The default is python, which has some default configuration.
1 maintainer
Metadata
1 maintainer
Release files for vdt.versionplugin.hotfix 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vdt.versionplugin.hotfix-0.0.8.tar.gz | 3.9 kB | Without provenance | Details |
Release files / vdt.versionplugin.hotfix-0.0.8.tar.gz
| Download URL | vdt.versionplugin.hotfix-0.0.8.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f5a4bf07a455d7c2b38855984ad35f74e76230670f2dad4401d8e3b502ed028
|
|
BLAKE2b-256 checksum How to use checksums |
5eede357881c103a0f5053633b0d64ef7191baea6be07dbdf4cc34a4d35016a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for vdt.versionplugin.hotfix 0.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
