create more robust ci-cd pipeline

[lemonman96]

No description provided.

[lemonman96]

New pipeline changes to allow more control over publishing/enable auto snapshot publishing. Essentially there are 3 cases:

Manual workflow and run_all is true: publish all packages with version described in build.gradle

Manual workflow and run_all is false: publish subproject specified in run_specificwith version described in build.gradle. run_specific should be of the form sensorhub-*

Workflow started via push (or merge) to master: Changes are detected and set difference is performed against the project list. Resulting list of projects are automatically published with -SNAPSHOT appended to the version number described in the build.gradle

In this way version numbers are still driven via the individual build.gradle files, so manual updates to these version numbers must be in place before doing a non snapshot release.

[nickgaray]

Does this mean then that on a merge to master all changed modules will be published? Will this work for packages with classifiers as well?

[lemonman96]

Does this mean then that on a merge to master all changed modules will be published? Will this work for packages with classifiers as well?

Yes, and as long as the classifiers are added during the publish task then those should be published as well. Changed modules are appended with -SNAPSHOT and are allowed overwrites

[lemonman96]

@alexrobin @nickgaray I was able to test this via running workflows through my branch:

example single project publish:
https://github.com/opensensorhub/osh-addons/actions/runs/25011859652

example multi project publish:
https://github.com/opensensorhub/osh-addons/actions/runs/25012979259

this pr is fully ready for merge