Change Details

Currently, the repository is hosted on GitLab, which does not support our workflows as much as we want. Acceptance criteria: * Code from https://gitlab.com/fun-tech/fundraising-app-frontend is on GitHub * GitHub runs the CI actions (testing, linting, building) on every pull request * GitHub regularly updates the dependencies * The repository contains no GitLab-specific configuration * The deployment playbook fetches the branch-specific built artifacts (JavaScript, CSS) from the new location Implementation notes: * Use dependabot for updating the dependencies To discuss: * Which CI system to use - Travis or GitHub Actions? * Do we still need to build the Docker images? * GitHub is currently [[ https://github.com/actions/upload-artifact/issues/27 | missing ]] the Gitlab feature of build artifacts that are [[ https://github.com/actions/upload-artifact/issues/51 | accessible ]] by a predefined URL. This impacts the deployment, which fetches the branch-specific build artifacts. Possible workarounds: * Register dynamic artifact URL during build process (e.g. in a JSON file stored in a different git repository), the deployment would then query the JSON for the Artifact URL * Create an "artifact downloader" CLI that queries the GitHub API for a list of artifacts, looking for the right one according to a naming convention. * Use other storage provider. Which one? We need to think about threat and security models. * Use a separate Git repository for artifacts. See https://github.com/marketplace/actions/push-directory-to-another-repository

Currently, the repository is hosted on GitLab, which does not support our workflows as much as we want. Acceptance criteria: * Code from https://gitlab.com/fun-tech/fundraising-app-frontend is on GitHub * GitHub runs the CI actions (testing, linting, building) on every pull request * GitHub regularly updates the dependencies * The repository contains no GitLab-specific configuration * The deployment playbook fetches the branch-specific built artifacts (JavaScript, CSS) from the new location * Releases are created using the GitHub Actions API. Implementation notes: * Use dependabot for updating the dependencies * Building docker images is optional * Releases are named after the branch name (and overwritten if existing).

Currently, the repository is hosted on GitLab, which does not support our workflows as much as we want. Acceptance criteria: * Code from https://gitlab.com/fun-tech/fundraising-app-frontend is on GitHub * GitHub runs the CI actions (testing, linting, building) on every pull request * GitHub regularly updates the dependencies * The repository contains no GitLab-specific configuration * The deployment playbook fetches the branch-specific built artifacts (JavaScript, CSS) from the new location * Releases are created using the GitHub Actions API. Implementation notes: * Use dependabot for updating the dependencies To discuss: * Which CI system to use - Travis or GitHub Actions? * Do we still need to build the Docker images? * GitHub is currently [[ https://github.com/actions/upload-artifact/issues/27 | missing ]] the Gitlab feature of build artifacts that are [[ https://github.com/actions/upload-artifact/issues/51 | accessible ]] by a predefined URL. This impacts the deployment, which fetches the branch-specific build artifacts. Possible workarounds:Building docker images is optional * Register dynamic artifact URL during build process (e.g. in a JSON file stored in a different git repository), the deployment would then query the JSON for the Artifact URL* Releases are named after the branch name (and overwritten if existing). * Create an "artifact downloader" CLI that queries the GitHub API for a list of artifacts, looking for the right one according to a naming convention. * Use other storage provider. Which one? We need to think about threat and security models. * Use a separate Git repository for artifacts. See https://github.com/marketplace/actions/push-directory-to-another-repository