Skip to main content

Have you heard of "ngrok"?

It's a very cool tool that lets you expose a local webserver to the outside world (internet)- in short, it creates a secure tunnel on your local machine along with a public URL that you can use or give to your colleagues, friends, etc. for browsing or testing your local site. Go through this to know more about it: https://ngrok.com/docs I have used this where I wanted to expose my local running Jenkins to git for the webhook part.
Labels:

Comments

  1. Namit JainFebruary 3, 2021 at 1:04 PM

    Thanks for the nice information. I used it to expose my localhost URL (localhost:8080) on Jenkins to Git. From GIT, I wanted to send a push request to http://localhost:8080/github-webhook/

    With localhost in URL we would normally get an error that "We couldn't deliver this payload". To overcome this we need to provide a public IP address and this is where ngrok would come in handy.

    Mentioning below some of the steps:

    1. Download ngrok
    2. Run the .exe.
    3. Type ngrok http 8080 (8080 is where Jenkins is running)
    4. You will get an URL something like: 56139657bf53.ngrok.io , note that this is the substitute of localhost:8080.
    5. In your WebHook settings on git replace http://localhost:8080/github-webhook/ with http://56139657bf53.ngrok.io/github-webhook/ (no need to add 8080 again)
    6. Save it and you should be good to go.

    Point to note:
    1) Include "/" at the end of URL to avoid any issue
    2) For the generated link to work please keep the terminal window of ngrok open. Each time the terminal window is reopened it would generate a new link so keep it open to avoid any errors.
    3)Ensure that service (Jenkins in this case) should be running on the URL/port specified , else it would give an error.

    Thanks!

    ReplyDelete
    Replies
    1. Dheeraj GambhirFebruary 3, 2021 at 1:06 PM

      Thanks Namit for the detailed info. This should help others.

      Delete

Post a Comment

Popular posts from this blog

ARIA Snapshot in Playwright

  What is an ARIA Snapshot in Playwright? An  ARIA snapshot  in Playwright is a structured representation of a page’s  accessibility tree , which is used by assistive technologies (e.g., screen readers) to interpret the content of a web page. This snapshot helps verify if elements have the correct  roles, names, and properties  required for accessibility. Playwright provides the page.accessibility.snapshot() API to capture this accessibility tree at any given moment during test execution. How Does ARIA Work? ARIA ( Accessible Rich Internet Applications ) is a set of attributes that help improve accessibility by defining roles, states, and properties for elements that are not natively accessible. Example: In this case, the aria-label ensures that screen readers identify the button as “Submit Form.” How to Use ARIA Snapshots in Playwright? Playwright’s  accessibility.snapshot()   method retrieves the  accessible structure  of the page. Ex...
Post a Comment
Read more

Bruno vs Postman: Which API Client Should You Choose?

  As API testing becomes more central to modern software development, the tools we use to test, automate, and debug APIs can make a big difference. For years, Postman has been the go-to API client for developers and testers alike. But now, Bruno , a relatively new open-source API client, is making waves in the community. Let’s break down how Bruno compares to Postman and why you might consider switching or using both depending on your use case. ✨ What is Bruno? Bruno is an open-source, Git-friendly API client built for developers and testers who prefer simplicity, speed, and local-first development. It stores your API collections as plain text in your repo, making it easy to version, review, and collaborate on API definitions. 🌟 What is Postman? Postman is a full-fledged API platform that offers everything from API testing, documentation, and automation to mock servers and monitoring. It comes with a polished UI, robust integration, and support for collaborati...
Post a Comment
Read more

🔧 Self-Healing Selenium Automation with Java — A Smarter Way to Handle Broken Locators

  How to build smarter, more resilient automated tests? We’ve all been there — our Selenium test cases start failing because of minor UI changes like updated element IDs, renamed classes, or even reordered elements. It’s frustrating, time-consuming, and often the most dreaded part of maintaining automated tests. But what if your automation could heal itself? 💡 What is Self-Healing Automation? Self-healing automation  refers to the capability of a test automation framework to recover from minor UI changes by automatically trying alternative locators when the primary one fails. It’s like giving your test scripts a survival instinct. 🔨 🛠️ Implementation in Java + Selenium: Step by Step Step 1: Create a Self-Healing Wrapper We start by creating a custom class called SelfHealingDriver. This class wraps the standard WebDriver and handles locator failures gracefully. public   class   SelfHealingDriver { private   WebDriver driver ; public   SelfHealingDri...
Post a Comment
Read more