-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add maven verification workflow #1
Add maven verification workflow #1
Conversation
ab503e8
to
bd557f0
Compare
Please don't merge things until both repos are merged and switch is done to prevent any delays. |
bd557f0
to
662c54c
Compare
This should be independent of that or do you think there are any problems? |
@mickaelistria the build complains:
As this does not touch any code: could it be related to the recent move of the repository? |
Yes, most likely the merge commit has affected that module a way or another so the versions should be bumped. If you don't want to bump the version, you'll need to see what has changed in history compared to 3.22.300.v20220503-1634 and maybe exclude this file from the "watched" ones that are used to derive the qualifier. But just bumping is much easier... |
Okay as @akurtakov has already mentioned its maybe good to wait until the merge of the runtime is done (i'll try to find some time if no one else step up here), so we catch all bumps at once, I just wanted to make sure that its not a useless bump. |
Currently there was no merge just a direct push to a new repo. I only added
a new remote in my local clone and pushed to the new repo url
|
I think this can be finished/merged now. |
1142f2d
to
0401528
Compare
Once the Github action works correctly, we may want to discuss to stop using Jenkins for build verification. GH actions seems to be faster and easier to configure. |
I found it useful in the past two have both but of course this might change over time. |
0401528
to
a02a47a
Compare
No description provided.