Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Job id format inconsistent between /history and /jobs

#374

Using the 1.3-rc there is and inconsistency between the id's returned by /jobs and by /history. /jobs has uuid style id's, /history doesn't.

eg /api/2/jobs?authtoken=xxxxx&project=test1 returns

<?xml version="1.0"?>
<result success="true" apiversion="2">
  <jobs count="1">
    <job id="f4dc49a1-ea08-4d94-a753-8471451fc0f9">
      <name>uptime</name>
      <group/>
      <project>test1</project>
      <description/>
    </job>
  </jobs>
</result>

But /api/2/history?authtoken=xxxxxx&project=test1&recentFilter=1h returns

  <events count="3" total="3" max="20" offset="0">
    <event starttime="1310066105718" endtime="1310066109867">
      <title>uptime</title>
      <status>succeeded</status>
      <summary>uptime</summary>
      <node-summary succeeded="4" failed="0" total="4"/>
      <user>admin</user>
      <project>test1</project>
      <date-started>2011-07-07T19:15:05Z</date-started>
      <date-ended>2011-07-07T19:15:09Z</date-ended>
      <job id="1"/>
      <execution id="3"/>
    </event>

Reported by Gordon Johnston · July 8th, 2011 @ 07:55 AM

State: new
Milestone: none
Assigned to: nobody

Activity

  1. Greg Schueler
    Greg Schueler
    • Tag set to api, bug
    • Assigned user set to Greg Schueler
    • Milestone set to Rundeck 1.3
    • Milestone order changed from 72 to 0

    thanks for the report!

    July 8th, 2011 @ 10:31 AM

  2. Deleted User

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.