You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Only git is considered as a repository source for Concord workflows.
In scenarios where git is unavailable or teams adopting CIOPS approach for developing Concord workflows, support for a build or a package registry as a source will be necessary.
Support for mvn:// as the url source for concord repository
Support for triggers on publish of an artifact(Concord workflows) to the maven repository
The text was updated successfully, but these errors were encountered:
amithkb
changed the title
Support for Maven repository as a source for Concord repository
Feature: Support for Maven repository as a source for concord repository
Jan 11, 2024
amithkb
changed the title
Feature: Support for Maven repository as a source for concord repository
Feature: Support for maven repository as a source for concord repository
Jan 11, 2024
Support for triggers on publish of an artifact(Concord workflows) to the maven repository
If the repository supports webhooks (e.g. Nexus) that are basically just JSON being POSTed then it should be possible to consume such events using Generic Triggers
Currently, Only
git
is considered as a repository source for Concord workflows.In scenarios where git is unavailable or teams adopting CIOPS approach for developing Concord workflows, support for a build or a package registry as a source will be necessary.
mvn://
as the url source for concord repositoryThe text was updated successfully, but these errors were encountered: