Re: Rollout of Gitlab CI
On Sun, Oct 3, 2021 at 10:40 AM Ben Cooksley wrote: > As an update to this, work on FreeBSD and Android support is progressing > well and should be made available within the next week all going well. > As a FreeBSD user I'm extremely excited about this. Thanks for all your hard work! Cheers, > Ben >
Re: Rollout of Gitlab CI
On Wed, Sep 29, 2021 at 10:27 PM Ben Cooksley wrote: > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > I have now prepared a list of all the projects that fall under this umbrella of being the dependency of another project - https://invent.kde.org/sysadmin/ci-management/-/merge_requests/3 It would be appreciated if people could please review this for any issues. Please note that it is intentional Frameworks is missing as that will be built by the 'Frameworks' seed. With regards to the PIM seed, please note that Zanshin, Kube and SInk have all been included in this, to allow for the Independent Releases seed to minimize the number of PIM projects it builds. If your project is included in any of those and you have not added a .kde-ci.yml file, it is imperative you do it *now*. If you do not then you will block the rollout of Gitlab CI for non-Frameworks projects. At some point in the near future we will also transition all of the references to 'master' in the seed files to '@latest' to allow for those branches to be resolved and taken from https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/branch-rules.yml > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Thanks, Ben
Re: Rollout of Gitlab CI
On Wed, Sep 29, 2021 at 10:27 PM Ben Cooksley wrote: > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > I have now prepared a list of all the projects that fall under this umbrella of being the dependency of another project - https://invent.kde.org/sysadmin/ci-management/-/merge_requests/3 It would be appreciated if people could please review this for any issues. Please note that it is intentional Frameworks is missing as that will be built by the 'Frameworks' seed. With regards to the PIM seed, please note that Zanshin, Kube and SInk have all been included in this, to allow for the Independent Releases seed to minimize the number of PIM projects it builds. If your project is included in any of those and you have not added a .kde-ci.yml file, it is imperative you do it *now*. If you do not then you will block the rollout of Gitlab CI for non-Frameworks projects. At some point in the near future we will also transition all of the references to 'master' in the seed files to '@latest' to allow for those branches to be resolved and taken from https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/branch-rules.yml > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Thanks, Ben
Re: Rollout of Gitlab CI
On Sun, Oct 3, 2021 at 10:40 AM Ben Cooksley wrote: > As an update to this, work on FreeBSD and Android support is progressing > well and should be made available within the next week all going well. > As a FreeBSD user I'm extremely excited about this. Thanks for all your hard work! Cheers, > Ben >
Re: Rollout of Gitlab CI
On Wed, Sep 29, 2021 at 10:27 PM Ben Cooksley wrote: > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > As an update to this, work on FreeBSD and Android support is progressing well and should be made available within the next week all going well. > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Cheers, Ben
Re: Rollout of Gitlab CI
On Wed, Sep 29, 2021 at 10:27 PM Ben Cooksley wrote: > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > As an update to this, work on FreeBSD and Android support is progressing well and should be made available within the next week all going well. > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Cheers, Ben
Re: Rollout of Gitlab CI
On Fri, Oct 1, 2021 at 10:40 AM David Hurka wrote: > On Thursday, September 30, 2021 10:12:35 PM CEST Albert Astals Cid wrote: > > Does this means we can no longer have interesting CI like > > "install this special distro that has openssl3 so that the QCA code > > doesn't regress" or > > "install this old Ubuntu since we still want to code to build in an > older > > Qt version" ? > > Yeah, the “GitLab CI” that comes with GitLab will probably stay, and just > the > CI templates in the sysadmin repositories will be removed? > > .gitlab-ci.yml allows to define quite flexible scenarios, but most KDE > repositories which I have seen just include a few templates from the > sysadmin > repositories, so I assume you are talking about the latter. :) > That is correct. Given that it is not an uncommon scenario, we may consider adding specific CI support for an LTS distribution (potentially along with it's corresponding Frameworks) depending on the interest. The new system makes it substantially easier to add more platforms compared with our Jenkins environment (which was a bit of a nightmare tbh). > > Cheers, > > Albert > > > > > Thanks, > > > Ben > > Cheers, David > Cheers, Ben
Re: Rollout of Gitlab CI
On Sat, Oct 2, 2021 at 7:28 AM Amber Schenck wrote: > On 9/30/21 5:05 PM, Nate Graham wrote: > > On 9/30/21 17:00, Amber Schenck wrote: > >> Would it be possible for a project outside of KDE infra > >> (https://sourceforge.net/projects/kuroo/) to use KDE CI? Unit tests > have > >> been on the TODO list for a long time, but the extra effort of setting > >> up CI has discouraged it so far. Using KDE CI would make that a lot > >> easier. > >> > >> > >> Thanks, > >> > >> -Amber > > > > Sounds like a good incentive to move to KDE infrastructure. :) > > > Alas and alack, there's that whole /effort/ thing again. . . This > project was around before git or Gitlab existed, and sourceforge and > subversion have served it just fine. Alternately, does Invent do any > mirroring? > Invent does not have any mirroring functionality i'm afraid - it's built to be the primary code hosting for KDE projects. There is some outbound mirroring to GitHub but that is in the wrong direction for what you are looking for. With regards to Subversion, there are a variety of tools out there for performing a Git conversion. > Nate > > Cheers, Ben
Re: Rollout of Gitlab CI
On 9/30/21 5:05 PM, Nate Graham wrote: > On 9/30/21 17:00, Amber Schenck wrote: >> Would it be possible for a project outside of KDE infra >> (https://sourceforge.net/projects/kuroo/) to use KDE CI? Unit tests have >> been on the TODO list for a long time, but the extra effort of setting >> up CI has discouraged it so far. Using KDE CI would make that a lot >> easier. >> >> >> Thanks, >> >> -Amber > > Sounds like a good incentive to move to KDE infrastructure. :) > Alas and alack, there's that whole /effort/ thing again. . . This project was around before git or Gitlab existed, and sourceforge and subversion have served it just fine. Alternately, does Invent do any mirroring? > Nate OpenPGP_signature Description: OpenPGP digital signature
Re: Rollout of Gitlab CI
On Thursday, September 30, 2021 10:12:35 PM CEST Albert Astals Cid wrote: > Does this means we can no longer have interesting CI like > "install this special distro that has openssl3 so that the QCA code > doesn't regress" or > "install this old Ubuntu since we still want to code to build in an older > Qt version" ? Yeah, the “GitLab CI” that comes with GitLab will probably stay, and just the CI templates in the sysadmin repositories will be removed? .gitlab-ci.yml allows to define quite flexible scenarios, but most KDE repositories which I have seen just include a few templates from the sysadmin repositories, so I assume you are talking about the latter. :) > Cheers, > Albert > > > Thanks, > > Ben Cheers, David
Re: Rollout of Gitlab CI
On 9/30/21 17:00, Amber Schenck wrote: Would it be possible for a project outside of KDE infra (https://sourceforge.net/projects/kuroo/) to use KDE CI? Unit tests have been on the TODO list for a long time, but the extra effort of setting up CI has discouraged it so far. Using KDE CI would make that a lot easier. Thanks, -Amber Sounds like a good incentive to move to KDE infrastructure. :) Nate
Re: Rollout of Gitlab CI
El dimecres, 29 de setembre de 2021, a les 11:27:08 (CEST), Ben Cooksley va escriure: > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. Does this means we can no longer have interesting CI like "install this special distro that has openssl3 so that the QCA code doesn't regress" or "install this old Ubuntu since we still want to code to build in an older Qt version" ? Cheers, Albert > > Thanks, > Ben >
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 8:04 PM Laurent Montel wrote: > On jeudi 30 septembre 2021 08:40:04 CEST Ben Cooksley wrote: > > On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > > > Hi, > > > > Hi Laurent, > > > > I added in .kde-ci.yml > > > > > 'kde/pim/akonadi-contacts': '@latest' > > > 'frameworks/kcontacts': '@stable' > > > > > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > > > What I missed ? > > > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > > > > As mentioned in my email, this is only available for projects that depend > > only on KDE Frameworks at the moment. > Ah ? I didn’t see this line :( too bad. > > > > > KGpg does not meet this criteria as it depends on akonadi-contacts - > which > > is in KDE PIM / Release Service, not Frameworks. > > For sure. > I will comment .kde-ci.yml for the moment. > The .kde-ci.yml file should remain in place unchanged. The .gitlab-ci.yml file certainly can be commented out yes. Cheers, Ben > > > > > Regards > > > > Cheers, > > Ben > > > > > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > > > Hi all, > > > > > > -- > > > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > > > Engineer > > > KDAB (France) S.A.S., a KDAB Group company > > > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > > > KDAB - The Qt, C++ and OpenGL Experts > > > -- > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > KDAB - The Qt, C++ and OpenGL Experts > > >
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 8:04 PM Laurent Montel wrote: > On jeudi 30 septembre 2021 08:40:04 CEST Ben Cooksley wrote: > > On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > > > Hi, > > > > Hi Laurent, > > > > I added in .kde-ci.yml > > > > > 'kde/pim/akonadi-contacts': '@latest' > > > 'frameworks/kcontacts': '@stable' > > > > > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > > > What I missed ? > > > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > > > > As mentioned in my email, this is only available for projects that depend > > only on KDE Frameworks at the moment. > Ah ? I didn’t see this line :( too bad. > > > > > KGpg does not meet this criteria as it depends on akonadi-contacts - > which > > is in KDE PIM / Release Service, not Frameworks. > > For sure. > I will comment .kde-ci.yml for the moment. > The .kde-ci.yml file should remain in place unchanged. The .gitlab-ci.yml file certainly can be commented out yes. Cheers, Ben > > > > > Regards > > > > Cheers, > > Ben > > > > > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > > > Hi all, > > > > > > -- > > > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > > > Engineer > > > KDAB (France) S.A.S., a KDAB Group company > > > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > > > KDAB - The Qt, C++ and OpenGL Experts > > > -- > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > KDAB - The Qt, C++ and OpenGL Experts > > >
Re: Rollout of Gitlab CI
On jeudi 30 septembre 2021 08:40:04 CEST Ben Cooksley wrote: > On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > > Hi, > > Hi Laurent, > > I added in .kde-ci.yml > > > 'kde/pim/akonadi-contacts': '@latest' > > 'frameworks/kcontacts': '@stable' > > > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > > What I missed ? > > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > > As mentioned in my email, this is only available for projects that depend > only on KDE Frameworks at the moment. Ah ? I didn’t see this line :( too bad. > > KGpg does not meet this criteria as it depends on akonadi-contacts - which > is in KDE PIM / Release Service, not Frameworks. For sure. I will comment .kde-ci.yml for the moment. > > > Regards > > Cheers, > Ben > > > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > > Hi all, > > > > -- > > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > > Engineer > > KDAB (France) S.A.S., a KDAB Group company > > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > > KDAB - The Qt, C++ and OpenGL Experts -- Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt, C++ and OpenGL Experts
Re: Rollout of Gitlab CI
On jeudi 30 septembre 2021 08:40:04 CEST Ben Cooksley wrote: > On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > > Hi, > > Hi Laurent, > > I added in .kde-ci.yml > > > 'kde/pim/akonadi-contacts': '@latest' > > 'frameworks/kcontacts': '@stable' > > > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > > What I missed ? > > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > > As mentioned in my email, this is only available for projects that depend > only on KDE Frameworks at the moment. Ah ? I didn’t see this line :( too bad. > > KGpg does not meet this criteria as it depends on akonadi-contacts - which > is in KDE PIM / Release Service, not Frameworks. For sure. I will comment .kde-ci.yml for the moment. > > > Regards > > Cheers, > Ben > > > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > > Hi all, > > > > -- > > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > > Engineer > > KDAB (France) S.A.S., a KDAB Group company > > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > > KDAB - The Qt, C++ and OpenGL Experts -- Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt, C++ and OpenGL Experts
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > Hi, > Hi Laurent, I added in .kde-ci.yml > 'kde/pim/akonadi-contacts': '@latest' > 'frameworks/kcontacts': '@stable' > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > What I missed ? > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > As mentioned in my email, this is only available for projects that depend only on KDE Frameworks at the moment. KGpg does not meet this criteria as it depends on akonadi-contacts - which is in KDE PIM / Release Service, not Frameworks. > Regards > Cheers, Ben > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > Hi all, > > -- > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > KDAB - The Qt, C++ and OpenGL Experts > > >
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 7:10 PM Laurent Montel wrote: > Hi, > Hi Laurent, I added in .kde-ci.yml > 'kde/pim/akonadi-contacts': '@latest' > 'frameworks/kcontacts': '@stable' > > for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? > What I missed ? > “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” > As mentioned in my email, this is only available for projects that depend only on KDE Frameworks at the moment. KGpg does not meet this criteria as it depends on akonadi-contacts - which is in KDE PIM / Release Service, not Frameworks. > Regards > Cheers, Ben > On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > > Hi all, > > -- > Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software > Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr > KDAB - The Qt, C++ and OpenGL Experts > > >
Re: Rollout of Gitlab CI
Hi, I added in .kde-ci.yml 'kde/pim/akonadi-contacts': '@latest' 'frameworks/kcontacts': '@stable' for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? What I missed ? “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” Regards On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > Hi all, -- Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt, C++ and OpenGL Experts
Re: Rollout of Gitlab CI
Hi, I added in .kde-ci.yml 'kde/pim/akonadi-contacts': '@latest' 'frameworks/kcontacts': '@stable' for kgpg and it doesn’t find akonadi-contacts. Do you have an idea ? What I missed ? “https://invent.kde.org/utilities/kgpg/-/jobs/134772/raw” Regards On mercredi 29 septembre 2021 11:27:08 CEST Ben Cooksley wrote: > Hi all, -- Laurent Montel | laurent.mon...@kdab.com | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel: France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt, C++ and OpenGL Experts
Re: Rollout of Gitlab CI
Le mer. 29 sept. 2021 à 19:37, Ben Cooksley a écrit : > On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > >> >> >> Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : >> >>> Hi all, >>> >>> As those of you who watch and work on Frameworks repositories will be >>> aware, we've just rolled out the first set of native Gitlab CI builds. >>> >>> These builds are at this time Linux only, but do include support for >>> both regular branch builds as well as for Merge Requests. It is anticipated >>> that Windows, FreeBSD and Android builds will follow in the near future - >>> there are a few extra things we need to get completed first before they can >>> be rolled out. As part of carrying out the build the scripts will also >>> gather Code Coverage and Code Quality information using gcovr and cppcheck >>> respectively, and this will be made available to you within the Gitlab >>> interface. >>> >>> With regards to availability to projects outside Frameworks, projects >>> that depend only on Frameworks (and no other KDE project) may enable CI for >>> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >>> to their repositories. I anticipate that once the necessary changes have >>> been made to the "seed" jobs used to provision the initial artifacts it >>> should be possible for all projects to rollout support (although i'd like >>> to add ccache support to the system to ensure larger project builds >>> complete promptly first). >>> >>> If anyone would like to help out with getting the seed jobs ready please >>> let me know as this is definitely something that the community can assist >>> with (and will also help with easing the rollout of Windows, FreeBSD and >>> Android builds). >>> >>> For those projects that do go ahead with enabling Gitlab CI support >>> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >>> in it the necessary Dependencies, as well as the necessary Options your >>> project needs to customise for their build. A list of all the possible >>> values in a .kde-ci.yml file can be found at >>> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >>> >>> For those projects that are not yet able to enable the system, it is >>> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >>> in your repository now - especially if other projects depend on your >>> project. This will allow the rollout of the CI system to those projects to >>> proceed much more smoothly (otherwise we will need to get them added to >>> those projects which have other projects depending on them). >>> >>> Please note that this new infrastructure replaces all existing Gitlab CI >>> jobs we provided in the initial testing phase, and those should be removed >>> (much like how I did for Frameworks) when switching to the new setup. >>> >>> Thanks, >>> Ben >>> >> >> Hi, >> >> is there a template for the .gitlab-ci.yml or should we use the same as >> https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e >> for example? >> > > You can use the same as that file. > > We're not providing a .gitlab-ci.yml template as there will be Windows, > FreeBSD and Android builds as well (and potentially in the future macOS as > well) which are options that won't necessarily apply to all projects. > > >> Cheers, >> >> Johnny >> > > Cheers, > Ben > Ok, super. It works fine for GCompris: https://invent.kde.org/education/gcompris/-/tree/master Thanks for providing this! Johnny
Re: Rollout of Gitlab CI
Le mer. 29 sept. 2021 à 19:37, Ben Cooksley a écrit : > On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > >> >> >> Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : >> >>> Hi all, >>> >>> As those of you who watch and work on Frameworks repositories will be >>> aware, we've just rolled out the first set of native Gitlab CI builds. >>> >>> These builds are at this time Linux only, but do include support for >>> both regular branch builds as well as for Merge Requests. It is anticipated >>> that Windows, FreeBSD and Android builds will follow in the near future - >>> there are a few extra things we need to get completed first before they can >>> be rolled out. As part of carrying out the build the scripts will also >>> gather Code Coverage and Code Quality information using gcovr and cppcheck >>> respectively, and this will be made available to you within the Gitlab >>> interface. >>> >>> With regards to availability to projects outside Frameworks, projects >>> that depend only on Frameworks (and no other KDE project) may enable CI for >>> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >>> to their repositories. I anticipate that once the necessary changes have >>> been made to the "seed" jobs used to provision the initial artifacts it >>> should be possible for all projects to rollout support (although i'd like >>> to add ccache support to the system to ensure larger project builds >>> complete promptly first). >>> >>> If anyone would like to help out with getting the seed jobs ready please >>> let me know as this is definitely something that the community can assist >>> with (and will also help with easing the rollout of Windows, FreeBSD and >>> Android builds). >>> >>> For those projects that do go ahead with enabling Gitlab CI support >>> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >>> in it the necessary Dependencies, as well as the necessary Options your >>> project needs to customise for their build. A list of all the possible >>> values in a .kde-ci.yml file can be found at >>> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >>> >>> For those projects that are not yet able to enable the system, it is >>> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >>> in your repository now - especially if other projects depend on your >>> project. This will allow the rollout of the CI system to those projects to >>> proceed much more smoothly (otherwise we will need to get them added to >>> those projects which have other projects depending on them). >>> >>> Please note that this new infrastructure replaces all existing Gitlab CI >>> jobs we provided in the initial testing phase, and those should be removed >>> (much like how I did for Frameworks) when switching to the new setup. >>> >>> Thanks, >>> Ben >>> >> >> Hi, >> >> is there a template for the .gitlab-ci.yml or should we use the same as >> https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e >> for example? >> > > You can use the same as that file. > > We're not providing a .gitlab-ci.yml template as there will be Windows, > FreeBSD and Android builds as well (and potentially in the future macOS as > well) which are options that won't necessarily apply to all projects. > > >> Cheers, >> >> Johnny >> > > Cheers, > Ben > Ok, super. It works fine for GCompris: https://invent.kde.org/education/gcompris/-/tree/master Thanks for providing this! Johnny
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > > > Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : > >> Hi all, >> >> As those of you who watch and work on Frameworks repositories will be >> aware, we've just rolled out the first set of native Gitlab CI builds. >> >> These builds are at this time Linux only, but do include support for both >> regular branch builds as well as for Merge Requests. It is anticipated that >> Windows, FreeBSD and Android builds will follow in the near future - there >> are a few extra things we need to get completed first before they can be >> rolled out. As part of carrying out the build the scripts will also gather >> Code Coverage and Code Quality information using gcovr and cppcheck >> respectively, and this will be made available to you within the Gitlab >> interface. >> >> With regards to availability to projects outside Frameworks, projects >> that depend only on Frameworks (and no other KDE project) may enable CI for >> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >> to their repositories. I anticipate that once the necessary changes have >> been made to the "seed" jobs used to provision the initial artifacts it >> should be possible for all projects to rollout support (although i'd like >> to add ccache support to the system to ensure larger project builds >> complete promptly first). >> >> If anyone would like to help out with getting the seed jobs ready please >> let me know as this is definitely something that the community can assist >> with (and will also help with easing the rollout of Windows, FreeBSD and >> Android builds). >> >> For those projects that do go ahead with enabling Gitlab CI support >> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >> in it the necessary Dependencies, as well as the necessary Options your >> project needs to customise for their build. A list of all the possible >> values in a .kde-ci.yml file can be found at >> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >> >> For those projects that are not yet able to enable the system, it is >> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >> in your repository now - especially if other projects depend on your >> project. This will allow the rollout of the CI system to those projects to >> proceed much more smoothly (otherwise we will need to get them added to >> those projects which have other projects depending on them). >> >> Please note that this new infrastructure replaces all existing Gitlab CI >> jobs we provided in the initial testing phase, and those should be removed >> (much like how I did for Frameworks) when switching to the new setup. >> >> Thanks, >> Ben >> > > Hi, > > is there a template for the .gitlab-ci.yml or should we use the same as > https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e > for example? > You can use the same as that file. We're not providing a .gitlab-ci.yml template as there will be Windows, FreeBSD and Android builds as well (and potentially in the future macOS as well) which are options that won't necessarily apply to all projects. > Cheers, > > Johnny > Cheers, Ben
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > > > Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : > >> Hi all, >> >> As those of you who watch and work on Frameworks repositories will be >> aware, we've just rolled out the first set of native Gitlab CI builds. >> >> These builds are at this time Linux only, but do include support for both >> regular branch builds as well as for Merge Requests. It is anticipated that >> Windows, FreeBSD and Android builds will follow in the near future - there >> are a few extra things we need to get completed first before they can be >> rolled out. As part of carrying out the build the scripts will also gather >> Code Coverage and Code Quality information using gcovr and cppcheck >> respectively, and this will be made available to you within the Gitlab >> interface. >> >> With regards to availability to projects outside Frameworks, projects >> that depend only on Frameworks (and no other KDE project) may enable CI for >> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >> to their repositories. I anticipate that once the necessary changes have >> been made to the "seed" jobs used to provision the initial artifacts it >> should be possible for all projects to rollout support (although i'd like >> to add ccache support to the system to ensure larger project builds >> complete promptly first). >> >> If anyone would like to help out with getting the seed jobs ready please >> let me know as this is definitely something that the community can assist >> with (and will also help with easing the rollout of Windows, FreeBSD and >> Android builds). >> >> For those projects that do go ahead with enabling Gitlab CI support >> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >> in it the necessary Dependencies, as well as the necessary Options your >> project needs to customise for their build. A list of all the possible >> values in a .kde-ci.yml file can be found at >> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >> >> For those projects that are not yet able to enable the system, it is >> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >> in your repository now - especially if other projects depend on your >> project. This will allow the rollout of the CI system to those projects to >> proceed much more smoothly (otherwise we will need to get them added to >> those projects which have other projects depending on them). >> >> Please note that this new infrastructure replaces all existing Gitlab CI >> jobs we provided in the initial testing phase, and those should be removed >> (much like how I did for Frameworks) when switching to the new setup. >> >> Thanks, >> Ben >> > > Hi, > > is there a template for the .gitlab-ci.yml or should we use the same as > https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e > for example? > You can use the same as that file. We're not providing a .gitlab-ci.yml template as there will be Windows, FreeBSD and Android builds as well (and potentially in the future macOS as well) which are options that won't necessarily apply to all projects. > Cheers, > > Johnny > Cheers, Ben
Re: Rollout of Gitlab CI
Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Hi, is there a template for the .gitlab-ci.yml or should we use the same as https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e for example? Cheers, Johnny
Rollout of Gitlab CI
Hi all, As those of you who watch and work on Frameworks repositories will be aware, we've just rolled out the first set of native Gitlab CI builds. These builds are at this time Linux only, but do include support for both regular branch builds as well as for Merge Requests. It is anticipated that Windows, FreeBSD and Android builds will follow in the near future - there are a few extra things we need to get completed first before they can be rolled out. As part of carrying out the build the scripts will also gather Code Coverage and Code Quality information using gcovr and cppcheck respectively, and this will be made available to you within the Gitlab interface. With regards to availability to projects outside Frameworks, projects that depend only on Frameworks (and no other KDE project) may enable CI for their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files to their repositories. I anticipate that once the necessary changes have been made to the "seed" jobs used to provision the initial artifacts it should be possible for all projects to rollout support (although i'd like to add ccache support to the system to ensure larger project builds complete promptly first). If anyone would like to help out with getting the seed jobs ready please let me know as this is definitely something that the community can assist with (and will also help with easing the rollout of Windows, FreeBSD and Android builds). For those projects that do go ahead with enabling Gitlab CI support please ensure you add the necessary .kde-ci.yml file beforehand, specifying in it the necessary Dependencies, as well as the necessary Options your project needs to customise for their build. A list of all the possible values in a .kde-ci.yml file can be found at https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 For those projects that are not yet able to enable the system, it is strongly encouraged that you go ahead and get the .kde-ci.yml files ready in your repository now - especially if other projects depend on your project. This will allow the rollout of the CI system to those projects to proceed much more smoothly (otherwise we will need to get them added to those projects which have other projects depending on them). Please note that this new infrastructure replaces all existing Gitlab CI jobs we provided in the initial testing phase, and those should be removed (much like how I did for Frameworks) when switching to the new setup. Thanks, Ben
Rollout of Gitlab CI
Hi all, As those of you who watch and work on Frameworks repositories will be aware, we've just rolled out the first set of native Gitlab CI builds. These builds are at this time Linux only, but do include support for both regular branch builds as well as for Merge Requests. It is anticipated that Windows, FreeBSD and Android builds will follow in the near future - there are a few extra things we need to get completed first before they can be rolled out. As part of carrying out the build the scripts will also gather Code Coverage and Code Quality information using gcovr and cppcheck respectively, and this will be made available to you within the Gitlab interface. With regards to availability to projects outside Frameworks, projects that depend only on Frameworks (and no other KDE project) may enable CI for their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files to their repositories. I anticipate that once the necessary changes have been made to the "seed" jobs used to provision the initial artifacts it should be possible for all projects to rollout support (although i'd like to add ccache support to the system to ensure larger project builds complete promptly first). If anyone would like to help out with getting the seed jobs ready please let me know as this is definitely something that the community can assist with (and will also help with easing the rollout of Windows, FreeBSD and Android builds). For those projects that do go ahead with enabling Gitlab CI support please ensure you add the necessary .kde-ci.yml file beforehand, specifying in it the necessary Dependencies, as well as the necessary Options your project needs to customise for their build. A list of all the possible values in a .kde-ci.yml file can be found at https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 For those projects that are not yet able to enable the system, it is strongly encouraged that you go ahead and get the .kde-ci.yml files ready in your repository now - especially if other projects depend on your project. This will allow the rollout of the CI system to those projects to proceed much more smoothly (otherwise we will need to get them added to those projects which have other projects depending on them). Please note that this new infrastructure replaces all existing Gitlab CI jobs we provided in the initial testing phase, and those should be removed (much like how I did for Frameworks) when switching to the new setup. Thanks, Ben
