[opensuse-buildservice] delays in web UI updates
Hi all, In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever. Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown. It seems like this is a bug in the design of the Web UI -- is there anything can be done to improve this? On an only slightly related point, I wonder if some AJAX tricks could be implemented for turning on/off building for specific repositories? It's rather slow when one is attempting to track down build errors on a particular platform: the Web UI is a bit cumbersome when it comes to turning off all building for all but one repository, as it requires as many page-reloads as one has repositories for building. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sunday 05 August 2007 14:42:10 John Pye wrote:
It seems like this is a bug in the design of the Web UI -- is there
Rather the scheduler is busy this moment at same other place... Bye, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-08-05 22:42:10 +1000, John Pye wrote:
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
patience is a virtue. the issue is not the webfrontend but the scheduler. it sometimes needs a few seconds to pickup your changes. so just wait.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
this wont help you. as it will just cause another rebuild and you have to wait even longer before you get your built package.
It seems like this is a bug in the design of the Web UI -- is there anything can be done to improve this?
patience on the user side and a few speed ups in the scheduler.
On an only slightly related point, I wonder if some AJAX tricks could be implemented for turning on/off building for specific repositories? It's rather slow when one is attempting to track down build errors on a particular platform: the Web UI is a bit cumbersome when it comes to turning off all building for all but one repository, as it requires as many page-reloads as one has repositories for building.
for such stuff i would use "osc meta pkg -e project package" to edit the project xml directly. another nice osc command for tracking down build errors is: "osc build repos arch *.spec" than it will setup a build chroot on your local box and you can debug in the local chroot before sending the changes to the buildservice. patience is a virtue! darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Rueckert wrote:
On 2007-08-05 22:42:10 +1000, John Pye wrote:
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
patience is a virtue. the issue is not the webfrontend but the scheduler. it sometimes needs a few seconds to pickup your changes. so just wait.
It often takes more like 30 seconds to a minute for me. Can I suggest that perhaps the web page request should block until the jobs have been submitted to the scheduler? Or that there be some kind of 'request pending' status that the packages be changed to in the interim? I'm sure that other users of the Web interface must be wondering whether it's working or broken... Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sunday 05 August 2007 14:42:10 wrote John Pye:
Hi all,
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
as written before, it is the scheduler you need to wait for. In General, if "trigger rebuild" does change anything, it is a bug of the build service. The service should always guarantee a clean up and consistent build. The button came when we had trouble with the virtualisation, but it could be removed again meanwhile, I think. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
On Sunday 05 August 2007 14:42:10 wrote John Pye:
Hi all,
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
as written before, it is the scheduler you need to wait for.
My concern is that the web interface doesn't even tell the user that they need to wait for the scheduler (or even that such a thing exists). I understand that you are dealing with the scheduler in some kind of asynchronous way. But there is just nothing about the web interface that tells the user that the request has been received: it's a open-loop user interface. I'd refer you to Jakob Nielson: http://www.useit.com/papers/responsetime.html The Build Service Web UI is really wonderful overall; I just wanted to emphasis this small issue, because as well as causing usability problems, it could be resulting in quite a bit of additional server load for you.
In General, if "trigger rebuild" does change anything, it is a bug of the build service. The service should always guarantee a clean up and consistent build.
We'll it's true in the sense that it doesn't do anything for 30sec or a minute or so. I consider that too long. I am puzzled as to why theres need to be such a long wait before the scheduler even tells me whether or not something has been scheduled? Surely it's just putting something into a queue? Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Monday 06 August 2007 10:13:18 wrote John Pye:
Adrian Schröter wrote:
On Sunday 05 August 2007 14:42:10 wrote John Pye:
Hi all,
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
as written before, it is the scheduler you need to wait for.
My concern is that the web interface doesn't even tell the user that they need to wait for the scheduler (or even that such a thing exists).
I understand that you are dealing with the scheduler in some kind of asynchronous way. But there is just nothing about the web interface that tells the user that the request has been received: it's a open-loop user interface.
Yes, I agree, but I think it is not easy to implement this, since the scheduler is actually trying to find out what is affected by the changes. However, it might be possibly to run 1 fast first path, just to mark possible affected projects, which could become a "unclean" tag in the UI ... Adding this as an item to discuss ...
I'd refer you to Jakob Nielson: http://www.useit.com/papers/responsetime.html
The Build Service Web UI is really wonderful overall; I just wanted to emphasis this small issue, because as well as causing usability problems, it could be resulting in quite a bit of additional server load for you.
In General, if "trigger rebuild" does change anything, it is a bug of the build service. The service should always guarantee a clean up and consistent build.
We'll it's true in the sense that it doesn't do anything for 30sec or a minute or so. I consider that too long. I am puzzled as to why theres need to be such a long wait before the scheduler even tells me whether or not something has been scheduled? Surely it's just putting something into a queue?
Just to get you a picture, a new started scheduler does need already 30 minutes to calculate the complete content of the OBS. And even though we will improve the performance of it, I expect it to run longer, since the hosted projects will increase ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Aug 06, 07 10:43:25 +0200, Adrian Schröter wrote:
On Sunday 05 August 2007 14:42:10 wrote John Pye:
Hi all,
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
as written before, it is the scheduler you need to wait for.
My concern is that the web interface doesn't even tell the user that they need to wait for the scheduler (or even that such a thing exists).
I understand that you are dealing with the scheduler in some kind of asynchronous way. But there is just nothing about the web interface that tells the user that the request has been received: it's a open-loop user interface.
Yes, I agree, but I think it is not easy to implement this, since the scheduler is actually trying to find out what is affected by the changes.
Adrian, I believe John would accept that the scheduler takes some time to actually start rebuilding. Je obviously was mislead by the UI into thinking that his rebuild requests are being ignored. I agree with John that this is an issue with UI software design. John, please prefer the reload button over the rebuild trigger. cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "This bug is visible to non-employees. Please be respectful." (bugzilla) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
John Pye -
Juergen Weigert -
Marcus Rueckert -
Stephan Binner