Snapshot Changes, New Buildbot

[BAILOPAN]

We've completed a major revamp of the snapshot and automated build system for SourceMod. We are now using Buildbot (http://buildbot.net/trac).

Builds now occur as soon as any change is pushed rather than on the hour. You can view the build progress page here:

http://www.sourcemod.net/builds/waterfall

Builds (and debugging symbols) will now be removed after 30 days. We will no longer be providing package layouts through Subversion, as this was extremely slow to manage and was using a huge amount of disk space.

The motivation behind this was to centralize what was previously a huge mess of terrible perl scripts. We now have a much more stable build layout that anyone can look at, with precise blaming, better change tracking, and better use of server resources.

Site Compatibility
In two weeks I will be completely removing /svnroot/Packages and /svnroot/Symbols. I've also removed the "changelog" link, as the waterfall page shows the changelog for each build.

I understand that some people have used /svnroot/Packages for doing automated upgrades. Unfortunately that model was not sustainable as each build used around 15MB and there were hundreds of builds. If you are interested in getting some of this functionality back -- file a bug and we can talk about it.

The buildbot setup we're using is available in the source tree under tools/buildbot.

[bl4nk]

Hmm, let me be the first to say that I'm not the biggest fan of the new changelog system. I'm all for it making your guys' life easier with everything, but me, as an end user of the site, it's rather difficult to figure out what's going on. There has to be something I'm missing that lays out the changes over time in a simple list (something like the old method), or else it seems like a very unorganized system (again, for the end users - I have no idea what it looks like on the server side of things). Hopefully you can take this confusing system and make it into something that's a bit more usable by the public.

Also, I'm a bit confused on the subject of the SVN stuff. As I understand it, you're completely disabling SVN packages. If this is true, that means to update the SM installations on our servers we would have to download the complete SourceMod package(s) from the website, correct? There would be no easy way to automate updating of the servers?

Anyways, I'm sure this whole situation is for the best, so I hope it helps you get the job done faster and easier.

[BAILOPAN]

Hopefully you can take this confusing system and make it into something that's a bit more usable by the public.

I don't see how it's confusing, you just click on the name of the author on the left-hand side. The only reason the "changelog.php" script existed was for when SourceMod was closed source. That's no longer the case. It's easy (http://svn.alliedmods.net/viewvc.cgi/trunk/?root=sourcemod&view=log) to get logs (http://svn.alliedmods.net/viewvc.cgi/branches/sourcemod-1.0.x/?root=sourcemod&view=log) from ViewVC that are even separated by branch.

The waterfall view can seem complicated but it makes sense after a few minutes. The graph is a timeline (bottom being the earliest date, top being "now"). As each build (column) progresses it starts a block for the timespan it's taking.

If this is true, that means to update the SM installations on our servers we would have to download the complete SourceMod package(s) from the website, correct?

Yup.

Unfortunately that model was not sustainable as each build used around 15MB and there were hundreds of builds. If you are interested in getting some of this functionality back -- file a bug and we can talk about it.

[bl4nk]

I don't see how it's confusing, you just click on the name of the author on the left-hand side.

Ah, ok. That makes it a lot easier. I just went onto that screen and saw a whole bunch of text everywhere that didn't really seem so organized. Now that I see that, it's all starting to fall into place. :)

As for the two links for the logs, that's exactly what I was looking for.

[DontWannaName]

Sounds cool, can you make the table text bigger on the snapshot download page by chance? I kinda miss the old changelog method, Im a tad confused with the new one. The link was also harder to find than last time for the changelog, can you move it next to the sourcemod license link like last time? Ok those 2 links you posted should be on the dl page, they make perfect sence and im guessing trunk is 1.1.

[Dominator]

So just to get this 110% strait after reading this, newest version of sourcemod will be at the top of the list and all previous ones will be at the bottom? Also just follow the comments if its stable or not because you guys test it, this is kind of a linux setup so theres gonna be good changes and I like the way this is going great job!

[willy1234x1]

Is there an autodelete for the SVN trunk? I'm asking because you have 2500 to 2530 all on the page currently.

[BAILOPAN]

So just to get this 110% strait after reading this, newest version of sourcemod will be at the top of the list and all previous ones will be at the bottom?!

Yes.

Is there an autodelete for the SVN trunk? I'm asking because you have 2500 to 2530 all on the page currently.

Not sure what you mean. As stated in the news post, the snapshots in SVN are stale and will be removed entirely in 2 weeks. The snapshots from buildbot will rotate out (everything older than a month gets deleted).

[willy1234x1]

Bail this table http://www.sourcemod.net/snapshots.php?branch=1.1 is going to get massive if you do once a month, wouldn't twice a month be much better?

[BAILOPAN]

If it gets too large I'll only display X rows and link to the archive directly.

[SaintK]

I might be blind as a bat, but were do i find the 1.1 changelogs now?

[bl4nk]

http://svn.alliedmods.net/viewvc.cgi/trunk/?root=sourcemod&view=log is the place that you can find it that's easiest to read.

[SaintK]

http://svn.alliedmods.net/viewvc.cgi/trunk/?root=sourcemod&view=log is the place that you can find it that's easiest to read.

Ah, i came across that but i couldn't figure out if those were for the 1.1 branche.

Cheers,

[bl4nk]

1.1 is the trunk revision
1.0 is a branch