Ability to freeze execution in custom mode

[huakim]

Is there a way to stop the execution for a certain time in the container in custom script mode?

[FrostyX]

Hello @huakim,
I am not sure if I understand what you are asking. More context may be needed.

You use the custom source method
https://docs.pagure.org/copr.copr/custom_source_method.html#custom-source-method
and in your script you want to wait for some number of seconds?

Then you can probably do something like this: echo "Wait for 5s"; sleep 5; echo "Done waiting"

[huakim]

I have found that when multiple builds are started, the newest builds wait until the older ones are finished, even if after-build-id is not set. If the custom script of the older builds is waiting for the package that needs to be created by the newest build to be started, and the newest build does not start, then the older builds will fail due to the timeout. If older builds can be frozen so that the newest builds can start, then the build will not fail. I believe, that there are an option to freeze and unfreeze manually, or in build process, and also believe there are method to freeze or unfreeze build by schedule manually or in build process

[FrostyX]

I believe, that there are an option to freeze and unfreeze manually, or in build process

There is an option to create your project repository manually
https://docs.pagure.org/copr.copr/user_documentation.html#id7
but I don't think that's what you want

I have found that when multiple builds are started, the newest builds wait until the older ones are finished, even if after-build-id is not set.

This shouldn't be the case. There are some quotas how many builds can one user/project build at once, so this can be why they wait. But unless you are submitting 30+ builds at once, you shouldn't hit this limitation.

My question is how do you submit the builds that this happens to you? Can I reproduce it? Do you use web UI or copr-cli?

[FrostyX]

There was a large build queue yesterday, so some builds also had to wait because of that

Maybe this was the problem?

[huakim]

I believe, that there are an option to freeze and unfreeze manually, or in build process

There is an option to create your project repository manually https://docs.pagure.org/copr.copr/user_documentation.html#id7 but I don't think that's what you want

I have found that when multiple builds are started, the newest builds wait until the older ones are finished, even if after-build-id is not set.

This shouldn't be the case. There are some quotas how many builds can one user/project build at once, so this can be why they wait. But unless you are submitting 30+ builds at once, you shouldn't hit this limitation.

My question is how do you submit the builds that this happens to you? Can I reproduce it? Do you use web UI or copr-cli?

I submitted 206 builds at once, using gui tool https://github.com/huakim/python-copr_wx
Builds are custom scripts which depends on obs_mockbuild, which does check for dependencies, sleep if dependencies absent and check dependencies again until all dependencies found