Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 960
    • Issues 960
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11980

Closed
Open
Created Nov 21, 2016 by intrigeri@intrigeriMaintainer2 of 2 tasks completed2/2 tasks

Create and provision a new Vagrant VM for every ISO build

Originally created by @intrigeri on #11980 (Redmine)

… using the basebox encoded in the build branch + a set of APT snapshots derived from what’s encoded in Git.

First of all: benchmark how much it slows down the build, to ensure this is a viable option.

The branch this VM is made for must be encoded in the VM itself, and Vagrant should abort if one tries to reuse it to build another branch (rationale: that other branch may point to an older set of APT snapshots, and then the Vagrant provisioning will try to downgrade the entire system, which won’t work reliably enough for our needs). With this sanity check in, we can add an option to keep the VM running and not delete it (#11981 (closed)), for faster development builds when one works on a branch.

Feature Branch: feature/11980-static-build-env

Parent Task: #5630 (closed)

Related issues

  • Blocked by #11979 (closed)
  • Blocks #11981 (closed)
  • Blocked by sysadmin#11972 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_3.0~rc1
Milestone
Tails_3.0~rc1 (Past due)
Assign milestone
Time tracking
None
Due date
None