关闭

关闭

封号提示

内容

首页 MagxGit.pdf

MagxGit.pdf

MagxGit.pdf

上传者: 胜歌 2011-06-03 评分1 评论0 下载12 收藏0 阅读量464 暂无简介 简介 举报

简介:本文档为《MagxGitpdf》,可适用于IT/计算机领域,主题内容包含PlatformCMToolsandDistributedDevelopmentJune,DRAFTSTATUSSteveWoodruffPoint符等。

PlatformCMToolsandDistributedDevelopmentJune,DRAFTSTATUSSteveWoodruffPointsofDiscussionPointsofDiscussionPartI–AlookatthecurrentplatformsituationPartII–CMToolsPartIII–ChallengestoImplementationPartICurrentSituationPartICurrentSituationFullsourceinClearCaseFullbuildsbydevelopersandCMs:–Nonpackaging:Anywherefrommin–hrs–Packagingbinarybuilds:minminVeryfewcomponentsusebuildavoidanceinLJ(moredoin)CentralizedsourcecontrolwithMultiSite:ReplicationonthehourMustbenetworkconnectedtobuildorusesnapshotviewswhichareinefficientGBsnapshowviewcreationtimeis~hoursComponentsdeliversourcelabelstoplatformPlatformdeliverssourcelabelstoproductswteamOpensourcecodemustbemassagedbeforeitsfullyintegratedintothebuildsystemTheDetailsTheDetailsLRTDevelopersWorldwideDomainsProjectsDeliverablesfromProjectTeamsAboutMillionLOC(excludingkernelandtoolchainlibs)LJregionsreplicaswithdevelopmentaboutofthoseregionsSnapshotviewsareaboutGBinsizeWhat'swrongwithitWhat'swrongwithitWe'renotoperatinginatrulydistributeddevelopmentenvironmentWiththemovetopackaging,wenolongerneedcentralizedsourcecoderepositoriesDeveloperswanttheabilitytowork“offline”innetworkdisconnectedscenarios(airplane,home,etc)Mustwaitforlabels,branches,andothermetadatatoreplicatetoeachsitebeforereleasingsoftwareorbeforebuildingsoftwareifyou'renotinilhNowaytovalidatesourcecodeintegrityWorkingWithoutBoundariesWorkingWithoutBoundariesWiththerolloutofpackaging,wearenolongertiedtobuildingoursourcecodeintheVOB–Thetoolchaincanbemadeavailableasabinarypackage–Developerscanbuildtheircomponentorthewholesbfimageusingwithoutaccesstoanysourcetoday(throughtheuseofpackaging)–WithsomechangestothebuildsystemtosupportGNUmakeinsteadof(orinadditionto)Clearmake,developerswillbeabletodotheirworkwithoutboundariesWorkfromhome,airport,orevenanairplane!Onlyneednetworkconnectivitytogetthepackages–MustcomplywithiProtectrulessuchasusingPointSEConWindowsworkstationsandanothersolutionmustbeinplaceforLinuxworkstationsPartIICMToolAlternativesPartIICMToolAlternativesIfwe'renowabletoworkwithoutboundaries,isClearCasetherightCMtoolfordevelopersPreviouslyexaminedCMtoolalternatives–RCS,CVS:Oldtechnologieswithnumerousdrawbacks–Subversion:VerypopularCMtool,butnotgreatfordistributeddevelopmentandiswastefulwithstorageresourcesandhaspoorbranchinglabeling–Git:ArelativelynewCMtoolthatsupportstruedistributeddevelopmentandmeetsourbasicrequirements–alsothetoolofchoicefortheLinuxkernelLets“Git”toknowGitLets“Git”toknowGitHaslightweightandrapidmethodforbranchingandmergingHasvisualtoolsfornavigatingnonlineardevelopmenthistory(gitk,gitgui)Supportstruedistributeddevelopment(nocentralizedrepository)SupportslargeprojectsandhasconceptofsuperprojectswithpointerstoprojectsIndividualprojectswouldmaptobuildcomponentsGuaranteedintegrityofcodeinrepositoryviaSHA'GoogleTechTalks'aboutGit'GoogleTechTalks'aboutGitTwoveryinformativeGoogleTechTalksessionswereheldwithGitasthesubject–LinusTorvoldsdiscussesthehistoryandbenefitsofGitoverotherCMtoolshttp:wwwyoutubecomwatchv=XpnKHJAok–RandalSchwartzdiscussestheuseanddesignofGitasaCMtoolhttp:videogooglecomvideoplaydocid=HowwecanuseGitforMAGXHowwecanuseGitforMAGXMigrateeachplatformLRTbasedcomponenttoanewGitrepositorywhereitbecomesastandaloneprojectEachprojectCMwouldmaintaintheirownGitrepositoryforthatdomainThereisno“true”mastercopy,buttheprojectCMswouldmaintainthe“logical”mastercopyBecauseeachprojectrepositorycanbemirroredbyothercomponentsandtheplatformnoofflinebackupsarerequiredasarewithClearCase–Backupsareneeded,butthesecanbetaken“live”WeDOneedadisasterrecoveryplanandbackupsmightberequiredforlegalpurposes–solutionprovidedbyITEasyMigrationswithGitEasyMigrationswithGitVOBmigrationstookseveralmonthstocompleteinWithGit,amigrationisassimpleascreatinganewrepositorywiththeselectedcontentfromabranchthatyouwant,intheformatdirectorystructurethatyouwantChangingCMroles(jobrotation)acrosssitesbecomesmucheasieralsoasthereisnobranchmastershiptoworryaboutGitatthePlatformLevelGitatthePlatformLevelPlatformintegrationteamwoulduseasuperprojecttoaccesstherepositoriesprojectsofeachdomainandverifyplatformreleasesPlatformcurrentlymaintainsa'release'repositorywhichcontainsthebinaryandSDKpackagesforeachplatformreleaseInthefuture,thiscouldalsoholdthesourcepackagesforeachprojectcomponentThisrepositoryiscurrentlyaccessedbyeachdeveloperwhowishestobuildfrombinarypackagesIfweallowcomponentCMstoreleasebinarypackages,theplatformteamwouldneedtodoverificationtoensurecomponentsourcepackagesmatchthebinaryreleasesPlatformInternalReleaseswithGitPlatformInternalReleaseswithGitWiththeadventofpackaging,theplatformIntegrationteamnolongerexecutesfullbuildsfromsourceintheVOBforeachreleaseTheintegrationteam'sfunctionisnolongerthatofa“builder”butratheran“assembler”and“integrityverifier”(buildfromsourcemust=binaryreleases)IntegrationteamverifiesthatprojectbinarypackagesworktogethertogenerateaSBFandthencanreleasea“recipe”ofcomponentprojectpackageswhichareusedtocreateaplatformreleaseTherearesomecaseswhentheplatformmustregeneratethebinarypackagesforcomponentsBuildPlanningBuildPlanningBuildplanningisstillcriticalattheplatformlevelPlannersmustcoordinateAPIchangeswhichoccasionallyoccurPlatformwouldneedtoregeneratebinarypackagesforsomeorallcomponentswhenanAPIchangesinoneoftheplatformcomponentsprojectsPrivateAPIswhichareillegallyusedbyothercomponentswouldpresentaproblemandmustbeaddressedaspartofmakelintcompliance–MakelintcomplianceisnotenforcedbythePRTcurrentlyGitattheComponentProjectLevelGitattheComponentProjectLevelPlatformdeveloperscheckouttheirproject'sGitrepositoryforsourcecodeaccessontheirworkstationProjectCMscanusesuperprojectsforeachdomainintheirdeliverableForexample,TherecanbeonesuperprojectwhichpointstoprojectsforAM,DM,andAFWCI,sincetheCMcurrentlymanageseachofthoselogicalcomponentsPlatformdevelopersalsoclonetheplatform'sreleaserepositorywhichcontainsthebinaryandSDKpackageofeachprojectforeachrelease(label)Thisallowsdeveloperstowork“offline”andthentheProjectCMscan“pull”thechangesfromthedevelopersintotheproject'smainlineparbranchbeforeBR'ingtotheplatformRebasingMadeEasy!RebasingMadeEasy!Developerswillstarttheircodingononebaselinebutbythetimetheyfinish,theycouldbeseverallabels“behind”Githasarebasefeaturewhichwill“catchup”yourbranchtothelabelyouspecifyAfterrebaseinginGit,youstillcaneasilydeterminewhatchangesyoumade–AfterrebaseinginClearCase,ALLofthechangesthattookplacebetweenyouroriginalbaselabelandthenewlabelnowappeartobe“newchanges”onyourbranchThisskewsthingslikeDLCmetricsandmakescodereviewdifficultbecauseyoucan'tdeterminewhatchangesyoumadeandwhatwas“pulledin”fromtherebaseingComponentIntegrationwithGitComponentIntegrationwithGitDevelopers'pull'fromataggedlabeledbranchthatthecomponentCMhasreleasedDevelopersmakechangesonabranchandwhenready,theBRtothecomponentwouldbetheinfofortheirbranchComponentCMdoesa'pull'tobringthedeveloper'schangesintoanintegrationbranchandresolveanymergeconflictsComponentCMdoesamergebacktotheparbranchforthedrumbeatThe“pulling”isdoneviascp,http,oroneofseveralotherprotocolsthatGitsupports,includingitsownnativeprotocolforcommunicatingbetweenreposComponentProjectReleaseswithGitComponentProjectReleaseswithGitProjectCMsgeneratethebinary,sourceandSDKpackageforeachdomainreleaseandcankeepthisinthesamerepositoryoraseparatereleaserepositorywithGitProjectCMsBRthesepackages(includingBinarypackages)totheplatformteamPlatformdropstothePRTPlatformdropstothePRTAtsomepoint,theplatformwillwanttoreleaseabaselinetotheproductintegrationteamsDropsconsistofsource,binaryandSDKpackagesforeachplatformprojectPRTshoulduseBinaryandSDKpackagesandthepackagebasedbuildenvironmentAnymodificationofplatformsourcebythePRTisattheirownriskandunsupportedbytheplatformPRTshouldmaintainseparatepatcheswhichcanbeappliedtoplatformreleasedpackagesandareeasilymanagedwithopensourcepackagingtoolssuchasQuiltGitTransitionPlansGitTransitionPlansWecurrentlysupportpackagingfromaVOBClearCaseenvironmentWedonotsupportsourcepackagebuildsyet,duetoproblemsincomponentarchitectureandcomponentmakefiles–NeedArchitectureteamtodrivethisPlatformreleaseswillbeavailableinbothClearCaseandaGitrepositoryComponentscanmigratetoGitinphasesandtheplatformcanbuildmomentumtowardsafullydistributeddevelopmentenvironmentCreatetoolstoimportexportbetweenGitandClearCasePhasedTransitiontoGitPhasedTransitiontoGitIndividualprojectscanmaketheswitchtoGitwithoutworryingabouttheotherplatformprojectsPlatformscriptstoolswillprovideforbuildingsoftwareinthismixedenvironmentChangesareneededinCMstrategyandtoolstosupportGitrepositoriesCMToolsandConcernsCMToolsandConcernsEzBRtoolswillbemodifiedtosupportGitrepositoriesDDTScancontinuetobetheCRtrackingtool,butanytoolwhichmeetsourCRtrackingandreportingneedscanbeused,suchasBugzillaorTracBRsite(wsdbuild)willneedminorchangestosupportBRsfromGitrepositories(noconfigspec–onlythebranchname)orwecanusesomethingentirelydifferent–MaybeaproductsuchasTracinsteadofDDTSWSDBuildLOCToolsmightneedtobeupdatedtoworkoutsideofclearcase(cleardlc)NeedtodetermineaprocedureprocessforGitrepositorypruningtopreventoutofcontrolgrowthWewillloseClearCasetriggershowdoweenforceourcurrentbranchlabelnamestandardsIsthisevenimportantLRTPRTInterfaceSuggestionsLRTPRTInterfaceSuggestionsPRTreceivesdropsinpackageformatfromtheplatformTheplatformdoesnotdictatewhatCMtoolthePRTusesPRTcanchoosetouseGit,ClearCaseoranythingelsebutusingGitwouldallowthemtoleveragetheadvantagesofGitfortheirownworkPRTwouldnothaveaccesstofullsourcecodehistoryofplatformprojects–onlysnapshotsofthesourcecodePRTchangestoplatformsourcecodearehandledmanagedbythePETPartIIIQuestionsPartIIIQuestionsThefollowingaresomequestionsorchallengeswehavetoimplementingGitattheplatformorcomponentlevelWebelievethatwecanfullyanswerthesequestionsandgetpastthechallengesaspartoffurtherinvestigationandprototypinginthebuildenvteamStillundecided:Whatisplatformandwhatisproduct–Security:Howtocontrolaccesstocertainrepositories–GitsupportsseveralmethodsofaccesscontrolHowdoweenforcebranchlabelnamestandards–EzBRcoulddothisforusHowdowepruneGitrepositories–MoreQuestionsMoreQuestionsDoweneedtodomoreVOBmigrationsnowtoremoveaccesstoproductSWcode–Nothehistoryisstillthere,sowe'renothidinganythingIsthereanequivalenttoPointSECforLinuxworkstations–ConceptofencryptedpartitionsexistsaswellasvirtualpartitionsviaTrueCrypt(OSS)WillwelookforanalternativetoDDTS–SeenextquestionWillwelookforanalternativetothewsdbuildBRwebsite–SomethinglikeTracmightallowustocombinebuildandCRtrackingintoasingleopensourcetoolEvenMoreQuestionsEvenMoreQuestionsWhatareourbackupandDRplanswhenusingGit–NeedtoworkwithCSC–CanwehostGitreposonsourceforgemotcomCurrentlyMOSTsupportsCVSandSubversion,butnotGityetRamiLevyknowsaboutothersaskingforthisAfteryoudetecttamperingofalabelrelease(viaSHA),howdoyourepairthis–SlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlideSlide

类似资料

  • git.pdf

  • Git.pdf

  • git.pdf

  • git.pdf

  • Git.pdf

  • Introduction_to_…

  • Getting-Git-Done…

  • git使用指南.pdf

该用户的其他资料

Exam 70-448 MCTS Self-Paced Training Kit.pdf

Exam 70-433 Training Kit SQL 2008 Database Development.pdf

Exams 70-432 and 70-450 SQL Server 2008 Administration - Real-World Skills for MCITP Certification and Beyond [Sybex, 2010].pdf

Exam 70-432 MCTS Sql Server 2008.pdf

Exam 70-433 Prep Kit The Real MCTS SQL Server 2008.pdf

职业精品

精彩专题

结婚彩礼真有那么重要吗?

原创于西周而后沿袭至今的彩礼,虽然被一部分家长奉为圭臬,但越来越多的年轻人对结婚必须要彩礼不以为然。彩礼引发的社会矛盾越来越受到关注,结婚是自己的事,如人饮水冷暖自知,至于要不要彩礼或者要多少彩礼,因人而异,因财力而已,不可一概而论。

用户评论

0/200
    暂无评论
上传我的资料

精选资料

热门资料排行换一换

  • 西方现代语言哲学.pdf

  • 手把手教你炒期货.pdf

  • 清名家诗丛刊初集 陈维崧诗_11…

  • 清名家诗丛刊初集 施闰章诗 下册…

  • 译员基础教程 如何组建翻译公司.…

  • 《李劼论红楼梦》历史文化的全息图…

  • 心灵的母体:对象关系与精神分析对…

  • 为何思考?进化与理性心灵.pdf

  • 资料评价:

    / 26
    所需积分:0 立即下载

    意见
    反馈

    返回
    顶部