Skip to content
Snippets Groups Projects

Add initial version of ci-flatdeb-builder

Merged Add initial version of ci-flatdeb-builder
wip/refi64/ci-flatdeb-builder into main
All threads resolved!
Merged Ryan Gonzalez requested to merge wip/refi64/ci-flatdeb-builder into main
All threads resolved!
Viewing commit b9fc98d7
Show latest version
1 file
+ 54
− 71
Compare changes
  • Side-by-side
  • Inline
README.md
+ 54
− 71
# ci-flatdeb-builder
GitLab pipelines to build Flatpak runtimes and applications
This repository contains GitLab pipelines and generators to build flatdeb and
flatpak-builder projects for Apertis.
## Getting started
## Local Development Environment
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Create a local virtualenv for this project, then simply `pip3 install -r
requirements-dev.txt` to install all of the development dependencies.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Running Tests
## Add your files
ci-flatdeb-builder has three types of tests:
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
- Local unit tests for various helpers in the pipeline generator, in
`tests/test_helpers.py`.
- Approval tests that check to ensure the output of ci-flatdeb-builder has not changed,
in `tests/test_approval.py` and `tests/approved_Files`.
- Integration-style tests that run a full pipeline on GitLab and then examine the
results, in `tests/test_build_pipelines.py`.
```
cd existing_repo
git remote add origin https://gitlab.apertis.org/infrastructure/ci-flatdeb-builder.git
git branch -M main
git push -uf origin main
```
The integration-style tests are marked with the `gitlab` marker, thus you can
exclusively run them via `pytest -m gitlab`, or run everything *except* for them via
`pytest -m 'not gitlab'`.
## Integrate with your tools
### Approval Tests
- [ ] [Set up project integrations](https://gitlab.apertis.org/infrastructure/ci-flatdeb-builder/-/settings/integrations)
If the ci-flatdeb-builder output changes for any reason, the approval tests will likely
start failing. You can run `tests/approval_all.sh` to mark all of the new, changed
results as approved, then `git diff tests/approved_files` to easily confirm that the
changes are as expected.
## Collaborate with your team
### GitLab Tests
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
In order to run the tests marked `gitlab`, you must provide a GitLab pipeline to
examine:
## Test and Deploy
- If you want to trigger a new pipeline run automatically, pass `--pipeline-id trigger`.
- If you instead want to run the tests on the results of a pipeline that already ran,
pass `--pipeline-id PIPELINE-ID`.
Use the built-in continuous integration in GitLab.
Note that, in either case, the build results examined from images.apertis.org will be
those resulting from the *latest* build of the current branch.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
By default, the tests will upload their artifacts to
`https://images.apertis.org/test/ci-flatdeb-builder-SLUG`, where `SLUG` is your current
branch name with all non-alphanumeric characters replaced with dashes (`-`).
***
#### Test Repositories
# Editing this README
There are four different pipelines run:
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
- Two on a [repository containing demo flatdeb runtimes](TODO), both marked with the
`gitlab_repo_runtimes` pytest marker:
- One for the stable `apertis/v2022` Git branch, marked with the `gitlab_branch_main`
marker.
- One for the `wip/fake/test` Git branch, marked with the `gitlab_branch_test` marker.
- Two on a [repository containing demo flatpak-builder applications](TODO), both marked
with the `gitlab_repo_apps` marker:
- One for the stable `main` Git branch, marked with the `gitlab_branch_main`
marker.
- One for the `wip/fake/test` Git branch, marked with the `gitlab_branch_test` marker.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
In order to run only some of these, you can pass their markers to `pytest -m`, e.g.
`pytest -m 'gitlab and gitlab_repo_runtimes and gitlab_branch_main'` will run the test
for the runtimes repo's stable branch, and `pytest -m 'gitlab and gitlab_repo_apps'`
will run the two tests for the apps repo.
## Name
Choose a self-explaining name for your project.
#### GitLab Instance Credentials
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
The credentials used to connect to the Apertis GitLab instance will, by default, be
taken from [the standard python-gitlab configuration
file](https://python-gitlab.readthedocs.io/en/stable/cli-usage.html#configuration-files),
with the server section name "apertis". To change the section name, pass
`--gitlab-instance NAME` to pytest.
Apertis Website Terms of Use Privacy Policy