[CDash] CDASH_MANAGE_CLIENTS

[Karol Molnár]

Thank you very much. I will try that webhooks, i want to test all commit. Is there a way to tell that other instance of ctest is running some build/test? Or is there a method to queue builds so when some commits are pushed in short interval and a build is not finished i don’t start new one. Or how to handle this kind of situations?

Ragards.

Ing. Karol Molnár
On 28 Jul 2021, 14:44 +0200, Zack Galbreath <zack.galbreath at kitware.com>, wrote:
> It sounds like you're on the right track.
>
> You're correct that the "simple cron job" approach has a drawback that some commits may go untested if a bunch of changes are pushed in rapid succession.
>
> Maybe Bitbucket webhooks would work for you? The idea here is that Bitbucket notifies some web service that you maintain whenever there's relevant changes to your repository. With this information you could launch a CTest job to build & test the new commit.
>
> docs: https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/
> example: https://support.atlassian.com/bitbucket-cloud/docs/create-and-trigger-a-webhook-tutorial/
>
> HTH,
> -Zack
>
>
> > On Wed, Jul 28, 2021 at 2:31 AM Karol Molnár <molnarkarol at gmail.com> wrote:
> > > Thank you for your answer.
> > >
> > > I am glad that you kept the simple solution because until discovering now as you say deprecated “build management” the cdash/ctest was well separated thing.
> > >
> > > I have a bitbucket repo so there are pipelines but if a simple cron job can do the work it would be better. I have now a ctest script that updates the repo, build and test what i want is to somehow keep running this so every commit is built and tested. I tried to run the same script while it was already running but it doesn’t bothered and started the same thing so i want to prevent this. So i am looking for something that continuously build new commits.
> > >
> > > Thank you for your answers.
> > >
> > > Regards
> > > On 27 Jul 2021, 20:32 +0200, Zack Galbreath <zack.galbreath at kitware.com>, wrote:
> > > > Thanks for reaching out!
> > > >
> > > > We removed this feature prior to the release of CDash v3.0 because it was seldom used and had a relatively high maintenance burden. We wanted to keep the focus of CDash on being a dashboard for displaying build/test results. Having it behave as a central build scheduler felt like feature creep.
> > > >
> > > > We've had good success with the following tools for running automated builds:
> > > >
> > > > • GitLab CI
> > > > • GitHub Actions
> > > > • CircleCI
> > > > • Jenkins
> > > > • cron jobs
> > > >
> > > > Please feel free to ask if you have any questions on how to use one of these build runners with CTest/CDash.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cdash/attachments/20210728/0d88fb4b/attachment-0003.htm>