On Wed, Mar 2, 2011 at 6:46 PM, Niklas Gustavsson wrote:
> I'm in the process of upgrading Hudson to Jenkins 1.399 which turned
> out a bit more involved than expected. So, be prepared for some
> restarts the next couple of hours.
And we're done. Let us know here if you see anything odd. We're no
YAY! Thanks Niklas!
Uli
On 02.03.2011 18:46, Niklas Gustavsson wrote:
> Hi
>
> I'm in the process of upgrading Hudson to Jenkins 1.399 which turned
> out a bit more involved than expected. So, be prepared for some
> restarts the next couple of hours.
>
> /niklas
Hi
I'm in the process of upgrading Hudson to Jenkins 1.399 which turned
out a bit more involved than expected. So, be prepared for some
restarts the next couple of hours.
/niklas
On 3/2/2011 9:04 AM, Niklas Gustavsson wrote:
> On Wed, Mar 2, 2011 at 2:32 PM, Scott O'Bryan wrote:
>> You might be right about he "safety" issue but trying to enforce this
>> all the time across all projects is not real feasible. I don't think
>> the plugin would hurt in either case and it pr
On Wed, Mar 2, 2011 at 2:32 PM, Scott O'Bryan wrote:
> You might be right about he "safety" issue but trying to enforce this
> all the time across all projects is not real feasible. I don't think
> the plugin would hurt in either case and it prevents releases from
> getting accidentally uploaded
You might be right about he "safety" issue but trying to enforce this
all the time across all projects is not real feasible. I don't think
the plugin would hurt in either case and it prevents releases from
getting accidentally uploaded to the snapshot repository.
Scott
On Mar 2, 2011, at 6:26 AM
On 2 March 2011 10:27, Marshall Schor wrote:
> If we check the box in a Job configuration that says "Deploy artifacts to the
> Maven Repository" and specify the Apache Nexus Snapshot repo, what happens if
> a
> build starts right at the moment when the Apache Release plugin has renamed
> the
> P
On Wed, Mar 2, 2011 at 11:17 AM, Marshall Schor wrote:
> Is this a known issue with Hudson? or can it be configured to work in a
> case-insensitive manner?
Known issue: http://issues.jenkins-ci.org/browse/JENKINS-850
/niklas
If we check the box in a Job configuration that says "Deploy artifacts to the
Maven Repository" and specify the Apache Nexus Snapshot repo, what happens if a
build starts right at the moment when the Apache Release plugin has renamed the
POMs to a non-Snapshot release version and checked those into
On the main GUI page for hudson, https://hudson.apache.org/hudson, there is a a
search field at the top, apparently intended for searching for configured Jobs
by name.
Users are conditioned by the behavior of most search engines to expect this to
work in a case-insensitive manner, but the one in H
on the page https://hudson.apache.org/hudson, in the main panel it shows all the
jobs configured on Hudson. At the top of this, is a set of tabs:
A-F, All, G-L, M-R, S-Z, and "+".
The "All" is selected.
When users are hunting for jobs for the first time, they push one of these tabs,
such as the
11 matches
Mail list logo