Automated Build/Package/Deployment System

[rcurtin]

Reported by speet3 on 4 Aug 2011
The ultimate end goal here is to free the developers from a lengthy and tedious release process. This ticket will be the catch-all ticket for which most build server related setup tickets will block.

[rcurtin]

Commented by speet3 on 4 Aug 2011
It appears I do not have the correct permission to modify the description of the ticket, so I'll just add it as a comment for now:
The following requirements are excerpted from ticket #18 for as a reminder of intended result of this ticket:

• Build each revision of MLPACK shortly after it is checked in
• Upon encountering a build error that was not present before, alert the developer who checked in the erroneous code with a nastygram
• Be able to run unit tests on the code
• Be able to run timing tests on the code (Remove fl-build system (all the build.py files) #19)
• Be able to get profiling information for the code; CMake can compile MLPACK easily with profiling information (though I've not yet checked the code to make that change in) and then gprof can get results (Minimize preprocessor macro usage #20)
• Compare timing information and profiling information across revisions of the code
• Produce working executables for Windows, Linux, and OS X
• Provide automatically built installation packages

[rcurtin]

Commented by rcurtin on 5 Aug 2011
Are you sure you can't modify the description? Authenticated users have TICKET_MODIFY permissions; shouldn't that be adequate?

[rcurtin]

Commented by speet3 on 5 Aug 2011
Unfortunately, no. Users require the TICKET_EDIT_DESCRIPTION permission to modify the description itself. I can send you a screenshot of what I see if you like.

[rcurtin]

Commented by rcurtin on 5 Aug 2011
Ok, I added both TICKET_EDIT_DESCRIPTION and TICKET_EDIT_CC to the authenticated group, so that should solve that issue. It doesn't address the actual reason the ticket was filed though. :)

[rcurtin]

Since Github doesn't have good support for blockers/master tickets, I'll go ahead and close this. The only real thing that needs to be completed still is the Windows executable build process; that needs to be integrated with Jenkins. But there's a ticket open for that already -- #365.