Guide on building a connector for Azure DevOps
I want to create connector for azure devops. how to build it
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
To build a new connector for Azure DevOps in Airbyte, you can follow these general steps: 1. Implement & Package your connector in an Airbyte Protocol compliant Docker image: You can use the interactive generator provided by Airbyte to create a new connector from a template. Run the following commands in your terminal: bash cd airbyte-integrations/connector-templates/generator ./generate.sh Choose the relevant template using the arrow keys. This will generate a new connector in the airbyte-integrations/connectors/<your-connector> directory. Follow the "TODO"s in the generated directory to implement your connector. For more detailed instructions, you can follow the relevant tutorial provided by Airbyte (source). 2. Add integration tests for your connector: All connectors must pass Airbyte’s standard test suite. You can also add your own tests. 3. Document how to build & test your connector: If you’re writing in a language other than Python or Java, document the commands needed to build your connector docker image and run any unit or integration tests in a Docker image (source). 4. Publish the Docker image containing the connector: Airbyte’s build system builds and tags your connector’s image correctly by default as part of the connector’s standard build process. Run the following command from the Airbyte repo root: bash ./gradlew clean :airbyte-integrations:connectors:source-<name>:build This is equivalent to running docker build . -t airbyte/source-<name>:dev from the connector root (source). Please note that while the guides are specific to the languages used most frequently to write integrations, Airbyte connectors can be written in any language. If you need help developing connectors in other languages, you can reach out to the Airbyte team (source). For more detailed information, you can refer to the Airbyte Connector Development documentation.