Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #15287
Closed
Open
Issue created Feb 05, 2018 by anonym@anonymMaintainer

Make it possible to reproducibly generate IUKs in CI

Originally created by @anonym on #15287 (Redmine)

Since we’ll generate a lot more of IUKs each release uploading them will be painful for RMs with slow internet connections.

For example, the following VM would do:

  • 4 virtual CPUs (so the IUK generation won’t take too long)
  • 1 GB of RAM (I used to generate IUKs in such a VM two years ago but YMMV)
  • 10 GB /tmp for tails-iuk’s needs, and where we store the generated IUKs (before uploading them to rsync.lizard)
  • Access to Jenkins build artifacts

Feature Branch: feature/15281-single-squashfs-diff

Related issues

  • Related to #17262 (closed)
  • Related to #17361 (closed)
  • Related to #15281 (closed)
  • Related to sysadmin#17385 (closed)
  • Related to #17412 (closed)
  • Blocks #16052
Edited May 15, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking