Thanks for fixing the build Vladimir! I like the idea of testing against other projects on a weekly basis. It will certainly help detect regressions early on. It might be a bit hard to maintain since there could be failures quite often but I guess we will not know till we try.
Even before adding 3rd-party projects in the CI, I would say that is worth running our integration tests (Druid, Cassandra, Postgres, etc.) at a regular basis by CI. I am checking them now and there seems to be again failures. Best, Stamatis On Sat, Feb 8, 2020 at 11:48 AM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > >Are current -SNAPSHOT packages on repository.apache.org up to date ? > > The snapshots were not up to date because Calcite-Snapshots Jenkins job was > using beam Jenkins node somehow. > I guess that was caused by misconfiguration of beam nodes. > > I've triggered the job manually, and it works now: > https://builds.apache.org/job/Calcite-Snapshots/ > On top of that, I've configured mails to dev@calcite list for the > snapshots > job so we'll know if it fails again. > > >I would like to test my projects in CI against current master > > I wonder if it makes sense to add GitHub Actions CI which would validate > third-party projects on a weekly basis. > For instance, I have https://github.com/vlsi/mat-calcite-plugin , which is > not that sophisticated, however, it would be nice to see > if the upcoming Calcite version is going to break or not that client. > > For instance, Beam has quite interesting post-commit tests page: > https://github.com/apache/beam#post-commit-tests-status-on-master-branch > > WDYT? > > Vladimir >
