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

Automated builds (CI) #2

Closed
tokejepsen opened this issue Jul 31, 2019 · 9 comments
Closed

Automated builds (CI) #2

tokejepsen opened this issue Jul 31, 2019 · 9 comments
Labels
build Related to building maya-usd repository enhancement New feature or request

Comments

@tokejepsen
Copy link

Goal

Automated the building process on merges.

Motivation

Having precompiled builds would lower the barrier for people wanting to use this plugin.

@xtvjxk123456
Copy link

great idea

@BigRoy
Copy link
Contributor

BigRoy commented Aug 1, 2019

As a reference, Victor Yudin created saturn which automatically builds USD using Appveyor and looking at his latest commits he has been looking into Azure too.

Azure pipelines would be most interesting as it should be able to compile for Windows, Mac OS and Linux.

Potentially @VictorYudin can contribute.

@gplsteph
Copy link

gplsteph commented Aug 2, 2019

+1 for Azure Pipelines

pmolodo referenced this issue in LumaPictures/maya-usd Aug 7, 2019
* Make sure the build and install folders have the variant (#2)
* Enable generating compile_commands.json by default
* Make sure the build and install folders have the variant 
* Fix typo in ReadMe
* temporarily revert line endings to windows to do merge
* standardize on linux-style line endings (newline only)
HamedSabri-adsk added a commit that referenced this issue Aug 9, 2019
* Enable generating compile_commands.json by default
* Make sure the build and install folders have the variant 
* Fix typo in ReadMe
HamedSabri-adsk pushed a commit that referenced this issue Aug 12, 2019
* Make sure the build and install folders have the variant (#2)
* Enable generating compile_commands.json by default
* Make sure the build and install folders have the variant 
* Fix typo in ReadMe
* temporarily revert line endings to windows to do merge
* standardize on linux-style line endings (newline only)

(cherry picked from commit 8073eaf)
kxl-adsk pushed a commit that referenced this issue Aug 23, 2019
mattyjams pushed a commit to mattyjams/maya-usd that referenced this issue Aug 29, 2019
* Check that all_tests target exists before adding dependencies

* add ref to include for OSS build

* use generic boost python

* Use boost python libraries variable

* add assetType metadata to OSS build
murphyeoin added a commit to AnimalLogic/maya-usd that referenced this issue Oct 30, 2019
* Check that all_tests target exists before adding dependencies

* add ref to include for OSS build

* use generic boost python

* Use boost python libraries variable

* add assetType metadata to OSS build
murphyeoin pushed a commit to AnimalLogic/maya-usd that referenced this issue Oct 30, 2019
73ab955 Fix OSS USD Transaction build Autodesk#2 (Autodesk#947)

git-subtree-dir: src
git-subtree-split: 73ab955
murphyeoin added a commit to AnimalLogic/maya-usd that referenced this issue Dec 5, 2019
Get Tests running on PR Autodesk#1 (Added class to provide an API to work with maya transform nodes types)
@HamedSabri-adsk
Copy link
Contributor

Can this issue be closed?

Azure pipelines would be most interesting as it should be able to compile for Windows, Mac OS and Linux.

Yes, Azure pipelines in particular is a good CI/DI system compare to the other ones out there. However, we won't be able to use it at all as this project has a dependency to the Maya binaries which we can't just deploy and use. We are currently exploring other possible solutions to the problem.

@tokejepsen
Copy link
Author

Can this issue be closed?

Has it been implemented, or it not going to be implemented?

@BigRoy
Copy link
Contributor

BigRoy commented Feb 3, 2020

Can this issue be closed?

Preferrably not if this helps us remind to have this as a set goal. If there's a way for automated releases to be pushed on e.g. "major/minor" tags in the near future that would be super helpful for quicker adoption of maya-usd and its updates by the less technically inclined crowd.

A big hurdle of course is also the dependency on USD itself. It raises the question of what version of USD specifically would you bundle with. Always the latest and greatest that works with the maya-usd branch?

@kxl-adsk
Copy link

kxl-adsk commented Feb 4, 2020

Sounds good, we can keep it as a reminder.

@kxl-adsk
Copy link

kxl-adsk commented Jun 9, 2020

FYI. We are actually testing PF for GitHub pull requests. More info will be available soon.

@kxl-adsk
Copy link

kxl-adsk commented May 3, 2021

We have been running GitHub actions for some time now - https://github.com/Autodesk/maya-usd/actions. This allows preflight for every pull request to test against a number of platforms and Maya versions.

Every time we post a new release, we are uploading Maya 2020 and Maya 2022 binaries. We are not anticipating generating and post binaries for every merge we do to the 'dev' branch.

With that said, I'm closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Related to building maya-usd repository enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants