Development blueprints

• UI views
  • Base layouts
    • base
    • base_rightbar
  • UI widgets
    • UI shortcuts
    • Sidebar items
• Uploading packages
  • Pipeline considerations
• Build instructions
  • Desired features
    • Control of architectures
    • Build architecture for arch-all builds
    • Control the build backend and the associated build environment
    • Control DEB_BUILD_PROFILES and DEB_BUILD_OPTIONS
    • Control workers assigned for specific packages/tasks
    • Control packages tested during autopkgtest of reverse dependencies
  • Proposed changes
    • Changes to the sbuild workflow
    • Changes to the Sbuild task
    • Changes related to the worker requirements feature
• Debian pipeline
  • CheckInstallability task
• Detecting regressions
  • Goals and requirements
  • Implementation of QA results regression analysis
    • For lintian
    • For autopkgtest
    • For piuparts and blhc
  • About the UI to display regression analysis
• URL redesign
  • Current URL structure
  • Use /-/ as path to non-data URL components
  • Leave /api/ as a toplevel special case
  • Remove /workspace/
  • URLs that should not be scoped
  • Restructure accounts
    • work-request/
  • Artifact URLs
    • /<scope>/artifact/<int:artifact_id>/
    • /<scope>/artifact/<int:artifact_id>/file/<int:file_in_artifact_id>/<path:path>
    • /<scope>/artifact/<int:artifact_id>/raw/<int:file_in_artifact_id>/<path:path>
    • /<scope>/artifact/create/
    • /<scope>/artifact/<int:artifact_id>/download/*
• URL redesign for /-/user
  • Current URL structure
  • Proposed URL structure
  • Permission checking
• Dynamic cloud compute scaling
  • Image building
  • Scheduler
  • User interface
• Workspaces for experiments
  • Parameters for the experiment
  • Experiment names
  • Ephemeral groups
  • Experiment workspace name
  • Experiment workspace contents
  • Expiration of experiment workspaces
  • Copying WorkflowTemplates
  • New server tasks
  • Permissions
  • Further desired features
  • Proposed changes
• Refactoring page titles
  • A basic refactoring proposal
    • Describing a page visually
    • Move titles to the base template
    • Introduce the concept of parent pages
    • Pages that may have multiple parents
    • Experiment with layouts
  • A more comprehensive proposal
• More flexible workflow templates
  • Possible future work
    • Nested structures
    • Additional variable templating
  • autopkgtest parameter choice restrictions
• Tag-based scheduling
  • General assumptions
  • Use cases
    • Replace BaseExternalTask.can_run_on
      • Potential tag-based solution:
      • Security boundaries:
    • Some packages are only built on “large” builders
      • Potential tag-based solution:
      • Security boundaries:
    • Official Debian packages need to be built on official Debian workers
      • Potential tag-based solution:
      • Security boundaries:
    • Official Debian workers only build packages uploaded by Debian developers or maintainers
      • Potential tag-based solution:
      • Security boundaries:
    • Have workers that are dedicated to specific scopes / workspaces
      • Potential tag-based solution:
      • Security boundaries:
  • Building tag sets for scheduling
    • Tag merging, validation and derivation
    • Workers providing tags
    • Workers requiring tags
    • Tasks providing tags
    • Tasks requiring tags
  • Draft tag ontologies
    • Worker-provided tag ontologies
      • worker:class
    • Task-provided tag ontologies
      • task:class
  • Postponed elements
    • Generate tags from task statistics
    • Supersede subject and runtime context
    • Scheduling preferences
    • Determining demand for worker pool provisioning