Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42160

Bitbucket notify plugin Enter a valid URL.

XMLWordPrintable

      I've set a jenkins in AWS and I've double checked my JENKINS_URL is properly set.

      It is private jenkins and it doesn't have public IP ou DNS and I'm also using pipeline.

      In my log shows :

      INFO: This request was sent: {
      "state": "SUCCESSFUL",
      "key": "547638fe58066db376e614e94721d075",
      "url": "http://my-privatejenkins.prd.dcd.company:8080/job/my-project-in-bitbucket/74/",
      "name": "my-project-in-bitbucket #74"
      }

      And the response is always

      INFO: This response was received: {"type": "error", "error": {"fields":

      {"url": ["Enter a valid URL."]}

      , "message": "Bad request"}}

      I've tried a workaround of setting JENKINS_URL as global env and got the same problem.

      I'm using the lateste docker image of jenkins in dockerhub and the latests version of the plugin.

      What am I missing? Is there any solution or workaround? Please any help would be appreciate.

          [JENKINS-42160] Bitbucket notify plugin Enter a valid URL.

          Elifarley added a comment - - edited

          The error message comes from BitBucket, so you need to ask them to solve this for you.

          BTW, the problem is that BitBucket doesn't accept uncommon domain suffixes (TLDs) in the URL field (this field corresponds to your Jenkins URL).

          In other words, "dcd.company" isn't a valid domain as seen by BitBucket.

          Elifarley added a comment - - edited The error message comes from BitBucket, so you need to ask them to solve this for you. BTW, the problem is that BitBucket doesn't accept uncommon domain suffixes (TLDs) in the URL field (this field corresponds to your Jenkins URL). In other words, "dcd.company" isn't a valid domain as seen by BitBucket.

            elifarley Elifarley
            gmotasilva Gustavo Mota
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: