Closed samuelcolvin closed 4 years ago
Some errors are so critical that it is not possible to communicate them to the UI. That being said, this could be improved.
Some of the errors you're encountering are probably fixed in the latest version, which is pending release. Please pull the latest sources from master and try again. Set DEBUG
to strider*
to capture all relevant output. If there are issues with plugins: https://github.com/Strider-CD/strider/wiki/Debugging
Please also take note of https://github.com/Strider-CD/strider/wiki/Advanced-Configuration
I've just found strider and was very excited, however after an hour or so trying to get it running locally (with docker using https://github.com/macropin/docker-strider) I'm pretty frustrated.
The primary problem I've found is that errors occurring in strider are not displayed in any way to the user in the web interface. Not even "something's gone wrong", surely as an admin I should get a stracktrace?
For example, I've been trying to build the public project https://github.com/samuelcolvin/arq as an experiment. I've tried with both the
python
plugin andcustom
. With both plugins I've got errors:(and numerous more)
None of these were displayed in the UI the build screen just hung.
I'm also not clear on how I would isolate services (eg. dbs) wrt separate builds and the configure > plugins page seems to have a UI bug where I can't remove a plugin once I've added it.
I'm really keen to get self hosted CI working, however with fundamental problems like error reporting not working I'm not particularly keen to invest more time in strider.