Hi,
I have a configuration set up to be triggered by a Plastic SCM repository check in on any branch. It isn’t working at the moment and I’m wondering if you have any suggestions for anything I can check out?
I have a feeling this might be a bug since it seems to have only stopped working after requesting a manual build and it’s now happened on two separate configurations. I can look at the configuration’s repository and see that it has detected the code check in and even displays the correct comments but no build has been triggered.
Regards,
Sean
Hi Sean,
The quickest way for us to work out the cause of this issue is with a debug log. If you can enable debug logging, restart the Continua CI server service and then add a similar changeset to the repository, the debug log will then shown us what happened when the trigger fails. Send the debug log to support@finalbuilder.com along with the names of the relevant repository and trigger.
It would also be useful if you could send us full details of the repository and trigger settings? The easiest way to do this is by downloading a diagnostics report from the Event Log page. Alternatively, you can send screenshots of the edit dialogs.
Also let us know which version of the Plastic SCM client is installed on the server and what version of the server you are using.