<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Create wheels and install/configure automation in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/create-wheels-and-install-configure-automation/m-p/134114#M50023</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Can a notebook be created that pushes new versions of code w/o having to go thru the manual process of creating a whl and other configuration files? In other words, can I create a notebook that will setup/configure and install the wheel? So far all tutorials and demos show several manual steps needed to create a wheel, since our code is likely to change often our team would like to automate the entire creation/update of the wheel including configuration files and code. Is this possible?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Oct 2025 20:04:42 GMT</pubDate>
    <dc:creator>adrianhernandez</dc:creator>
    <dc:date>2025-10-07T20:04:42Z</dc:date>
    <item>
      <title>Create wheels and install/configure automation</title>
      <link>https://community.databricks.com/t5/data-engineering/create-wheels-and-install-configure-automation/m-p/134114#M50023</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Can a notebook be created that pushes new versions of code w/o having to go thru the manual process of creating a whl and other configuration files? In other words, can I create a notebook that will setup/configure and install the wheel? So far all tutorials and demos show several manual steps needed to create a wheel, since our code is likely to change often our team would like to automate the entire creation/update of the wheel including configuration files and code. Is this possible?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 20:04:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/create-wheels-and-install-configure-automation/m-p/134114#M50023</guid>
      <dc:creator>adrianhernandez</dc:creator>
      <dc:date>2025-10-07T20:04:42Z</dc:date>
    </item>
    <item>
      <title>Re: Create wheels and install/configure automation</title>
      <link>https://community.databricks.com/t5/data-engineering/create-wheels-and-install-configure-automation/m-p/134125#M50026</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/70490"&gt;@adrianhernandez&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Technically yes, but it’s not recommended.&lt;/STRONG&gt;&lt;/P&gt;&lt;P class=""&gt;You could technically build everything needed to compile the wheel directly from a Databricks notebook using a &lt;SPAN class=""&gt;setup.py&lt;/SPAN&gt;, and store it in a volume, CodeArtifact, or any supported cloud storage location — provided you have the right permissions (for example, via an instance profile and a dedicated or single-user cluster).&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;However, this approach will likely cause issues in the long run. You won’t be able to properly version or validate your builds, you’ll lose traceability of changes, and eventually, someone will overwrite a working wheel with a broken one — which will be painful to troubleshoot.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;My recommendation is to &lt;SPAN class=""&gt;&lt;STRONG&gt;handle it through a proper repository with version control&lt;/STRONG&gt;&lt;/SPAN&gt; and a &lt;SPAN class=""&gt;&lt;STRONG&gt;CI/CD pipeline&lt;/STRONG&gt;&lt;/SPAN&gt; that validates the wheel, tags the release, and publishes it to an &lt;SPAN class=""&gt;&lt;STRONG&gt;artifact repository&lt;/STRONG&gt;&lt;/SPAN&gt; (e.g., CodeArtifact, Artifactory, or Nexus) that acts as a proxy for all users who need to install it.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;This way you maintain build consistency, version traceability, and deployment reliability — without the hidden risks of manual or in-notebook builds.&lt;BR /&gt;&lt;BR /&gt;Hope this helps :),&lt;BR /&gt;&lt;BR /&gt;Isi&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 22:23:03 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/create-wheels-and-install-configure-automation/m-p/134125#M50026</guid>
      <dc:creator>Isi</dc:creator>
      <dc:date>2025-10-07T22:23:03Z</dc:date>
    </item>
  </channel>
</rss>

