We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
On Wed, 2 Mar 2016 15:33:28 -0500 Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
kevin
On Wednesday, March 2, 2016 1:39:09 PM CST Kevin Fenzi wrote:
On Wed, 2 Mar 2016 15:33:28 -0500
Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
kevin
What he said
Dennis
On Wed, Mar 02, 2016 at 01:39:09PM -0700, Kevin Fenzi wrote:
On Wed, 2 Mar 2016 15:33:28 -0500 Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
Same for me and as PDC is designed to be an API exposing data, at worst we could always see about using it as a backend for a new version of the dashboard.
Pierre
On Wed, Mar 02, 2016 at 01:39:09PM -0700, Kevin Fenzi wrote:
On Wed, 2 Mar 2016 15:33:28 -0500 Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
Yeah, I mentioned this during on of the releng meetings yesterday.
We want to have a central place to aggregate composes, logs, test results, etc. PDC definitely seems like it could fit that role in the future.
One of our concerns was viewing QA/taskotron logs, and tflink mentioned that the resultdb frontend is not very user friendly for this. So, I'm wondering if PDC can currently support viewing failed composes along with their logs from both the compose itself and automated QA tests, or if that's an RFE that we'll need to file.
luke
On Thu, 2016-03-03 at 13:06 -0700, Luke Macken wrote:
On Wed, Mar 02, 2016 at 01:39:09PM -0700, Kevin Fenzi wrote:
On Wed, 2 Mar 2016 15:33:28 -0500 Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
Yeah, I mentioned this during on of the releng meetings yesterday.
We want to have a central place to aggregate composes, logs, test results, etc. PDC definitely seems like it could fit that role in the future.
One of our concerns was viewing QA/taskotron logs, and tflink mentioned that the resultdb frontend is not very user friendly for this. So, I'm wondering if PDC can currently support viewing failed composes along with their logs from both the compose itself and automated QA tests, or if that's an RFE that we'll need to file.
I suspect this may be going rather beyond what PDC wants to be, but I'm not sure the 'releng dash' would be appropriate for it either.
I think PDC wants to contain rather higher-level information, like a simple yes/no "did validation tests pass?" for the compose and perhaps a link to another system which would be expected to take care of displaying detailed results.
On Thu, Mar 03, 2016 at 12:32:40PM -0800, Adam Williamson wrote:
On Thu, 2016-03-03 at 13:06 -0700, Luke Macken wrote:
On Wed, Mar 02, 2016 at 01:39:09PM -0700, Kevin Fenzi wrote:
On Wed, 2 Mar 2016 15:33:28 -0500 Ralph Bean rbean@redhat.com wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
+1 to retire it.
I don't know that pdc is going to provide all the info the same way, but I think it would be better to modify/improve PDC than maintain another thing.
Yeah, I mentioned this during on of the releng meetings yesterday.
We want to have a central place to aggregate composes, logs, test results, etc. PDC definitely seems like it could fit that role in the future.
One of our concerns was viewing QA/taskotron logs, and tflink mentioned that the resultdb frontend is not very user friendly for this. So, I'm wondering if PDC can currently support viewing failed composes along with their logs from both the compose itself and automated QA tests, or if that's an RFE that we'll need to file.
I suspect this may be going rather beyond what PDC wants to be, but I'm not sure the 'releng dash' would be appropriate for it either.
I think PDC wants to contain rather higher-level information, like a simple yes/no "did validation tests pass?" for the compose and perhaps a link to another system which would be expected to take care of displaying detailed results.
Yes, this is precisely what I was attempting to convey. Pass/fail status of each compose, with links to the compose & test logs which will live on other systems like the koji & the resultsdb.
luke
On Thu, 2016-03-03 at 14:29 -0700, Luke Macken wrote:
I think PDC wants to contain rather higher-level information, like a simple yes/no "did validation tests pass?" for the compose and perhaps a link to another system which would be expected to take care of displaying detailed results.
Yes, this is precisely what I was attempting to convey. Pass/fail status of each compose, with links to the compose & test logs which will live on other systems like the koji & the resultsdb.
Ah, I see - I misunderstood. Sorry!
On Wed, 2016-03-02 at 15:33 -0500, Ralph Bean wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
FWIW I used to use it but don't any longer, so I'm fine with you killing it :)
On Wed, Mar 02, 2016 at 03:33:28PM -0500, Ralph Bean wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
OK - the old dash has been replaced by a redirect to PDC now. We can consider re-vamping the old dash backed by PDC data if people express interest in the future.
On Wed, 2016-03-02 at 15:33 -0500, Ralph Bean wrote:
We have a site up at https://apps.fedoraproject.org/releng-dash that is supposed to trawl through the fedmsg history and display the latest status about our various artifacts (nightlies, live cds, bodhi repos, etc..).
With the move to pungi4, we will need to do some repair work on it to get that part working again.. however it crossed my mind that PDC will display a similar set of information. https://pdc.fedoraproject.org/
Question to the list: should we retire fedora-releng-dash and replace it with a redirect to PDC, or bring it up to speed on the pungi4 changes?
So for anyone who didn't see me mention it elsewhere, I wrote a thing for nightlies:
https://www.happyassassin.net/2016/04/12/fedora-nightly-image-finder/
The code is at https://pagure.io/fedora_nightlies%C2%A0, output currently lives at https://www.happyassassin.net/nightlies.html%C2%A0, but I'm all for moving it onto something more official if people like it.
For now it's doing all the work of deciding if an image 'passed the tests' itself; a future improvement may be to get openQA, autocloud etc. reporting that to PDC, and just have this tool query it from there. So far I only implemented openQA support, I'm gonna look at autocloud tomorrow (it still doesn't seem to have an API, but I can likely do something with fedmsgs).
todo: see if we still own israwhidebroken.com and set up a redirect ;) https://fedoraproject.org/wiki/Israwhidebroken.com_Proposal
rel-eng@lists.fedoraproject.org