Improvement feedback: Renaming job should allow build number reset

[James Lorenzen]

I recently came across a new use case when renaming a job and I created a Jira improvement HUDSON-6694 to accomodate this use case.

According to @dty, this rename page doesn't support plugins so it would have to be a modification to core. Is this correct?

More importantly, before coding this improvement, I'd like to know if it's something that would be accepted and incorporated into hudson? I really don't want to spend the time learning hudson and making this change if the improvement isn't seen as valuable or useful.

[Sean McAfee-2]

James Lorenzen wrote:

> I recently came across a new use case when renaming a job and I created a
> Jira improvement  http://issues.hudson-ci.org/browse/HUDSON-6694 HUDSON-6694
> to accomodate this use case.
>
> According to @dty, this rename page doesn't support plugins so it would have
> to be a modification to core. Is this correct?
>
> More importantly, before coding this improvement, I'd like to know if it's
> something that would be accepted and incorporated into hudson? I really
> don't want to spend the time learning hudson and making this change if the
> improvement isn't seen as valuable or useful.

The checkbox would be nice, but if a configurable refresh interval can
be rejected in the name of UI simplicity, this might be as well.

I've had this same problem, but got around it by copying it to the new
name, then deleting the old job.

--
Sean McAfee
Senior Systems Engineer


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

[James Lorenzen]

Thanks Sean,
Yeah I read somewhere that UI simplicity is a high priority (which I admire) and one of the reasons I am asking before coding.

Fortunately, the rename job page is already pretty lite (only a single text box for the new job name), so adding another checkbox shouldn't confuse users. But I can see where this feature is not used a ton.

Like you said, the work around is copy/delete, which works, but probably not as convenient as providing a reset checkbox.

Is there anyone who can "approve" this change before I proceed? Or how hard would it be to make that page support plugins?

[Kohsuke Kawaguchi]

I can certainly add an extension point to allow plugins to contribute
additional UIs to the rename page, and give those extensions pre/post
notifications to enable additional processing.

I'm not sure what's the justification of tying the build number
resetting to a renaming though. To me, they sounded like two entirely
orthogonal operations. I also assume that resetting the number implies
deleting build records. Is that so?

So I wonder if it's better off as a plugin that allows you to reset
the build number (by deleting the builds whose numbers are bigger than
the new value) --- IIRC, there's already a plugin for setting the
build number to a bigger value, so this could be a good enhancement to
that.

2010/6/25 James Lorenzen <[hidden email]>:

>
> Thanks Sean,
> Yeah I read somewhere that UI simplicity is a high priority (which I admire)
> and one of the reasons I am asking before coding.
>
> Fortunately, the rename job page is already pretty lite (only a single text
> box for the new job name), so adding another checkbox shouldn't confuse
> users. But I can see where this feature is not used a ton.
>
> Like you said, the work around is copy/delete, which works, but probably not
> as convenient as providing a reset checkbox.
>
> Is there anyone who can "approve" this change before I proceed? Or how hard
> would it be to make that page support plugins?
> --
> View this message in context: http://hudson.361315.n4.nabble.com/Improvement-feedback-Renaming-job-should-allow-build-number-reset-tp2268467p2268509.html
> Sent from the Hudson dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi

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