Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Build server upgrade -- status


Since build2 is the server where signing occurs, we can't sign our builds.  We are building toward 3.7M1 today so it would be great if the build2 could be restarted so we could have signed builds.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=321506

Kim




Denis Roy <denis.roy@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

08/01/2010 12:58 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
[cross-project-issues-dev] Build server upgrade -- status





Folks,

Yesterday I upgraded the build server to SLES 11 SP1 (from SLES10 SP2).  
It all went surprisingly well, but there are some issues :

- subversion: because SVN is not packaged with our entreprise OS, it has
to be compiled.  The upgrade process removed the compiled package we
had, and now we must hunt down the dependencies and troubleshoot the
compilation issues.

- git: same as above

- NNTP and forums: a major upgrade occurred to the NNTP daemon, and now
it refuses to start.  We need to troubleshoot this.

- build2: since it relies on build to be always there, it is currently
spaced out and in need of a cold restart.

There will be other issues that will crop up, but for now this is what
is on our radar.  If you see other issues, please open a bug against
community/servers.

Thanks for your understanding,

Denis
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top