Skip to content
Snippets Groups Projects
Commit 9e0f1c80 authored by Gregory Szorc's avatar Gregory Szorc
Browse files

automation: push changes affecting .hgtags

When I went to build the 5.1 tag using the in-repo automation, the
automatic version calculation failed to deduce the clean 5.1 version
string because we had only pushed the changeset corresponding to the 5.1
tag and not the changeset containing the 5.1 tag. So from the
perspective of the remote repo, the 5.1 tag didn't exist yet and
automatic version deduction failed.

This commit changes the `hg push` to also push all changesets affecting
the .hgtags file, ensuring the remote has up-to-date tags information.

I tested this by creating a local draft changeset with a dummy tag
value on a different DAG head and instructed the automation to build
a revision that didn't have this change to .hgtags. The tag was
successfully pushed and the built package had a version number
incorporating that tag.

Sending this to stable so the 5.1.1 automation hopefully "just works."
parent e0cf09bc
No related branches found
No related tags found
No related merge requests found
......@@ -485,7 +485,9 @@
'python2.7', str(hg_bin),
'--config', 'ui.ssh=ssh -F %s' % ssh_config,
'--config', 'ui.remotecmd=/hgdev/venv-bootstrap/bin/hg',
'push', '-f', '-r', full_revision,
# Also ensure .hgtags changes are present so auto version
# calculation works.
'push', '-f', '-r', full_revision, '-r', 'file(.hgtags)',
'ssh://%s//hgwork/src' % public_ip,
]
......
......@@ -176,7 +176,9 @@
'python2.7', hg_bin,
'--config', 'ui.ssh=ssh -F %s' % ssh_config,
'--config', 'ui.remotecmd=c:/hgdev/venv-bootstrap/Scripts/hg.exe',
'push', '-f', '-r', full_revision,
# Also ensure .hgtags changes are present so auto version
# calculation works.
'push', '-f', '-r', full_revision, '-r', 'file(.hgtags)',
'ssh://%s/c:/hgdev/src' % public_ip,
]
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment