11
34
Fork
You've already forked request-access
2

Access request #375

Closed
opened 2023年06月23日 21:38:09 +02:00 by Volker_Weissmann · 1 comment

Hi, I'd like to request access to the codeberg CI for my project.

Since the project attemps to rewrite the build system of OpenFOAM, a FOSS software that takes hours to compile on my machine, the CI will take a bit longer. I hope that does not conflict with the "Resource usage must be reasonable for the intended use-case" rule.

See also: https://develop.openfoam.com/Development/openfoam/-/issues/2718

Hi, I'd like to request access to the codeberg CI for [my project](https://codeberg.org/Volker_Weissmann/foam_meson). Since the project attemps to rewrite the build system of OpenFOAM, a FOSS software that takes hours to compile on my machine, the CI will take a bit longer. I hope that does not conflict with the "Resource usage must be reasonable for the intended use-case" rule. See also: https://develop.openfoam.com/Development/openfoam/-/issues/2718
Owner
Copy link

Hmm, generally we want to offer CI even for complex projects, but since our resources are currently still very limited, it might not yet suit your needs. The main problem is that computing usage varies a lot over the day. For example, if you start your project, you'd probably block computing for some hour(s), while for the rest of the day, the machines mostly idle. We are not fond of scaling up right now, because we already waste a lot of computing power for most of the day which is not used, but have some short spikes.

That said, I'll grant you access. Please try not to run your job continously and ideally check with the Matrix channel to receive feedback if your project jams the queue.

If it is an option, consider running your job outside of the CEST-evening (say 16.00 to 23.00 CEST), because this is the period with most traffic on Codeberg right now.

... at least until we have enough usage that justifies more computing power dedicated to CI.

Hmm, generally we want to offer CI even for complex projects, but since our resources are currently still very limited, it might not yet suit your needs. The main problem is that computing usage varies a lot over the day. For example, if you start your project, you'd probably block computing for some hour(s), while for the rest of the day, the machines mostly idle. We are not fond of scaling up right now, because we already waste a lot of computing power for most of the day which is not used, but have some short spikes. That said, I'll grant you access. Please try not to run your job continously and ideally check with the Matrix channel to receive feedback if your project jams the queue. If it is an option, consider running your job outside of the CEST-evening (say 16.00 to 23.00 CEST), because this is the period with most traffic on Codeberg right now. ... at least until we have enough usage that justifies more computing power dedicated to CI.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg-CI/request-access#375
Reference in a new issue
Codeberg-CI/request-access
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?