Skip to content

[JENKINS-23228] Support the range notation for pagination in API #23143

Closed

Description

@jenkins-infra-bot

This issue tracks the integration of jenkinsci/stapler#29 into core.

This needs to be documented in _api.jelly.


Originally reported by kohsuke, imported from: Support the range notation for pagination in API
  • assignee: kohsuke
  • status: Resolved
  • priority: Major
  • component(s): core
  • resolution: Fixed
  • resolved: 2014-06-08T17:17:39+00:00
  • votes: 0
  • watchers: 4
  • imported: 2025-11-24
Raw content of original issue

This issue tracks the integration of jenkinsci/stapler#29 into core.

This needs to be documented in _api.jelly.

Activity

  1. jenkins-infra-bot commented on May 29, 2014

    @jenkins-infra-bot
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment:

      Released as Stapler 1.226

    Released as Stapler 1.226

  2. jenkins-infra-bot commented on Jun 8, 2014

    @jenkins-infra-bot
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original comment:

      Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml core/src/main/resources/hudson/model/Api/index.jelly http://jenkins-ci.org/commit/jenkins/c95777e47638fa7483611a2a09a4b26de8e9a327 Log: [FIXED JENKINS-23228]

      Documented this feature and integrated a newer version of Stapler.

      I took the opportunity to reorder the content in the section, so that the tree parameter becomes the main subject.

      At this point, the depth parameter should be only used in a limited circumstance, so it should be treated as such.

    Code changed in jenkins
    User: Kohsuke Kawaguchi
    Path:
    changelog.html
    core/pom.xml
    core/src/main/resources/hudson/model/Api/index.jelly
    http://jenkins-ci.org/commit/jenkins/c95777e47638fa7483611a2a09a4b26de8e9a327
    Log:
    [FIXED JENKINS-23228]

    Documented this feature and integrated a newer version of Stapler.

    I took the opportunity to reorder the content in the section, so that
    the tree parameter becomes the main subject.

    At this point, the depth parameter should be only used in a limited
    circumstance, so it should be treated as such.

  3. jenkins-infra-bot commented on Jun 8, 2014

    @jenkins-infra-bot
    Author
    dogfood:

    Integrated in jenkins_main_trunk #3443
    [FIXED JENKINS-23228] (Revision c95777e)

    Result = SUCCESS
    kohsuke : c95777e47638fa7483611a2a09a4b26de8e9a327
    Files :

    • core/pom.xml
    • changelog.html
    • core/src/main/resources/hudson/model/Api/index.jelly
  4. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original is_duplicated_by from Jira: JENKINS-22977]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions