kwin/.gitlab-ci.yml

# SPDX-FileCopyrightText: None
# SPDX-License-Identifier: CC0-1.0

include:
  - project: sysadmin/ci-utilities
    file:
      - /gitlab-templates/linux-qt6.yml
      # - /gitlab-templates/freebsd-qt6.yml

suse_tumbleweed_qt67_reduced_featureset:
    extends: suse_tumbleweed_qt67
    script:
    - git config --global --add safe.directory $CI_PROJECT_DIR
    - python3 -u ci-utilities/run-ci-build.py --project $CI_PROJECT_NAME --branch $CI_COMMIT_REF_NAME --platform Linux --extra-cmake-args="-DKWIN_BUILD_KCMS=OFF -DKWIN_BUILD_SCREENLOCKER=OFF -DKWIN_BUILD_TABBOX=OFF -DKWIN_BUILD_ACTIVITIES=OFF -DKWIN_BUILD_RUNNERS=OFF -DKWIN_BUILD_NOTIFICATIONS=OFF -DKWIN_BUILD_GLOBALSHORTCUTS=OFF -DKWIN_BUILD_X11=OFF -DKWIN_BUILD_EIS=OFF" --skip-publishing
Add GitLab CI 2021-11-27 02:10:09 +00:00			`# SPDX-FileCopyrightText: None`
			`# SPDX-License-Identifier: CC0-1.0`

			`include:`
Port to the new .gitlab-ci.yml include project syntax As Ben said on the mailing list. 2023-11-20 07:22:35 +00:00			`- project: sysadmin/ci-utilities`
			`file:`
			`- /gitlab-templates/linux-qt6.yml`
Disable freebsd ci It's broken and it blocks normal workflow. 2024-04-03 08:02:54 +00:00			`# - /gitlab-templates/freebsd-qt6.yml`
gitlab-ci: Add minimal build configuration Ensures KWin is also built with features disabled to catch when code is added that requires a build-time guard Signed-off-by: Eike Hein <eike.hein@mbition.io> 2022-02-23 14:44:16 +00:00
ci: Switch to suse_tumbleweed_qt67 2024-04-22 12:26:22 +00:00			`suse_tumbleweed_qt67_reduced_featureset:`
			`extends: suse_tumbleweed_qt67`
Adjust reduced feature CI to run unprivileged Same thing was done to the common templates. 2022-10-03 08:35:46 +00:00			`script:`
			`- git config --global --add safe.directory $CI_PROJECT_DIR`
Add a libeis input backend plugin This adds a libeis backend via plugin which supports clients sending emulated input events. No public listening socket is exposed, clients are expected to go through the RemoteDesktop portal. In order to restrict the device types available to clients according to what was approved via the portal a separate eis context per portal request is created. The communication with the portal happens through a simple dbus interface where cookies are handed out for each eis context so the portal can inform KWin when the portal session is closed/should end. 2024-03-21 11:11:16 +00:00			`- python3 -u ci-utilities/run-ci-build.py --project $CI_PROJECT_NAME --branch $CI_COMMIT_REF_NAME --platform Linux --extra-cmake-args="-DKWIN_BUILD_KCMS=OFF -DKWIN_BUILD_SCREENLOCKER=OFF -DKWIN_BUILD_TABBOX=OFF -DKWIN_BUILD_ACTIVITIES=OFF -DKWIN_BUILD_RUNNERS=OFF -DKWIN_BUILD_NOTIFICATIONS=OFF -DKWIN_BUILD_GLOBALSHORTCUTS=OFF -DKWIN_BUILD_X11=OFF -DKWIN_BUILD_EIS=OFF" --skip-publishing`