Merge ~smoser/curtin:cleanup/curtainer-patch-version into curtin:master
Status: | Merged |
---|---|
Approved by: | Scott Moser |
Approved revision: | 1af5e654857c70bc762ced0e968b605b077cb99e |
Merge reported by: | Scott Moser |
Merged at revision: | 50c0007c083564e82e359f86f34e05dcd436b078 |
Proposed branch: | ~smoser/curtin:cleanup/curtainer-patch-version |
Merge into: | curtin:master |
Diff against target: |
72 lines (+21/-6) 1 file modified
tools/curtainer (+21/-6) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Needs Fixing | |
Ryan Harper (community) | Approve | ||
Review via email: mp+346651@code.launchpad.net |
Commit message
curtainer: patch source version from --source.
After adding 'CURTIN_
we now see nice output for runs from trunk. But when running from
a package via curtainer, we see:
CURTIN_
CURTIN_
CURTIN_
That is confusing as it appears our vmtest version is different
from our exe version.
That is because the patching of the version that we do in debian/rules
only applies to the built binaries, the source still has the un-modified
@@PACKAGED_
The change here is patch the source code output by --source
by default, so that running 'curtin version' from that source will
provide the correct output. Jenkins is the only known consumer of this
ouput so it was easier to change the default behavior than have the caller
become aware. To disable this behavior pass '--no-patch-
Note that curtin has verified that it downloaded the
version of the source that it is patching in, so this is
known-to-
Description of the change
Note, we will have to have the jenkins job start passing '--patch-version' to curtainer.
and we will also probably want to first check if curtainer *has* that option.
./tools/curtainer --help | grep -q -- --patch-version &&
pverarg=
./tools/curtainer ubuntu-daily:xenial $pverarg ....
FAILED: Continuous integration, rev:6f7f6eaed47 8f2b623ec68d94e 499f279f4e0540 /jenkins. ubuntu. com/server/ job/curtin- ci/949/ /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= metal-amd64/ 949/console /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= metal-arm64/ 949/console /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= metal-ppc64el/ 949/console /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= metal-s390x/ 949/console
https:/
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/curtin- ci/949/ rebuild
https:/