BugBug and Jenkins Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between BugBug and Jenkins on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about BugBug and Jenkins

Detailed info you need to know about BugBug and Jenkins integrations in WEXTL. Explore which modules apps support and how you connect them.

  • BugBug

    • Developer Tools
    • 3 triggers
    • 51 searches
    • 50 actions

    No-code browser test automation for web apps.[5]

  • Jenkins

    • Developer Tools
    • 2 triggers
    • 25 searches
    • 39 actions

    Manage Jenkins jobs, builds, nodes, views, plugins, and credentials on a self-hosted CI server.[6]

How to connect BugBug to Jenkins

Set up your BugBug and Jenkins integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between BugBug and Jenkins work in WEXTL?

WEXTL exposes actions and triggers for BugBug and Jenkins that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

BugBug triggersJenkins actions

BugBug modules

  • Check a Project Import Tests a project export File against BugBug before importing it. Reports whether it is Valid along with a Summary of its content.
  • Check a Test Import Looks over a test File and reports if it is Valid, with a Summary, without creating anything.
  • Create a Component Adds a reusable block of steps that tests can share. Give it a Name and switch Is Active to run it.
  • Create a Folder Makes a folder of a given Kind for organizing items. Set Parent ID to nest it inside another folder.
  • Create a Group Adds a group of steps to a test. Use At Index to place it, Is Component to make it a reusable component and Folder ID to file that component in a folder.
  • Create a Step Adds one action to a group, with a Type and optional Position or Name. Fill Step Fields (JSON) with the parameters of that action.
  • Create a Suite Creates a suite of tests that run together under a Run Profile ID. Set Run In Parallel to run its tests side by side, Auto Retry to retry failed tests and Auto Add New Tests to include every new test in it.
  • Create a Tag Creates a tag, using Color for its hex value and Project ID to place it in a specific project rather than the one tied to the token.
  • Create a Test Makes a browser test and keeps its Notes. Use Screen Size Type to run it on desktop, mobile or a custom screen, Folder ID to file it and Tag Names to tag it.
  • Create a Variable Defines a variable by Key and Type, with an optional Value. Turn on Is Secret to hide the value in BugBug.
  • Delete a Folder Removes a folder. Turn on Force to delete it even when it has content.
  • Delete a Group Deletes a group of steps from a test.
  • Delete a Project File Removes one uploaded file from a BugBug project.
  • Delete a Reference Screenshot Deletes a stored baseline image that visual comparison relies on.
  • Delete a Step Removes one action from a test.
  • Delete a Suite Deletes a suite of tests from your project.
  • Delete a Tag Removes a label from your project.
  • Delete a Test Removes a test from your BugBug project.
  • Delete Project Files in Bulk Deletes many project Files in one call and reports how many Steps Affected used them.
  • Detach a Component from a Test Turns a component used by a test into ordinary steps of that test, so edits no longer touch the shared block.
  • Download a Project Backup Downloads one saved Backup of a project as a file, with its File Name and Content Type.
  • Download a Project File Fetches the content of an uploaded project file as a File with its File Name and Content Type.
  • Download a Suite Run JUnit Report Gets the JUnit XML report of a finished suite run for use in CI tools.
  • Download a Test Run JUnit Report Gets the JUnit XML report of a single test run, which CI tools can read.
  • Download Test Run Logs Downloads the log file of one test run with its File Name and Content Type.
  • Export a Project as ZIP Packs the whole BugBug project into a ZIP file, which you can import elsewhere.
  • Export a Test as YAML Returns the full definition of a test, written as YAML text.
  • Export a Test as ZIP Packs a test with what it needs into a ZIP file for import elsewhere, with step passwords removed.
  • Get a Folder Reads one folder with its Name, Kind, Depth and Parent ID.
  • Get a Group Reads a step group with its Name, Is Component flag and Folder ID.
  • Get a Project File Pulls the record of an uploaded file with Extension, Size and URL, but not its bytes.
  • Get a Reference Screenshot Reads one baseline image record with its Screenshot URL and Browser Name.
  • Get a Run Profile Shows a run profile with its Name and whether it Is Default for new runs.
  • Get a Step Reads one step with its Type, Name and Group ID.
  • Get a Step Run Looks up how one step went in a test run, with its Status and Test Run ID.
  • Get a Suite Reads a suite, including Auto Retry, Before After All Enabled and Auto Add New Tests.
  • Get a Suite Run Loads a suite run with its Duration, Ended time and Error Code.
  • Get a Tag Returns one tag with its Color and Name. Pass a Project ID when the tag belongs to another project.
  • Get a Test Fetches a test with its Name, Tags and the Groups of steps.
  • Get a Test Run Pulls a test run with the Browser Name, Browser Version and Duration.
  • Get a Test Run Debug Artifact Retrieves one debugging file of a test run, by its Artifact Kind, with its File and Content Type.
  • Get a Variable Reads one variable by Variable Key, with its Value, Type and whether it Is Secret.
  • Get Component Usage Finds which tests use a component, returned as Usage and the Tests Ids.
  • Get Project File Usage Finds where an uploaded file is used and reports the Steps Count plus the Tests that reference it.
  • Get Project Settings Shows the defaults of your project, including Browser Width, Browser Height, Browser Language and the Initial Run Profile ID.
  • Get Suite Run Screenshots Pulls the screenshots taken during a suite run, grouped as Tests Runs.
  • Get Suite Run Status Checks how far a suite run has come, showing Status and Finished Tests.
  • Get Test Run Screenshots Pulls the screenshots taken during a test run, grouped as Steps Runs.
  • Get Test Run Status Checks how far a test run has come, showing Status and Finished Steps.
  • Get the API Status Checks that BugBug is reachable and says whether you are Authenticated.

Jenkins modules

  • Add a Job to a View Adds an existing Jenkins job to a view of your choice in Jenkins.
  • Build a Job Queues a build of a Jenkins job and returns the Queue item ID and Queue item URL of the waiting build.
  • Build a Job With Parameters Starts a parameterized job. Use Build parameters to send name and value pairs with the build, then follow it through the Queue item ID.
  • Cancel a Queue Item Cancels an item in the Jenkins build queue.
  • Cancel the Quiet Down Mode Ends quiet down mode on the Jenkins controller, switching it off again.
  • Copy a Job Creates a new job as a copy of an existing one. Use Newname to name the copy and From to say which job to copy.
  • Create a Credential Stores a new credential under a credentials Domain. Use Credential XML to supply the Jenkins configuration of the credential.
  • Create a Folder Creates a folder in Jenkins for organizing jobs. Use Folder name to label it.
  • Create a Job Defines a new Jenkins job from a Job name and its Config XML.
  • Create a Node Registers a new node, meaning a build machine, with the Jenkins controller.
  • Create a View Creates a view in Jenkins. Use View name to label the new view.
  • Delete a Build Removes one build from the history of a Jenkins job.
  • Delete a Credential Deletes one stored credential in a Jenkins domain.
  • Delete a Job Deletes a job from your Jenkins controller.
  • Delete a Node Removes a build node from Jenkins.
  • Delete a View Removes a view from the list of views in Jenkins.
  • Disable a Job Marks a Jenkins job as disabled on the controller.
  • Disable a Node Disables a build node in Jenkins through its toggle offline action.
  • Enable a Job Switches a disabled Jenkins job back on.
  • Enable a Node Enables a build node in Jenkins through its toggle offline action.
  • Enable the Quiet Down Mode Puts the Jenkins controller into quiet down mode. Use Reason to record why it was switched on.
  • Get a Build Fetches the JSON details Jenkins keeps about a build.
  • Get a Build Artifact Retrieves a single artifact file that a build has stored on the controller.
  • Get a Build Console Output Reads the plain-text console log that Jenkins recorded for a build.
  • Get a Build Test Report Retrieves the test report that Jenkins attached to a build, with the results of its test run.
  • Get a Credential Config Reads the stored configuration of a credential in a credentials domain, returned as Config XML.
  • Get a Job Fetches the JSON that Jenkins reports for a job.
  • Get a Job Config Downloads the XML that defines a job, returned as Config XML.
  • Get a Label Looks up a node label and returns what Jenkins knows about it.
  • Get a Node Pulls what Jenkins reports about a build node, as JSON.
  • Get a Node Config Reads how a node is configured and returns it as Config XML.
  • Get a Queue Item Looks up one item waiting in the build queue and returns what Jenkins reports for it.
  • Get a View Gets the JSON description that Jenkins keeps for a view.
  • Get a View Config Fetches the setup of a view and returns it as Config XML.
  • Get Build Environment Variables Lists the environment variables that Jenkins injected into a build while it ran.
  • Get Build Pipeline Stages Describes the pipeline stages of a build, as reported by the Jenkins workflow API.
  • Get Jenkins Server Info Reads the root information that the Jenkins server publishes about itself.
  • Get Overall Load Statistics Reads the load figures that Jenkins publishes for the whole controller.
  • Get the Current User Shows which Jenkins user your credential signs in as.
  • Install a Plugin Asks the Jenkins plugin manager to install the necessary plugins.
  • Kill a Build Forces a running build to end by calling the kill action of Jenkins.
  • Launch a Node Agent Starts the agent process that runs on a build node.
  • List Build Artifacts Lists the artifact files that a given build produced in Jenkins.
  • List Credentials Lists the credentials stored in a credentials Domain. Use Limit to set how many results are returned.
  • List Jobs Returns the jobs on your Jenkins controller. Use Limit to cap how many are returned.
  • List Nodes Finds the nodes registered with Jenkins. Use Limit to keep the results short.
  • List Plugins Shows the plugins installed in Jenkins, as reported by the plugin manager. Use Limit to read fewer of them.
  • List Queue Items Gets the items waiting in the build queue. Set Limit to cap how many are returned.
  • List Views Retrieves the views configured on the controller. Use Limit to keep the list short.
  • Make an API Call Calls the Jenkins REST API directly with a free-form request under your saved credential.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with BugBug and Jenkins integrations. Pick any from the list below if the current combination isn't the one you need.

Automate BugBug and Jenkins on WEXTL®

Claim your 3-day trial to build BugBug with Jenkins integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting BugBug and Jenkins.

How do I connect BugBug and Jenkins?

Connect your BugBug and Jenkins accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between BugBug and Jenkins?

Example: when the "Watch Events" trigger in BugBug fires, WEXTL can "Add a Job to a View" in Jenkins. BugBug has 3 triggers (including Watch Events, Watch Suite Runs, and Watch Test Runs). Jenkins has 64 actions (including Add a Job to a View, Build a Job, and Build a Job With Parameters). Add filters and transforms between steps when you need them.[1]

Can BugBug trigger actions in Jenkins, and Jenkins in BugBug?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate BugBug and Jenkins?

No. BugBug-to-Jenkins automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does BugBug integrate with Jenkins in real time?

Yes. Trigger-based automations start the moment BugBug (or Jenkins) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a BugBug + Jenkins integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect BugBug with Jenkins?

You can build your BugBug + Jenkins automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the BugBug and Jenkins integration.

  1. BugBug and Jenkins integration source code, module specs and credentials implementation.
  2. Our BugBug and Jenkins integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for BugBug and Jenkins, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. BugBug integration information
  6. Jenkins integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted BugBug and Jenkins integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore BugBug and Jenkins, or get started