On Fri, Jun 18, 2021 at 7:33 AM Milian Wolff wrote:
> On Donnerstag, 17. Juni 2021 11:25:15 CEST Ben Cooksley wrote:
> > On Thu, Jun 17, 2021 at 8:44 AM Milian Wolff wrote:
> > > On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote:
> > > > Hi all,
> > > >
> > > >
> > > > The following is
On Donnerstag, 17. Juni 2021 11:25:15 CEST Ben Cooksley wrote:
> On Thu, Jun 17, 2021 at 8:44 AM Milian Wolff wrote:
> > On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote:
> > > Hi all,
> > >
> > >
> > > The following is notice that I intend to withdraw CI services from the
> > > follo
On Thu, Jun 17, 2021 at 7:26 AM Avamander wrote:
> Hi,
>
Hi there,
>
> This is indeed an issue that has occurred previously, and actually
> I've written to you, Ben, once before about this. Now I'm asking again, why
> is it necessary to email *FIVE* mailing lists for issues that are
> primaril
On Thu, Jun 17, 2021 at 8:44 AM Milian Wolff wrote:
> On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote:
> > Hi all,
>
> > The following is notice that I intend to withdraw CI services from the
> > following two KDE projects due to faults in their code or build system
> > which are hav
Hi,
This is indeed an issue that has occurred previously, and actually
I've written to you, Ben, once before about this. Now I'm asking again, why
is it necessary to email *FIVE* mailing lists for issues that are primarily
solved by a much much smaller subgroup of people? Maybe send it to a few
C+
How about if we add a config flag for our ci machines and configure cmake
of these 2 project's test to ignore building/adding those problematic tests
whenever it saw those flags?
I don't know why but it doesn't sound correct to me to kill the ci build of
any project because of these types of proble
This kind of problem will be generically solved for everyone once we get
GitLab's pre-commit CI, which can block merging of MRs until the
failures are resolved--so they actually *will* be resolved. How soon can
we get that finally rolled out across KDE?
Until that happens, this sort of problem
On Mittwoch, 16. Juni 2021 20:28:25 CEST Ben Cooksley wrote:
> Hi all,
>
> The following is notice that I intend to withdraw CI services from the
> following two KDE projects due to faults in their code or build system
> which are having a significant adverse impact on the CI system and
> negative
Hi Ben,
On 16.06.21 20:28, Ben Cooksley wrote:
Hi all,
The following is notice that I intend to withdraw CI services from the
following two KDE projects due to faults in their code or build system
which are having a significant adverse impact on the CI system and
negatively impacting on other p
On Thu, Jun 17, 2021 at 6:41 AM Nate Graham wrote:
> This kind of problem will be generically solved for everyone once we get
> GitLab's pre-commit CI, which can block merging of MRs until the
> failures are resolved--so they actually *will* be resolved. How soon can
> we get that finally rolled
Hi all,
The following is notice that I intend to withdraw CI services from the
following two KDE projects due to faults in their code or build system
which are having a significant adverse impact on the CI system and
negatively impacting on other projects:
- KDevelop
- KDE Connect
This withdrawa
11 matches
Mail list logo