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

When configure job the list of credentials returns HTTP 504

    • 934.4.2

      Related to https://issues.jenkins.io/browse/JENKINS-75184

      I am still unable to list credentials when creating or updating a Jenkins multibranch pipeline using Bitbucket Branch Source Plugin. I have this issue since version 933.0.1, so the last valid version was 932.vff504b_2003fe. There is no error log in system logs. On the other hand, we lost the build notifications in the PRs, this feature was fixed on 933.2.1 but we can't upgrade to that version because of the problem described in this ticket.

      As you can see in the following image, the credentials' dropdown keeps waiting

      Until I get a 504 Gateway timeout.

          [JENKINS-75225] When configure job the list of credentials returns HTTP 504

          Daniel created issue -
          Daniel made changes -
          Description Original: Related to [https://issues.jenkins.io/browse/JENKINS-75184]

          I am still unable to list credentials when creating or updating a Jenkins multibranch pipeline using Bitbucket Branch Source Plugin. I have this issue since version 933.0.1, so the last valid version was [932.vff504b_2003fe|https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/932.vff504b_2003fe/cloudbees-bitbucket-branch-source.hpi]. On the other hand, we lost the build notifications in the PRs, this feature was fixed on [933.2.1|https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/933.2.1/cloudbees-bitbucket-branch-source.hpi] but we can't upgrade to that version because of the problem described in this ticket.

          As you can see in the following image, the credentials' dropdown keeps waiting

          !image-2025-02-04-08-24-35-631.png!

          Until I get a 504 Gateway timeout.

          !image-2025-02-04-08-25-11-934.png!
          New: Related to [https://issues.jenkins.io/browse/JENKINS-75184]

          I am still unable to list credentials when creating or updating a Jenkins multibranch pipeline using Bitbucket Branch Source Plugin. I have this issue since version 933.0.1, so the last valid version was [932.vff504b_2003fe|https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/932.vff504b_2003fe/cloudbees-bitbucket-branch-source.hpi]. There is no error log in system logs. On the other hand, we lost the build notifications in the PRs, this feature was fixed on [933.2.1|https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/933.2.1/cloudbees-bitbucket-branch-source.hpi] but we can't upgrade to that version because of the problem described in this ticket.

          As you can see in the following image, the credentials' dropdown keeps waiting

          !image-2025-02-04-08-24-35-631.png!

          Until I get a 504 Gateway timeout.

          !image-2025-02-04-08-25-11-934.png!
          Nikolas Falco made changes -
          Summary Original: Unable to list Credentials New: When configure job the list of credentials returns HTTP 504
          Nikolas Falco made changes -
          Remote Link New: This issue links to "PR (Web Link)" [ 30515 ]

          Nikolas Falco added a comment -

          Workaround is move any bitbuket credentials under a specific domain (*bitbucket.org) so than any AmazonECR credentials are excluded by the host filter

          Nikolas Falco added a comment - Workaround is move any bitbuket credentials under a specific domain (*bitbucket.org) so than any AmazonECR credentials are excluded by the host filter
          Nikolas Falco made changes -
          Link New: This issue is related to JENKINS-75184 [ JENKINS-75184 ]

          Nikolas Falco added a comment - Incremental build available https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/cloudbees-bitbucket-branch-source/934.4.21001.v8351205fe227/cloudbees-bitbucket-branch-source-934.4.21001.v8351205fe227.hpi

          Daniel added a comment -

          Thank you Nikolas! Is the workaround something that we can test with the old and 'failing' version, or is what you included in the incremental version?

          I will update and test tomorrow morning

          Daniel added a comment - Thank you Nikolas! Is the workaround something that we can test with the old and 'failing' version, or is what you included in the incremental version? I will update and test tomorrow morning

          Nikolas Falco added a comment - - edited

          Is the workaround something that we can test with the old and 'failing' version

          Yes of course, we use to limite the credentials list to avoid show credentials related to other kind of software.

          EDIT: I test the workaround and amazon ECR token should be moved in a specific domain because credentials are listed looking into each domain that matches the host list so if ECR credentials are in global domain o in a domain for which include or exclude list matches bitbucket.org than you have the issue.

          Nikolas Falco added a comment - - edited Is the workaround something that we can test with the old and 'failing' version Yes of course, we use to limite the credentials list to avoid show credentials related to other kind of software. EDIT: I test the workaround and amazon ECR token should be moved in a specific domain because credentials are listed looking into each domain that matches the host list so if ECR credentials are in global domain o in a domain for which include or exclude list matches bitbucket.org than you have the issue.
          Nikolas Falco made changes -
          Attachment New: image-2025-02-04-12-55-20-182.png [ 63898 ]

            nfalco Nikolas Falco
            daniel_gomez Daniel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: