Details

    • Similar Issues:

      Description

      see stackoverflow http://stackoverflow.com/questions/34270130/jenkins-next-execution-plugin-how-to-get-details-through-rest-api

      Please add support to expose the next-execution time in REST API. (in view)
      http://<url>/view/<view name>/api/json?pretty=true&depth=3

        Attachments

          Activity

          Hide
          ghulam_aleku ghulam alekuzei added a comment - - edited

          How can I get the widgets info? I tried from 0 to 5, it also return HTTP ERROR 404 not found.

          I opened a question in Stackoverflow too and didn't get any help there

          https://stackoverflow.com/questions/55476456/how-to-get-job-specific-scheduled-time-in-jenkins

          Show
          ghulam_aleku ghulam alekuzei added a comment - - edited How can I get the widgets info? I tried from 0 to 5, it also return HTTP ERROR 404 not found. I opened a question in Stackoverflow too and didn't get any help there https://stackoverflow.com/questions/55476456/how-to-get-job-specific-scheduled-time-in-jenkins
          Hide
          larrycai Larry Cai added a comment -

          thanks !!

          Show
          larrycai Larry Cai added a comment - thanks !!
          Hide
          ialbors Ignacio Albors added a comment -

          To be released soon

          Show
          ialbors Ignacio Albors added a comment - To be released soon
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ignacio Albors
          Path:
          src/main/java/hudson/plugins/nextexecutions/NextBuilds.java
          src/main/java/hudson/plugins/nextexecutions/NextExecutionsWidget.java
          http://jenkins-ci.org/commit/next-executions-plugin/bb75b6fb13133c10e0f3f113e995ad269bd0c3e9
          Log:
          Expose widget data through API.

          The URL pattern to view this info is:

          • <jenkins_url>/widgets/n/api/[json/xml...]
          • <jenkins_url>/view/<view_name>/widgets/n/api/[json/xml...]

          n - the order in which the widget appears in the sidebar being 0 (zero) the
          first widget.

          Fixes JENKINS-36210

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ignacio Albors Path: src/main/java/hudson/plugins/nextexecutions/NextBuilds.java src/main/java/hudson/plugins/nextexecutions/NextExecutionsWidget.java http://jenkins-ci.org/commit/next-executions-plugin/bb75b6fb13133c10e0f3f113e995ad269bd0c3e9 Log: Expose widget data through API. The URL pattern to view this info is: <jenkins_url>/widgets/n/api/ [json/xml...] <jenkins_url>/view/<view_name>/widgets/n/api/ [json/xml...] n - the order in which the widget appears in the sidebar being 0 (zero) the first widget. Fixes JENKINS-36210
          Hide
          larrycai Larry Cai added a comment -

          yes, I see <jenkins_url>/view/<view_name>/widgets/n for my jenkins server, it is part html.

          so will be good to have <jenkins_url>/view/<view_name>/widgets/n/api/json available

          Rgs, Larry

          Show
          larrycai Larry Cai added a comment - yes, I see <jenkins_url>/view/<view_name>/widgets/n for my jenkins server, it is part html. so will be good to have <jenkins_url>/view/<view_name>/widgets/n/api/json available Rgs, Larry
          Hide
          ialbors Ignacio Albors added a comment -

          There's this option:

          • <jenkins_url>/widgets/n/api/json...
          • <jenkins_url>/view/<view_name>/widgets/n/api/json...

          Where "n" would be the nth widget shown in the sidebar being 0 the first one.

          You should be able to see something now following that URL pattern without the /api... part.

          Does it sound reasonable?

          Show
          ialbors Ignacio Albors added a comment - There's this option: <jenkins_url>/widgets/n/api/json... <jenkins_url>/view/<view_name>/widgets/n/api/json... Where "n" would be the nth widget shown in the sidebar being 0 the first one. You should be able to see something now following that URL pattern without the /api... part. Does it sound reasonable?
          Hide
          larrycai Larry Cai added a comment -

          First thought is the url like you stated "/view/<view name>/api/json?pretty=true&depth=3". And if it is not possible, you can decide the suitable url to use.

          Surely I hope the url can contain the view name.

          Thanks.

          Rgs, Larry

          Show
          larrycai Larry Cai added a comment - First thought is the url like you stated "/view/<view name>/api/json?pretty=true&depth=3". And if it is not possible, you can decide the suitable url to use. Surely I hope the url can contain the view name. Thanks. Rgs, Larry
          Hide
          ialbors Ignacio Albors added a comment -

          Where do you expect to find this information?

          I mean, in "/view/<view name>/api/json?pretty=true&depth=3" there is no data exposed related to any widget. And, AFAIK, there's no way to show it in that kind of URL (bound to a View).

          Would it be ok an independent URL only for this widget?

          Show
          ialbors Ignacio Albors added a comment - Where do you expect to find this information? I mean, in "/view/<view name>/api/json?pretty=true&depth=3" there is no data exposed related to any widget. And, AFAIK, there's no way to show it in that kind of URL (bound to a View). Would it be ok an independent URL only for this widget?

            People

            • Assignee:
              ialbors Ignacio Albors
              Reporter:
              larrycai Larry Cai
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: