1. 21 Jan, 2021 1 commit
  2. 15 Jan, 2021 1 commit
  3. 14 Jan, 2021 2 commits
    • Volker Krause's avatar
      KOpeningHours was moved out of playground · ab8b7d0f
      Volker Krause authored
      kde/pim is not really the right prefix, nor does it match the category
      on invent, but we don't seem to have "kde/libs". With that apparently
      having little impact beyond this file and the dependency metadata, I've
      just followed what was previously done for similar modules that also don't
      really belong into kde/pim, like kosmindoormap.
      ab8b7d0f
    • Ben Cooksley's avatar
      Ensure libffi-dev is included within our image. · 72019434
      Ben Cooksley authored
      CCBUG: 424196
      
      Ref T14046
      72019434
  4. 07 Jan, 2021 2 commits
  5. 05 Jan, 2021 1 commit
  6. 04 Jan, 2021 2 commits
  7. 02 Jan, 2021 1 commit
  8. 01 Jan, 2021 2 commits
  9. 31 Dec, 2020 1 commit
  10. 29 Dec, 2020 1 commit
  11. 28 Dec, 2020 2 commits
  12. 23 Dec, 2020 1 commit
    • Milian Wolff's avatar
      Use the latest devtoolset-9 · 94854da7
      Milian Wolff authored
      Sadly the docker base image isn't available from docker hub. So we
      need to setup the latest devtoolset manually ourselves. This is
      required to update ld.gold to a version which fixes a linker bug
      encountered while building qtwayland.
      94854da7
  13. 09 Dec, 2020 1 commit
    • Milian Wolff's avatar
      Add experimental centos 7 docker file · 5a3c2730
      Milian Wolff authored
      The package list was tested over at [1], and I now adapted the
      other steps from the ubuntu craft image too. But I'm not sure how
      to test whether this docker image is usable by jenkins now? Can
      anyone tell me how I could test this?
      
      I also noticed that there's now a devtoolset-8, which we may want
      to use instead of version 7 to get an even newer compiler. But I
      can't pull from centos/devtoolset-8-toolchain-centos7, so apparently
      that's not ready yet. Version 7 is good enough for now anyways.
      
      [1]: https://invent.kde.org/mwolff/kf5-appimage-centos7/
      5a3c2730
  14. 02 Dec, 2020 2 commits
  15. 01 Dec, 2020 1 commit
  16. 30 Nov, 2020 1 commit
  17. 28 Nov, 2020 1 commit
  18. 27 Nov, 2020 7 commits
  19. 26 Nov, 2020 1 commit
  20. 22 Nov, 2020 1 commit
  21. 21 Nov, 2020 1 commit
  22. 09 Nov, 2020 1 commit
  23. 08 Nov, 2020 3 commits
    • Nicolás Alvarez's avatar
      GitLab CI: make build dir an artifact only if static analysis is used · 59bb8766
      Nicolás Alvarez authored
      In fd8cc96a we introduced ci-static-analysis.yml with GitLab jobs to run
      clazy. The normal build job uploads its 'build' directory as an artifact
      and the static-analysis job then uses that artifact and runs clazy on it.
      
      Making the entire 'build' directory an artifact is making *all* builds
      take very long and sometimes even timeout, even if they don't use static
      analysis. This commit removes 'build' as an artifact in ci-before.yml, and
      adds it to ci-static-analysis.yml, so that it's only done for projects
      using the static analysis job.
      
      Ideally we should find a way to run clazy without having to pass artifacts
      between jobs, eg. run it on the same job as the compilation.
      59bb8766
    • Bhushan Shah's avatar
      keysmith: remove the build for the Android Qt5.15 · 479b8eb0
      Bhushan Shah authored
      It does not make much sense to build it on the build.kde.org since it is
      already covered by the binary-factory.kde.org as well as to my knowledge
      build.kde.org does not do full APK build anyway, so this is not much
      useful for application
      479b8eb0
    • Johan Ouwerkerk's avatar
      a8718db1
  24. 06 Nov, 2020 2 commits
    • Nicolás Alvarez's avatar
      Don't limit the number of cores on GitLab · f4f0b082
      Nicolás Alvarez authored
      The build script was using 75% of the available CPUs if there were >=4.
      This makes sense on our Jenkins build nodes, since we run multiple
      concurrent jobs, some of them in VMs where even the load limit via -l won't
      avoid overcommitting resources. However, on GitLab we currently run 1 job
      at a time, and using max 75% CPU is being very wasteful.
      
      This commit makes the 75% limit apply only to Jenkins.
      f4f0b082
    • Johan Ouwerkerk's avatar
      0bf2ef44
  25. 05 Nov, 2020 1 commit