Re: [proteowizard-developer] Remaining Pwiz/TeamCity tasks

[Darren K. <da...@pr...>]

Wow -- great work, Matt.

So here's a summary of what we want to publish.

Daily builds (on TeamCity server):
 - zip files of the binaries; for each platform, this will be the
contents of the build/???-release directory after a clean build, minus
any un-redistributables.
 - build logs

Releases (on SourceForge):
- zip files from selected daily build of each platform
- the various source tarballs

With Matt's work, the source tarballs are part of our Jamfile.  The
binary zip files are created differently in two different scripts
(autobuild, create_packages), so we'll want to move to a single
script, or get this in the Jamfiles as well.



Darren




On Wed, Aug 26, 2009 at 11:12 AM, Matthew
Chambers<mat...@va...> wrote:
> Moving thread to pwiz-developer.
>
> Through an excruciating right of passage I've learned a lot more about
> the Boost.Build build process - enough to create bcp and tar modules.
> The bcp module builds the bcp program from the boost tarball, takes a
> list of targets, traverse their dependencies down to the source code and
> passes that list to bcp. BCP traverses the files it's given for boost
> dependencies and copies them to a target location. Then I use the tar
> module to create a subset boost tarball. Then I make 4 pwiz source tarballs:
> * pwiz-full-source (mixed licenses)
> * pwiz-full-source-without-vendor-support (still has some mixed licenses)
> * pwiz-psi-source (pure Apache licensed with limited vendor support)
> * pwiz-psi-source-without-vendor support (pure Apache licensed)
>
> The final tarball sizes are currently 37.3mb, 13.4mb, 37.1mb, 13.2mb.
> But that includes all the DLLs, some of which we can't yet redistribute.
> The boost tarball is down to just about a meg of that. There isn't much
> difference between the full source and just the PSI-related source (by
> which I mean MSData, mzIdentML, TraData, etc.), so it might not be worth
> it to split it up on that unless we really care about providing a pure
> Apache tarball.
>
> There are places we can still optimize for size, especially the Bruker
> unit test data. The FeatureDetector test data is pretty big too. Making
> SeeMS use a dynamically built pwiz bindings will shave off 3mb.
>
> Right now the tar module only supports creating tars, but I'm soon going
> to add tar extraction as well.
>
> I'm most interested in just getting the damn thing working and committed
> though since I've spent over a week on it now. :) Most of the work I do
> on the pwiz build system I justify by copying it to our own group's
> build system, so it's not too bad.
>
> -Matt
>
>
> Darren Kessner wrote:
>> Hi Dave,
>>
>> We would like to have the same tarballs/zips published for daily
>> builds (on LabKey's servers) and for official releases (on
>> SourceForge).
>>
>> Currently the official releases are created by a different script,
>> pwiz/scripts/release/create_packages.
>>
>> I believe Matt (who I've added to this email) was thinking of putting
>> the package creation in the Jamfile, so really it would be a matter of
>> just publishing those zips as artifacts for the daily builds, and then
>> selecting certain daily builds for release.  I don't have a strong
>> opinion about whether the releases would be selected manually or
>> automatically, but I would lean toward an automatic once-a-month
>> release.
>>
>> Matt, how does all this fit with your plans?
>>
>>
>> Darren
>>
>>
>>
>>
>> On Tue, Aug 25, 2009 at 3:27 PM, Dave Stearns<da...@la...> wrote:
>>
>>> Hi Darren,
>>>
>>> The Mac agent is now up and running and I'll continue to monitor it and fix
>>> any configuration issues that it might have. As I recall, the one remaining
>>> task now is to do some sort of automated publishing of the Pwiz tools to
>>> Sourceforge. I have some questions about that:
>>>
>>> - What do you want published? I'm assuming both the source tarball and the
>>> various binaries in zip files you have linked from your web site. Let me
>>> know if you want something different.
>>>
>>> - Do you have a script/batch file that builds those zip files? If not, I'll
>>> need a list of which files should be included in each zip. I assume that the
>>> source tarball should include the clean sources.
>>>
>>> - How do you want to trigger this? Manually or on a regular basis?
>>>
>>> Let me know what you think,
>>> -dave
>>>
>>>
>>>
>>>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> proteowizard-developer mailing list
> pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proteowizard-developer
>