We capitalize the first word in task names in general - and when you
follow a log and suddenly see a single lower-case one flying along...
Fix those names that I could find and that are not variables etc.
Change-Id: I9ccde577413270d49fd790c41767b859366dc2f6
For logs stored in object storage services we want to be able to shard
into different containers. This improves scalability of the object
stores. To do this consistently we prefix all log paths with the first 3
characters of the build uuid. This way we get container names like
log_123, log_abc, and so on for a total of 4096 containers.
This behavior is off by default because users of filesystems stores
without a zuul dashboard may still want periodic/ to be filed into a top
level dir for browseability.
Change-Id: I8e72a6e587edcbdf89b793cad2d7c96c535601e7
At least until we have a good dashboard to make periodic job logs
easier to find, include the project and branch names in the log path
so that they can be disambiguated from one another now that we're
sharing common job names across them.
Change-Id: Ifaca0dbcf39792094c23c3bd4ca1f3d207f80e26
No, we *really* meant to use /AB/ABC..XYZ/ not /C...YZ/ABC..XYZ/.
Depends-On: I1c98508fe227f7f6aa1d0b2f7dcf270cecaa60d8
Change-Id: I3a6963c1a20793407b706d2decdace90521510d0
We renamed log_path to zuul_log_path everywhere but where we set the
fact. Make sure the fact setting uses the name we expect everywhere
else.
Change-Id: Ib4616ab4634ae7c5a5e93ea4e49bf218e125a9cb
Make log_path zuul_log_path because log_path is rather generic.
Rename generate-log-url to set-zuul-log-path-fact to make it
clearer what it does.
Change-Id: I91ae1e396b3ef04939edebaeea8e5b16cc50315a
Andreas Jaeger