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

Jenkins API conitnues to make use of "Hudson" namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • core
    • None
    • ANY

      Understanding how to use the Jenkins API is made especially complex by the fact that much of the useful functionality is only available within the "Hudson" namespace - or at least this is how the documentation appears to present it.

      This is just plain dumb. It is totally unclear under what circumstances a developer should look in "Hudson" or in "Jenkins" to find the API of interest.

      As a (very) experienced software developer I am at a complete loss as to how to script what - to my initial impression - should be a trivial script to discover the "culprits" of a build break.

            Unassigned Unassigned
            smouch Smouch Smouch
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: