FAQ page #14

Open
opened 9 months ago by pstorch · 15 comments
pstorch commented 9 months ago
Owner

Seein the "running" status is very good! Are the timestamps UTC or local? How long does it take on average for an update of the "last modified" in running? (ideas for a "FAQ" screen).

Timestamps are local times.

Seein the "running" status is very good! Are the timestamps UTC or local? How long does it take on average for an update of the "last modified" in running? (ideas for a "FAQ" screen). Timestamps are local times.
pstorch added the
enhancement
label 9 months ago
Poster
Owner

Also suggestion from @Izzy: will you somehow integrate the essence of that with some "info page" in your app, Peter?

With "essence" it's meant to describe what the F-Droid build status API is providing currently, what the caveats are, special situations (build and running are the same) etc.

Also suggestion from @Izzy: will you somehow integrate the essence of that with some "info page" in your app, Peter? With "essence" it's meant to describe what the F-Droid build status API is providing currently, what the caveats are, special situations (build and running are the same) etc.

Plus maybe a raw outline of how the entire "process cycle" works, like

Not sure where https://f-droid.org/repo/status/update.json fits in.

Plus maybe a raw outline of how the entire "process cycle" works, like * checkUpdates (https://f-droid.org/repo/status/checkupdates.json) triggered cia cron job * build process (obviously triggered manually) with running/finished * manual signing * deploy (https://f-droid.org/repo/status/deploy.json) – most likely triggered manually as final step of the signing process Not sure where https://f-droid.org/repo/status/update.json fits in.
Poster
Owner

Maybe it would be good to have this also on the F-Droid documentation page. I don't think this API is already documented, is it?

Maybe it would be good to have this also on the F-Droid documentation page. I don't think this API is already documented, is it?

Hi @pstorch @izzy

All is there: https://f-droid.org/wiki/page/Main_Page

See the doc section.

Hi @pstorch @izzy All is there: https://f-droid.org/wiki/page/Main_Page See the doc section.

@pstorch I don't know if it's the goal of your app, but maybe you should add everything about the server and the clients (apps but also F-Droid Android client) in your interface. A central point to get the logs, builds, errors... instead of browsing the wiki, all is aggregated there.

I also see as header a summary of failed, success with big letters like this:
Dashboard

@pstorch I don't know if it's the goal of your app, but maybe you should add everything about the server and the clients (apps but also F-Droid Android client) in your interface. A central point to get the logs, builds, errors... instead of browsing the wiki, all is aggregated there. I also see as header a summary of failed, success with big letters like this: ![Dashboard](https://about.gitlab.com/images/11_5/group-security-dashboard.png)

@hotlittlewhitedog that wiki is deprecated. A new wiki (for notes, scratch-pad etc. of contributors as well as collecting and pre-formulating ideas for the documentation) was just created here.

@pstorch AFAIK it's not yet documented. But I'm not the person for that part; I'd prefer someone with "deeper knowledge/experience" should do that. Truth be told, I'm already split too often, I cannot keep up with yet another task… If you want to drop your notes there, that would certainly be welcomed. You know how it works: Ask someone to document it, and you'll wait for that 'til judgement day. Just set up a totally wrong documentation, and everyone jumps in fixing it ("someone is wrong on the Internet" effect) 🤣

@hotlittlewhitedog that wiki is deprecated. A new wiki (for notes, scratch-pad etc. of contributors as well as collecting and pre-formulating ideas for the documentation) was just [created here](https://gitlab.com/fdroid/wiki). @pstorch AFAIK it's not yet documented. But I'm not the person for that part; I'd prefer someone with "deeper knowledge/experience" should do that. Truth be told, I'm already split too often, I cannot keep up with yet another task… If you want to drop your notes there, that would certainly be welcomed. You know how it works: Ask someone to document it, and you'll wait for that 'til judgement day. Just set up a totally wrong documentation, and everyone jumps in fixing it ("someone is wrong on the Internet" effect) :rofl:
Poster
Owner

Just came in: https://gitlab.com/fdroid/fdroid-website/-/issues/530

Someone is reading our mind 😁

Just came in: https://gitlab.com/fdroid/fdroid-website/-/issues/530 Someone is reading our mind 😁

Yay, thanks for the pointer! I just threw in my 2 ct.

Yay, thanks for the pointer! I just threw in my 2 ct.

PS: Funny thing. I currently watch running here – and just saw apps are not only added, but also removed from succeeded as well as from failed. Very strange.

PS: Funny thing. I currently watch running [here](https://monitor.f-droid.org/builds/running) – and just saw apps are not only added, but also removed from succeeded as well as from failed. Very strange.
Poster
Owner

That is strange indeed. I thought my app tricks me. Because I got a build update notification, opened the App and the number was decreasing.

That is strange indeed. I thought my app tricks me. Because I got a build update notification, opened the App and the number was decreasing.
Poster
Owner

Wondering: could it be that there are two instances of the build server are running in parallel overwriting each others running.json?
No, this can't be, right?

Wondering: could it be that there are two instances of the build server are running in parallel overwriting each others running.json? No, this can't be, right?

Probably not, but technically it's possible. That's why the PID (process id) and a reference of the instance server would be crystal clear.

Probably not, but technically it's possible. That's why the PID (process id) and a reference of the instance server would be crystal clear.
Poster
Owner

That's not provided by the current API. But I think a good idea.

BTW: I still see a flapping between 10 and 13 successful builds.

Other theory: does the website have several cluster nodes? Maybe one was not updated correctly with the last running.json?

That's not provided by the current API. But I think a good idea. BTW: I still see a flapping between 10 and 13 successful builds. Other theory: does the website have several cluster nodes? Maybe one was not updated correctly with the last running.json?
Poster
Owner

Regarding the counts of failed and successful builds: I just found an error in the deduplication logic in the app. 😢

Regarding the counts of failed and successful builds: I just found an error in the deduplication logic in the app. 😢

could it be that there are two instances of the build server are running in parallel

Not yet AFAIK. That's something that was discussed, though, too speed up the build process – but the "sync" between the two must be implemented. Back then it was decided to do the usual trick: slain it with hardware (more cores, more RAM). It's still on the list, though, as parallel processing would have another advantage: if one machine chokes, the other goes on (hopefully).

> could it be that there are two instances of the build server are running in parallel Not ***yet*** AFAIK. That's something that was discussed, though, too speed up the build process – but the "sync" between the two must be implemented. Back then it was decided to do the usual trick: slain it with hardware (more cores, more RAM). It's still on the list, though, as parallel processing would have another advantage: if one machine chokes, the other goes on (hopefully).
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.