• Runtimes

  • ci/cd pipeline for building art assets

    inglese

Trying to figure out the best way to set up a CI/CD pipeline to automatically build assets and export them to an S3 bucket.

Main thought right now is to use AWS Lambda that gets triggered on pushes to our main branch. The lambda would download latest linux Spine binary using our licensed link, clone repo with assets, run spine.sh against the assets, upload built files to S3 bucket.

Am curious when it comes to licensing if there is any issue with this approach? If there are issues, what is the recommended way for us to get an automated build pipeline?

Related Discussions
...

  • Mario

  • Messaggio #3
  • Questo post è in inglese

Regarding the technical side, your approach sounds good. The only issue that might crop up is that the machines executing the lambda don't have a GPU (or software GPU implementation) which would prevent Spine from exporting. Only one way to find out 🙂

Regarding licensing, if you are a Spine Enterprise customer, you need to buy an additional seat for your CI/CD pipeline.

25 giorni dopo

Thanks for the response @Mario !

We upgraded to enterprise license. With this new license, we are planning to download Spine in the container and run the following command to install. This will occur each time the pipeline runs using a script in the container. Please let us know if this approach doesn't make sense.

./Spine.sh --install <activation_code>

since each time the pipeline runs it is technically a new container/computer – will each of those instances be a hit to our license or will they grouped within one user?

  • Davide ha risposto a questo messaggio

    • Davide

    • Messaggio #5
    • Questo post è in inglese

    akchiru

    The seat dedicated to your builds can be activated as many times as needed by your pipelines. The purpose of this special license is to avoid raising any red flags due to the number of activations by pipelines.