cirrus-ci-docs icon indicating copy to clipboard operation
cirrus-ci-docs copied to clipboard

Documentation for Cirrus CI 📚

Results 133 cirrus-ci-docs issues
Sort by recently updated
recently updated
newest added

# Description Will be nice to have a temporary registry with simplified authentication for repositories to store intermediate containers before pushing to Docker Hub. # Context Right now if you...

feature

# Description Support script instruction which will result in the VM rebooting, requiring the Cirrus agent to re-connect before the next script instruction can run. # Context Occasionally testing low-level...

feature

It'd be useful to see percentages of when caches are hit/missed and also uploaded. A cache that is good today might get broken in future (eg. every build writes into...

enhancement
UX

# Description Need to generate a human readable schema similar to the JSON one: http://json.schemastore.org/cirrus Should describe all the required fields and optional fields as well as "combinable" fields like...

feature

# Description Right now one can only use `only_if` on `task` nodes. It can be useful to allow usage of it on any nodes like `speps` in a `pipe`

feature

# Description It will be nice to support option to have GPUs attached to containers. ```yaml container: image: nvidia/cuda:10.0-runtime-ubuntu18.04 cpu: 4 memory: 12G gpu: 2 gpu_type: nvidia-tesla-v100 # do we...

feature

It will be nice to have a separate status page for Cirrus CI services. Right now the only communication channel is Twitter account [@cirrus_labs](https://twitter.com/cirrus_labs). At least the status page should...

feature
UX

If no other instructions are provided, please run simply the entrypoint or cmd defined in the image metadata. This is a follow up from https://github.com/cirruslabs/cirrus-ci-docs/issues/388#issuecomment-516235417

feature

I had an experience this afternoon that was quite frustrating and where more transparency would have been really helpful. I am trying to run a few PRs, each of which...

feature

# Description Sometimes it useful to have a monotonically increasing number of a task within the same repository for tagging purposes (of builds and other artifacts). `CIRRUS_TASK_ID` is not suitable...

feature