Update CICD build to use Leap v5 #140
Conversation
There was a problem hiding this comment.
I would suggest upgrading the build to ubuntu22 at the same time. on ubuntu20, libtester 5.0 is built with gcc10 where as eos-system-contracts CI will still use gcc9 as currently configured. This will one day cause grief (it's why libtester on ubuntu20 isn't tested any longer in leap repo), and regardless of grief is probably a ODR violation like this too.
Alternatively we could change the current ubuntu20 workflow to use gcc10 just like libtester. But it's more forward looking (and cleaner imo) to just upgrade to ubuntu22.
You will need to change at least
No problem, we can make those changes. Can we upgrade to v4 build actions as well? This would pull in changes from PR #109 |
|
Note:start |
Currently set to use Leap v3, need to update CICD to Leap v5. Fixes #139