{"id":80112,"date":"2026-11-22T18:09:29","date_gmt":"2026-11-22T18:09:29","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=80112"},"modified":"2026-11-22T18:09:31","modified_gmt":"2026-11-22T18:09:31","slug":"how-to-build-a-reliable-ci-pipeline-for-3d-assets","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-build-a-reliable-ci-pipeline-for-3d-assets\/","title":{"rendered":"How to Build a Reliable CI Pipeline for 3D Assets"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A repository that performs well with source code can become slow and difficult to maintain once a team begins adding 3D models, textures, animations, and generated previews. Unlike text files, binary assets cannot be reviewed through ordinary line-by-line diffs, and even a small change may cause Git to store another large object.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This becomes especially noticeable in web-based 3D applications, games, product configurators, and augmented reality projects. Artists may deliver FBX source files, developers may need GLB files at runtime, and automated builds may create thumbnails or compressed variants. Without clear boundaries, all of these files can end up in the same repository.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A reliable pipeline starts by deciding which assets belong in version control, which should be generated during a build, and which should be stored elsewhere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Classify Assets Before Building the Pipeline<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Treating every 3D file in the same way makes storage and release policies harder to understand. A project should distinguish among three categories.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Source assets<\/strong> are editable working files used by artists. They may include high-resolution meshes, layered textures, rigs, and application-specific project files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Runtime assets<\/strong> are approved files prepared for the application. A web project might use optimized GLB models, while another platform may require a different format.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Build artifacts<\/strong> are files that can be recreated from a known source. Examples include compressed models, generated thumbnails, preview videos, and packaged asset bundles.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Source and approved runtime assets may need version control because they represent intentional creative decisions. Reproducible build artifacts usually belong in an artifact repository, object store, or release package rather than in the main Git history.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This separation prevents the repository from filling with files that can be regenerated on demand.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Define the Accepted Formats<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A pipeline cannot validate assets consistently if every contributor chooses a different format.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Document which formats are accepted at each stage. For example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>FBX as an interchange format for certain editable assets<\/li>\n\n\n\n<li>GLB as the standard runtime format<\/li>\n\n\n\n<li>PNG or WebP for approved textures<\/li>\n\n\n\n<li>JSON for asset metadata<\/li>\n\n\n\n<li>MP4 for generated previews stored outside the source repository<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A browser-based <a href=\"https:\/\/www.meshy.ai\/3d-tools\/file-converter\" rel=\"noopener\">3D file converter<\/a> can help a designer manually convert files such as OBJ, STL, FBX, GLB, and 3MF during asset preparation. However, converting a file does not prove that the result is production-ready.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"512\" src=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2026\/11\/image-49.png\" alt=\"\" class=\"wp-image-80113\" style=\"aspect-ratio:2;width:624px;height:auto\" srcset=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2026\/11\/image-49.png 1024w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2026\/11\/image-49-300x150-1.png 300w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2026\/11\/image-49-768x384.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The converted model may still contain missing textures, unexpected scale, inefficient geometry, unsupported materials, or broken animation data. Format conversion should therefore happen before validation, not replace it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For automated builds, use a command-line converter or project-controlled script whose version can be pinned and reproduced inside the CI environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Configure Git LFS Before Adding Large Assets<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Git Large File Storage replaces large files in the normal Git repository with small pointer files while keeping the binary content in separate LFS storage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Install Git LFS locally, initialize it, and define the file patterns that should be tracked. For a project using GLB and FBX assets, the setup might include:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">git lfs install<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">git lfs track &#8220;*.glb&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">git lfs track &#8220;*.fbx&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">git add .gitattributes<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">git commit -m &#8220;Configure Git LFS for 3D assets&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The .gitattributes file must be committed. This ensures that new clones and forks apply the same tracking rules rather than depending on one contributor\u2019s global configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GitHub\u2019s Git LFS documentation also recommends committing .gitattributes so collaborators receive the repository\u2019s LFS configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tracking an extension does not retroactively remove files already committed through ordinary Git. If large models entered the repository before LFS was configured, their previous versions remain in Git history. Migrating them may require history-rewriting tools and coordination with every contributor who has an existing clone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Teams should plan that migration separately instead of assuming a new tracking rule will reduce the old repository immediately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Add a Machine-Readable Asset Manifest<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Binary files provide little context by themselves. Store a small text manifest beside each approved asset or asset group.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A manifest can record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Asset identifier and human-readable name<\/li>\n\n\n\n<li>Source file and runtime file<\/li>\n\n\n\n<li>Intended platform<\/li>\n\n\n\n<li>Unit scale and orientation<\/li>\n\n\n\n<li>Expected dimensions<\/li>\n\n\n\n<li>Texture dependencies<\/li>\n\n\n\n<li>Animation names<\/li>\n\n\n\n<li>Tool and model version<\/li>\n\n\n\n<li>Prompt or reference source, when applicable<\/li>\n\n\n\n<li>License and attribution requirements<\/li>\n\n\n\n<li>Approval status<\/li>\n\n\n\n<li>Maximum permitted file size<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This information makes automated validation possible and reduces guesswork during later maintenance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If an AI-assisted tool contributed to an asset, record that fact without treating it as a quality guarantee. The file must pass the same technical and visual review as any manually created model.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Build Fast Checks for Every Pull Request<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pull-request validation should catch inexpensive problems quickly. The first job can inspect changed asset paths rather than scanning the entire library.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Useful checks include:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Allowed extensions:<\/strong> Reject unsupported formats in runtime directories.<\/li>\n\n\n\n<li><strong>File-size limits:<\/strong> Flag assets that exceed the team\u2019s established budget.<\/li>\n\n\n\n<li><strong>Filename rules:<\/strong> Prevent spaces, inconsistent casing, and ambiguous names.<\/li>\n\n\n\n<li><strong>Parse test:<\/strong> Confirm that the selected library or engine can open the model.<\/li>\n\n\n\n<li><strong>Manifest presence:<\/strong> Require metadata for every new runtime asset.<\/li>\n\n\n\n<li><strong>Dependency check:<\/strong> Verify that referenced textures and related files exist.<\/li>\n\n\n\n<li><strong>Scale and bounds:<\/strong> Detect objects with implausibly large, small, or offset dimensions.<\/li>\n\n\n\n<li><strong>Material count:<\/strong> Warn when a simple asset introduces an excessive number of materials.<\/li>\n\n\n\n<li><strong>Animation inventory:<\/strong> Compare available clips with the names declared in the manifest.<\/li>\n\n\n\n<li><strong>License field:<\/strong> Block release when ownership or usage information is missing.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Not every threshold should cause an immediate failure. A large hero model may be justified, while the same size would be inappropriate for a background prop. Use warnings for conditions that require judgment and failures for rules that must never be violated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Run Expensive Validation After the Fast Gate<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Geometry analysis, texture conversion, rendering, and engine import tests may take longer. Run these jobs only after basic checks pass.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A deeper stage can inspect polygon counts, degenerate faces, invalid normals, texture dimensions, missing UVs, and unsupported material features. It can also open the asset in a headless engine process and produce a neutral preview render.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The preview is useful for human review, but CI should not claim that it has approved the model\u2019s appearance. Automation can detect a missing texture; it cannot determine whether a character\u2019s expression matches the art direction or whether a product visualization accurately represents the physical item.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Publish the report and preview as pull-request artifacts so artists and developers can review the same evidence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Avoid Committing Generated Outputs<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the pipeline creates optimized assets from editable sources, the resulting files do not always need to return to the repository.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Store reproducible outputs in artifact storage and associate them with the commit hash, pipeline run, and converter version. This preserves traceability without adding a new binary revision to Git after every build.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Release packages can contain the approved runtime files, manifests, checksums, and validation reports. A developer should be able to identify exactly which source commit produced an asset bundle.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Caching can reduce repeated conversion time, but the cache key should include the source-file checksum and relevant tool versions. Otherwise, a build may reuse an output created under different conversion settings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Treat Uploaded Assets as Untrusted Input<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A pipeline that accepts models from external contributors should process them cautiously. File parsers, converters, and rendering tools handle complex binary data and may contain vulnerabilities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run conversion and preview jobs in isolated containers with limited permissions, restricted network access, bounded CPU and memory, and no production credentials. Avoid processing unknown assets directly on privileged, persistent runners.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep conversion tools patched and pin their versions in the pipeline configuration. Log failures without exposing secrets or internal paths.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Make the Asset Handoff Reproducible<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A dependable 3D pipeline does more than move large files through Git. It defines what enters the repository, how each asset is described, which checks are automated, where generated outputs are stored, and where human approval remains necessary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Git LFS addresses one important storage problem, but it is not a complete asset-management strategy. Format rules, metadata, validation, artifact storage, security isolation, and visual review must work together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When those boundaries are explicit, artists can submit assets without guessing what developers need, and engineering teams can introduce new models without turning every release into a manual investigation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A repository that performs well with source code can become slow and difficult to maintain once a team begins adding 3D models, textures, animations, and generated previews&#8230;. <\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[49],"tags":[],"class_list":["post-80112","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/80112","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=80112"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/80112\/revisions"}],"predecessor-version":[{"id":80114,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/80112\/revisions\/80114"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=80112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=80112"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=80112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}