kc3-lang/libjpeg-turbo/ci

Diff

• Show log

  Commit

• Hash : 2d4b2f14
  Author :
  Date : 2016-10-20T17:55:55
  

  Travis: Deploy to S3 rather than SourceForge
  
  This has the following advantages:
  -- It doesn't require checking a private SSH key into the repository.
  (With SourceForge, an SSH key is the "keys to the kingdom".)
  -- If the S3 key is compromised, it is very easy to revoke it and
  generate a new one.
  -- The S3 bucket is isolated, so even if it becomes compromised, then
  the damage that one could do is limited.
  -- It's much easier to manage files through S3's web interface than
  through SourceForge.
  -- The files are served via HTTPS.
  -- Travis fully supports S3 as a deployment target, so this simplifies
  .travis.yml somewhat.
  

• Files

• keys.enc

• Properties

• Git HTTP	https://git.kmx.io/kc3-lang/libjpeg-turbo.git
  Git SSH	git@git.kmx.io:kc3-lang/libjpeg-turbo.git
  Public access ?	public
  Description	Fork of libjpeg with SIMD Upstream Homepage Github Fork Github
  Users
  Tags