Menu
▾
▴
Re: [proteowizard-developer] building pwiz in mingw
|
From: Josh E. <je...@la...> - 2011-04-19 18:12:48
|
Hi guys, Would this build require a new machine type that isn't currently part of the build machine pool? If not, I don't think it would be a big issue to add another build configuration without adding an agent. If it makes sense to add another agent to the pool, which is totally fine by us, it's likely that it would qualify for the free non-commercial open source license: http://www.jetbrains.com/teamcity/buy/index.jsp The agents that we run at LabKey don't qualify since we're a for-profit company, but I think this one probably would. Thanks, Josh On 4/18/2011 9:56 AM, Matthew Chambers wrote: > Hi Joe, > > The build agent just needs an install of the small TeamCity build agent daemon. It's fairly simple > to set up on Windows. The only tricky part is working past firewall issues. At Vanderbilt we have a > weird port range 37200-37299 that are the only non-standard ports open at the perimeter firewall. I > set up our Mac OS X agent to listen on port 37290; the default is 9090. > > -Matt > > > On 4/18/2011 11:28 AM, Joseph Slagel wrote: >> Matt, >> >> What other resources would be needed to run a build agent? Do we need to install TeamCity? >> >> -Joe >> >> >> On Mon, Apr 18, 2011 at 9:27 AM, Matthew Chambers<mat...@gm... >> <mailto:mat...@gm...>> wrote: >> >> Hi Brian, >> >> If I dig into this to get MinGW building the full pwiz distro, I'd want to keep testing it with a >> TeamCity agent. LabKey's already given us enough resources though. I'm wondering if Insilicos or >> ISB/SPC would be interested in hosting a MinGW build agent? >> >> -Matt >> >> >> On 3/21/2011 2:26 PM, Brian Pratt wrote: >> > No joy, with >> > obj pwiz_utility_clickwrap_prompter : ClickwrapPrompter.cpp : >> > <toolset>msvc:<using-clr>true ; >> > >> > >> > Building pwiz... >> > NOTICE: WORKING COPY HAS 1 MODIFIED FILES. >> > ProteoWizard 2.1.2575.modified (last committed change: 2011-3-17) >> > tar.list gd-2.0.33.tar.bz2 >> > Missing revision info in: >> > c:\ProteoWizard\pwiz\pwiz_tools\SeeMS\Misc\ChromatogramDataSet.Designer.cs >> > Missing revision info in: >> > c:\ProteoWizard\pwiz\pwiz_tools\SeeMS\Misc\SpectrumDataSet.Designer.cs >> > Missing revision info in: >> > c:\ProteoWizard\pwiz\pwiz_tools\SeeMS\Properties\Resources.Designer.cs >> > Missing revision info in: >> > c:\ProteoWizard\pwiz\pwiz_tools\SeeMS\Properties\Settings.Designer.cs >> > Missing revision info in: >> > c:\ProteoWizard\pwiz\pwiz\utility\bindings\CLI\AssemblyInfo.cpp >> > tar.extract gd-2.0.33.tar.bz2 (already extracted) >> > tar.list boost_1_43_0.tar.bz2 >> > tar.extract boost_1_43_0.tar.bz2 (already extracted) >> > tar.list zlib-1.2.3.tar.bz2 >> > tar.extract zlib-1.2.3.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/ABI] Non-MSVC build: Reader_ABI can only >> > identify files, not read them. >> > [pwiz/data/vendor_readers/ABI/T2D] Non-MSVC build: Reader_ABI_T2D can >> > only identify files, not read them. >> > [pwiz/data/vendor_readers/Agilent] Non-MSVC build: Reader_Agilent can >> > only identify files, not read them. >> > [pwiz/data/vendor_readers/Bruker] Non-MSVC build: Reader_Bruker can >> > only identify files, not read them. >> > [pwiz/data/vendor_readers/Thermo] Non-MSVC build: Reader_Thermo can >> > only identify files, not read them. >> > [pwiz/data/vendor_readers/Waters] Non-MSVC build: Reader_Waters can >> > only identify files, not read them. >> > Warning: No mascot support found for the mzIdentML library. >> > Skipping build of: ./bgddll<build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/misc/automation_vector_test >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/misc/COMInitializerTest<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ParamTypes<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/MSDataDiff<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/MSData<build>no in >> > common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/MSDataFile<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/MSDataReader >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/MSData_examples >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/spectrum_processing >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/SpectrumList_PeakFilter >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/chemistry<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/proteome<build>no in >> > common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ProteomeDataDiff >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ProteomeData >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ProteomeDataFile >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ProteomeDataReader >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/ProteomeData_examples >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/TraDataDiff<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/TraData<build>no in >> > common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/TraDataFile<build>no >> > in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/TraDataReader >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/TraData_examples >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/pwiz_bindings_cli >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/pwiz_bindings_cli.xml >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/common/SharedCLITest >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/common/ParamTypesTest >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/msdata/MSDataTest >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/msdata/DiffTest >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/analysis/spectrum_processing_test >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/proteome/proteome_test >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/proteome/ProteomeDataTest >> > <build>no in common properties >> > Skipping build of: >> > /c:/ProteoWizard/pwiz/pwiz/utility/bindings/CLI/proteome/DiffTest >> > <build>no in common properties >> > tar.list Reader_ABI_Test.data.tar.bz2 >> > tar.extract Reader_ABI_Test.data.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/ABI] Non-MSVC build: Reader_ABI_Test is only >> > testing that it can identify files, not read them. >> > tar.list Reader_Agilent_Test.data.tar.bz2 >> > tar.extract Reader_Agilent_Test.data.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/Agilent] Non-MSVC build: Reader_Agilent_Test >> > is only testing that it can identify files, not read them. >> > tar.list Reader_Bruker_Test.data.tar.bz2 >> > tar.extract Reader_Bruker_Test.data.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/Bruker] Non-MSVC build: Reader_Bruker_Test >> > is only testing that it can identify files, not read them. >> > tar.list Reader_Thermo_Test.data.tar.bz2 >> > tar.extract Reader_Thermo_Test.data.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/Thermo] Non-MSVC build: Reader_Thermo_Test >> > is only testing that it can identify files, not read them. >> > tar.list Reader_Waters_Test_Legacy.data.tar.bz2 >> > tar.extract Reader_Waters_Test_Legacy.data.tar.bz2 (already extracted) >> > [pwiz/data/vendor_readers/Waters] Non-MSVC build: Reader_Waters_Test >> > is only testing that it can identify files, not read them. >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\feature.jam:320: in >> > validate-feature from module feature >> > error: unknown feature "<using-clr>" >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\feature.jam:354: in >> > expand-subfeatures-aux from module feature >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\feature.jam:419: in >> > expand-subfeatures from module feature >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\feature.jam:849: in >> > feature.expand from module feature >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:970: in >> > evaluate-requirements from module targets >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:1065: in >> > common-properties2 from module targets >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:937: in >> > targets.common-properties from module targets >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:1232: in >> > object(typed-target)@9122.generate from module >> > object(typed-target)@9122 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:732: in >> > generate-really from module object(main-target)@9179 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:704: in >> > object(main-target)@9179.generate from module object(main-target)@9179 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@9117.generate from module >> > object(project-target)@9117 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@9114.generate from module >> > object(project-target)@9114 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@9111.generate from module >> > object(project-target)@9111 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@9085.generate from module >> > object(project-target)@9085 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@310.generate from module >> > object(project-target)@310 >> > c:/ProteoWizard/pwiz/libraries/boost-build/build\targets.jam:258: in >> > object(project-target)@40.generate from module >> > object(project-target)@40 >> > c:/ProteoWizard/pwiz/libraries/boost-build\build-system.jam:710: in >> > load from module build-system >> > c:\ProteoWizard\pwiz\libraries\boost-build\kernel\modules.jam:283: in >> > import from module modules >> > c:\ProteoWizard\pwiz\libraries\boost-build\kernel\bootstrap.jam:142: >> > in boost-build from module >> > c:\ProteoWizard\pwiz\libraries\boost-build\boost-build.jam:8: in >> > module scope from module >> > >> > At least one pwiz target failed to build. >> > >> > ------------------------------------------------------------------------------ >> > Colocation vs. Managed Hosting >> > A question and answer guide to determining the best fit >> > for your organization - today and in the future. >> > http://p.sf.net/sfu/internap-sfd2d >> > _______________________________________________ >> > proteowizard-developer mailing list >> > pro...@li... >> <mailto:pro...@li...> >> > https://lists.sourceforge.net/lists/listinfo/proteowizard-developer >> >> ------------------------------------------------------------------------------ >> Benefiting from Server Virtualization: Beyond Initial Workload >> Consolidation -- Increasing the use of server virtualization is a top >> priority.Virtualization can reduce costs, simplify management, and improve >> application availability and disaster protection. Learn more about boosting >> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev >> _______________________________________________ >> proteowizard-developer mailing list >> pro...@li...<mailto:pro...@li...> >> https://lists.sourceforge.net/lists/listinfo/proteowizard-developer >> >> >> >> >> ------------------------------------------------------------------------------ >> Benefiting from Server Virtualization: Beyond Initial Workload >> Consolidation -- Increasing the use of server virtualization is a top >> priority.Virtualization can reduce costs, simplify management, and improve >> application availability and disaster protection. Learn more about boosting >> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev >> >> >> >> _______________________________________________ >> proteowizard-developer mailing list >> pro...@li... >> https://lists.sourceforge.net/lists/listinfo/proteowizard-developer > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > proteowizard-developer mailing list > pro...@li... > https://lists.sourceforge.net/lists/listinfo/proteowizard-developer |