Add GitHub Actions workflow to build and deploy plugin to OMCSI - #141
Add GitHub Actions workflow to build and deploy plugin to OMCSI#141dmccoystephenson with Copilot wants to merge 3 commits into
Conversation
Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>
|
This draft is being closed as stale. It was opened on 2026-03-07 and has not been touched since 2026-03-22 — roughly five months idle. The head is now 24 commits behind The underlying request is not being dropped: #140 remains open and continues to track the OMCSI build-and-deploy workflow. The head branch This review and closure were performed by Claude. drafted by Claude on behalf of Daniel Stephenson |
Adds a CI/CD workflow that builds the plugin JAR and deploys it to an omcsi instance, modeled after the Activity Tracker deploy workflow.
DEPLOY_BRANCH(default:main) + manualworkflow_dispatchdependencies/dir, thenmvn --batch-mode clean packagetarget/, excludesoriginal-*/*-sources.jar/*-javadoc.jarOMCSI_DEPLOY_URL/api/plugins/deploywith bearer authThe only deviation from the reference workflow is an additional step to
mvn install:install-filethe Ponder dependency, which isn't available from any public Maven repository.Required repo configuration
OMCSI_DEPLOY_URLOMCSI_DEPLOY_TOKENDEPLOY_AUTH_TOKENfrom omcsi.envPLUGIN_JAR_NAMESimpleSkills.jarDEPLOY_BRANCHmain)Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.