... | ... | @@ -99,6 +99,32 @@ flatpak: |
|
|
|
|
|
Currently template downloads the flatpak manifest from the `flatpak-kde-applications` repository. This is subject to change, and in future we might ship flatpak manifest in repo directly.
|
|
|
|
|
|
# Custom builds
|
|
|
|
|
|
Gitlab CI is fairly customizable in terms of what you can run with it. If your project have specific build/testing that you want to run you can extend or create your own `.gitlab-ci.yml`.
|
|
|
|
|
|
Example of this is kde/kdesrc-build> project, which have custome `.gitlab-ci.yml` file,
|
|
|
|
|
|
```
|
|
|
image: ubuntu:18.04
|
|
|
|
|
|
before_script:
|
|
|
- apt-get --quiet -qq update
|
|
|
- apt-get --quiet -qq install perl-modules git cmake g++ libio-socket-ssl-perl libyaml-perl
|
|
|
|
|
|
test:
|
|
|
stage: build
|
|
|
script:
|
|
|
- prove -I modules
|
|
|
```
|
|
|
|
|
|
You can learn more about Gitlab CI from the links in Resources section.
|
|
|
|
|
|
# Acceptable usage policy
|
|
|
|
|
|
- For frameworks, applications, and other repos which are used by other projects you can add your own builds, but you can't remove the KDE CI configuration. This is to ensure that, your project artifacts are available to projects which are using your project as dependencies.
|
|
|
- Gitlab runners are using the docker executor, which generally speaking have needed security measures, but any attempt to circumvent the security will be considered the violation of code of conduct.
|
|
|
|
|
|
# Resources
|
|
|
|
|
|
- [Gitlab CI documentation](https://docs.gitlab.com/ee/ci/yaml/README.html)
|
... | ... | |