Powered by Jets
- Register free runner for your project.
- Running jobs on AWS lambda.
- Access to the website
- Login as GitLab user account
- Login to GitLab Serverless Runner
- Click "Create a new runner"
- Enter the gitlab instance URL (e.g. https://gitlab.com)
- Enter a registration token
- Enter a description for the runner
- Enter runner tags
- Choose Lambda Runtime (See https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html)
And your runner will automatically start requesting jobs.
GET /
... Login pagePOST /
... LoginGET /runners
... Show all runnersGET /runners/new
... Runner creation pagePOST /runners
... Create a new runnerGET /runners/:runner_id
... Show a runner detailGET /runners/:runner_id/edit
... Runner edit pagePUT /runners/:runner_id
... Update a existing runner
POST api/v4/runners
... Registers a new Runner (requires: token)DELETE api/v4/runners
... Deletes a registered Runner (requires: token)
POST api/v4/jobs/request
... Request a job (requires: token)PUT api/v4/jobs/:id
... Updates a job (requires: token, id)PATCH api/v4/jobs/:id/trace
... Appends a patch to the job trace (requires: id)POST api/v4/jobs/:id/artifacts/authorize
... Authorize artifacts uploading for job (requires: id)POST api/v4/jobs/:id/artifacts
... Upload artifacts for job (requires: id)GET api/v4/jobs/:id/artifacts
... Download the artifacts file for job (requires: id)
- MAX_REGISTABLE_RUNNER_COUNT ... The maximum registable runner counts per user
You can start postgres instance by executing bin/start-dev-db
.
Please make sure .env.development
is properly configured, like the following:
# Example .env.development, meant to be updated.
DB_USER=postgres
DB_PASS=mysecretpassword
DB_HOST=localhost
This README would normally document whatever steps are necessary to get the application up and running.
Things you might want to cover:
- Dependencies
- Configuration
- Database setup
- How to run the test suite
- Deployment instructions