Gsoc 18 Project | Collect build statistics

Mojca Miklavec mojca at macports.org
Mon Mar 26 12:04:39 UTC 2018


On 26 March 2018 at 11:54, Vishnu wrote:
> Also i wanted to know.Like if a new port is created .Buildbot is
> compulsorily run right?
> and if it is deleted.There is no need for buildbot to run.So buildbot wont
> send updates to the log that port has been deleted.

I was already thinking about that and I'm not yet sure about the best
solution. Feel free to propose one. (You cannot solve all problems in
proposal though, so it's not that bad if you just plan the time to
think about the best solution :)

> In that case i want to know how / where is the port deleted from.What code?

Git logs.

> Because i would have to do changes there.That as soon as port is deleted log
> of that port is updated.

It won't be the end of the world if removal is delayed for a day.

> " Buildbot master and this website will live on a different server. How
> exactly do you plan to update the log file? "
> In that case. I would need to make a mediator

What would be a mediator? Independent script? Your app?

> (present on same server as that
> of website) of some sort. Wherein requests would be sent to that mediator.
> And that mediator would inturn write in the log files.
>
> or i think that would be hectic.
> It would be best to have the logs on the Buildbot master side.Because every
> time buildbot is used it can easily update the log at that time only.No need
> for continuously sending stuff to mediator as i previously planned above.
> As at max the logs(history) required by the web app is 20 logs.It can make a
> request to the backend to get them.
>
> I think this would be better.

I'm not particularly eager about this idea.
Relying on the buildbot to keep random logs for you is way too fragile
and you have absolutely no control of the build master, so if you'll
want to get something changed, to delete some file, to update the
format ... how will you take care of that?

It might be ok to have 20 logs per port at maximum. But it might be
that the port was last built "40.000 builds ago".

Rainer recently implemented the functionality on our build master that
sends feedback to GitHub:
https://github.com/macports/macports-infrastructure/commit/d9aeeb32b22a06eb39f1a0317869e9c12e3ed021
It could do something similar for this website.

> Also is backend and your website lives on different servers ?
> How does the interaction happen ?

I don't understand this question. Which backend and which website?

Mojca


More information about the macports-dev mailing list