Redports User Guide requires that you register an account first because you also get your own Subversion subtree connected to it. Once you have verified your email some staff will activate it so that you can fully use it. Until that has happened you will get "Warning: No permissions to schedule builds for this repository" when scheduling new jobs.


Now that you have your account you should join a few buildgroups first. A buildgroup is a specific Environment in which your port will be build. This can be a stock FreeBSD 8.2/amd64 or some custom FreeBSD 10-CURRENT with CLANG/LLVM as default ports compiler. That allows you to test your port on many different environments which you probably could not do otherwise.

Use "Join Buildgroup" on the right to join available buildgroups that you want your ports to be build on automatically on every commit.

Redports Buildgroups Screenshot

Subversion Repository

With your account you also get your own Subversion repository where you can maintain your own ports. There is no policy about the quality of them so beware if you test other peoples ports from their repository. Every time you commit something to it redports will automatically create new jobs of all affected ports for all buildgroups that you have joined. If you want to prevent automatic building for a specific commit you can add Redports: ignore to your commit message. For very important builds you can add Redports: urgent but please try to keep that at a minimum.

Example commit message:

- Update to 0.24.2

Redports:       ignore

You can follow the progress of your builds by watching your buildqueue or the global buildqueue.

Notice: All ports in your repository replace the complete directory of the official ports whenever you build a port. There is only one exception to that rule which is the /usr/ports/Mk directory. So if you want to modify it is enough to put the modified in your repository. You don't have to copy all other files from Mk to your repository.

Your Builds

Your Builds is your central point where you can see what has been build and what the result was. You usually get an link to the buildlog as soon as the build has finished and if it failed you also get a download link to the work directory of your port. That sometimes helps debugging what went wrong with your port.

If you want to rebuild some ports you can do this with "Rebuild Port" on the right. You can also add a space separated list of ports to build multiple ports in one job.

Even when you delete the jobs they will always be available in the archive for at least 2 months so it's safe to share links to the archive.

Redports Buildqueue Screenshot

Wiki User Page

You have full access to the Wiki and should create a small wiki page for your account that briefly describes your work.

Usage Example

At the beginning your repository will be empty so we add a new port to it that we want to build. The directory layout of the repository should be the same as the FreeBSD portstree in /usr/ports.

Our example adds the port www/phpvirtualbox from the FreeBSD portstree to our repository.

svn co<yourusername>
cd <yourusername>
mkdir www
cp -pr /usr/ports/www/phpvirtualbox www/
svn add www
svn commit -m "phpvirtualbox added"

Now you should be able to see some new entries in your buildqueue.

Last modified 21 months ago Last modified on Feb 7, 2013, 12:04:33 PM

Attachments (2)

Download all attachments as: .zip