Re: [PATCHES rtems, source-builder] Add GitHub Actions scripts
Am 20.01.23 um 06:21 schrieb Chris Johns: On 20/1/2023 1:50 am, Christian MAUDERER wrote: Am 19.01.23 um 15:42 schrieb Gedare Bloom: Nice. I would like some time to look at this and think about it a little more. What would be the plan for removing this capability? Will it leave any artifacts behind in the RTEMS github mirror? As soon as we want to get rid of the scripts again (because we have found and implemented a proper CI/CD that we officially want to use and not only have in a test phase), we can just remove the scripts with a new commit. If we use both commits, we will have a bot that adds a comment to pull requests, that patches should be sent to the mailing list as soon as they are tested. It will close pull requests after 30 days. That can be disabled again with removing that action. All artefacts can be removed by everyone with enough rights in the RTEMS GitHub organization. That should be most maintainers. What github account does all this happen on? Chris Hello Chris, at the moment, I have a prototype at an embedded-brains account (see links in my first mail). My suggestion is to add the scripts to the official RTEMS GitHub mirror repositories to get some feedback from users and developers what is good or bad in this prototype CI system. Based on this we should discuss in one or two months what features we need and select and implement a long-term CI system for RTEMS. Best regards Christian -- embedded brains GmbH Herr Christian MAUDERER Dornierstr. 4 82178 Puchheim Germany email: christian.maude...@embedded-brains.de phone: +49-89-18 94 741 - 18 mobile: +49-176-152 206 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCHES rtems, source-builder] Add GitHub Actions scripts
On 20/1/2023 1:50 am, Christian MAUDERER wrote: > Am 19.01.23 um 15:42 schrieb Gedare Bloom: >> Nice. I would like some time to look at this and think about it a >> little more. What would be the plan for removing this capability? Will >> it leave any artifacts behind in the RTEMS github mirror? > > As soon as we want to get rid of the scripts again (because we have found and > implemented a proper CI/CD that we officially want to use and not only have > in a > test phase), we can just remove the scripts with a new commit. > > If we use both commits, we will have a bot that adds a comment to pull > requests, > that patches should be sent to the mailing list as soon as they are tested. It > will close pull requests after 30 days. That can be disabled again with > removing > that action. > > All artefacts can be removed by everyone with enough rights in the RTEMS > GitHub > organization. That should be most maintainers. What github account does all this happen on? Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCHES rtems, source-builder] Add GitHub Actions scripts
Am 19.01.23 um 15:42 schrieb Gedare Bloom: Nice. I would like some time to look at this and think about it a little more. What would be the plan for removing this capability? Will it leave any artifacts behind in the RTEMS github mirror? As soon as we want to get rid of the scripts again (because we have found and implemented a proper CI/CD that we officially want to use and not only have in a test phase), we can just remove the scripts with a new commit. If we use both commits, we will have a bot that adds a comment to pull requests, that patches should be sent to the mailing list as soon as they are tested. It will close pull requests after 30 days. That can be disabled again with removing that action. All artefacts can be removed by everyone with enough rights in the RTEMS GitHub organization. That should be most maintainers. Best regards Christian On Mon, Jan 16, 2023 at 6:42 AM Christian Mauderer wrote: Hello, some weeks ago I created a GitHub Actions based CI script that we (embedded brains) wanted to use to test patches (see https://github.com/embedded-brains/rtems/tree/ci). I don't think much of the RTEMS community noted these. I would like to suggest adding the scripts to the official RTEMS repositories so that the actions are executed in the official GitHub RTEMS mirrors. To make sure that GitHub pull requests are not perceived at the official way to make RTEMS contributions, an auto-responder action notifies the pull request user that the current way to make contributions is sending patch sets to devel@rtems.org. This step will allow users to easily test patches on a number of simulators before they send them to the mailing list. No one is forced to do it, but everyone can try it. For RTEMS, it has the advantage that the patches are at least guaranteed to be compile-clean on a selected number of BSPs and that they survived a test run on a simulator. Please note: With this patch I do not intent to push GitHub as the RTEMS CI or to move from mailing list patches to push-requests. My idea is to allow everyone to experiment with a proof of concept prototype. Based on your experiences in this test phase, I would suggest that we have a review discussion in a month or two to select a suitable way forward for RTEMS CI. I think after that test phase we all know better what we want or expect which helps selecting the best CI system that then can replace this proof of concept system with GitHub. But now to make make it more clear what we will get with merging these patches: You can find a (not yet cleaned up) version of the patches in these repositories: https://github.com/embedded-brains/rtems https://github.com/embedded-brains/rtems-source-builder The results from a current run on RTEMS are here: https://github.com/embedded-brains/rtems/actions/runs/3901364934 If you scroll down on that page, you get a summary that shows which tests fail on three (mostly) randomly selected simulator BSPs. GR740 usually can run all tests but currently jffs2_fsrdwr fails. The full output of the rtems tester is in the Artifacts in case you want to take a look at the test output. If you want to try the CI with some of your patches before we merge this to the official repositories, feel free to create a pull request to the ci branches of the embedded-brains/rtems repositories. See the github manual for guidance how to create a pull request: https://docs.github.com/articles/creating-a-pull-request Note: It is important that you somewhen forked from the official RTEMS repositories or from one of the forks using (for example) the fork button in the github web interface. If you just pushed a repo to an empty one, github doesn't recognize the link and won't allow you to create a pull-request towards the embedded-brains repository. Best regards Christian ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel -- embedded brains GmbH Herr Christian MAUDERER Dornierstr. 4 82178 Puchheim Germany email: christian.maude...@embedded-brains.de phone: +49-89-18 94 741 - 18 mobile: +49-176-152 206 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCHES rtems, source-builder] Add GitHub Actions scripts
On 19.01.23 15:42, Gedare Bloom wrote: Nice. I would like some time to look at this and think about it a little more. What would be the plan for removing this capability? Will it leave any artifacts behind in the RTEMS github mirror? It seems by default stuff is kept for about 90 days: https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCHES rtems, source-builder] Add GitHub Actions scripts
Nice. I would like some time to look at this and think about it a little more. What would be the plan for removing this capability? Will it leave any artifacts behind in the RTEMS github mirror? On Mon, Jan 16, 2023 at 6:42 AM Christian Mauderer wrote: > > Hello, > > some weeks ago I created a GitHub Actions based CI script that we > (embedded brains) wanted to use to test patches (see > https://github.com/embedded-brains/rtems/tree/ci). I don't think much of > the RTEMS community noted these. I would like to suggest adding the > scripts to the official RTEMS repositories so that the actions are > executed in the official GitHub RTEMS mirrors. > > To make sure that GitHub pull requests are not perceived at the official > way to make RTEMS contributions, an auto-responder action notifies the > pull request user that the current way to make contributions is sending > patch sets to devel@rtems.org. > > This step will allow users to easily test patches on a number of > simulators before they send them to the mailing list. No one is forced > to do it, but everyone can try it. For RTEMS, it has the advantage that > the patches are at least guaranteed to be compile-clean on a selected > number of BSPs and that they survived a test run on a simulator. > > Please note: With this patch I do not intent to push GitHub as the RTEMS > CI or to move from mailing list patches to push-requests. My idea is to > allow everyone to experiment with a proof of concept prototype. Based on > your experiences in this test phase, I would suggest that we have a > review discussion in a month or two to select a suitable way forward for > RTEMS CI. I think after that test phase we all know better what we want > or expect which helps selecting the best CI system that then can replace > this proof of concept system with GitHub. > > But now to make make it more clear what we will get with merging these > patches: > > You can find a (not yet cleaned up) version of the patches in these > repositories: > > https://github.com/embedded-brains/rtems > https://github.com/embedded-brains/rtems-source-builder > > The results from a current run on RTEMS are here: > > https://github.com/embedded-brains/rtems/actions/runs/3901364934 > > If you scroll down on that page, you get a summary that shows which > tests fail on three (mostly) randomly selected simulator BSPs. GR740 > usually can run all tests but currently jffs2_fsrdwr fails. The full > output of the rtems tester is in the Artifacts in case you want to take > a look at the test output. > > If you want to try the CI with some of your patches before we merge this > to the official repositories, feel free to create a pull request to the > ci branches of the embedded-brains/rtems repositories. See the github > manual for guidance how to create a pull request: > > https://docs.github.com/articles/creating-a-pull-request > > Note: It is important that you somewhen forked from the official RTEMS > repositories or from one of the forks using (for example) the fork > button in the github web interface. If you just pushed a repo to an > empty one, github doesn't recognize the link and won't allow you to > create a pull-request towards the embedded-brains repository. > > Best regards > > Christian > > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCHES rtems, source-builder] Add GitHub Actions scripts
Hello, some weeks ago I created a GitHub Actions based CI script that we (embedded brains) wanted to use to test patches (see https://github.com/embedded-brains/rtems/tree/ci). I don't think much of the RTEMS community noted these. I would like to suggest adding the scripts to the official RTEMS repositories so that the actions are executed in the official GitHub RTEMS mirrors. To make sure that GitHub pull requests are not perceived at the official way to make RTEMS contributions, an auto-responder action notifies the pull request user that the current way to make contributions is sending patch sets to devel@rtems.org. This step will allow users to easily test patches on a number of simulators before they send them to the mailing list. No one is forced to do it, but everyone can try it. For RTEMS, it has the advantage that the patches are at least guaranteed to be compile-clean on a selected number of BSPs and that they survived a test run on a simulator. Please note: With this patch I do not intent to push GitHub as the RTEMS CI or to move from mailing list patches to push-requests. My idea is to allow everyone to experiment with a proof of concept prototype. Based on your experiences in this test phase, I would suggest that we have a review discussion in a month or two to select a suitable way forward for RTEMS CI. I think after that test phase we all know better what we want or expect which helps selecting the best CI system that then can replace this proof of concept system with GitHub. But now to make make it more clear what we will get with merging these patches: You can find a (not yet cleaned up) version of the patches in these repositories: https://github.com/embedded-brains/rtems https://github.com/embedded-brains/rtems-source-builder The results from a current run on RTEMS are here: https://github.com/embedded-brains/rtems/actions/runs/3901364934 If you scroll down on that page, you get a summary that shows which tests fail on three (mostly) randomly selected simulator BSPs. GR740 usually can run all tests but currently jffs2_fsrdwr fails. The full output of the rtems tester is in the Artifacts in case you want to take a look at the test output. If you want to try the CI with some of your patches before we merge this to the official repositories, feel free to create a pull request to the ci branches of the embedded-brains/rtems repositories. See the github manual for guidance how to create a pull request: https://docs.github.com/articles/creating-a-pull-request Note: It is important that you somewhen forked from the official RTEMS repositories or from one of the forks using (for example) the fork button in the github web interface. If you just pushed a repo to an empty one, github doesn't recognize the link and won't allow you to create a pull-request towards the embedded-brains repository. Best regards Christian ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel