Generate sceenshots and store at release.
I need to generate the full set of screenshots for
1) releases 5.3, 5.4 and 6.0 (master), separately
2) for all released languages.
The command is "make screenshots" at release time and for the released build and all languages built.
At the end of the command, zip the workdir/screenshots/ folder and place it somewhere for public access.
- The screenshots will be used in http://helponlinelibreoffice.org
- expect the size of the zipped screenshots for all released languages, per release to be about 250MB
#1 Updated by Florian Effenberger about 1 year ago
Cloph has a couple of urgent topics on his desk I asked him for, so
before assigning this and #2300 to him, I'd like to know:
- How much time it will approximately take
- When the deadline is
The tasks I assigned to him have a rather high priority, and I'd like
them to get done first.
#2 Updated by Olivier Hallot about 1 year ago
I'll say the command "make screenshot" should take 1 hour to execute and can run unattended until completion, for all released languages in an Linux machine. It is done once after the build. Then the command "tar" to compress and "ftp" to store somewhere takes seconds.
The screen shooting - ideally - should be included in the release process and run automatically.
#3 Updated by Florian Effenberger about 1 year ago
- Target version changed from Recurring to Pool
My proposal then is for Cloph to have a look next week, at least not
before the other urgent tasks I tasked him with are done
#4 Updated by Florian Effenberger 12 months ago
Olivier: Is this something required for the current/changed documentation approach?
Cloph: Do you have an estimation how much time this requires from your side?
#5 Updated by Florian Effenberger 11 months ago
- Status changed from New to Feedback
Feedback from last team call:
- Brought that to ESC, advised to let the issue raise to take action/decide.
- there's jenkins build-config that is disabled atm: https://jenkins.libreoffice.org/job/lo_tb_master_win_screenshot/
#6 Updated by Florian Effenberger 9 months ago
Is there any concrete action for Cloph to take before he goes on vacation next week? I don't think so according to the ticket and todo list, but please raise the flag if so
#7 Updated by Christian Lohmaier 7 months ago
pending overall update of the buildslave, so once that is back in business, can look into build-failures, solve any that might arise and then extend to upload artifacts somewhere, similar to daily build (if that's not already part of what it is supposed to do on a successful build)
#8 Updated by Christian Lohmaier 7 months ago
- Blocked by Task #2433: Screenshot daily build currently busted added
#9 Updated by Florian Effenberger 5 months ago
- Status changed from Feedback to In Progress
build slave working again, no build errors - Cloph working on uploading the artifacts
#11 Updated by Christian Lohmaier 20 days ago
screenshot builds are working now (failures not due to screenshot part, but would be due to regular build issues) - next step is creating an upload step to the jenkins build configuration.
Hardest part on that is to decide who the files should be managed. If it is OK to just overwrite a set of screenshots with current ones it is pretty easy to do, otherwise need to add some rotation.
Also question is whether it is enough to have them uploaded to jenkins as build artifact in a zip or whether we need flat hierarchy/access to individual files. (I guess I'll start with jenkins build artifact first, as that's easiest to manage by just messing around in jenkins job definition)
#12 Updated by Florian Effenberger 19 days ago
screenshot builds are working now (failures not due to screenshot part,
Thanks a lot!
but would be due to regular build issues) - next step is creating an
upload step to the jenkins build configuration.
Can you look into that?
Hardest part on that is to decide who the files should be managed. If it
is OK to just overwrite a set of screenshots with current ones it is
pretty easy to do, otherwise need to add some rotation.
Also question is whether it is enough to have them uploaded to jenkins
as build artifact in a zip or whether we need flat hierarchy/access to
individual files. (I guess I'll start with jenkins build artifact first,
as that's easiest to manage by just messing around in jenkins job
Olivier? The easier for Cloph, of course, the better it is and the
sooner will happen :-)
#13 Updated by Olivier Hallot 19 days ago
[nitpick] the sentence "who the file should be managed() is indeed "how the files should be managed", right? [/nitpick]
I agree with Christian, let's make it flat in Jenkins.
NOte: not every screenshot is good to insert into Help. Some are just meaningless or even broken.
The current build process for the new help lists all used screenshots in the file helpcontent2/AllLangPackage_html_media_lang.mk
To simplify, we can upload all screenshots and we will pick only the good ones for the build in the makefile.
Does it make sense?
#14 Updated by Christian Lohmaier 14 days ago
FYI: while trying to set up the publishing of the screenshots, I noticed that the translation of the screenshots is broken, as is the directory layout re translated shots.
Instead of having
which makes handling them more difficult (and nullifies the efforts the screenshot target does at creating per-language zips)
So has to be considered WIP unfortunately, only English ones are usable atm.