Gsoc 18 Project | Collect build statistics

[Jackson Isaac]

On Mon, Apr 30, 2018 at 10:06 PM, Vishnu <vishnum1998 at gmail.com> wrote:
> Hey
>
> Repository names:
> MacPorts-features?
> Macportsinfo?
> Or just simple
> gsoc18?
>
>

I was thinking about macports-portstatistics or macports-portstats.

>
> I will look into the feedback.
> Also i am currently using create.
>
> And also in the long term. Parser would be run only once in forever or say a
> year.

If we run the parser once a year, wouldn't it be outdated pretty soon ?

> And before running the original db must be cleared.
>
> And then obvious question arise. What if a new port is added in macports.
>

You are on a right path I would say. We would want it to update after
every port is added/updated
and built.

> For that i would like to know the mechanics of new port addition.
>
> I think before the new port is added. It is obviously built before right? So
> maybe we can add some code there to update the table with a row when new
> port is added.

When a port is submitted, it is built by Travis CI and also our
buildbots, which builds
the port for mac 10.6 to 10.13 versions and gives the build status. We
would be more
interested in the status provided by the buildbot.

There could be a trigger or a listener which runs whenever a build job
is initiated and then
updates the DB on completion. I believe there would be some mechanism
to know the status
of each job.

Maybe someone more familiar with buildbot could share some insights ?

>
> Just brainstorming.
>
>
> Thanks
>
> On Mon, Apr 30, 2018, 2:23 PM Mojca Miklavec <mojca at macports.org> wrote:
>>
>> On 30 April 2018 at 02:22, Vishnu wrote:
>> > Hi
>> >
>> > After hours of fixing error in heroku and my ubuntu .
>> > Finally got to run the so far app.
>>
>> Yay! That's great since it will be much easier for the whole community
>> to test the app much more quickly.
>>
>> Now, it would be great to pick some name for the repository and
>> populate it, to simplify further work.
>>
>> > Here all the ports are listed:
>> > sleepy-wave-33400.herokuapp.com/port/
>> >
>> > When you'll open the page..probable the ports would not be there because
>> > i
>> > cleared the DB.
>> >
>> > To add the ports info into DB..we need to open this url:
>> > sleepy-wave-33400.herokuapp.com/port/parser
>> >
>> > Parsing is done using the portindex.json i have.
>> > For simplicity i have only 6 portfile data in it.
>> >
>> > Once you open sleepy-wave-33400.herokuapp.com/port/
>> > you can click on individual port to get further informant about that
>> > port.
>> > infact u can access this information using :
>>
>> Cool. Some feedback:
>> - the css should go to a separate static file
>> - allowing port id might be a bad idea because there might be a port
>> called "123"
>> - calling parser multiple times populates the database with multiple
>> copies of the same port, you should use something like
>> "create_or_update"
>> - we need to figure out the best way to call the "parser"
>>
>> I might have a few other comments, but the initial purpose was to
>> check if we have an easy way to deploy the development version and
>> this has been achieved.
>>
>> Please come up with proposal(s) for project name, so that we can make
>> an explicit request to the infrastructure team to create a new repo.
>>
>> Random brainstorming ideas: webapp, "port guardian" (in whatever
>> spelling), ...
>>
>> Mojca



-- 
Jackson Isaac