Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST] Automation that Compiles and Uploads to LakeFs #19

Open
Lypsolon opened this issue Sep 18, 2024 · 2 comments
Open

[REQUEST] Automation that Compiles and Uploads to LakeFs #19

Lypsolon opened this issue Sep 18, 2024 · 2 comments
Assignees

Comments

@Lypsolon
Copy link

Lypsolon commented Sep 18, 2024

Preamble

Currently building C++ software is fully manual.
This is very time consuming for the developer.

Request

Build an automation that is aware of the project-depending build process in a repo and upload the output to lakeFs.

Specs

  • Compile based on given commands/parameters
  • Projects that use Ayon-Automator(to be renamed) should use its system to automate the build and tests
  • Ensure that changes in the build process dont need the workflow to change (CMake to Bazle)
  • Make the Compile output available to the workflow user
  • Upload the correct output to lakeFs using a LakeFs commit
  • Automatically push the build artifacts main / when a release is created
  • Creat new LakeFs branches from GitHub branches and upload load artifcts onto them automatically. (For Testing)
@Lypsolon Lypsolon added the feature Additional functionality which doesn't exist yet label Sep 18, 2024
@Lypsolon Lypsolon changed the title Your issue title here [REQUEST] Automation that Compiles and Uploads to LakeFs Sep 18, 2024
@philnewm
Copy link
Collaborator

@Lypsolon where can I find the commands currently used to do that?
Just to get a general overview

@Lypsolon
Copy link
Author

@Lypsolon where can I find the commands currently used to do that? Just to get a general overview

the ayon cpp api is currently the furthest in temrs of ease of use.
https://github.com/ynput/ayon-cpp-api

the resolver should have this in the future. but it will need to work a good bit different as it needs to build against the different DCCs and all those DCCs need different ENV variables.

this is a small portion of how my internal build setup works for AyonUsdResolver but we did not yet move this into a Corporate Repo(and the method should change soonTM).

os.environ["COMPILEPLUGIN"] = "AyonUsdLinux/AyonUsd23_5_Py39_Linux"
os.environ["AyonUsdRoot"] = os.path.abspath(os.path.expandvars("$HOME/Documents/GitHub/Lyonh/ayon_usd_files/usd-24.03_linux_py39/24.03/"))

python build.py --DEV=0 --JTRACE=0 --Clean

@mkolar mkolar removed the feature Additional functionality which doesn't exist yet label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants