Small feedback on Hudson

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Small feedback on Hudson

Stephan Zeissler (KUTTIG)
Hi everyone,

i just want to give a short feedback on hudson. I'm currently using it
to build some java ant projects for my company.
I really enjoy using hudson and I'm working hard that some of my
colleagues start using it too :) , but I noticed some things i want you
to notice:

- The description feature for views and projects are a nice idea, but
special chars like < ü ... are evaluated when send back. So when
you save < its saved as < but when you re-edit the description you
get back a <. When you now save again, your < is lost as a html element.
Same for others special characters.
- Consider renaming the javadoc/ URI to web/ or something like this. In
one project I misuse the javadoc/ feature to populate my jnlp project,
which works fine, but the javadoc/ in the URL is confusing. Furthermore
projects that use maven may want to use this feature to populate their
project documentation.
- Global disable all builds checkbox: I'm currently moving hudson + svn
repositories to a new server and after copying and starting the server
it startet builds some projects which failed because the svn server
wasn't available.

Well, the rest is nice and works like charm ;)

Regards,
Stephan Zeissler

KUTTIG Computeranwendungen GmbH
Frankfurter Stra├če 35
53840 Troisdorf
MOB +49 (173) 7207900
FON +49 (2241) 9833-413
FAX +49 (2241) 9833-100
EMAIL [hidden email]
WEB www.kuttig.com
GF Dipl.-Kfm. Klaus Kuttig
Michael Wessels
HR Siegburg Nr 2848


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

stephan.zeissler.vcf (307 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Small feedback on Hudson

Stephen Connolly-2

Stephan Zeissler (KUTTIG) wrote
- Global disable all builds checkbox: I'm currently moving hudson + svn
repositories to a new server and after copying and starting the server
it startet builds some projects which failed because the svn server
wasn't available.
Manage Hudson | Prepare for shutdown

does what you're looking for
Reply | Threaded
Open this post in threaded view
|

Re: Small feedback on Hudson

Kohsuke Kawaguchi
Administrator
In reply to this post by Stephan Zeissler (KUTTIG)
Stephan Zeissler (KUTTIG) wrote:
> - The description feature for views and projects are a nice idea, but
> special chars like &lt; &uuml; ... are evaluated when send back. So when
> you save &lt; its saved as &lt; but when you re-edit the description you
> get back a <. When you now save again, your < is lost as a html element.
> Same for others special characters.

Ah, good point. Can you file this as an issue in the issue tracker.

> - Consider renaming the javadoc/ URI to web/ or something like this. In
> one project I misuse the javadoc/ feature to populate my jnlp project,
> which works fine, but the javadoc/ in the URL is confusing. Furthermore
> projects that use maven may want to use this feature to populate their
> project documentation.

If the URL (and more importantly the link to URL) doesn't say "javadoc",
people will not find it very intuitive. For things like you are
describing, we should really have plugins.

A plugin that publishes a jnlp file (and by parsing the jnlp file, it
can automatically discover all the jars, too, right?) and display the
JNLP launch icon sounds like very useful. The ditto for the publishing
of maven site. Again, it would be great if you can file them as issues.

I guess the problem that prevents people from writing plugins is that
it's still too hard. If we can make simple plugins really simple, or
perhaps come up with a way to do a parametric plugin so that all
JjavadocArchiver-like plugins can be created with a single description
file or something, that could be very useful.

Hmm...


> - Global disable all builds checkbox: I'm currently moving hudson + svn
> repositories to a new server and after copying and starting the server
> it startet builds some projects which failed because the svn server
> wasn't available.

Stephen is right on this. The "prepare for shutdown" feature is for this.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Small feedback on Hudson

Jesse Glick
In reply to this post by Stephan Zeissler (KUTTIG)
Stephan Zeissler (KUTTIG) wrote:
> Consider renaming the javadoc/ URI to web/ or something like this. In
> one project I misuse the javadoc/ feature to populate my jnlp
> project, which works fine, but the javadoc/ in the URL is confusing.
> Furthermore projects that use maven may want to use this feature to
> populate their project documentation.

I have noticed this Java-centrism also. (Workaround, if you really hate
the javadoc/ URL, is to publish as an artifact rather than "Javadoc".
Unfortunately this does not automatically serve index.html from the top
dir if you have one.)

Could you file a bug for this?

-J.

--
[hidden email]  netbeans.org  ant.apache.org  hudson.dev.java.net
             http://google.com/search?q=e%5E%28pi*i%29%2B1

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Small feedback on Hudson

Kohsuke Kawaguchi
Administrator
Jesse Glick wrote:
> I have noticed this Java-centrism also. (Workaround, if you really hate
> the javadoc/ URL, is to publish as an artifact rather than "Javadoc".
> Unfortunately this does not automatically serve index.html from the top
> dir if you have one.)
>
> Could you file a bug for this?

Hmm, but Hudson is Java centric in its choice of default
publishers/builders. We ship with Ant and Maven builders, etc. So
javadoc archiver isn't the only thing.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

AW: Re: Small feedback on Hudson

Stephan Zeissler (KUTTIG)
In reply to this post by Kohsuke Kawaguchi
> > - The description feature for views and projects are a nice idea, but
> > special chars like &lt; &uuml; ... are evaluated when send back. So when
> > you save &lt; its saved as &lt; but when you re-edit the description you
> > get back a <. When you now save again, your < is lost as a html element.
> > Same for others special characters.
>
> Ah, good point. Can you file this as an issue in the issue
> tracker.

https://hudson.dev.java.net/issues/show_bug.cgi?id=654

>
> > - Consider renaming the javadoc/ URI to web/ or something like this. In
> > one project I misuse the javadoc/ feature to populate my jnlp project,
> > which works fine, but the javadoc/ in the URL is confusing. Furthermore
> > projects that use maven may want to use this feature to populate their
> > project documentation.
>
> If the URL (and more importantly the link to URL) doesn't say "javadoc",
> people will not find it very intuitive. For things like you are
> describing, we should really have plugins.
>
> A plugin that publishes a jnlp file (and by parsing the jnlp file, it
> can automatically discover all the jars, too, right?) and display the
> JNLP launch icon sounds like very useful. The ditto for the publishing
> of maven site. Again, it would be great if you can file them as issues.
>
> I guess the problem that prevents people from writing plugins is that
> it's still too hard. If we can make simple plugins really simple, or
> perhaps come up with a way to do a parametric plugin so that all
> JjavadocArchiver-like plugins can be created with a single description
> file or something, that could be very useful.

Hi,

why do you want to create a special plugin for each case when a rename is adequate? And having the folder named web/ for the webresources of a project is ok, imho.
Normally a project only want to populate one thing (javadoc, maven doc, doxygen, jnlp, webroot). In the rare case that there are more things, the user can simply create subfolders for these inside a populated folder. Having a plugin for every use-case where the result is the same is unneeded work.

btw, i filed a bug for these, proposing my idea under https://hudson.dev.java.net/issues/show_bug.cgi?id=653

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AW: Re: Small feedback on Hudson

Kohsuke Kawaguchi
Administrator
[hidden email] wrote:
> why do you want to create a special plugin for each case when a rename
> is adequate? And having the folder named web/ for the webresources of a
> project is ok, imho.
 >
> Normally a project only want to populate one thing (javadoc, maven doc,
> doxygen, jnlp, webroot). In the rare case that there are more things,
> the user can simply create subfolders for these inside a populated
> folder. Having a plugin for every use-case where the result is the same
> is unneeded work.

The main problem with having something very generic like "web/" is that
it's unintuitive for users visiting Hudson web pages. There's a lot of
difference in the link titled "javadoc" vs the link titled "web contents".

I guess there should be some middle ground. Perhaps Hudson could be
smart enough to figure out by itself what's being archived. For example,
javadoc files have a fairly distinct file structure (and ditto for maven
docs), so maybe Hudson could still provide intuitive labeling and icons
even though the configuration screen could phrase things in a bit more
general fashion. The recognizer could be also made extensible to allow
implementations by plugin.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

AW: Re: AW: Re: Small feedback on Hudson

Stephan Zeissler (KUTTIG)
Isn't the laberling already dynamic? In my JNLP Project the Javadoc link is labeled "Document", in the project with a real Javadoc folder, the link is called "Javadoc".

Regards,
Stephan Zeissler

-----Originalnachricht-----
Von Kohsuke Kawaguchi <[hidden email]>
Gesendet Mo 23.07.2007 07:45
An [hidden email]
Betreff Re: AW: Re: Small feedback on Hudson

[hidden email] wrote:
> why do you want to create a special plugin for each case when a rename
> is adequate? And having the folder named web/ for the webresources of a
> project is ok, imho.
 >
> Normally a project only want to populate one thing (javadoc, maven doc,
> doxygen, jnlp, webroot). In the rare case that there are more things,
> the user can simply create subfolders for these inside a populated
> folder. Having a plugin for every use-case where the result is the same
> is unneeded work.

The main problem with having something very generic like "web/" is that
it's unintuitive for users visiting Hudson web pages. There's a lot of
difference in the link titled "javadoc" vs the link titled "web contents".

I guess there should be some middle ground. Perhaps Hudson could be
smart enough to figure out by itself what's being archived. For example,
javadoc files have a fairly distinct file structure (and ditto for maven
docs), so maybe Hudson could still provide intuitive labeling and icons
even though the configuration screen could phrase things in a bit more
general fashion. The recognizer could be also made extensible to allow
implementations by plugin.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AW: Re: AW: Re: Small feedback on Hudson

Kohsuke Kawaguchi
Administrator
Stephan Zeissler (KUTTIG) wrote:
> Isn't the laberling already dynamic? In my JNLP Project the Javadoc link
> is labeled "Document", in the project with a real Javadoc folder, the
> link is called "Javadoc".

I completely forgot about that, but you are right. I have apparently
already implemented some of what I'm just proposing.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment