siggame / colisee-builder Goto Github PK

• Push built docker image to docker registry

epic: siggame/colisee#9

The builder is a backend service. Delete frontend stuff that was pulled from the template.

It should probably have one BUILD_ARG, specifying where to copy the zip file from the host machine.

It should

• copy the zip from host
• unzip the zip
• verify a Makefile and run files exist
• install dependencies
• run make

I made the realization that any fully runnable service should be named app and any library (for purposes of easy importing) should be index

• Update db on queued
• Update db onbuilding
• Update db on finished
• Update db on failed

epic: siggame/colisee#9

• Add multipart form support
• Convert .zip archive to .tar archive (if applicable)

epic: siggame/colisee#9

Pipeline description:

• Receive build context (API)
  • Prevent upload of excessively large archives
  • Get appropriate Dockerfile for chosen language
• Prepare build context (Preparator)
  • Convert to appropriate archive format
  • Insert chosen Dockerfile (overwrite existing one)
• Enqueue build context (Build queue)
  • Insert new entry into database
  • Enter into distinct queue for given team_id
• Process queues (Executor)
  • Round robin, but prefer oldest uploads (Dequeue, handled by the map of queues)
  • Limit number building
  • set resource limits on build
  • set timeout on build
• Verify images are pushed to registry (Surveyor/Verifier)
  • Query the image registry to prove existence of image in repo
  • Update db when success verified
• Clean up failed builds (Janitor)
  • update db on failure
  • clean up intermediate stages, occasionally

• Produce list of all submissions
• Produce submission based on id
• Produce submissions based on team name

epic: siggame/colisee#9

Make sure things in the vagrantfile are good, such as the NVM installation.

Should the builder care about updating the db?
Should it be the responsibility of the party enqueueing the build?

No db interaction:

Benefits:

• simpler

Problems:

• More information is needed in POST request
• Relies on outside party to update db properly

similar to limits placed on running clients, this prevents misconfigured builds from getting out of hand

Allow someone to choose the language when uploading. Based on that value choose the correct Dockerfile to insert. If a Dockerfile exists at the top level already, then overwrite it with one the builder owns.

• Ingest .tar archive and build docker image using that context
• Store/Stream output from build

epic: siggame/colisee#9

• Determine file type and convert to .tar
• Prefer in memory storage vs on disk

story: #7

• Add multer as dependency
• Add POST /{team_name} endpoint

story: #7

• Add dockerode dependency

GET /

• report status of all builds

POST /

form: {
    team_id: number, // needed to tag docker image correctly and update db
    build: tar.gz archive
}

• Return build id to request
• enqueue incoming build request
• build image, write archive to storage, push image to registry

GET /build/{id}

id: number

• Return all information for build with {id}