Hello CI folks!
Suppose I have this in my tests.yml:
repositories: - repo: "https://src.fedoraproject.org/rpms/pyproject-rpm-macros.git" dest: "pyproject-rpm-macros"
This is currently always cloned on the default branch (master). How do I clone it on a different branch or switch to it? In particular, I need it to be the same branch we are on -- aka if the tests runs on a f32 Pull Request, the branch should be f32.
We currently keep rpms/pyproject-rpm-macros identical across braches, but if we ever stop doing that, I need the approprioate tests to be executed, not rawhide tests.
Thanks,
Hi Miro,
you can use the "version" parameter to choose the desired branch: https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation
psss...
On Mon, 20 Apr 2020 at 12:41, Miro Hrončok mhroncok@redhat.com wrote:
Hello CI folks!
Suppose I have this in my tests.yml:
repositories: - repo: "https://src.fedoraproject.org/rpms/pyproject-rpm-macros.git" dest: "pyproject-rpm-macros"This is currently always cloned on the default branch (master). How do I clone it on a different branch or switch to it? In particular, I need it to be the same branch we are on -- aka if the tests runs on a f32 Pull Request, the branch should be f32.
We currently keep rpms/pyproject-rpm-macros identical across braches, but if we ever stop doing that, I need the approprioate tests to be executed, not rawhide tests.
Thanks,
Miro Hrončok
Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On 20. 04. 20 13:01, Petr Šplíchal wrote:
Hi Miro,
you can use the "version" parameter to choose the desired branch: https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation
Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?
On Mon, 20 Apr 2020 at 13:14, Miro Hrončok mhroncok@redhat.com wrote:
On 20. 04. 20 13:01, Petr Šplíchal wrote:
Hi Miro,
you can use the "version" parameter to choose the desired branch: https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation
Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?
So you want to prevent storing "version: f32" for the referenced repository in the f32 branch of the component being tested? I don't think there is currently a way to auto-magically set the version to the current branch.
psss...
On 20. 04. 20 13:30, Petr Šplíchal wrote:
On Mon, 20 Apr 2020 at 13:14, Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
On 20. 04. 20 13:01, Petr Šplíchal wrote: > Hi Miro, > > you can use the "version" parameter to choose the desired branch: > https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?So you want to prevent storing "version: f32" for the referenced repository in the f32 branch of the component being tested? I don't think there is currently a way to auto-magically set the version to the current branch.
Yes, because storing "version: f32" means I would need to diverge all the beanches only because of this. An I'd need to do this very time a new Fedora version is branched from rawhide. Possibly on dozens of packages.
On Mon, Apr 20, 2020 at 1:33 PM Miro Hrončok mhroncok@redhat.com wrote:
On 20. 04. 20 13:30, Petr Šplíchal wrote:
On Mon, 20 Apr 2020 at 13:14, Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
On 20. 04. 20 13:01, Petr Šplíchal wrote: > Hi Miro, > > you can use the "version" parameter to choose the desired branch: > https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?So you want to prevent storing "version: f32" for the referenced repository in the f32 branch of the component being tested? I don't think there is currently a way to auto-magically set the version to the current branch.
Yes, because storing "version: f32" means I would need to diverge all the beanches only because of this. An I'd need to do this very time a new Fedora version is branched from rawhide. Possibly on dozens of packages.
We don't really support this, but I think it is a nice feature to have. Could you open a Fedora ci general issue [1] so we can track this?
There is "ansible_distribution_version", but it doesn't work for rawhide, so the pipeline would probably need to pass some arguments to the playbook what might require some change to standard test interface...
https://pagure.io/fedora-ci/general/issues
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On 20. 04. 20 14:00, Bruno Goncalves wrote:
On Mon, Apr 20, 2020 at 1:33 PM Miro Hrončok mhroncok@redhat.com wrote:
On 20. 04. 20 13:30, Petr Šplíchal wrote:
On Mon, 20 Apr 2020 at 13:14, Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
On 20. 04. 20 13:01, Petr Šplíchal wrote: > Hi Miro, > > you can use the "version" parameter to choose the desired branch: > https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?So you want to prevent storing "version: f32" for the referenced repository in the f32 branch of the component being tested? I don't think there is currently a way to auto-magically set the version to the current branch.
Yes, because storing "version: f32" means I would need to diverge all the beanches only because of this. An I'd need to do this very time a new Fedora version is branched from rawhide. Possibly on dozens of packages.
We don't really support this, but I think it is a nice feature to have. Could you open a Fedora ci general issue [1] so we can track this?
There is "ansible_distribution_version", but it doesn't work for rawhide, so the pipeline would probably need to pass some arguments to the playbook what might require some change to standard test interface...
https://pagure.io/fedora-ci/general/issue/106
On Mon, 20 Apr 2020 at 13:33, Miro Hrončok mhroncok@redhat.com wrote:
On 20. 04. 20 13:30, Petr Šplíchal wrote:
On Mon, 20 Apr 2020 at 13:14, Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
On 20. 04. 20 13:01, Petr Šplíchal wrote: > Hi Miro, > > you can use the "version" parameter to choose the desired branch: > https://docs.fedoraproject.org/en-US/ci/share-test-code/#_implementation Thank you. That is first half of the problem. The second half is: How do I set "version" to current branch of the package being tested?So you want to prevent storing "version: f32" for the referenced repository in the f32 branch of the component being tested? I don't think there is currently a way to auto-magically set the version to the current branch.
Yes, because storing "version: f32" means I would need to diverge all the beanches only because of this. An I'd need to do this very time a new Fedora version is branched from rawhide. Possibly on dozens of packages.
Maybe another potential use-case for a generic text preprocessing language (preproc) that I wanted to use also for https://hackmd.io/kIje9yXTRdWITwP7cFK2pA
But that's only if the evaluation of the version can be done on builder, not directly on the central orchestrating server. Otherwise, a different mechanism would be needed.
(i didn't look into details so, please, don't judge me if preproc cannot be used there but i think it would be good to evaluate)
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
Hi,
Jumping into this regarding the Zuul CI context. In a Zuul job definition we can tell Zuul to clone additional repositories (required-projects [1]) on the test node. Zuul will clone them respecting the target branch of tested PR but also it will fetch the right open PR(s) of the additional repositories if some of them have been defined as dependencies through the "Depends-on" keyword.
So I'm wondering if it could be possible in Standard test Roles library to add the support for an option such as: "populate: no|default('yes')" that the caller can set to skip the checkout of the repositories specified in tests.yml. In the Zuul context we could let Zuul provision those repositories by setting populate: no and by setting the list of repositories in required-projects.
What do you think?
Fabien
[1]: https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.required-proje...
On Mon, Apr 20, 2020 at 12:41 PM Miro Hrončok mhroncok@redhat.com wrote:
Hello CI folks!
Suppose I have this in my tests.yml:
repositories: - repo: "https://src.fedoraproject.org/rpms/pyproject-rpm-macros.git" dest: "pyproject-rpm-macros"This is currently always cloned on the default branch (master). How do I clone it on a different branch or switch to it? In particular, I need it to be the same branch we are on -- aka if the tests runs on a f32 Pull Request, the branch should be f32.
We currently keep rpms/pyproject-rpm-macros identical across braches, but if we ever stop doing that, I need the approprioate tests to be executed, not rawhide tests.
Thanks,
Miro Hrončok
Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
-
Bruno Goncalves -
clime -
Fabien Boucher -
Miro Hrončok -
Petr Šplíchal