Hey guys, with the staging jobs and workflow working the way it does, we have a slight problem in using some tools.
Specifically, we have https://git.opendaylight.org/gerrit/#/c/78864/ to add a reasonable release name to our bootup banner. My take on resolving that request would be to use git-commit-id-plugin, in the format: "${git.closest.tag.name}+${git.closest.tag.commit.count} (${git.commit.id}}" Which I think would result in very reasonable automatically-generated release name. The key points here are: 1) local tagging would have to occur *before* maven build autorelease/stage build starts 2) once promoted, the tag must be part of history Our current process does not satisfy 2), as release happen off-branch, i.e. if I go to stable/fluorine and do 'git log' I will not see any release tags. This effectively means that the release mechanics is somehow plugged into branch locking and making sure the tag/bump-to-non-snapshot/tag-to-next-snapshot are pushed to the branch -- very much like maven-release-plugin does it. Assuming automated staging repo promoting, is there a way we can have this mechanics? Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
