Infrastructure

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.

Undestand.

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.

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?

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

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)

Any updates on that, can this be closed?

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)

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
definition)

Olivier? The easier for Cloph, of course, the better it is and the
sooner will happen :-)

[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?

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
<lang>/dir/screenshot.png
<lang>/dir2/anothershot.png
it is
/dir/<lang>/screenshot.png
/dir2/<lang>/anotherscreenshot.png
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.

Talked to Cloph, and ETA is unknown, as the bug has not been identified
Let's talk about this during the next team call (Olivier, can you add that to the agenda for the next team call?) to see how urgent this is and how to handle it

Florian Effenberger wrote:

Talked to Cloph, and ETA is unknown, as the bug has not been identified
Let's talk about this during the next team call (Olivier, can you add that to the agenda for the next team call?) to see how urgent this is and how to handle it

Olivier? Can you raise this topic during the next call if still an issue?

Florian Effenberger wrote:

Florian Effenberger wrote:

Talked to Cloph, and ETA is unknown, as the bug has not been identified
Let's talk about this during the next team call (Olivier, can you add that to the agenda for the next team call?) to see how urgent this is and how to handle it

Olivier? Can you raise this topic during the next call if still an issue?

Screenshots are useful and I use some of them in help pages. However, taking screenshots for a specific release is not in the build process and must be done manually. Furthermore, screenshots are not enough stable, some of them have undesired artifacts.

Better close or postpone this task.

Any update on this ticket?

Ping? :)