HISE Logo Forum
    • Categories
    • Register
    • Login

    Pamplejuce/Studiorack & Github Actions

    Scheduled Pinned Locked Moved General Questions
    4 Posts 2 Posters 241 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • modularsamplesM
      modularsamples
      last edited by

      Is anyone using Github actions to automate the build process for HISE projects? How hard was it to setup? Was it worth the effort?

      I've come across a couple of projects that suggest that it is possible to (after some initial setup) to build validated, cross platform plugins automatically. [Pamplejuce] (https://github.com/sudara/pamplejuce) (love the name) seems the more mature, better documented project, though Studiorack looks pretty interesting too, but with a broader set of goals.

      As I understand it, once setup a user could build & download a version of a plugin that includes the most recent commit at the push of a button. In my case, this would be (excuse the hyperbole) a game changer!

      Christoph HartC 1 Reply Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart @modularsamples
        last edited by

        Sure you can automate everything using the command line interface of HISE and the projucer.

        https://github.com/christophhart/vcsl_hise/blob/master/build.bat
        https://github.com/christophhart/vcsl_hise/blob/master/build.sh

        modularsamplesM 1 Reply Last reply Reply Quote 1
        • modularsamplesM
          modularsamples @Christoph Hart
          last edited by

          @Christoph-Hart Thanks, these scripts seem reasonable easy to understand. It's just a case of integrating them into Actions, I guess. If I can get it working, I'll see about writing a tutorial.

          Christoph HartC 1 Reply Last reply Reply Quote 1
          • Christoph HartC
            Christoph Hart @modularsamples
            last edited by

            @modularsamples I haven't setup GitHub actions for this repo, but I'm using it for the HISE CI build, which does more or less the same (check out the repo and then run a script):

            name: CI Build
            on: 
              workflow_dispatch:
              push:
                branches: 
                  - develop
            jobs:
              ci_macos:
                runs-on: [self-hosted, macos]
                steps:
                  - name: Cleanup working directory
                    run: rm -rf "${{github.workspace}}" 
                  - name: Checkout HISE repository
                    uses: actions/checkout@v1
                    with:
                      ref: 'develop'
                  - name: Build & Run CI script
                    working-directory: ${{ github.workspace }}/tools/auto_build/
                    run: sh ./build_ci.sh
              ci_windows:
                runs-on: [self-hosted, windows]
                steps:
                  - name: Cleanup working directory
                    working-directory: ${{ github.workspace }}
                    run: del *.* /Q /S
                    shell: cmd
                  - name: Checkout HISE repository
                    uses: actions/checkout@v1
                    with:
                      ref: 'develop'
                  - name: Build HISE CI, run unit tests & export demo project
                    working-directory: ${{ github.workspace }}/tools/auto_build/
                    run: build_ci.bat
                    shell: cmd
            
            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            25

            Online

            1.7k

            Users

            11.7k

            Topics

            102.0k

            Posts