<div dir="ltr">" <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I just wanted to say that in the long term it's more important to make</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">sure that new builds are stored soon after they finish, but it's</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">probably much easier to start with historical data (and it's also</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">super useful in the short term), so that you have immediately</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">something to work with.</span> "<br><br>yes i definitely agree with you.It would be best to first work upon history.That will allow me to understand the code more.<br><br>Can you help me with where does that json api work from?where is the code that sends request to the backend.To get that data.<br>Once i get to know that it will simplify my job to send request to backend for port <br><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Also is there any existing method to show all ports of a maintainer?</span><br style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">or to show all ports of a category?say python?<br><br><br>It would be best if i start working gmy gsoc with 3 most important things .<br>1) Basic Port information through portindex2json</span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">2) Port Build history. It would use JSON API</span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">3) Buildbot code updation to send updates to the logs.<br><br><br>And as you said logs would be ineffective to store .For history of builds of the port.I think logfile would be the bestway to store history.<br>And regarding the syntax . I was thinking of storing the build history in json format in one line in log.txt of a particular port.<br><br>Also mojca can i know your working hours.or atleast the timezone where you live.<br>I will try to do most of the work on proposal during that time.Because only one day is left and a lot to change.</span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Thanks</span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif,sans;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(245,245,245);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Vishnu<br><br><br><br><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 March 2018 at 05:46, Mojca Miklavec <span dir="ltr"><<a href="mailto:mojca@macports.org" target="_blank">mojca@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Vishnu,<br>
<br>
On Mon, Mar 26, 2018 at 2:58 AM, Vishnu wrote:<br>
><br>
> Hi,<br>
><br>
> I wanted some help in build bot summary.<br>
> I am not sure i completely understand what's happening here.<br>
> Could you please explain me about buildbot summary more?<br>
><br>
> what i understand is :<br>
> There can be n number of builds for each port.<br>
> So how am i supposed to get the information of what all builds have<br>
> already been done for that particular port.Where can i find that history<br>
> from? from <a href="http://build.macports.org" rel="noreferrer" target="_blank">build.macports.org</a> ?<br>
<br>
Yes, that information can be obtained from <a href="http://build.macports.org" rel="noreferrer" target="_blank">build.macports.org</a>.<br>
<br>
> First and foremost I think first i have to implement the Buildbot idea<br>
> .That would create logs.<br>
> But for that idea..how to get all the exiting build history of ports?Build<br>
> history such as timestamp,os,Succesful or not?<br>
> Where to get exclusive information about a port.<br>
<br>
You cannot get that at the moment.<br>
That's what the whole idea is about: to implement the functionality<br>
that will let developers query a single port.<br>
<br>
Take a look at<br>
    <a href="https://build.macports.org/builders/ports-10.13_x86_64-builder" rel="noreferrer" target="_blank">https://build.macports.org/<wbr>builders/ports-10.13_x86_64-<wbr>builder</a><br>
<br>
You'll see a list of builds. The one currently being built is<br>
    <a href="https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/21976" rel="noreferrer" target="_blank">https://build.macports.org/<wbr>builders/ports-10.13_x86_64-<wbr>builder/builds/21976</a><br>
for the port "sumo".<br>
<br>
The task is then to go back to the history by decreasing that number<br>
(21976) one by one and fetching information from each individual build<br>
until you reach number 1 or the first build where the information is<br>
no longer available. I believe the build logs get deleted after cca.<br>
10.000 builds and we have 9 builders, so you would end up querying<br>
roughly 100k entries. That could take a couple of days and might need<br>
some coordination with Ryan, but you can start with as little as two<br>
entries per builder.<br>
<br>
This information can be queried via JSON interface<br>
(<a href="https://build.macports.org/json/help" rel="noreferrer" target="_blank">https://build.macports.org/<wbr>json/help</a>). You can infer OS version from<br>
the build slave name. Timestamp, port name, whether the build was<br>
successful etc. are all available in that JSON API, but there might be<br>
some information missing which you can only get by reading additional<br>
files/logs.<br>
<br>
For example,<br>
    <a href="https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/21973/steps/install-port/logs/files" rel="noreferrer" target="_blank">https://build.macports.org/<wbr>builders/ports-10.13_x86_64-<wbr>builder/builds/21973/steps/<wbr>install-port/logs/files</a><br>
will give you the list of files installed by the package. I don't know<br>
if we want to store that particular information or not.<br>
And<br>
    <a href="https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/21973/steps/gather-archives/logs/stdio" rel="noreferrer" target="_blank">https://build.macports.org/<wbr>builders/ports-10.13_x86_64-<wbr>builder/builds/21973/steps/<wbr>gather-archives/logs/stdio</a><br>
might give you information about whether the tarball was uploaded or not.<br>
<br>
It might be necessary to adapt/improve the buildbot setup to make some<br>
variables more easily accessible. At the moment it's pretty cumbersome<br>
to extract the version information, for example. Assigning the correct<br>
commit that lead to this build would also need some additional work.<br>
<br>
<br>
I just wanted to say that in the long term it's more important to make<br>
sure that new builds are stored soon after they finish, but it's<br>
probably much easier to start with historical data (and it's also<br>
super useful in the short term), so that you have immediately<br>
something to work with.<br>
<br>
<br>
The part "A" (buildbot idea) I initially mentioned was meant to<br>
simplify such queries. If we extended the buildbot (configuration),<br>
this might enable querying a single port (making the need for a<br>
separate website like the one in proposal slightly less urgent, but<br>
not irrelevant as we still want installation statistics etc.).<br>
<span class="HOEnZb"><font color="#888888"><br>
Mojca<br>
</font></span></blockquote></div><br></div>