[opensuse-buildservice] Suggestion for Buildservice web interface
Hello, Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s? Would save a lot of clicks and should be easy implemented. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Monday 29 January 2007 16:49 schrieb Dirk Stoecker:
Hello,
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
I plan todo this since month, but I was always too lazy ... But I would apply any patch from you :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 29-01-2007 at 18:02, Adrian Schröter <adrian@suse.de> wrote: Am Monday 29 January 2007 16:49 schrieb Dirk Stoecker: Hello,
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
I plan todo this since month, but I was always too lazy ...
But I would apply any patch from you :)
bye adrian
Adrian, is the web interface part of the lately released OBS? Or would you like to get patches against another source tree? I could be ineterested in supply some things for you :-) Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Monday 29 January 2007 17:05 schrieb Dominique Leuenberger:
On 29-01-2007 at 18:02, Adrian Schröter <adrian@suse.de> wrote:
Am Monday 29 January 2007 16:49 schrieb Dirk Stoecker:
Hello,
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
I plan todo this since month, but I was always too lazy ...
But I would apply any patch from you :)
bye adrian
Adrian,
is the web interface part of the lately released OBS?
The API and the Web Interface were always open source.
Or would you like to get patches against another source tree?
Our default tree https://forgesvn1.novell.com/svn/opensuse/trunk is fine :)
I could be ineterested in supply some things for you :-)
That would be really great :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 29 Jan 2007, Adrian Schröter wrote:
Am Monday 29 January 2007 16:49 schrieb Dirk Stoecker:
Hello,
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
I plan todo this since month, but I was always too lazy ...
But I would apply any patch from you :)
I had a look. Althought it is pretty easy, it is nothing I can develop blind. So as long as I cannot directly test the results of my changes I need to leave it to you. Ciao -- http://www.dstoecker.eu/ (PGP key available)
Am Tuesday 30 January 2007 09:14 schrieb Dirk Stoecker:
On Mon, 29 Jan 2007, Adrian Schröter wrote:
Am Monday 29 January 2007 16:49 schrieb Dirk Stoecker:
Hello,
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
I plan todo this since month, but I was always too lazy ...
But I would apply any patch from you :)
I had a look. Althought it is pretty easy, it is nothing I can develop blind. So as long as I cannot directly test the results of my changes I need to leave it to you.
Why can't you ? You know that you can run the web frontend on your local system, connected to api.opensuse.org ? Have a look in the README.devel file in the svn for details. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 30 Jan 2007, Adrian Schröter wrote:
I had a look. Althought it is pretty easy, it is nothing I can develop blind. So as long as I cannot directly test the results of my changes I need to leave it to you.
Why can't you ?
You know that you can run the web frontend on your local system, connected to api.opensuse.org ? Have a look in the README.devel file in the svn for details.
I'll try it. Let's see if I can get it working with the README.devel text. Ruby: Again programming in a new language. I really loose the overview. There are too much of them. :-) Ciao -- http://www.dstoecker.eu/ (PGP key available)
Hello,
I had a look. Althought it is pretty easy, it is nothing I can develop blind. So as long as I cannot directly test the results of my changes I need to leave it to you.
Why can't you ?
You know that you can run the web frontend on your local system, connected to api.opensuse.org ? Have a look in the README.devel file in the svn for details.
Ok, first results, please tell me how to proceed: Fixes in README.devel: a) gem install switchtower does not work. It seems this has been replaced with Capistrano. At least I got a step further with "gem install capistrano". b) I think "gem install -y rails" should be replace by "install gem-rails" package. The deployment: a) Why using named SVN access for the data download. Anonymous access would also work for me and others. As I understand it it is only to get data and not to make a real working copy. Anonymous SVN should be the best option. Everything else: a) I got the webclient running. But it accepts any login/password combination without error. At http://localhost:3000/ shows the start page with user "dstoecker" logged in. Clicking on home project fails with Error Details: Errorcode: 500 Message: Failed to establish connection: Address family not supported by protocol - socket(2) Exception from Webclient: ActiveXML::Transport::ConnectionError: Failed to establish connection: Address family not supported by protocol - socket(2) Stack Trace: b) When doing rake deploy in webclient dir I get following: - Why does it try to access /u/? Running the webclient as normal user works, why accessing anything in /?. stoecker@daneel:~/sources/buildservice/src/webclient> rake deploy (in /home/stoecker/sources/buildservice/src/webclient) * executing task deploy * executing task update ** transaction: start * executing task update_code * querying latest revision... * executing "if [[ ! -d /u/apps/releases/20070130101546 ]]; then\n svn co -q -r1123 /u/apps/releases/20070130101546 &&\n (test -e /u/apps//revisions.log || (touch /u/apps//revisions.log && chmod 666 /u/apps//revisions.log)) && echo `date +\"%Y-%m-%d %H:%M:%S\"` $USER 1123 20070130101546 >> /u/apps//revisions.log;\n fi" *** [update_code] transaction: rollback * [update_code] rolling back * executing "rm -rf /u/apps/releases/20070130101546" ** [update_code] exception while rolling back: RuntimeError, The update_code task is only run for servers matching {:desc=>"Update all servers with the latest release of the source code. All this does\nis do a checkout (as defined by the selected scm module).\n", :except=>{:no_release=>true}}, but no servers matched rake aborted! The update_code task is only run for servers matching {:desc=>"Update all servers with the latest release of the source code. All this does\nis do a checkout (as defined by the selected scm module).\n", :except=>{:no_release=>true}}, but no servers matched (See full trace by running task with --trace) Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday, 30. January 2007 11:27, Dirk Stoecker wrote:
Ok, first results, please tell me how to proceed:
Fixes in README.devel: a) gem install switchtower does not work. It seems this has been replaced with Capistrano. At least I got a step further with "gem install capistrano".
True, I'll update the readme.
b) I think "gem install -y rails" should be replace by "install gem-rails" package.
Both options work.
The deployment: a) Why using named SVN access for the data download. Anonymous access would also work for me and others. As I understand it it is only to get data and not to make a real working copy. Anonymous SVN should be the best option.
You don't need to deploy when you're developing locally. The rails applications bring their own web server, which can be run from the checkout directory. This seems to be not clear in the readme, I'll try to make it more obvious.
Everything else: a) I got the webclient running. But it accepts any login/password combination without error. At http://localhost:3000/ shows the start page with user "dstoecker" logged in. Clicking on home project fails with Error Details: Errorcode: 500 Message: Failed to establish connection: Address family not supported by protocol - socket(2)
Exception from Webclient: ActiveXML::Transport::ConnectionError: Failed to establish connection: Address family not supported by protocol - socket(2) Stack Trace: b) When doing rake deploy in webclient dir I get following: - Why does it try to access /u/? Running the webclient as normal user works, why accessing anything in /?.
/u is the default path where switchtower tries to deploy. As mentioned earlier, you don't need to. To get it to work anyway, you would have to modify the settings in webclient/config/deploy.rb.template and save it as deploy.rb.
stoecker@daneel:~/sources/buildservice/src/webclient> rake deploy (in /home/stoecker/sources/buildservice/src/webclient) * executing task deploy * executing task update ** transaction: start * executing task update_code * querying latest revision... * executing "if [[ ! -d /u/apps/releases/20070130101546 ]]; then\n svn co -q -r1123 /u/apps/releases/20070130101546 &&\n (test -e /u/apps//revisions.log || (touch /u/apps//revisions.log && chmod 666 /u/apps//revisions.log)) && echo `date +\"%Y-%m-%d %H:%M:%S\"` $USER 1123 20070130101546 >> /u/apps//revisions.log;\n fi" *** [update_code] transaction: rollback * [update_code] rolling back * executing "rm -rf /u/apps/releases/20070130101546" ** [update_code] exception while rolling back: RuntimeError, The update_code task is only run for servers matching {:desc=>"Update all servers with the latest release of the source code. All this does\nis do a checkout (as defined by the selected scm module).\n",
:except=>{:no_release=>true}}, but no servers matched
rake aborted! The update_code task is only run for servers matching {:desc=>"Update all servers with the latest release of the source code. All this does\nis do a checkout (as defined by the selected scm module).\n",
:except=>{:no_release=>true}}, but no servers matched
(See full trace by running task with --trace)
Ciao
-- Andreas Bauer - Novell - SUSE Internal Tools --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 1 Feb 2007, Andreas Bauer wrote:
b) I think "gem install -y rails" should be replace by "install gem-rails" package.
Both options work.
Sure, but only one keeps track of installed files using RPM :-) Same as for Perl and CPAN, isn't it?
The deployment: a) Why using named SVN access for the data download. Anonymous access would also work for me and others. As I understand it it is only to get data and not to make a real working copy. Anonymous SVN should be the best option.
You don't need to deploy when you're developing locally. The rails applications bring their own web server, which can be run from the checkout directory. This seems to be not clear in the readme, I'll try to make it more obvious.
So now I'm totally confused. I have the web frontend running, but how do I connect it to api.opensuse.org, so that login and data access is done there? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thursday, 1. February 2007 15:40, Dirk Stoecker wrote:
On Thu, 1 Feb 2007, Andreas Bauer wrote:
b) I think "gem install -y rails" should be replace by "install gem-rails" package.
Both options work.
Sure, but only one keeps track of installed files using RPM :-) Same as for Perl and CPAN, isn't it?
True. I'll change the paragraph to something like 'when binary packages for your distribution are available use those, else use gem install ...'
The deployment: a) Why using named SVN access for the data download. Anonymous access would also work for me and others. As I understand it it is only to get data and not to make a real working copy. Anonymous SVN should be the best option.
You don't need to deploy when you're developing locally. The rails applications bring their own web server, which can be run from the checkout directory. This seems to be not clear in the readme, I'll try to make it more obvious.
So now I'm totally confused. I have the web frontend running, but how do I connect it to api.opensuse.org, so that login and data access is done there?
You have to change the FRONTEND_HOST constant in /srv/www/obs/webclient/config/environments/development.rb.
Ciao
-- Andreas Bauer - Novell - SUSE Internal Tools --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 1 Feb 2007, Andreas Bauer wrote:
The deployment: a) Why using named SVN access for the data download. Anonymous access would also work for me and others. As I understand it it is only to get data and not to make a real working copy. Anonymous SVN should be the best option.
You don't need to deploy when you're developing locally. The rails applications bring their own web server, which can be run from the checkout directory. This seems to be not clear in the readme, I'll try to make it more obvious.
So now I'm totally confused. I have the web frontend running, but how do I connect it to api.opensuse.org, so that login and data access is done there?
You have to change the FRONTEND_HOST constant in /srv/www/obs/webclient/config/environments/development.rb.
Ok. One step more done. Now what's the port? 3001 does not react 9001 does not react 443 is not supported, as requests go out in unencrypted form 80 is not supported, as server redirects to https are the result. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, I'm still not able to run the webclient locally and accessing the build service on api.opensuse.org. Any help would be fine. Can't patch it if I can't run it.
You have to change the FRONTEND_HOST constant in /srv/www/obs/webclient/config/environments/development.rb.
Ok. One step more done.
Now what's the port?
3001 does not react 9001 does not react 443 is not supported, as requests go out in unencrypted form 80 is not supported, as server redirects to https are the result.
Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag 06 Februar 2007 13:19:58 schrieb Dirk Stoecker:
Hello,
I'm still not able to run the webclient locally and accessing the build service on api.opensuse.org.
Any help would be fine. Can't patch it if I can't run it.
You shave a look in /srv/www/obs/webclient/log/ , maybe you can see what wents wrong. Or post a relevant snippet here. bye adrian
You have to change the FRONTEND_HOST constant in /srv/www/obs/webclient/config/environments/development.rb.
Ok. One step more done.
Now what's the port?
3001 does not react 9001 does not react 443 is not supported, as requests go out in unencrypted form 80 is not supported, as server redirects to https are the result.
Ciao
-- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 6 Feb 2007, Adrian Schröter wrote:
I'm still not able to run the webclient locally and accessing the build service on api.opensuse.org.
Any help would be fine. Can't patch it if I can't run it.
You shave a look in /srv/www/obs/webclient/log/ , maybe you can see what wents wrong. Or post a relevant snippet here.
Reading the post by "Rafal Kwasny" I asume api.opensuse.org port 80 is correct. Well then there error lays here:
80 is not supported, as server redirects to https are the result.
I started wireshark to watch the I/O data stream. So I see what goes out and in: The first thing the interface tries to do is load http://api.opensuse.org/person/dstoecker So let's try this also:
wget http://api.opensuse.org/person/dstoecker --17:28:43-- http://api.opensuse.org/person/dstoecker => `dstoecker' Auflösen des Hostnamen »api.opensuse.org«.... 195.218.123.20 Verbindungsaufbau zu api.opensuse.org|195.218.123.20|:80... verbunden. HTTP Anforderung gesendet, warte auf Antwort... 302 Found Platz: https://api.opensuse.org/person/dstoecker[folge]
As you can see, instead of an answer a 302 redirect is sent. This results in wrongly interpreted data, ... If you want I can attach the error messages, but I think the problem is clear. Server configuration changed inbetween? Ciao -- http://www.dstoecker.eu/ (PGP key available)
On 2/6/07, Dirk Stoecker <opensuse@dstoecker.de> wrote:
Hello,
I'm still not able to run the webclient locally and accessing the build service on api.opensuse.org.
Quick howto on setting up local web interface: Ruby on rails depending on which mode you are running development/testing/production takes different configs into account config/environments/development.rb for development config/environments/test.rb for testing config/environments/production.rb for production when you run ./script/server it assumes you are developing and read development.rb What you have to do to work directly with buildservice is edit config/environments/development.rb and set: FRONTEND_HOST = "api.opensuse.org" FRONTEND_PORT = 80 ICHAIN_MODE = "on" delete ( or # ) ICHAIN_TEST_USER= "test" EOF now run ./script/server point your browser to http://localhost:3000 and you've got a fully functioning web client on your machine -- Regards ^^MAg^^ mailto:/jid: rafal.kwasny@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
now run ./script/server point your browser to http://localhost:3000 and you've got a fully functioning web client on your machine
I mean it worked before ichain switch I am a fool, I entered login/pass and logged on to real client because https://build.opensuse.org/ICSLogin/auth-up is hard linked in app/views/layouts/application.rhtml Adrian, how can we get around this? -- Regards ^^MAg^^ mailto:/jid: rafal.kwasny@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag 06 Februar 2007 18:36:12 schrieb Rafal Kwasny:
Hi,
now run ./script/server point your browser to http://localhost:3000 and you've got a fully functioning web client on your machine
I mean it worked before ichain switch
I am a fool, I entered login/pass and logged on to real client because https://build.opensuse.org/ICSLogin/auth-up is hard linked in app/views/layouts/application.rhtml
Adrian, how can we get around this?
Let's ask Andreas ;) Andreas, can you make this conditional ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dirk Stoecker wrote:
Could the texts in "Project xxx Status Monitor" directly link to the corresponding "Build Log"s?
Would save a lot of clicks and should be easy implemented.
Hi! Trigger rebuild button next to FAILED status in Project Status Monitor would be also great! :) (And maybe Trigger complete rebuild next to project name). - -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFygV9ASE5C6aRcUQRAjJwAKC7Ggu80zYmGsFnhu4DG3PHagTDqACgiSrM AOzLIXM+klnwW2Jk0B4uTSk= =5231 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Also I would welcome if <title> tag in HTML code contained the same string as the one in <h2> tag (with openSUSE BuildService prepended). So if we have <h2>Xfce4 desktop enviroment</h2> then the head will contain <title>openSUSE BuildService: Xfce4 desktop enviroment</title>. This will make navigation in history much better as you will not see hundreds of "openSUSE BuildService" entries, but the ones with more concrete captions. - -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFyhZnASE5C6aRcUQRArGbAJ9ZmC5dCAnldPFUZhemv8zuOU9OqgCfcFMp PQhDHZHkkbgiRfeOrCMOaDk= =T4hE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Pavol and all other build service users, Am Mittwoch, 7. Februar 2007 19:11 schrieb Pavol Rusnak:
Also I would welcome if <title> tag in HTML code contained the same string as the one in <h2> tag (with openSUSE BuildService prepended). So if we have <h2>Xfce4 desktop enviroment</h2> then the head will contain <title>openSUSE BuildService: Xfce4 desktop enviroment</title>. This will make navigation in history much better as you will not see hundreds of "openSUSE BuildService" entries, but the ones with more concrete captions.
done in SVN rev. 1219. Enjoy using the build service :-) -- David Mayr, http://davey.de openSUSE LINUX, http://opensuse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 13 Feb 2007, David Mayr wrote:
Also I would welcome if <title> tag in HTML code contained the same string as the one in <h2> tag (with openSUSE BuildService prepended). So if we have <h2>Xfce4 desktop enviroment</h2> then the head will contain <title>openSUSE BuildService: Xfce4 desktop enviroment</title>. This will make navigation in history much better as you will not see hundreds of "openSUSE BuildService" entries, but the ones with more concrete captions.
done in SVN rev. 1219. Enjoy using the build service :-)
Very nice. Two remarks: - Project Status Monitor should be "Project xxx Status Monitor" - Could "openSUSE Build Service" be shortened? "SUSE Build" would be fine. Or only build, as the SUSE logo is anyway displayed in front of it. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Also I would welcome if <title> tag in HTML code contained the same string as the one in <h2> tag (with openSUSE BuildService prepended). [...]
done in SVN rev. 1219.
Very nice.
Two remarks:
- Project Status Monitor should be "Project xxx Status Monitor"
You're right. Just commited in rev. 1221.
- Could "openSUSE Build Service" be shortened? "SUSE Build" would be fine. Or only build, as the SUSE logo is anyway displayed in front of it.
Hmmm. Me personally, I wouldn't like this short version. What's the problem with the full name? In my browser, there's no problem to display the long version, even with long package/project names appended to it ... -- David Mayr, http://davey.de openSUSE LINUX, http://opensuse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 13 Feb 2007, David Mayr wrote:
- Project Status Monitor should be "Project xxx Status Monitor"
You're right. Just commited in rev. 1221.
- Could "openSUSE Build Service" be shortened? "SUSE Build" would be fine. Or only build, as the SUSE logo is anyway displayed in front of it.
Hmmm. Me personally, I wouldn't like this short version. What's the problem with the full name? In my browser, there's no problem to display the long version, even with long package/project names appended to it ...
E.g. konqueror using Tabs, you see "openSUSE Build Service: Pro..." as title. What about moving it to the end? From openSUSE Build Service: Project Status Monitor to Project Status Monitor - openSUSE Build Service or Project Status Monitor (openSUSE Build Service) Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
E.g. konqueror using Tabs, you see "openSUSE Build Service: Pro..." as title.
What about moving it to the end?
From openSUSE Build Service: Project Status Monitor to Project Status Monitor - openSUSE Build Service
You're right, that's better. I changed it in rev. 1222 ... -- David Mayr, http://davey.de openSUSE LINUX, http://opensuse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Dirk Stoecker wrote:
- Could "openSUSE Build Service" be shortened? "SUSE Build" would be fine. Or only build, as the SUSE logo is anyway displayed in front of it.
Swap the ordering: "<page description> (openSUSE Build Service)". That way you see the most important stuff on your firefox tabs even if you have lots of them ;) cheers, Gerd -- Gerd Hoffmann <kraxel@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2/13/07, Gerd Hoffmann <kraxel@suse.de> wrote:
Swap the ordering: "<page description> (openSUSE Build Service)". That way you see the most important stuff on your firefox tabs even if you have lots of them ;)
+1 for this
cheers, Gerd
-- Gerd Hoffmann <kraxel@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- Regards ^^MAg^^ mailto:/jid: mag@entropy.be --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 13. Februar 2007 12:36 schrieb Rafal Kwasny:
On 2/13/07, Gerd Hoffmann <kraxel@suse.de> wrote:
Swap the ordering: "<page description> (openSUSE Build Service)". That way you see the most important stuff on your firefox tabs even if you have lots of them ;)
+1 for this
Done, see my previous mail (or see SVN rev. 1222) ... :-) -- David Mayr, http://davey.de openSUSE LINUX, http://opensuse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Pavol,
Trigger rebuild button next to FAILED status in Project Status Monitor would be also great!
done in SVN rev. 1195 ... -- David Mayr, http://davey.de openSUSE LINUX, http://opensuse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (8)
-
Adrian Schröter -
Andreas Bauer -
David Mayr -
Dirk Stoecker -
Dominique Leuenberger -
Gerd Hoffmann -
Pavol Rusnak -
Rafal Kwasny