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

Provide more hints that Gitea plugin requires global configuration

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • gitea-plugin
    • None

      While creating the multibranch pipeline, if you add branch source as gitea it would give not happen.

      As in repository we need to give the clone url for the project but that is a drop down and no data is there to select in that dropdown. Because of which there is blocker in creating the multibranch pipeline for gitea repo.

          [JENKINS-71430] Provide more hints that Gitea plugin requires global configuration

          Mark Waite added a comment -

          There is not enough information included in this issue report for anyone to take action. Please provide the detailed information requested in "How to report an issue". If that information is not provided, this issue will be closed as "Cannot reproduce".

          I'm using the Gitea plugin with my Gitea server through an HTTPS connection without any issue. I suspect that this is a local configuration issue, not anything that the Jenkins Gitea plugin can resolve.

          Mark Waite added a comment - There is not enough information included in this issue report for anyone to take action. Please provide the detailed information requested in "How to report an issue" . If that information is not provided, this issue will be closed as "Cannot reproduce". I'm using the Gitea plugin with my Gitea server through an HTTPS connection without any issue. I suspect that this is a local configuration issue, not anything that the Jenkins Gitea plugin can resolve.

          Mark Waite added a comment - - edited

          You've not provided the information listed in "How to report an issue". That makes it much more difficult for others to help you, since they need to guess what you were doing and they need to guess the context where you were doing it. Those guesses are often wrong. They are a waste of time for the person doing the guessing and for the person submitting the issue.

          My guess is that you have not defined the Gitea server in the Jenkins global configuration. That is described in the Gitea plugin documentation under initial configuration.

          My initial configuration looks like this:

          After completing the initial configuration, then my multibranch job configuration looks like this:

          Mark Waite added a comment - - edited You've not provided the information listed in "How to report an issue". That makes it much more difficult for others to help you, since they need to guess what you were doing and they need to guess the context where you were doing it. Those guesses are often wrong. They are a waste of time for the person doing the guessing and for the person submitting the issue. My guess is that you have not defined the Gitea server in the Jenkins global configuration. That is described in the Gitea plugin documentation under initial configuration . My initial configuration looks like this: After completing the initial configuration, then my multibranch job configuration looks like this:

          Lauri added a comment -

          The issue is that it is not immediately obvious that you must enter the "Owner" before you can select the repositories.

          I also thought something was broken, but it was just that I hadn't entered the owner.

          Lauri added a comment - The issue is that it is not immediately obvious that you must enter the "Owner" before you can select the repositories. I also thought something was broken, but it was just that I hadn't entered the owner.

          Mark Waite added a comment -

          lauri thanks for the comment. You and I are making the same assumption. Since the original submitter of the issue did not provide clarification, that seems like the best that we can do.

          I'm interested in ideas and (even better) pull requests to the Gitea plugin to improve the experience for users.

          If the repository field had red text near it when the system level configuration was incomplete, would that be enough? The red text might include a hyperlink to the system configuration page so that the user could provide the global configuration.

          Mark Waite added a comment - lauri thanks for the comment. You and I are making the same assumption. Since the original submitter of the issue did not provide clarification, that seems like the best that we can do. I'm interested in ideas and (even better) pull requests to the Gitea plugin to improve the experience for users. If the repository field had red text near it when the system level configuration was incomplete, would that be enough? The red text might include a hyperlink to the system configuration page so that the user could provide the global configuration.

          Lauri added a comment -

          markewaite, yes, just an asterisk or text that the Owner field is mandatory would be enough. Even better would be to add a message "No repositories were found for this owner (user/organization)".

          Lauri added a comment - markewaite , yes, just an asterisk or text that the Owner field is mandatory would be enough. Even better would be to add a message "No repositories were found for this owner (user/organization)".

            Unassigned Unassigned
            ritukiit Rituraj
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: