librelist archives

« back to archive

Java.net migration fun

Java.net migration fun

From:
Andrew Bayer
Date:
2010-11-14 @ 22:00
So the java.net migration seems to have started earlier than expected -
they've already started transitioning users, etc. This seems to have caused
problems with some people's JRIA logins, as well as the Maven repo/update
center problems. We thought we'd have another 6 weeks or so to handle
migrating off java.net, but looks like we need to get things done faster.
Kohsuke and I worked out the beginnings of a migration plan - moving source
to Github (we're meeting with Github this Friday to talk about the
logistics, recommended organization structure, etc), mailing lists to Google
Groups, using our own Maven repo, and using our own LDAP server for
authentication for JIRA and the Maven repo. From what I can tell, we should
probably continue using Crowd in front of LDAP for JIRA - the issues with
group membership not showing up right away for new users seems to be a
configuration problem, not inherent Crowd behavior. I'm not entirely sure
how user signup works in this setup - I'd hope that users could sign up at
JIRA and get accounts created in LDAP. That certainly seems like how it
should work.

Anyway - we need to get rolling on all this fairly quickly, given the
problems that are already showing up, so I wanted to make sure we were all
talking about this.

A.

Re: [hudson.infra] Java.net migration fun

From:
Kohsuke Kawaguchi
Date:
2010-11-16 @ 02:14
On 11/14/2010 02:00 PM, Andrew Bayer wrote:
> So the java.net migration seems to have started earlier than expected -
> they've already started transitioning users, etc. This seems to have caused
> problems with some people's JRIA logins, as well as the Maven repo/update
> center problems. We thought we'd have another 6 weeks or so to handle
> migrating off java.net, but looks like we need to get things done faster.

Right.

> Kohsuke and I worked out the beginnings of a migration plan - moving source
> to Github (we're meeting with Github this Friday to talk about the
> logistics, recommended organization structure, etc), mailing lists to Google
> Groups, using our own Maven repo, and using our own LDAP server for
> authentication for JIRA and the Maven repo. From what I can tell, we should
> probably continue using Crowd in front of LDAP for JIRA - the issues with
> group membership not showing up right away for new users seems to be a
> configuration problem, not inherent Crowd behavior.

A later conversation with Andrew revealed that the delay is still there 
for all the applications except where the user was created.

 > I'm not entirely sure
> how user signup works in this setup - I'd hope that users could sign up at
> JIRA and get accounts created in LDAP. That certainly seems like how it
> should work.
>
> Anyway - we need to get rolling on all this fairly quickly, given the
> problems that are already showing up, so I wanted to make sure we were all
> talking about this.

+1. Let's do a bit more experiments to verify the feasibility and other 
details.

For example, I was playing with Google Groups and it doesn't look like 
we can import the past e-mail logs as archives (at least in a way that 
saves the timestamp.)


-- 
Kohsuke Kawaguchi | InfraDNA, Inc. | http://infradna.com/