Open
Description
Currently, this repository evaluates all commits in a GitHub repository and for each commit with a .GitLab-CI.yml
, it will:
0. Clone the repository from GitHub to local
- Ddelete the repository if it already exists in the GitLab server
- Push the repository to the GitLab server.
- Run the CI on that commit and push the build status of that commit result back to GitHub.
This is inefficient, because one could also clone the complete repository into GitLab at once, (and wait until all build statusses have been computed in GitLab before pushing the build status results back to GitLab). Look at:run_ci_on_github_repo() {
in here.
- Find a way to clone the complete repository at once to GitLab (Integrating this code in automatic GitLab server deployment ubc/github2gitlab#1)
- Update the code to wait until all build statusses have been computed in GitLab, and push the new build status badges once for the complete cloned repository, back to GitHub.
- Allow user to specify an option: "Monitor and push build status batches continuously" in case they want to have a more frequent build status updating after the clone, at the cost of consuming more GitHub push bandwidth.
- Do constantly monitor the build statusses in GitLab and automatically push the buildstatus to GitHub if a build is completed. (Ideally with a post-receive script).
- Allow the user to specify GitLab starts computing build statusses from most recent commit backwards.
Metadata
Metadata
Assignees
Labels
No labels