-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup Jenkins status to GitHub branches #9
Comments
Could we also (or instead) use Github actions? |
If I remember correctly: an issue is to be able to do authentication, involving a (client) secret, which we have tooling for in Jenkins. It's probably also possible to set something up in Github actions, but that will take a lot more time to figure out I guess |
@soxofaan How can I setup the authentication on Jenkins for |
hmm yes, the annoying thing is that you want to connect to multiple backends (VITO, CDSE, ...), which makes things less straightforward |
As far as I can see, the jenkins run is broken because the test collection fails, it doesn't even reach trying to create a connection. e.g. I see this
|
@GriffinBabe is that something you also get when running |
I get that error too when running |
Import issues mentioned above have been resolved now I've also set up a bunch of code quality things that do not require auth or openeo processing (linting, formatting, ...) under #16 |
@soxofaan do you know the status of the jenkins pipelines? If we want to get going with a first UDF in the |
The Terrascope auth seems to work in the feature branch I'm working in |
I think I now got the auth stuff working with #30 going to close this one for now |
See with Jeroen Verstraelen
The text was updated successfully, but these errors were encountered: