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

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

Stop Overengineering: Why Test IDs Beat AI-Powered Locator Intelligence for UI Automation

  We have all read the blogs. We have all seen the charts showing how Generative AI can "revolutionize" test automation by magically resolving locators, self-healing broken selectors, and interpreting UI changes on the fly. There are many articles that paints a compelling picture of a future where tests maintain themselves. Cool story. But let’s take a step back. Why are we bending over backward to make tests smart enough to deal with ever-changing DOMs when there's a simpler, far more sustainable answer staring us in the face? -             Just use Test IDs. That’s it. That’s the post. But since blogs are supposed to be more than one sentence, let’s unpack this a bit. 1. Test IDs Never Lie (or Change) Good automation is about reliability and stability. Test IDs—like data-testid ="submit-button"—are predictable. They don’t break when a developer changes the CSS class, updates the layout, or renames an element. You know...
Post a Comment
Read more