An upgrade to Bamboo will occur at the listed time.

This is to deal with some severe memory leak issues we’re facing.

Fisheye will be upgraded to 1.5.1 this evening.

We’re on a collision course with running out of space on codehaus03 (the grunty server with all your artifacts).

To that end, we will be pruning SNAPSHOT distribution and SNAPSHOT repositories over the weekend.

This pruning will progressively remove older artifacts until we have appropriate breathing space.

Please contact us if you have any questions / concerns.

We are aware of the Bamboo instability under the new strain of new users.

We’re working with Atlassian to get the bugs fixed and a new version deployed, but it will be a week or two.

Codehaus is mostly excited to now offer integrated continuous integration services.

This service is provided by a Contegix managed server in our core network.

There are several things that still remain to be improved, but you are free to start making requests in JIRA for assistance setting up plans etc.

Please subscribe to discuss@codehaus.org if you wish to discuss new capabilities / requirements from CI (e.g. pushing snapshot artifacts across to the distribution / repository servers)

The new server for continuous integration has been built.

We will be loading the required software (Bamboo and Hudson) onto it over the next few days.

Bamboo is loaded, however needs quite a bit of tweaking to build properly

We will be addressing the Bamboo configuration over next 2 days

We have a new CI server being provisioned. Stay tuned for more news!

Bamboo (cheddar.codehaus.org) is offline.

(Background: Continuous Integration was not a core offering for a long time. As such we left it on a non-Contegix machine. We were getting closer to bringing it inside Contegix, but did not currently have funding for that. This is the risk of using donated hardware in unknown datacentres.)

UPDATE The machine hosting Bamboo was taken offline as part of datacentre maintenance. It will be brought back online to transfer the data, but will not be offering build services.

Continuous Integration services will be hosted within Contegix once we acquire appropriate funding for it.

Please contact support@codehaus.org if you wish to sponsor CI services.

Bamboo (cheddar.codehaus.org) is offline.

We have no ETA on it coming back online, or what state it will be in when it gets back

(Background: Continuous Integration was not a core offering for a long time. As such we left it on a non-Contegix machine. We were getting closer to bringing it inside Contegix, but did not currently have funding for that. This is the risk of using donated hardware in unknown datacentres.)

codehaus01 is getting a RAM upgrade to help cope with all the code you irresponsible people keep committing (JIRA and FishEye are straining!)

Should only be a 30 minute outage.

Unless they get Captain Static to install it…

March is being taken down for an upgrade of the PostgreSQL database that it runs on.

Best and most likely return is 5am.

The exact return time is unpredictable due to the large amount of data being migrated.

In the meantime; use http://codehaus.markmail.org/ for most of your mail archive needs!

Xircles is being taken down for an upgrade of the PostgreSQL database that it runs on.

Best and most likely return is 2am.

JIRA will be upgraded to 3.12.2 to fix some glitches in the behaviour with Safari and keep us up-to-date with the latest version.

yWorks has graciously updated our license for yDoc to version 3.0.

We hope it comes in handy for some of your projects!

FishEye will be upgraded to the latest version to get us ready for reporting some stability problems we’re having (or potentially fix them)

We will be upgrading Bamboo to correct some memory leaks and outages we’ve been experiencing.

(If anyone wants to sponsor a Contegix server for continuous integration services and make it part of our core infrastructure, then please raise your hand to support@codehaus.org!)

We also have some changes in the pipeline to allow publishing of artifacts into the project snapshot repository etc.

UPDATE The upgrade is still in progress, we’re moving to 2.0 beta 4 as it corrects some memory leaks we’re experiencing.

Unfortunately the XML export is broken in 1.2.4 and data cleanup is required.

UPDATE

After a lot of painful search and replace to fix an XML error; the import loaded. Bamboo is now “running”.

We’re having a few integration issues between Unity and Confluence (the new version).

Problems we’ve seen:

• stack traces being displayed to user
• pages not refreshing
• pages not updating after being changed

Should have it all sorted out very soon.

UPDATE: All sorted

For some reason the system switched back to the Resin XML parser that doesn’t work the way we need it to. Now fixed.

UPDATE: All sorted now!

Ok, there were a few more glitches due to an upgrade of some java libraries as well. These are also fixed now.

In order to combat a rise of spam with invalid email addresses (you’d think they’d at least get that right!); we’ve instituted additional email validation rules.

Some of these rules may be against the RFC, however we’ve checked that all seemingly valid addresses in our system can still be used.

If you experience difficulties, please contact us at support@codehaus.org

As some of you are aware, we’ve started indexing lists into MarkMail.

While Xircles doesn’t currently point users across at the MarkMail archives, this will occur in the near future.

You can search the > 400K Codehaus mails from one convenient interface at http://codehaus.markmail.org/

There will be a Confluence outage from

February 16, 2008 1 AM CST to February 16, 2008 4 AM

We will be upgrading Confluence to the latest version; we do not expect the outage to take that long; but want breathing space to iron out issues.

This outage will also affect Unity powered sites (we’re currently upgrading Unity to better cope with a Confluence outage)

For those amongst you who are concerned by Confluence slowness / outages…

Atlassian are now on the job and they’re reviewing our instance and suggesting configuration changes to make Confluence perform more reliably.

Some of you have noticed that you are getting list moderation messages.

This is caused by you being a moderator for that list; some default logic made everyone a moderator by default!

This has since been corrected and we’re removing user moderator status flags from EZMLM.

You will stop receiving erroneous moderator messages once this has taken effect.

As many of you have noticed (and pointed out to us!); Confluence is very temperamental.

We’ve narrowed this down to “something” in Resin (our J2EE server).

We’ve also prodded Contegix into changing how Confluence is monitored so it can detect stalls (which it previously ignored some of the time).

Hopefully this will mean that there are less stalls (you might notice more breakages though as the server is bounced).

We are still working on making Confluence reliable however.

Contegix will be applying upgrades to all Codehaus servers.

All services will be interrupted for the duration of the outage.

February 05, 2008 0300-0500 CDT (GMT-0600)

New license for IntelliJ has been made available now.

Login and view:

http://xircles.codehaus.org/my/licenses/view/8

We are waiting on JetBrains to send us a new licence.

You do not need to remind us that it will expire on the 11th.

UPDATE We have discovered an additional hurdle; and hurdled it. The license should be available soon.

Bamboo will be upgraded from 1.2.3 to 1.2.4 as part of our application maintenance plan.

SUCCESSFUL

We are attempting the upgrade to JIRA 3.11 again.

This upgrade was successful

We are now running JIRA 3.11 using the FishEye plugin.

Please report any issues; as we are unable to comprehensively test every piece of functionality without our trusty users!

We’ve ditched the Subversion in favour of the JIRA-Fisheye plugin (at the recommendation of Atlassian).

This should let us perform our Jira 3.11 upgrade successfully (as the Subversion plugin was the cause of the previous failures).

We’re going to do an upgrade of JIRA to 3.10 to fix some Xircles integration problems that have appeared.

Scheduled for 1am-2am CDT (-0500) 13 Oct 2007.

Codehaus services will be temporarily interrupted during between 03:30 and 05:00 CDT Monday, Oct 8th for RedHat security upgrades.

This is a routine upgrade and we do not expect any extended outages.

We will be upgrading to JIRA 3.10 at 3am CDT 29th Sep 2007.

This will require a 1 hour outage window for JIRA (3am – 4am).

No other services will be affected

Codehaus has been granted a sitewide licence for Install4J for use with opensource projects hosted at Codehaus.

You can get the licence at http://xircles.codehaus.org/my/licenses/view/6

Due to some spam problems (from authenticated users) we’ve enabled CAPTCHA on the docs.codehaus.org Confluence site.

Since CAPTCHA is incredibly annoying for regular users; you can disable it by visiting http://xircles.codehaus.org/captcha

If you’re a Xircles user, then your account is already flagged for No-CAPTCHA. Praise be to Xircles!

There’s a lot of dead projects at the Haus; or so it would seem from their metadata.

Please take the two minutes it takes to update the information about your project (labels; short descriptions etc).

Upload logos if you have them.

We will be hiding projects that don’t have a minimum metadata describing them; if you don’t care about your project; then neither do we.

Old-school Haus users should also fill in their name properly, lest you find your commit privileges conspicuously non-functional.

Date: 01 September 2007 Time: 0400 CDT (UTC-0500) Duration: 4 hours

We will be migrating all Subversion repositories to another server; this should be a relatively transparent operation if you are using the URLs as provided by Xircles.

The result should be

• much better FishEye performance
• much better Subversion performance (whether this will be noticed over https is another thing)
• generally better responsiveness from most other services.

If you have any concerns / queries, please contact us.

THIS MIGRATION WAS SUCCESSFULLY COMPLETED

Due to infrastructural changes within Codehaus to improve performance; we will be disabling SVN+SSH access to the repositories.

This will occur at Thursday 30 August 2007; 4am CDT (UTC+0700)

Active users of this method have been emailed; but for all other this will be your notification.

To relocate your working copy:

(in your working copy) svn info | grep URL

1. which becomes https://svn.codehaus.org/[path]

1. will return something like
2. URL: svn+ssh://svn.[project].codehaus.org/[path]

svn switch --relocate \
svn+ssh://svn.[project].codehaus.org/[path] \
https://svn.codehaus.org/[path]

svn info | grep URL

1. will then return something like
2. URL: https://svn.codehaus.org/[path]

LDAP is being taken down NOW for an emergency repair.

There seems to be some internal corruption of the LDAP directory due to an unplanned outage earlier this week.

System affected: SVN, WebDAV, Authenticated FishEye

Worse case recovery scenario – we rebuild the directory from the Xircles database; no data will be lost.

You may have received notifications that issues were being deleted from JIRA.

This was due to “someone” deleting projects from a test system with the notifications enabled. We had no idea that notifications would be sent when deleting a project.

There is NO impact to your projects (apart from a bit of spam).

Sorry for the confusion.

Two pieces of news:

• We’ve upgraded Bamboo to v1.2.1
• We’ve upgraded the default Maven 2 on the CI server to Maven 2.0.7

The major feature with this release (that we care about) is the ability to delegate administrative tasks.

So if you use Bamboo, and you want to be able to manage your project, shoot us a support request and we’ll get it sorted. (Xircles is not Bamboo aware… yet)

If you were set to a specific version of Maven 2 on the build server, then this has not changed. If you were set to the generic Maven 2.0; then you have automatically been upgraded to 2.0.7

You might have noticed you can select favorite projects (and lists) now. Once you’re logged in, just click on the favorite star.

We’re still toying around with this functionality, so feel free to drop us an email (support@codehaus.org) with any suggestions.

We’ve got great news that every one will be super excited about!!

You can now create dodgy email addresses with addresses like super+excitedgmail.com if your email address is supergmail.com

While you do still have to verify each address, this is for the convenience of our lazy coding monkey who doesn’t have any great desire to parse your verified addresses and permit +suffix style changes.

Ok, it’s not even remotely exciting.

(Why didn’t it work in the first place? Apache doesn’t escape URLs as it passes them back to Mongrel. We changed the URL so the address was no longer included, thus bypassing this issue)

In order to offer better performance and reduce the immense thrashing on our poor codehaus03 server, we’re going to be moving Subversion repositories from codehaus03 to codehaus01 (our new ‘grunty’ box).

In the short to medium term this also means that svn+ssh will no longer be offered due to the extra complexity of provisioning ssh accounts on multiple servers.

To this end, we recommend all users switch to using https to access their subversion repositories.

This is just an advance warning, there will be further notices provided ahead of this change-over.

There will be short interruptions to service as RedHat security patches are applied to the 3 primary servers.

All service should return to normal at the completion of these updates.

Start:  June 16, 2007 03:00 AM CDT
End:  June 16, 2007 06:00 AM CDT

There will be an outage at 12:01am – 1:01am 24th June 2007 (CDT) for an upgrade of Confluence.

We’ve had some excessive slowness creating new issues in JIRA.

Contegix is working on it and have escalated it to Atlassian for rectification.

They may potentially require an upgrade to JIRA 3.9

1am-3am CDT – Wednesday 16th May 2007

Sorry for the inconveniece.

We lost a disk on codehaus03 (this is the machine that does everything but Confluence and JIRA)

Of all the machines that can lose a disk – this isn’t the one. It’s running under massive load 24×7 and has no spare capacity.

Contegix discovered it, replaced the drive and rebuilt the array while Bob was off drinking beer at JavaOne. Praise be to Contegix.

The side effect was that the machine went into even higher load level, slowed down further and we ended up with 6000 mail messages in the queue. At that point, some spammers thought sending us a few 1000 emails would be helpful; it wasn’t.

This is why your emails were getting delayed

This is now 90% cleared, and things are returning to normal.

Any problems; contact support at codehaus.org.

Thank you for your patience. We’ve lived through how this could have gone (1 year ago…) – this is a much better scenario.

Yes, our SSL certificate is expired. Yes, we are renewing it.

It should be done in a day or two depending on how annoying the provider is.

You were clicking through the warnings anyway…

Update The new certificate is now in place on all servers.

We are making some (theoretically transparent) changes to the permission schemes on jira.codehaus.org

You should not notice any significant differences to project permissions; however it’s a manual process so mistakes happen. Some users will gain extra privileges, but these are inline with the Codehaus standard set; so should not put your project at risk.

If you notice any aberrant behaviour, please contact us at support@codehaus.org

(We’re rationalising permission schemes so our automated tools work correctly; this involves updating each project that is on a custom permission scheme and correctly configuring it)

There are many users who do not have email forwarding configured and do not download their email via POP.

Your email boxes are overflowing (some users have upwards of 20000 emails stored on the Codehaus servers)!

To improve performance (backup times mainly), we will start pruning all emails over 30 days old.

(This has nothing to do with project mailing lists)

There will be a JIRA upgrade and server migration at 0200 CDT Sat April 7th.

The outage will run up to 4 hours; but we’re hoping it will be shorter than that.

As… always… support@codehaus.org for any concerns.

We’re switching from the old snippet plugin up to the Atlassian semi-supported plugin.

The new plugin is a lot smarter – it has configuration to block XSS attacks. However depending on how we configure it, it will break existing snippets.

We’re initially configuring it in a relatively lenient mode. However will review the use of snippets later this week.

Contact support with any issues.

Codehaus is now accepting applications for Google Summer of Code 2007

See our Summer of Code site

The mail archives (archives.codehaus.org) are not indexing new emails to the lists.

We are looking into it and should have it resolved in the next 24 hours.

No emails have been lost, all will be indexed when we bring it back to life.

UPDATE The mail archive has been fixed and is now processing missing emails. Over the next hour or so it will catch up with incoming mails.

Thank you for your patience!

All Codehaus servers will be having security upgrades that wlll require reboots over the next few days.

We could find out exactly when they were going to happen, but most people don’t care.

Suffice to say we’re expecting a maximum of 30 minutes outage on each server during the upgrade.

“cheddar” – the continuous integration machine (Bamboo / Continuum) is moving datacentres. Apparently Brett kicked it with his foot one too many time.

The outage is scheduled for February 25th Sunday 12 am PST, and it could be down for up to 36 hours.

As always – support@codehaus.org

UPDATE It’s still not back. We’re waiting on Simula to let us know when it will be. It is probable that they didn’t update the DNS after the move.

UPDATE They had updated the DNS, but the TTLs were set to 1 day – hence we didn’t see the upgrades in a timely manner. All sorted now.

Now that JIRA is fixed (after a dodgy RPC call!); we’ve started updating all your projects to use Project Roles.

The security changes should be seamless, unless you had some weird config I didn’t notice when I was porting you over.

Notifications – you should now start receiving notifications on your dev list.

This is a gradual migration, I aim to complete it over the next day or two as patience permits.

Contact support@codehaus.org with any issues.

JIRA is still broken, we’ve still got duplicate user ids in there (YAY DB integrity!).

Atlassian has a ticket, it’s open, we’ve sent them a db dump, and they’re awake in Sydney again.

So we should be expecting it fixed in the next 2 hours or so.

UPDATE Atlassian have provided us with the fix and it has been applied. Everything should be back to normal.

As we have no way of contacting users without email addresses set, we’re going to disable those accounts (soonishly) to get their attention.

There are currently 86 users in this state.

They can avoid this situation by setting an email address in Xircles.

If you’re checking your email via POP, (i.e. that means you Mr Topping), then we’re letting you off this round.

You should also set your JIRA / Confluence user IDs in Xircles as you will possibly lose access to Jira / Confluence under the permission rework we’re about to undertake soon.

As always – support@codehaus.org

JIRA is currently broken due to some unspecified problem.

We have a support call in with Atlassian and they will hopefully resolve it in the next few hours.

UPDATE Nothing has happened.

GSoC is ramping up again. We’re really going to try and run it a bit better this year. Honest.

See the Codehaus GSoC project for more information.

We’ve started pruning back the number of JIRA administrators now that Xircles manages users and groups in JIRA.

The eventual state will have JIRA fully managed by Xircles with no need for Administrators.

If you believe you need administrator privileges, send an email to ops@codehaus.org stating your rationale.

UPDATE If your initiais are V and M (either order) then you need not fear that we will steal your powers immediately!

Upgrading Rails has had a deleterious effect on some of the other applications on the same server (march / foci – which are mail archives and stats respectively).

We’ll be bringing these back online over the next few days and indexing in the data that was lost in the interim.

UPDATE We’ve brought the archives back online, however Rails 1.2 and March don’t like each other very much. March occasionally eats all our memory on the box.

Contegix will monitor and potentially take down the instance until we have time to resolve the problems.

We’re doing a major upgrade of Xircles (mainly at the Rails level – 1.2 (god what a painful upgrade that was!), and also some usability updates).

We’ll be taking email subscription offline (it will queue requests) for a period of time, as well as the Xircles web interface.

All other services will continue to operate normally.

The outage will commence at 2300 UTC, 30 Jan 2007. For 1 hour (barring any major problems).

Please report any weirdness to ops@codehaus.org

UPDATE The upgrade is complete. There are some minor problems left over, but these will be resolved over the next few days.

You may notice that older artifacts on the dist site (dist.codehaus.org) are now redirecting to ibiblio.

This has been done to lower the load on the Codehaus boxes and reduce the amount of bandwidth we’re using (up in the terabytes/month – spikes of 25.5M/second).

Contegix has been very supportive of our growth, but now we have to lessen the traffic usage or face increased costs in the near future.

This may impact older Maven clients. If this is a huge impact, we might be able to permit direct access if they have identifiable User-Agents set. Otherwise… tough…

Only artifacts older than 24 hours will redirect to the ibiblio mirrors. So if you put new files out there, they will not redirect until ibiblio has had an opportunity to synchronise them.

UPDATE

dist mirroring has been disabled due to ibiblio being out of date. repository.codehaus.org mirroring has been enabled.

UPDATE

This all broke Maven 2 somehow. So we’ve disabled it.

In the near future we’ll be teaming up with ibiblio to offer mirroring of just Codehaus distributions.

You can now request the creation of a new project at Codehaus (or any Xircles powered community!) using the Project Request feature.

This feature can be accessed at /projrequests/ and lets you fill in the relevant details about your project.

Once we’ve had a look at it, we will either approve or deny your request.

An approved project is automatically created and you are assigned privileges (if you were logged in when you request the project). Otherwise you’ll need to create an account and then email ops@codehaus.org

UPDATE You will need to have a registered mail session or user account to raise project requests. The spammers managed to start filling in project requests within 2 days of us adding the functionality.

By popular demand we now have a new licence for IntelliJ IDEA.

http://xircles.codehaus.org/my/licenses/view/4

If you’ve been having problems accessing our SVN sites using the SVN protocol, fear not, we’ve got it under control.

We were under an accidental “denial of service” attack from a party who shall rename nameless.

We’ve increase the maximum rate of SVN connections, and blocked the party in question until they sort things out at their end.

So, those “connection closed” should be a thing of the past.

We’re currently trialling Bamboo (Atlassian’s new CI product).

It’s derived from Beetlejuice – the build tool we were previously using, but adds some of the security options that we need at the Haus.

You can see our test install at http://bamboo.ci.codehaus.org/

Create an account (use your Xircles username or I will stab thee in the eye with a sharpened chicken leg).

You will need to send ops@codehaus.org details of your project as there’s no way to delegate authority to do project administration.

We’re scheduling in major Jira / Confluence upgrades over the Christmas period.

While we’re still determining the exact time of the upgrades, it is expected to be early AM (CDT) and will disrupt the applications, and in the case of Confluence – the websites.

The aim is to upgrade our rendering software so that future Confluence upgrades do not affect website availability; however this is unlikely to be in place by next week.

All comments / concerns to ops@codehaus.org

We have enabled Spamhaus SBL+XBL DNS blocking on our mail servers.

If this is causing you angst, then let us know – ops@codehaus.org

(>50% of our email comes from hosts that are arguably bad)

(This is now actually enabled, there were no complaints about the theoretical implementation, now lets see if there are complaints about the actual implementation!)

It is now possible for you to rsync your SVN repository backup (you are not able to rsync your live repository for safety reasons).

Please restrict rsyncs to once per day (that’s the frequency of our backups in any event).

Also, we recommend not taking backups between 0000-0200 (GMT) as that is when the SVN backups occurs and we can not guarantee transactional consistency.

Only Codehaus users may take backups.

Use a command like

rsync -vr [project].codehaus.org:/projects/[project]/repo/

See your project rsync page for more information about rsync and the limitations we have imposed.

Due to load issues on codehaus03 (the main server); we’ve had to disable awstats processing on all domains.

Basically it was pushing the backup times out over 24 hours and compromising the recoverability of that server – not something we want.

We’re working on a replacement for awstats / fixing awstats processing in the interim.

You may have noticed that some issues in JIRA have been smashed with trackback spam (some issues have 9000 trackbacks).

We’ve disabled trackbacks; and will be cleaning out the spam in the next few days.

We’ll have to wait and see if Atlassian has a solution around allowing some trackbacks but not all.

If you’re running on Unity (the Confluence renderer); you can now use a new template.

As opposed to multiflex blue (half-baked at best), the new template actually works.

You can select the template “Codehaus Green Experimental” from your project settings.

See an example at http://codehaus.org/

(Internet Explorer rendering is a little bit off at the moment – if you know why let us know (ops@codehaus.org) – otherwise you’ll have to wait until we stumble onto it)

In order to curb the flow of spam, Contegix is making some changes to our mail servers.

This will take place starting at 12:01am CDT on Sunday 8th October, for 5 hours (or less).

The MX records will be adjusted to queue email on a backup server during the outage.

We’re currently receiving a huge quantity of random spam. Contegix are on the job and are looking into stemming the tide, but at present it’s interfering with normal mail delivery.

While 99% of it is not delivering, it takes time to process each message. 27000 in the local queue, 23000 in the inbound queue (and rising).

This is the reason that emails are not coming through on your lists.

This post will be updated when the end is in sight.

Update: The spam is clearing and we expect things to return to normal around 9am CDT (+4 hours from now).

If you’re a keen user of Xircles you might have noticed that we now have links to mail archives for each project list.

These can be reached via codehaus archive or project archive

Note that these archives are experimental; at this stage, we’re not interested in bug reports about:

• a lack of history for some projects (we’re loading them soon!)
• poor performance
• bad rendering of messages / general L&F problems (except for radical problems in fringe browsers like IE)

We are interested in bug reports about

• bad links
• new messages not appearing in the archive

Enjoy!

All feedback welcome as usual.

We’ve finished implementing the first round of support for project contributors – users who are not part of your core development team, but have varied items that are of value for the use and development of your product.

Contributors are able to write to a special -contrib repository and are able to perform updates to the Confluence site.

You simply need to enable your project for contribution in Project Settings, and then prod one of us on IRC to restart Apache / FishEye to pick up the new SVN repository settings – it’s still too risky to automate this stage.

We’ll also need to reset some Confluence permissions in certain cases to support the new groups, but that’s easily done by our scripts if you let us know. We’re not rolling this out haus wide as yet because it may cause problems with non-standard space configurations.

Once the project has contribution enabled, new users will be able to signup and apply to become contributors. Details can be found in Xircles.

As always, contact us with any issues.

Project despots – please see Project Contributors .

Please supply feedback as page comments.

At the request of the maven project, we’ve taken snapshots.maven.codehaus.org offline

Apparently you shouldn’t have been using it anyway – this just makes sure of that!

For concerns, issues and any other problems regarding this, try asking for help on #maven (irc://irc.codehaus.org/#maven)

Update: snapshots.maven.codehaus.org was actually required; it now redirects to snapshots.repository.codehaus.org

We’ve wound back the number of Confluence administrators. With the automated group management there should be less requirement for administrators within the system.

If you’ve got some particularly desperate need for administrator rights, contact us and we will consider how to resolve this most appropriately.

Thanks to some debugging from Holger, rsync support should be functioning a lot better now.

This means that you can transfer your project sites far more quickly than ever before (faster even than WebDAV!!!!).

Grab the rsync connection details from Xircles.

Technical Details:

Internally we intercept your rsync ssh requests and check all the arguments to ensure they are valid and safe. We also rewrite the target paths so that we can internally change the filesystem locations.

The side-effect of all this rewriting is that you should only use the basic options for rsync (we support quite a large subset of the options). If you get rsync protocol errors, try again with less options or contact us for support.

We’ve just added support to Xircles to allow user membership changes to propagate into Confluence.

For the most part this is transparent to projects – it just works.

Technical Details:

Users added to <project>-developers will be added to the Confluence group <project>-developers; likewise for despots.

New spaces in Confluence will be configured with a new set of permissions that differentiate between despots, developers (and soon – editors).

Users will only be synchronised with Confluence during a membership change, when they’ve set their Confluence username in their user settings in Xircles. Hence, users should set their Confluence username and then leave / join the project with the help of their project despots.

As always, contact us if there are any issues with this or any other functionality.

Our Movable Type trackback script is currently being hit by a massive botnet attack.

As such we’ve had to disable it before it brought down further services on codehaus03 (confluence, svn, fisheye, mail, xircles).

We’re investigating several solutions, and will be implementing a solution in the next few days.

A Confluence upgrade is underway, starting roughly

11pm Saturday 22 July 2006, US Eastern

And possibly running until

11pm Sunday 23 July 2006, US Eastern

We will attempt to keep the downtime as short as possible, but due to the size of our Confluence, and following best upgrade practices, it may be the full 24 hours.

Project sites that use Unity for presentation of Confluence content will be offline while Confluence is offline. All other services are presumed to be working as well as they ever do.

Update

Well, the upgrade did not succeed. We’ll try again later with Atlassian holding our hands.

To conserve our limited CPU resources we have disabled anonymous access to the HTTPS exposed SVN repositories.

Previously, you could anonymously read repositories such as https://svn.codehaus.org/xfire/

You will now need to use the anonymous version – http://svn.codehaus.org/xfire/

To convert an existing working copy –

svn switch --relocate \
 https://svn.codehaus.org/xfire/ \
 http://svn.codehaus.org/xfire/ \
 .

Over the weekend, JIRA was upgraded to version 3.6.2, along with several other software upgrades to improve performance.

Please let us know if anything broke! (or was fixed if you had outstanding chores raised against JIRA).

Today, Sunday, we did a fairly large deployment of Xircles. We don’t think anything broke permanently, but if you notice strangeness, please let us know (via IM, email or IRC).

DNS did get thrashed for a while for top-level codehaus.org sites such as Confluence, JIRA and Xircles itself. Project DNS managed to escape unscathed.

DNS has been repaired and should be propagating to your ISPs.

Further news if we discover anything else out-of-service.

If the system has detected that your account or projects you manage need some adjustment, your personal page will display some red boxes explaining the action you need to take.

Some of them may refer to your user settings, such as your full name or non-Codehaus email address. Others may apply to project settings or membership requests from prospective contributors.

A while ago yWorks donated a license for yDoc. We have now made it available through the license-management pages.

So, you might have noticed the front page of Xircles containing a list of featured projects. You might notice that yours is not amongst them.

“How do I get my project listed?” you may ask yourself. Well, go forth and adjust your project’s settings. Fill out the short and long descriptions. Tag your project. Basically, use the features of the system.

Then lobby to Ben or Bob and we’ll tag your project if we feel you’re worthy of linking from the front page.

Another small deployment of Xircles…

• Organizational updates to make menus a tad cleaner and clearer and more compact.
• Allow users to configure their various non-codehaus IM accounts.
• Provide a contacts page enumerating individuals you share projects with, along with contact information.

We have deployed the latest Xircles for the haus. Included in this deployment are:

• Tag cloud
• New look and feel
• Tool licenses
• News (like this) with RSS

And probably some other things we’ve already forgotten we did. Poke around, explore!.