Continuous integration of the Red Hat LSP4iJ plug-in.

[mrglavas]

As Liberty Tools for IntelliJ transitions from the MicroShed version of LSP4iJ on to the common shared plug-in being built from https://github.com/redhat-developer/lsp4ij we should consider automation for continuous integration of this plug-in. There are nightly builds being published here: https://plugins.jetbrains.com/plugin/23257-lsp4ij/versions.

Can we automate the detection of new nightly builds of LSP4iJ and then integrate and test with Liberty Tools for IntelliJ? This would provide us with constant feedback and provide early warning if something breaks, so that we may act on it sooner. Perhaps this could even be triggered by a PR push to the main branch of LSP4iJ and the automation first builds the LSP4iJ plug-in from the current state of that repository.

---

Tasks for this Epic (as of July 11th)

• Set up a GHA workflow as a cron job #756
• Run the LTI Tests against each open lsp4ij PR and lsp4ij main branch #757
• Build lsp4ij plugin from a branch to use in the LTI automated tests  #758
• Determine Parameterization for Running the LTI Build #783
• Despite specifying the version, only the latest Marketplace version of Lsp4ij gets installed during buildPlugin. #793
• Run LTI tests for LSP4IJ PRs only if they do not contain a merge conflict. #845
• Upload artifacts corresponding to each PR buils using lsp4ij. #866
• Send LSP4IJ integration build results to Slack channel #759
• Run LSP4iJ continuous integration builds with existing LTI releases. #815
• Enhance the names of LTI build artifacts to make them easier to read by consumers. #868
• Cron Job Builds are Taking PRs with Merge Conflicts #889
• Start running the cron job in the LTI repo  #895
• Documentation for developers to understand continuous build integration  #896

[anusreelakshmi934]

We're aiming to automate GHA workflows for daily cron jobs, facilitating the initiation of lsp4ij integration builds. Our current focus involves extracting details about all opened PRs in the Red Hat lsp4ij repository. Then, we'd pull the merge commit of each open PR and build lsp4ij from the corresponding checked-out branches.
Additionally, we intend to execute lsp4ij integration builds using the lsp4ij main branch atop the open PRs. This approach accommodates scenarios where a PR might be opened and merged before our cron job executes.

[TrevCraw]

All items complete.