Jamie Astin <jamie.as...@gmail.com> writes: > Morning All, > > We have been investigating the idea of moving our builds into GitLab CI > from a Jenkins setup. > > This has proven to be a beneficial step forward, particularly in regards to > pre-merge builds. We have now deleted most of our Jenkins jobs. However, > there is still one "style" of jobs that we've not managed to cater for. > > Every night we run a full SonarQube analysis on our codebase. This is > achieved by using a specific gradle task `gradle sonarqube`. > > How should one attempt to set-up this kind of build in GitLab? It doesn't > seem to support scheduled jobs. > > The only compromise I have imagined is having some external stimulus to > start the job, which seems counter-intuitive. The last thing I want is a > Jenkins job to trigger a GitLab CI build (via the web hooks). > > Am I overlooking something? > > Any help / advice would be greatly appreciated.
I'd use some other scheduler (like cron) to trigger a job: https://gitlab.com/help/ci/triggers/README.md /M -- Magnus Therning, magnus.thern...@cipherstone.com Cipherstone Technologies AB Theres Svenssons gata 10, 417 55 Gothenburg, Sweden Finagle's Fifth Law: Always draw your curves, then plot your readings. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/871t49xt9r.fsf%40sobel.cipherstone.com. For more options, visit https://groups.google.com/d/optout.
