Build and Gated Check-in - презентация, доклад, проект скачать

Нажмите для полного просмотра!

Содержание ▲

Вы можете ознакомиться и скачать презентацию на тему Build and Gated Check-in. Доклад-сообщение содержит 129 слайдов. Презентации для любого класса можно скачать бесплатно. Если материал и наш сайт презентаций Mypresentation Вам понравились – поделитесь им с друзьями с помощью социальных кнопок и добавьте в закладки в своем браузере.

Слайды и текст этой презентации

Слайд 1

Описание слайда:

Build and Gated Check-in

Слайд 2

Описание слайда:

Goals Develop understanding of: Build system architecture Differences between AX6.x, and AX7 Current system state Roadmap Common operations scenarios

Слайд 3

Описание слайда:

Knowledge Process FAQ - AX FAQ - SharePoint sites: ESS Ops Build Infrastructure Dev Infrastructure ESS Documents Happydev -

Слайд 4

Описание слайда:

Overview

Слайд 5

Описание слайда:

Build Central Infrastructure

Слайд 6

Описание слайда:

Lab Footprint

Слайд 7

Описание слайда:

Source Depot - Overview Server Info: Hosted/Managed by BGIT Connect To - vedbuitfsa06:4020 Actual Server - TK5SDSERVDAX01 What to do when you notice the depot is down

Слайд 8

Описание слайда:

Source Depot - Overview Contd. Proxies Enhance local user experience Both BGIT-managed and private Current proxies : “sd proxies -o” 14 exist today Administration //depot/Admin/… SD Admin Explorer -

Слайд 9

Описание слайда:

Source Depot - Overview Contd. Help Sd help Sd help undoc Protections Controls who has permission to what Modifying protections Triggers Logic to run on command execution Main usage – preventing direct submits Modifying triggers

Слайд 10

Описание слайда:

Source Depot - Overview Contd. Maintenance BGIT-managed updates to server/SD instance Remove unused clients Client components sd.exe sdapi.dll sdb sdv Packing tools: sdp, jjpack

Слайд 11

Описание слайда:

Source Depot - Branching

Слайд 12

Описание слайда:

Source Depot - Integrations Introduction …it is “to propagate changes happened to a namespace (source namespace) during a certain period of time into another namespace (target namespace)”. -SD Integrations Guide Four States to Consider: State of the source just before a given period of time State of the source exactly at the end of a given period of time State of the target at the moment of integration State of the target at the end of the integration

Слайд 13

Описание слайда:

Source Depot - Integrations Contd. Revision Versioning at the file level Referenced with ‘#’ Example – sd sync //depot/rainier/rainfnd/foo.txt#2 Changelist Collection of file revisions commited at a single point in time Referenced with ‘@’, -c , Example – sd describe 123456 Label Collection of changelists Referenced with ‘@’ Example – sd sync …@7.0.123.0

Слайд 14

Описание слайда:

Source Depot - Integrations Contd. SD Integrate Forward Integrate (FI) versus Reverse Integrate (RI) Full branch integration sd integrate -b @ Point integration Sd integrate -b @, Manual mapping - renaming or baseless integrates sd integrate //depot/b1/foo.txt#1,2 //depot/b2/foo.txt

Слайд 15

Описание слайда:

Source Depot - Integrations Contd. SD Resolve Automatic resolve – sd resolve -as Manual resolve – sd resolve Accept Thiers (at) vs. Accept Yours (ay) vs. manual merge (e) Conflict/Manual resolution: >>>> ORIGINAL sources.all#2 ++++++++++++++++++++++++++++++++++++++++++++++++ #endif MSBUILD_VERSION=4.0 ==== THEIRS sources.all#3 ++++++++++++++++++++++++++++++++++++++++++++++++ #endif ==== YOURS sources.all ++++++++++++++++++++++++++++++++++++++++++++++++ #endif MSBUILD_VERSION=12.0

Слайд 16

Описание слайда:

Source Depot - Integrations Contd. AutoIntegrate tool Set of automation wrapping “sd.exe integrate” Custom resolvers MSBuild custom tasks/targets //depot/../Build/AX_Tools/AutoIntegrate/... Web Resolve Run via command line “Integrate” command or BuildTracker jobs

Слайд 17

Описание слайда:

Source Depot - Pack Files Jjpack.exe Primary packing format used in build/gates Supports integrations Does not support ‘undo’ – downgrades file op SDP.exe Does not support integrate options Double-click diff Used more commonly by Engineers to pass around changes

Слайд 18

Описание слайда:

BuildTracker Our Instance: BT product site: BT Lab Solutions DG: btracker

Слайд 19

Описание слайда:

BuildTracker - Services

Слайд 20

Описание слайда:

BuildTracker - Lab Maintenance Build Team Services Project Windows update on clients Reports DB Backups Auto-archive and drop cleanup Gate Queue Processor check BT Automation rules

Слайд 21

Описание слайда:

BuildTracker - Lab Maintenance Contd. Build Tracker Automation Library Rules framework for enforcing consistent practices in our BT instance Runs daily at 3am PST Source in BuildServices at \build\source\MS.Dynamics.Build\...

Слайд 22

Описание слайда:

BuildTracker - BT.exe Wrapper for common lab maintenance and reporting functions using BuildTracker’s APIs Available functions differ between BuildServices and product branches Source - \build\ax_tools\buildtracker\bt\...

Слайд 23

Описание слайда:

AX7 / Rainier

Слайд 24

Описание слайда:

The Product CTP Technical Concepts guide on HappyDev

Слайд 25

Описание слайда:

The Product CTP Technical Concepts guide on HappyDev

Слайд 26

Описание слайда:

Lab Footprint (AX7)

Слайд 27

Описание слайда:

Ax7 / Rainier Branches

Слайд 28

Описание слайда:

CoreXT - Introduction What is it? A layer of rules, processes, features and automation A common set of tools for developers, testers, builders and labs alike. Generic and decoupled from the applications being built Community effort within Microsoft Existed since 2000 – estimate is used by 1/3 of the company Latest release – v5.0 More information –

Слайд 29

Описание слайда:

CoreXT - Our Environment Overview Current version – v3.2 Build.exe to each project node Dependency Based Build (DBB) enabled Tracer/Analyzer disabled No adoption of CoreXT integration targets/properties CoreXT V5 package manager backported

Слайд 30

$CoreXT - Environment Setup Entry point %inetroot%\tools\path1st\myenv.cmd Shortcut by: Open cmd.exe Navigate to enlistment root Run “setenv”...$

Описание слайда:

CoreXT - Environment Setup Entry point %inetroot%\tools\path1st\myenv.cmd Shortcut by: Open cmd.exe Navigate to enlistment root Run “setenv” Branch-specific configurations %inetroot%\build\branchcfg\myenv_.cmd

Слайд 31

Описание слайда:

CoreXT – Package Management Branch package dependencies defined in a checked-in package manifest On CoreXT startup, missing packages are retrieved and installed into a local cache directory. Build processes consume package contents from the local cache More information on HappyDev

Слайд 32

Описание слайда:

CoreXT - Externals Public Externals ANY external reference or toolset ANY internal reference or toolset submitted as a binary Location – NuGet package repository (previously: %inetroot%\public\ext\...) Toolsets Often accompanied by makefiles/targets which integrate into CoreXT Approvals True external libraries (both Non-Dynamics Microsoft produced or 3rd party) need to receive LCA approval before check-in. External Components Search

Слайд 33

Описание слайда:

CoreXT - Build Build.exe Windows build tool Orchestrator for building/traversing the build graph Our version – 6.2.8427.0 ‘dirs’ and ‘sources’ amd64 is default build target Dependency Based Build (DBB) Build node dependencies drive build graph traversal Sources.dep

Слайд 34

Описание слайда:

CoreXT - Build Contd. PASS[0|1|2] PASS0 – Generation of files, copying of static content PASS1 – Compilation, X++, C#, C++ (both compile and link) all happen here PASS2 – Packaging/Binplacing/Setup Assembling the content from PASS0 and PASS1 into their final containers PASS2_BINPLACE – binplacing of built bits (mostly from PASS1) Project Inclusion Integrating your project into CoreXT’s build Dirs, sources, sources.dep, makefile, makefile.inc

Слайд 35

Описание слайда:

CoreXT - Build Contd. Rainier Build Topics XPPC Proxies/FormAdaptors DBSync Packaging

Слайд 36

$CoreXT - MSBuild Current Version – v14.0 Build.exe to MSBuild Handoff \public\ext\tools\msbuild.def inclusion in project makefile...$

Описание слайда:

CoreXT - MSBuild Current Version – v14.0 Build.exe to MSBuild Handoff \public\ext\tools\msbuild.def inclusion in project makefile \tools\path1st\msbuild.cmd wraps msbuild.exe MSBUILD_PROJECT in sources

Слайд 37

$CoreXT - FxCop Source: All Branches: %inetroot%\public\ext\fxcop\... Runs on: Binplace via %inetroot%\tools\build\buildtypes\fxcop_build.cmd MSBuild...$

Описание слайда:

CoreXT - FxCop Source: All Branches: %inetroot%\public\ext\fxcop\... Runs on: Binplace via %inetroot%\tools\build\buildtypes\fxcop_build.cmd MSBuild project when RunCodeAnalysis=true Nothing currently enforcing correct ruleset here Relevant Sources Macros: Specify additional parameters - FXCOP_USER_FLAGS Skip FxCop on Binplace - BINPLACE_FLAGS=--no-postbuild-fxcop

Слайд 38

Описание слайда:

CoreXT - FxCop Contd. Rule Categories SWI/Stock – rules fulfilling QE requirements or shipped with FxCop Example – Require CultureInfo be specified when calling a member that accepts it Dynamics source - enforce Org-specific patterns Example - Format of Copyright on binary’s properties Dynamics Test – enforce patterns on test code Example – Enforce inclusion of required test attributes on test cases

Слайд 39

Описание слайда:

CoreXT - FxCop Contd. Common Problems Missing reference assembly Multi-proc/race condition Deadlock/timeout Custom rule crashes Logs XML format per scanned assembly From Build log root – FXCopLogs%BuildType% FxCop error codes -

Слайд 40

$CoreXT - Customization Stock CoreXT Most source scripts under \tools\... Makefiles under \public\ext\tools\... As a rule don’t modify stock CoreXT...$

Описание слайда:

CoreXT - Customization Stock CoreXT Most source scripts under \tools\... Makefiles under \public\ext\tools\... As a rule don’t modify stock CoreXT Customization points \build\automation\... \build\path1st\... \build\buildtypes\... \build\sources.all \build\preenv.cmd \build\myenv.cmd

Слайд 41

$CoreXT - Automation CoreXT + BuildTracker Stock automation scripts - %inetroot%\tools\build\automation\... Customized automation scripts -...$

Описание слайда:

CoreXT - Automation CoreXT + BuildTracker Stock automation scripts - %inetroot%\tools\build\automation\... Customized automation scripts - %inetroot%\build\automation\... bldTree.cmd bldCommon.cmd bldDone.cmd bldStart.cmd bldShare.cmd

Слайд 42

$CoreXT - Codereview Wizard based on AutoProcess console that wraps CodeFlow submissions Binaries\Configuration - \build\CodeReview\... Source -...$

Описание слайда:

CoreXT - Codereview Wizard based on AutoProcess console that wraps CodeFlow submissions Binaries\Configuration - \build\CodeReview\... Source - \build\source\checkinwizard\... Managed pack share - \\dcsrdchkinfsa\CodeReviews Packs retained for ~2 years. Command: “Codereview -c ”

Слайд 43

Описание слайда:

CoreXT - DynCop Home-grown static analysis tool Developed and used initially for CoreXT v3.2 upgrade Develop rules which enforce consistency and best practices across the build environment Executes locally, in gates, and LMC Source – VSTS DynCop Git repo Documentation on HappyDev Product teams adopting for enforcing practices in their teams

Слайд 44

Описание слайда:

CoreXT – Platform-As-A-Binary Historically, AX has been a monolithic codebase Re-architect product into Platform component and Application component to be build/deployed/validated/released/serviced independently Platform and Application are exchanged with one another as Last Known Good (LKG) zip packages Further work expected to the product and ESS infrastructure supporting this More on LKG Management here

Слайд 45

Описание слайда:

CoreXT - Dirs Filtering Framework Mechanism used to partition codebase for initial Platform/Application build separation Uses build.exe’s filtering on dirs {tokens} Tool source - \build\ax_tools\DirsFilterManager\... Executable - \build\ax_tools\bin\DirsFilterManager.exe DynCop rules enforcing correct tokens HappyDev documentation

Слайд 46

Описание слайда:

CoreXT - Dirs Filtering Framework Contd.

Слайд 47

Описание слайда:

CoreXT - Odds and ends Aliases Maps a command to an alias Example – ‘codereview’ invokes the script to launch the code review wizard Specified globally per branch in %inetroot%\build\aliases\aliases.pub PrivateDev Global private directory Include //depot/private/privatedev/developer//… in your client spec Map to %inetroot%\private\developer\ Private aliases Add a file \build\aliases\aliases.pub under private directory

Слайд 48

Описание слайда:

Gates

Слайд 49

Описание слайда:

Gates - Technologies WTT Workflow engine Machine management/maintenance Powershell Log parsing Reporting Queue processor

Слайд 50

Описание слайда:

Gates - 50k Feet

Слайд 51

Описание слайда:

Gates - Submitting

Слайд 52

$Gates - “Checkin” Command Usage: checkin Source script: \public\ext\tools\x86\checkin.cmd$

Описание слайда:

Gates - “Checkin” Command Usage: checkin Source script: \public\ext\tools\x86\checkin.cmd

Слайд 53

$Gates - Checkin Wizard Wizard for submitting to the gates Based on AutoProcess console framework Configuration: \build\CheckinWizard\... Source:...$

Описание слайда:

Gates - Checkin Wizard Wizard for submitting to the gates Based on AutoProcess console framework Configuration: \build\CheckinWizard\... Source: \build\source\CheckinWizard\... Command: checkin submit -c

Слайд 54

Описание слайда:

Gates - Queue Processor Core Orchestrates scheduling of requested check-ins Scheduling dimensions: Machine availability Blocking files Branch lockdown Main script is written in Powershell Cmd wrapper manages logs and invokes core PS script Logs retained for 24 hours Executes every 5 minutes as a schedule task on gate server

Слайд 55

$Gates - Queue Processor Contd. Core Contd. BuildServices branch - %inetroot%\build\wtt_checkin\SetExternalReferences.cmd Log location -...$

Описание слайда:

Gates - Queue Processor Contd. Core Contd. BuildServices branch - %inetroot%\build\wtt_checkin\SetExternalReferences.cmd Log location - %QueueProcessLogDirectory% Execution server - %QueueProcessServer% BuildServices - %inetroot%\build\wtt_checkin\QueueProcessor\... BBCheck.exe Core scheduling utility to the gate WTT pool Wrapped by “checkin” command Abort, Submit, Resubmit, Status, Diff, Apply, BypassQueueLock, Prioritize, Repack, debug All branches - %inetroot%\build\source\BBCheckSystem\bbcheck\...

Слайд 56

Описание слайда:

Gates - Queue Processor Contd. Merge Resolution Check Every 15 minutes for branches that have queued, blocked checkins 3-way merge attempted on all files involving: Depot state of the file State of file in checkin blocked on State of file in checkin that’s blocked 0 conflicts on all blocked files unblocks checkin All branches - %inetroot%\build\wtt_checkin\MergeCheck\... QueueParse.exe Part of ReportingParser cycle Reflects blocking file state into DB BuildServices - %inetroot%\build\source\QueueParse\...

Слайд 57

Описание слайда:

Gates - Execution

Слайд 58

Описание слайда:

Gates - Execution Contd. Primary Machine Maintains checkin state Executes retail build Schedules leg builds and SCRAM runs Deploys Executes unit tests (C# and X++) Evaluates task results Submits (or rejects) changelist Sends alerts Updates bugs Hosts checkin build share Retained for up to 3 days \\\CheckinBuilds\\

Слайд 59

Описание слайда:

Gates - Execution Contd. Legs Build leg Applies change Executes a build Reports result back to primary machine (via file share) Test leg (SCRAM) Runs in SCRAM infrastructure Consumes build hosted on primary machine Returns result summary to primary machine (via SCRAM.exe/XML file)

Слайд 60

$Gates - Execution Contd. Environment %binFolder% - %inetroot%\build\wtt_checkin %workFolder% - %inetroot%\build\wtt_checkin\work %parm% - Value from...$

Описание слайда:

Gates - Execution Contd. Environment %binFolder% - %inetroot%\build\wtt_checkin %workFolder% - %inetroot%\build\wtt_checkin\work %parm% - Value from WTT job parameter %workFolder%\WTTFlag.tmp – indicates running in the gates %binFolder%\SetExternalReferences.cmd Sets things like %StatisticsDatabaseServer%, %QueueProcessorServer%, etc.

Слайд 61

Описание слайда:

Gates - Tasks Task Intro Single script under %binFolder% Invoked from WTT job task Format Set up gate-specific variables (includes getting WTT job parameters) Log task start in [Statistics].[dbo].[GateTask] Determine if task can run (disabled, pre-req missing, aborted) Task setup – E.g. restoring DBs, stopping/starting services Task logic – E.g. running “build” command Evaluate result – Write as semaphore file to %workFolder% Finalize the task in [Statistics].[dbo].[GateTask] Update task detail in [Statistics] Exit

Слайд 62

Описание слайда:

Gates - Tasks Contd. Primary Machine Preparation Sync Apply Changelist Pre-Checkin Checks Pre-Build Preparation Build Retail-platform (if applicable) Build Retail-application (if applicable) Post-Build Schedule Tests Deploy MSTest Tests (C# UTs) Xref-selected tests (if applicable) Unit tests (X++ CITs) * Wait Submit Bug Update Log Copy

Слайд 63

$Gates - Tasks Contd. Adding a task Create a task script Create it under %inetroot%\build\wtt_checkin\.cmd Add the task to the WTT job (usually...$

Описание слайда:

Gates - Tasks Contd. Adding a task Create a task script Create it under %inetroot%\build\wtt_checkin\.cmd Add the task to the WTT job (usually requires a new job version) Update determine results to evaluate if the task ran, passed or failed Create the task code in [Statistics].[dbo].[GateTaskCode] Create the task exit codes in [Statistics].[dbo].[GateTaskExitCode] Update GCM and DB to include configuration of the task. Create the shell for GateTask to execute it locally (create it under %inetroot%\build\wtt_checkin\FE.cmd) Update GateTask.cmd to include the option and execution for the task

Слайд 64

Описание слайда:

Gates - Fast Build Consists of multiple processes to shorten gate execution time by using “seed” builds Processes use common infrastructure %inetrot%\Build\wtt_checkin\FastBuild\...

Слайд 65

Описание слайда:

Gates - Fast Build Eligibility Eligibility for each process evaluated at the start of the checkin Sets flag that’s evaluated during the execution of the fast build process

Слайд 66

Описание слайда:

Gates - Fast Build Execution Valid seed build if: All churned files themselves qualify for the fast build process Sync point of seed build is greater than the defined minimum changelist

Слайд 67

Описание слайда:

Gates - Fast Build : FastApp Uses regular rolling builds of the platform to skip building of the platform at check-in time Eligible check-ins also skip BVT, MSTest, Primitive and Stress test tasks Impact: shortens checkins by up to 40% Invalidated by: Platform changes: build\ax_tools\bin\DirsFilterManager.exe GetBuildDirectories –FilterGroup Platform One or more files not in whitelist: build\wtt_checkin\FastBuild\FastAppBuildWhitelist.txt One or more files in blacklist: build\wtt_checkin\FastBuild\FastAppBuildBlacklist.txt Retail team – can still use static platform build but forced to run BVT/MSTest tasks still FAQ for more details, FAQ on Troubleshooting failures

Слайд 68

Описание слайда:

Gates - Fast Build : NightlyBootstrap Uses nightly build’s DemoData bootstrap instead of building from scratch. Prior to retail-application, discovers and copies bootstrap local At build time, consume the bootstrap in \axpackage\dbsync\ In the Post-Build task, skip loading of DemoData Impact: saves ~14 minutes Invalidated by changes to: DP.exe Build infrastructure DemoData data set or post-import scripts FAQ on disabling the process

Слайд 69

Описание слайда:

Gates - Symbol/binary indexing Every gate build indexed to Deduplication and filtering of binaries (RemoveDuplicates.exe) Location set in branch config as %GateSynShare% Process invoked in Post Build Build\wtt_checkin\CheckinBuildDrop.cmd Space-based retention handled by the file share Additional Documentation here

Слайд 70

Описание слайда:

Gates - Synthetic Checkins Service scheduling regular test checkins to assess the stability of a branch/checkin path Windows service hosted on RDVMHL1109-05 Source in BuildServices branch at \build\source\SyntheticCheckinService Current flavors: SyntheticCheckin – default type, executes like a typical checkin in the branch BuildOnly – executes a checkin that just does a build in a dedicated pool Differentiated in reporting on [Statistics].[Stats].[SyntheticType]

Слайд 71

Описание слайда:

Gates - Reporting / Alerts MBSUSP MBSRPT Email Status Volume Build Breaks Offline Machines Queue Cycle Report …many many more…

Слайд 72

Описание слайда:

Gates - Statistics DB / BuildService Statistics Primary repository of gate execution and configuration data Lives on dcsredbbcfs01 FAQ on common tables Exposed via BuildService (for new development) BuildService WCF Service Expose gate data from [statistics], [unittests]; build data from [dynamicsaxbuilds] Source in BuildServices branch - \build\source\BuildService Hosted on dcsrdgtdfs01

Слайд 73

$Gates - Development Task Source %inetroot%\build\wtt_checkin\... Tools Source %inetroot%\build\ax_tools\... %inetroot%\build\source\......$

Описание слайда:

Gates - Development Task Source %inetroot%\build\wtt_checkin\... Tools Source %inetroot%\build\ax_tools\... %inetroot%\build\source\... %inetroot%\build\scripts\... WTT Artifacts Checkin jobs - $\GatedCheckin Utilities/Maintenance - $\GatedCheckin\Utilities

Слайд 74

$Gates - Development Contd. Maintenance and core tools BuildServices branch %inetroot%\build\wtt_checkin\MachineConfiguration\......$

Описание слайда:

Gates - Development Contd. Maintenance and core tools BuildServices branch %inetroot%\build\wtt_checkin\MachineConfiguration\... %inetroot%\build\wtt_checkin\ Test environment Run locally using “gatetask” command Redirect to private WTT pools Create new synthetic checkin type

Слайд 75

Описание слайда:

Gates - Monitoring / Analysis Gated Checkin Monitor (GCM) Gate/build monitoring dashboard Quick access to common actions (e.g. Resubmit, diff, incident creation) Gate configuration Queue processor by branch Gate tasks by branch Source in ‘BuildServices’ branch %inetroot%\build\source\GatedCheckinMonitor\... Logs Console log vs. build.exe vs. detail log

Слайд 76

Описание слайда:

BuildTracker Managed Builds

Слайд 77

Описание слайда:

BuildTracker Builds - Official Builds Purpose Produce a ship-quality build All infrastructure in place to be ‘All On’ Provide a rollup of changes to validate against Cadence Runs daily with sporadic OOB runs Kick-off staggered across branches RainMain* – 9pm PST RainFND* – 10pm PST

Слайд 78

Описание слайда:

BuildTracker Builds - Buddy Builds Purpose Provide engineers with a private build containing their pending changes to be used in pre-checkin validation. Cadence On-demand/user initiated Initiated either directly from the BuildTracker web UI or by running “buddybuild –c ” in CoreXT Permissions controlled by groups: redmond\bbscramu europe\axsrcacc_ram Resources Jobs– SCRAM Buddy Build-Redmond – Platform, SCRAM Buddy Build-Redmond - Application Machine pool – Redmond – Rainier Buddy Build Drop share - \\dcsrdblddrop03\Build1\BuddyBuilds\Rainier Retention is space-based and managed external to BuildTracker

Слайд 79

$BuildTracker Builds - Buddy Build Wizard Binaries/Configuration - %inetroot%\build\BBCheckinWizard Source locations Source control grid (first...$

Описание слайда:

BuildTracker Builds - Buddy Build Wizard Binaries/Configuration - %inetroot%\build\BBCheckinWizard Source locations Source control grid (first screen): build\Source\CheckinWizard\src\CheckinComponents\Generic\ Buildtracker screen (second screen): build\BTCheckinWizard\ExternalContributors\Produc\ Managed pack share Location - \\dcsrdblddrop03\BuddyBuildPackages Retention – 30 day policy

Слайд 80

Описание слайда:

BuildTracker Builds - Rolling Builds Purpose Provide faster build/validation cycle than nightly official builds Cadence RainFND Rolling Master 4x per day Initiates PDL runs per build

Слайд 81

Описание слайда:

BuildTracker Builds - Jobs

Слайд 82

Описание слайда:

BuildTracker Builds – Master Builds

Слайд 83

Описание слайда:

CodeSign Authenticode versus Strong Name Signing process Delay signing Authsign.exe Certificates Non-standard formats/processes CSPKG APPX ClickOnce/VSTO VSIX Packages (general) Links: CodeSign – CodeSignInfo –

Слайд 84

Описание слайда:

Localization LSBuild Command line build tool to create localized product files Uses English version of file as input Consumes LCL files provided by MBSI %inetroot%\source\translation\LCL Use various parsers to determine what to do Only one custom one – KTD files

Слайд 85

Описание слайда:

Localization - Contd. PseudoLoc Simulated localized content Intended to catch localization problems as early as possible Pseudoloc examples from AX 2012 R3 Build Legs Localization-initialize – copies drop\translation to release share Localization-server – Builds localized KTD files Retail-Platform - \source\Platform\Localization\GeneratedPASS2 Retail-Application - \source\net64resources Build localized resource files %inetroot%\build\localization\localization.binaries.config.xml Translation-submit – Signs and submits localized files to \source\translation\

Слайд 86

Описание слайда:

QE / LMC Quality Essentials (QE) Set of validations focused on ensuring overall release quality Regulatory/legal Industry standards Customer Experience Security Consistency with Microsoft Engineering Policies More information - Last Minute Checks (LMC) Executes QE and Org-specific build quality checks Example from DAX62

Слайд 87

Описание слайда:

Post-ship activities Local and long-term backup Source code archive Symbol index/archive

Слайд 88

Описание слайда:

Visual Studio Online (VSO) What is VSO? Our instance: VSO-hosted Source control via Git Work item tracking Build definitions Build requests/scheduling/reporting On-Premises Build controller/agent – RBLD0071AC-TFS Build drops - \\DCSRDBLDDROP04\Build1\Drop

Слайд 89

Описание слайда:

In-Market

Слайд 90

Описание слайда:

AX6.x Product AX 2012 Technet site AX 2012 Architecture AX 2012 MSDN Developer site

Слайд 91

Описание слайда:

AX6.x Product Contd. AX32.exe – Win32 client AX32Serv.exe - Server component running as a Windows Service MorphX – development environment Model store – database storing the P-code representing the application inside the platform AXDBBuild_Model – build-time instance name AXDBDev_Model – runtime instance name build/gates/deploy.cmd AXDB – common runtime instance name on other lab machines Business database – application database housing the data model for business logic AXDBDev – runtime instance name

Слайд 92

Описание слайда:

Lab Footprint (In-Market)

Слайд 93

Описание слайда:

In-Market Branches

Слайд 94

Описание слайда:

Servicing Concepts Dependency toolset Hotfix Binary vs. Application Rollup Cumulative Update (CU)

Слайд 95

Описание слайда:

CoreXT - Our Environment Overview Current version – v1 Build.exe to each project node SYNCHRONIZE_BLOCK, SYNCHRONIZE_DRAIN and dirs file ordering used to drive build ordering Custom ‘mydirs’ logic used to partition the build tree corresponding to custom build types Binplace, Placefiles/miscfiles both supported

Слайд 96

$CoreXT - MSBuild Current Version – v4.0 Build.exe to MSBuild Handoff Automatically included in all project makefiles via \build\makefile.inc...$

Описание слайда:

CoreXT - MSBuild Current Version – v4.0 Build.exe to MSBuild Handoff Automatically included in all project makefiles via \build\makefile.inc \build\makefiles.msbuild creates a response file (msbuild.rsp) in the project directory and invokes msbuild.exe directly. MSBUILD_PROJECT in sources

Слайд 97

Описание слайда:

CoreXT - Build Build.exe Windows build tool Orchestrator for building/traversing the build graph Our version – 4.22.4093 ‘dirs’ and ‘sources’ i386 is default build target Depth-first Traversal of Dirs SYNCHRONIZE_BLOCK/DRAIN Filter on platform tokens {i386}, {amd64}

Слайд 98

Описание слайда:

CoreXT - Build Contd. PASS[0|1|2] PASS0 – Generation of files, copying of static content PASS1 – C++ compilation PASS2 – C++ linking, managed code builds, setup/packaging, binplacing PASS2_BINPLACE – binplacing of built bits (mostly from PASS2) Project Inclusion Integrating your project into CoreXT’s build Dirs, sources, makefile, makefile.inc, placefile

Слайд 99

Описание слайда:

CoreXT - mydirs If a “mydirs” file is present in a directory, build.exe will use it instead of any “dirs” file to determine what to traverse in that directory. CoreXT build logic to copy/rename “mydirs.” to “mydirs” when matches the current build command.

Слайд 100

Описание слайда:

CoreXT - Build types

Слайд 101

Описание слайда:

CoreXT - Layer Build Builds the application component for a specific workload on a specific layer Near 1:1 mapping of Product workload : Layer Exceptions – industry solutions in DAX6HF and DAX5SP1HF Settings for layer product: \build\productConfig.cmd Example: call %inetroot%\build\productConfig.cmd -Product RUPayrollSE Build command: build layer .product: Example: build layer .product:FoundationSE

Слайд 102

Описание слайда:

CoreXT - Layer Build Contd.

Слайд 103

Описание слайда:

CoreXT - Layer Build Contd.

Слайд 104

Описание слайда:

CoreXT - Layer Build Contd.

Слайд 105

Описание слайда:

CoreXT - Layer Build Contd.

Слайд 106

$CoreXT - VCSDef MorphX version control settings defined in dynamically-generated file %inetroot%\Definition\VCSDef.xml Defines source/label file...$

Описание слайда:

CoreXT - VCSDef MorphX version control settings defined in dynamically-generated file %inetroot%\Definition\VCSDef.xml Defines source/label file locations for the models in the current layer Layer template location: %inetroot%\build\ax_public\deployment\tools\vcsdef_.xml Template values expand from branch and product configs (e.g. label ID ranges) Changing layers: SetStartupLayer

Слайд 107

Описание слайда:

CoreXT - Label Files AX Label (.ald) files edited through the label editor in MorphX. 1..* label files per layer product Located under %inetroot%\source\application\labels LabelUtil command – validates correctness of label files prior to submitting

Слайд 108

Описание слайда:

CoreXT – Deploy.cmd Installs the AX components onto a developer’s machine and initializes the developer environment Discovery of latest official build Initialize test environment (import of framework and tests) Used for local developer and gated check-in deployments Source: \build\ax_public\deployment\...

Слайд 109

Описание слайда:

Gates

Слайд 110

Описание слайда:

Gates - Execution

Слайд 111

Описание слайда:

Gates - FastKernel Uses a pre-build kernel build to seed the gate process and skip the retail-kernel and retail-amd64 builds Seed build share: \\dcsrdgtdfs01\KernelSeedDropShare Impact – can save over 60 minutes per checkin Invalidated by: One or more files not in whitelist: build\wtt_checkin\FastBuild\FastKernelBuildWhitelist.txt One or more files in blacklist: build\wtt_checkin\FastBuild\FastKernelBuildBlacklist.txt

Слайд 112

Описание слайда:

Gates - FastApp Uses a pre-build application drop to replace the layer build done prior to PreSubmitSDDump Seed builds come from the Rolling Hotfix BuildTracker jobs Impact – can save over 3 hours per checkin Invalidated by: One or more files not in whitelist: build\wtt_checkin\FastBuild\FastAppBuildWhitelist.txt One or more files in blacklist: build\wtt_checkin\FastBuild\FastAppBuildBlacklist.txt

Слайд 113

Описание слайда:

Gates - SDDump Process used to capture the affected elements of a change Dependency data submitted to a central DB on DCSRDRPTSQLA Dependency Database per servicing branch: DependencyDB_ Data later used to generate a dependency bucket for hotfix packages SDDump Validation Macro (Pre-Checkin & Pre-Submit SDDump) Changelist is unique Changelist description contains bug ID Bug is in the expected state and contains a valid KB number Checkin layer is enabled for servicing Micro (Pre-Submit SDDump) Changes don’t result in deleted elements Changes don’t result in elements reverting to base layer logic

Слайд 114

Описание слайда:

Gates - SDDump Contd. Create scripts to revert/restore non-X++ changes Prepare environment without changes applied

Слайд 115

Описание слайда:

Gates - Multi-product Check-in Only in DAX6HF Checkin workflow to validate changes to multiple industry solutions in a single checkin Enables SYP and dependenent overlayered chanes to IS solutions to be submitted in one change Primary machine does submit and post-submit SDDump

Слайд 116

Описание слайда:

BuildTracker Managed Builds

Слайд 117

Описание слайда:

BuildTracker Builds - Rollup Purpose Produce a full kernel + application build to the tip of the current depot state Checkpoint build to execute automations against BVT, BAT, Full X++, Full Best Practice, LMC Refresh localization binaries that subsequent hotfix builds will use Build type for Cumulative Update releases Produces update package for all changes since RTM Cadence Full Rollup master with validation occurs ~3 times per week Runs daily when stabilizing a CU release

Слайд 118

Описание слайда:

BuildTracker Builds - Application Hotfix Purpose Produce a granular hotfix containing the X++ change fixing a specific product issue + any dependent change since RTM Builds Application against RTM kernel to assert no dependency taken on binary hotfixes Cadence On-demand. Auto-initiated in R3 branches on successful check-in. Otherwise manually initiated by issue owner. Also produced as part of Rolling Hotfix schedule

Слайд 119

Описание слайда:

BuildTracker Builds - Binary Hotfix Purpose Produce a cumulative build of the kernel and frameworks components Create patch installers (.msp) to apply fix to existing deployments Cadence On-demand. Also produced as part of Rolling Hotfix schedule

Слайд 120

Описание слайда:

BuildTracker Builds - Jobs

Слайд 121

Описание слайда:

UA Build

Слайд 122

Описание слайда:

UABuild – Overview (Core Concepts) UABuild – UABuild is our documentation build process Content is generated for word doc format, AX Help Server format, MSDN, and Technet format. DXStudio – Content editor used by writers Content is store in DB: Axapta01 on DBServer: DCSRDUASQL01 CoreXT/SD – Used for source control and to build content branch: MainUA Get For Build – Process to pull content from DXStudio and check it into Source Depot.

Слайд 123

Описание слайда:

UABuild – Core Build Types A GFB (Get For Build) pulls content from a DxStudio project into Source Depot HXS Build – Builds content into HxS format, and optionally publishes the compiled content to MTPS (MSDN or TechNet) using DxPublisher HelpServer -- Builds content into a format suitable for the Dynamics AX Help Server DocBuild – Builds content into Doc, Chm, and/or PDF formats. ManagedReference -- Builds MRef content into HxS format.

Слайд 124

Описание слайда:

UABuild - Core Build Flow

Слайд 125

Описание слайда:

Daily Activities

Слайд 126

Описание слайда:

Assessing Official Build State Nightly builds scheduled, ran as expected, kicked off test runs Expected state - everything runs as scheduled and finishes in a timely manner Troubleshooting - For scheduling problems, check BuildTracker. For failures and extended execution times, analyze the build logs. Evaluate build drop share resource check report Expected state - all drop shares report a healthy amount of free space Troubleshooting - if any drop shares show errors about low space (like the one linked above) Run the bt.exe tool to get failed retention jobs and retry them. If they continue failing, manually delete the drops If all retention jobs are passing, investigate if per-build size has increased or retention policies have changed to result in more or larger builds on the drop. Log bugs accordingly

Слайд 127

Описание слайда:

Assessing BuddyBuild State Check on buddy build queue Expected state - majority of the time the queue is shrinking or 0 and jobs are completing (queue can be growing during peak times) Troubleshooting - Check on machine availability (e.g. are any offline). Check if running jobs are experiencing hangs or other systemic issues causing them to take longer

Слайд 128

Описание слайда:

Assessing Gated Check-in State Check queue length on MBSRPT Expected state - Queue as small as possible Troubleshooting Queue processor not running If queue is closed due to a break, work with owner of the issue to drive to resolution then reopen the queue. Check if checkins are taking longer to complete or if there are fewer resources available to schedule against Check running checkins Expected state - no checkins experiencing systemic issues resulting affecting the execution of the gate workflow Troubleshooting – check WTT for machine states, check recent changes to build\wtt_checkin

Слайд 129

Описание слайда:

Assessing Gated Check-in State contd. Look through latest failures Expected state - All failures have been classified with incidents, all non-dev induced incidents have bugs Check machine pools Expected state - All machines in the gate WTT pools are heartbeating and are in a ready or running state Troubleshooting If the machine is ping-able and you can connect, log on and try cycling the WTTSvc windows service. You may need to change the machine status in WTT studio to Unsafe if it has been without a heartbeat for an extended time If you can't connect, log an issue through for someone in the lab to take a look In either case, if a checkin job was interrupted when the machine lost heartbeat, be sure to inform the owner and resubmit their checkin/abort the old one.