-
Notifications
You must be signed in to change notification settings - Fork 4
Move to Egeria 4.1 #46
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Mandy Chessell <[email protected]>
Signed-off-by: Mandy Chessell <[email protected]>
…to maintenance
Signed-off-by: Mandy Chessell <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The codeQL tests are currently using 'autobuild' which should build using either maven or gradle as appropriate, though we have had issues in the past both with autobuild, and codeQL more generally.
In this case the checks didn't fail as such, but we saw no results.
This project also currently doesn't have a verification in build -- perhaps in part as it's a series of small projects. I do think it would be worthwhile adding such a build, please let me know if you need some tips, but it's similar to our other gradle based projects.
Given codeQL I will set the codeQL we could set the checks to be optional for now. These can be reenabled in settings if the checks need to be mandatory in future. But first, reopening and closing the PR may kick codeQL into action, so I will try that.
I do not know why codeQL was enabled - I agree it should not be required - particularly as it is not working :) |
After close/open, the codeQL action was kicked off. However it failed.
I tried building the PR locally. One warning
In core egeria the top level build.gradle sets us up to fail when a dependency violation occurs This is done by ensuring this is set
I appprove the change, but suggest we do
Let me know if you need any advice/help with the above. |
No description provided.