BuildKite
Run fast, secure, and scalable CI pipelines on your own infrastructure
Integrate the BuildKite API with the Python API
Setup the BuildKite API trigger to run a workflow which integrates with the Python API. Pipedream's integration platform allows you to integrate BuildKite and Python remarkably fast. Free for developers.
Popular BuildKite and Python Actions#
Returns basic details about the user account that sent the request
Write Python and use any of the 350k+ PyPi packages available. Refer to the Pipedream Python docs to learn more.
Overview of BuildKite#
The BuildKite API is a powerhouse for automating your continuous integration and delivery (CI/CD) pipelines. With it, you can trigger builds, get information on agents and artifacts, and manage your organization's setup programmatically. Pipedream leverages this API to connect BuildKite with a myriad of other services, allowing for customized workflows that go beyond the standard CI/CD process. You can automate notifications, synchronize with project management tools, or even gather analytics to optimize your build processes.
Connect BuildKite#
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
buildkite: {
type: "app",
app: "buildkite",
}
},
async run({steps, $}) {
return await axios($, {
url: `https://api.buildkite.com/v2/user`,
headers: {
Authorization: `Bearer ${this.buildkite.$auth.api_token}`,
},
})
},
})
Overview of Python#
Develop, run and deploy your Python code in Pipedream workflows. Integrate seamlessly between no-code steps, with connected accounts, or integrate Data Stores and manipulate files within a workflow.
This includes installing PyPI packages, within your code without having to manage a requirements.txt file or running pip.
Below is an example of using Python to access data from the trigger of the workflow, and sharing it with subsequent workflow steps:
Connect Python#
def handler(pd: "pipedream"):
# Reference data from previous steps
print(pd.steps["trigger"]["context"]["id"])
# Return data for use in future steps
return {"foo": {"test":True}}