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

SCMSource.id should be part of out of the box API jelly

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Looks like after some of refactorings SCMSource.id become bundled in SCMSource that has DataBound annotations, but nowhere mentioned that implementators should insert invisible fields for scmsource, either it's id will be constantly changing that influence on a lot of places.
      branch-api is already wrapping config-details, so it should handle `id` itself out of the box.

        Attachments

          Activity

          Hide
          stephenconnolly Stephen Connolly added a comment -

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Show
          stephenconnolly Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            People

            • Assignee:
              Unassigned
              Reporter:
              integer Kanstantsin Shautsou
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: