https://pantsbuild.org/ logo
Powered by
#development
  • g

    gorgeous-alligator-94763

    10/10/2017, 11:38 PM
    🙂
  • w

    witty-crayon-22786

    10/11/2017, 4:22 PM
  • w

    witty-crayon-22786

    10/11/2017, 4:23 PM
  • a

    average-vr-56795

    10/11/2017, 4:23 PM
    Thanks 🙂
  • w

    witty-crayon-22786

    10/11/2017, 4:23 PM
    (oh, nvm: hasn't started yet)
  • r

    rough-minister-58256

    10/11/2017, 4:23 PM
    afaict, git-lfs only exists in Github Enterprise?
  • r

    rough-minister-58256

    10/11/2017, 4:23 PM
    wasn’t able to find any hosting offerings for normal oss repos
  • w

    witty-crayon-22786

    10/11/2017, 4:24 PM
    ah.
  • r

    rough-minister-58256

    10/11/2017, 4:24 PM
    github does write their own impl of git-lfs too thats open sourced
  • r

    rough-minister-58256

    10/11/2017, 4:24 PM
    but it’d be awesome if we didnt have to host our own
  • w

    witty-crayon-22786

    10/11/2017, 4:24 PM
    yea, no thanks. the pantsbuild bank account is sufficiently healthy to pay for something hosted.
  • r

    rough-minister-58256

    10/11/2017, 4:25 PM
    yeh
  • r

    rough-minister-58256

    10/11/2017, 4:25 PM
    afaict there are no hosted git-lfs offerings, which seems crazy
  • w

    wide-energy-11069

    10/11/2017, 4:25 PM
    this is only for oss yeah? we would still have to somehow sync it internally
  • w

    witty-crayon-22786

    10/11/2017, 4:25 PM
    @wide-energy-11069: we already have scripts for that.
    👍 1
  • a

    average-vr-56795

    10/11/2017, 4:26 PM
    The other thing we could do is just store a big content-addressed pile of binaries somewhere, and only version control the name -> content-digest mapping. But I guess that's just re-implementing git-lfs
  • w

    witty-crayon-22786

    10/11/2017, 4:26 PM
    and the s3 setup for the actual hosting is solid
  • r

    rough-minister-58256

    10/11/2017, 4:26 PM
    yeh we’d still have to serve the artifacts from an HTTP endpoint for consumption
  • w

    witty-crayon-22786

    10/11/2017, 4:26 PM
    @average-vr-56795: right... at least in this case that would be preferable to git-lfs most likely.
  • w

    witty-crayon-22786

    10/11/2017, 4:27 PM
    had previously discusssed
  • r

    rough-minister-58256

    10/11/2017, 4:27 PM
    guess we could just use S3 directly as the source of truth
  • r

    rough-minister-58256

    10/11/2017, 4:28 PM
    kill the actual storage of binaries in pantsbuild/binaries
  • r

    rough-minister-58256

    10/11/2017, 4:28 PM
    and just version control the build + sync scripts
  • r

    rough-minister-58256

    10/11/2017, 4:28 PM
    seems reasonable
  • r

    rough-minister-58256

    10/11/2017, 4:29 PM
    build + sync + name->content digest
  • r

    rough-minister-58256

    10/11/2017, 4:29 PM
    tho non-deterministic builds could leak S3 resources
  • a

    average-vr-56795

    10/11/2017, 4:31 PM
    How does the setup actually work today?
  • w

    witty-crayon-22786

    10/11/2017, 4:32 PM
    @average-vr-56795: commit to git as source of truth, then sync to an s3 bucket
  • r

    rough-minister-58256

    10/11/2017, 4:33 PM
    but we’re already exceeding the soft quota of 10GB for github repos
  • r

    rough-minister-58256

    10/11/2017, 4:33 PM
1...352353354...906Latest