This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Id83a351a8aa24c455f2cd030e01feb776acd0013
Because old migrations haven't been removed from nova turbo-hipster
was happy to upgrade all the way to trunk from any old version.
However, we should step through each branch as that's the method
we as deployers to use.
Change-Id: Ie8d57379c316e25deef720bfa8872f38218dde1f
Python in ubuntu 12.04 needs an older version of greenlet. This is
a workaround while turbo-hipster is upgraded to 16.04.
Change-Id: Iaa1c806583f79378e40b76abf11bbce2a4361c45
To speed up bootstrapping time for turbo-hipster, check if the database
exists before creating it with the seed data as part of the job run.
This allows us to preload the database (as part of a nodepool image
build) which will save a lot of time.
Change-Id: Ieb09e714e24fe6df3ce148e44d5c1148739751c0
The testing datasets are being updated to include this. This would
still be useful to test in the future if we fix kilo
Change-Id: I9d8849ce7b58eb5e2fd61c91ce691b58d27f3745
This patch exports a new env var for the script, the $TH_RESULT_FILE. If
the launched script writes something into the file name specified in
that env var and if the content of that file doesn't appear to indicate
a successful build, the content of the file is used as summary message
sent back to Zuul.
Originally, this patch attempted to do a similar thing through reading
back stuff from the shell's output log and reporting the last line from
that output, but the two major disadvantages were the inclusion of
timestamps in the log output, and Python's enrichment of the log line
with timestamps. I pondered writing a custom Python's logging.Handler
which simply remembers the last message, but the required changes in
utils.execute_to_log appeared rather messy to my untrained eye.
The main driver behind this change is a need to differentiate from hard
build failures (where we don't get any build artifacts because the build
simply failed) from "mere" test failures. Yes, our (KDE) tests are still
sloppy, and we have a fair amount of broken test still around, which is
why this difference matters to us. The result field in Zuul is more or
less free-form, so this patch does not impose any restrictions about its
format, except the "cannot start with 'SUCCESS'" because that one is
indeed very, very special.
It can be seen in action at http://ci-logs.kde.flaska.net/matrix.html .
Change-Id: I48c29d2566da12b02dcf27a551a058ecc4a303d4
Rather than stepping through the migrations just in master (which
works fine assuming they are no different to previous releases)
checkout the correct stable branch and walk through that.
Change-Id: Iff79684990cbbaa8c6ed2474aca77a2f73d64b96
It's a little hacky but saves checking the logs for a failed upgrade
and then applying the migration and re-doing it. (Which would be
complicated due to the way handle_results works).
Change-Id: I8fd0c206c027f8cf984ba9fbd011cb6c6277f2b7
Fetching from git sometimes fails. Log the IP in these cases
so we can investigate the git.o.o logs
Change-Id: I09994cf0706670c44412f5d6da97c67329b40d1b
We still need to handle testing the API database as well at some
point, but for now just handle that there are two possible places
that the cell db could be.
Change-Id: I6f718d7037d7b01ccb772013ad367367a66f82e5
Closes-Bug: 1423662
Turbo-hipster now produces different levels of logs for each job. These
need to be uploaded an in some cases have indexes generated for (eg
swift has no directory listing).
Support for zuul's swift instructions still need updating.
Change-Id: I572c8edfc856bb33998d1cfa0a8d31d274ab1bef
This way the publisher will upload all of the logs and the individual
plugin doesn't need to handle pushing the files.
Change-Id: Ib13fd149828118518a115e473b4bae06d592b28e
Improve the logging for jobs in turbo-hipster so that if something fails
in a plugin (for example the db migration checks) it is logged and uploaded
appropriately.
This causes multiple logs per job.
Change-Id: I01e73ea418defbc0c1abd3b2b4357a816ddf99c3
self.job_name is something like "shell_script-${hostname}-${number}",
and job_arguments doesn't contain anything like a job name, either.
Change-Id: I775609990c740c29016abe89c5dce9ab81ca61b9
The idea is that Zuul passes a lot of useful information, such as the
project name, target branch etc., as ZUUL_* options within the JSON job
data. Let's pass all of these variables to the launched shell script.
This will make it possible to e.g. have a single script that can do the
"right thing" for different projects with distinct build steps, etc.
Change-Id: I6f57ed19e9eef1b987fe2493d409b3ee51af22b6
