Search Unity

Allow publishing build artifacts via an API

Discussion in 'Unity Build Automation' started by liortal, Nov 15, 2016.

  1. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    I've worked with TeamCity in the past (a CI server) which allowed "publishing" various artifacts from the build.

    This used to work by specifying paths (full paths or using wildcards), which would then get copied and published as the build's "results". I could then download those, or go over artifacts from different builds.

    It would be nice to be able to support this with cloud build (for example - using an API).

    You already have the BuildManifestObject for "advanced" uses. I'd like to see more things like that, for example let me run a Post build step that will do something like:
    Code (CSharp):
    1. // Export all .txt files from the output folder (can then download from cloud build dashboard
    2. CloudBuild.ExportArtifacts(new [] { "output/*.txt" });
     
  2. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    Ya I like this idea a lot. Will discuss internally and see how this might fit in with our current plans.
     
  3. tgouala-wellfiredLtd

    tgouala-wellfiredLtd

    Joined:
    Jun 8, 2013
    Posts:
    99
  4. Trisibo

    Trisibo

    Joined:
    Nov 1, 2010
    Posts:
    245