Summarize


Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
First, ensure that the Google Cloud SDK is installed on the machine where Jenkins is running. This SDK will enable you to interact with Google Cloud services. Download and install the SDK from the [Google Cloud SDK website](https://cloud.google.com/sdk/docs/install). Once installed, authenticate the SDK by running `gcloud init` and follow the prompts to log in to your Google Cloud account.
In the Google Cloud Console, navigate to Pub/Sub. Create a new topic to which Jenkins will publish messages. This can be done by selecting "Create Topic" and providing a unique name for your topic. Make sure to note the topic name as it will be needed later.
Create a service account in Google Cloud Console with the necessary permissions to publish messages to the Pub/Sub topic. Go to the "IAM & Admin" section, select "Service Accounts," and create a new service account. Assign it the "Pub/Sub Publisher" role. Generate and download a JSON key for this service account, as Jenkins will use it to authenticate.
Ensure that the "Pipeline" plugin is installed in Jenkins, as it allows for the creation of Jenkins pipelines which can contain custom scripts. Go to "Manage Jenkins" -> "Manage Plugins" and install the "Pipeline" plugin if it is not already installed.
Create a Jenkins pipeline job that includes a script to publish data to Google Pub/Sub. The script should use the `gcloud` command-line tool to publish messages. Here is a basic example of a pipeline script:
```groovy
pipeline {
agent any
environment {
GOOGLE_APPLICATION_CREDENTIALS = ''
}
stages {
stage('Publish to Pub/Sub') {
steps {
script {
def message = 'Your message data'
sh "gcloud pubsub topics publish --message '${message}'"
}
}
}
}
}
```
Replace `` and `` with your specific file path and topic name.
Store your service account JSON key file securely on the Jenkins server. Use Jenkins credentials to handle sensitive information. Go to "Manage Jenkins" -> "Manage Credentials" to add a new credential for your service account key. In your pipeline script, reference this credential using Jenkins' environment variables.
Run the Jenkins pipeline to ensure that data is being successfully published to Google Pub/Sub. Monitor the logs in Jenkins to verify that the `gcloud` command executes without errors. You can also check the Google Cloud Console under Pub/Sub to confirm that messages are being received in the specified topic.
By following these steps, you can efficiently move data from Jenkins to Google Pub/Sub without relying on third-party connectors or integrations.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Jenkins is an open-source automation server. It helps automate parts of software development that facilitate build, test, and deployment, continuous integration, and continuous delivery. It is a server-based system that runs in servlet containers such as Apache Tomcat. It supports version control tools including AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clear Case, and RTC, and can execute arbitrary shell scripts and Windows batch commands alongside Apache Ant, Apache Maven and etc.
Jenkins is an open-source automation server that provides a wide range of APIs to access data related to the build process. The Jenkins API provides access to various types of data, including:
1. Build Data: Information about the build process, such as build status, build duration, build logs, and build artifacts.
2. Job Data: Information about the jobs, such as job status, job configuration, job parameters, and job history.
3. Node Data: Information about the nodes, such as node status, node configuration, and node availability.
4. User Data: Information about the users, such as user details, user permissions, and user activity.
5. Plugin Data: Information about the plugins, such as plugin details, plugin configuration, and plugin compatibility.
6. System Data: Information about the Jenkins system, such as system configuration, system logs, and system health.
7. Queue Data: Information about the build queue, such as queued jobs, queue status, and queue history.
Overall, the Jenkins API provides a comprehensive set of data that can be used to monitor, analyze, and optimize the build process.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: