Filtering through UI between releases
|
Alon Kochba
Hi,
I noticed that when filtering a specific project [1], there is a bar to compare between releases timeframe. The same is available when filtering author/org, but it doesn't seem to be available in the general view.
What I'm interested in is the spread of commits by project, in Carbon (compare master and stable/boron). We have that in the main page, but I could only find how to do it since the beginning of time. (I do have the results using spectrometer report, but it would be nice to see it in the UI).
Another question - how often is the public spectrometer's server data updated? It seems to me like it's not being updated all the time (last commits show 20 days ago)/
[1] https://spectrometer.opendaylight.org/projects
Thanks, --alon
|
|
Thomas Nadeau
If you click on the top-most folder icon (selecting a view by project), you then get how many commits were made by that project across each release cycle. If you click on the release name in the graph that selects commits within that time line. You can also select (and drag) another end point in the release timeline to constrain that way.
Commits that are 20 days old seems way off. —Tom
|
|
Alon Kochba
Hey Thomas,
I noticed the timeline graph per-project, which was why I asked.. What I was referring to (which I think is very similar but missing) is the "Overview" graph, showing how many commits there are per project, comparing all the projects, but on a per-release basis.
See attached for what we do have (which is all-time I think)
--alon
From: Thomas Nadeau [mailto:tnadeau@...]
Sent: Sunday, February 12, 2017 21:42 PM To: Kochba, Alon <alonko@...> Cc: Thanh Ha <thanh.ha@...>; spectrometer-dev@... Subject: Re: [spectrometer-dev] Filtering through UI between releases
If you click on the top-most folder icon (selecting a view by project), you then get how many commits were made by that project across each release cycle. If you click on the release name in the graph that selects commits within that time line. You can also select (and drag) another end point in the release timeline to constrain that way.
The default setting is 600 seconds, but Thanh should confirm what is set in the production deployment. Commits that are 20 days old seems way off.
—Tom
|
|
Thanh Ha <thanh.ha@...>
On Sun, Feb 12, 2017 at 2:41 PM, Thomas Nadeau <tnadeau@...> wrote: The backend updates repos every 300 seconds by default. The frontend on the other hand I'm not sure about and Vasu would have to comment here. My experience though is the frontend only updates the recently view every time we restart the frontend. It's been pretty static from my perspective.
Regards, Thanh |
|
Vasu Srinivasan <vasya10@...>
Thanh, Can you pls send me the logs from the nodejs start? Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Sun, Feb 12, 2017 at 3:07 PM, Thanh Ha <thanh.ha@...> wrote:
|
|
Thanh Ha <thanh.ha@...>
Hi Vasu, Here's a link to the full node.out log. It's 500MB. Regards, Thanh On Sun, Feb 12, 2017 at 7:55 PM, Vasu Srinivasan <vasya10@...> wrote:
|
