GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Is they any way we can get the UTPLSQL historical runs by using RUN ID and their coverage · Issue #192 · utPLSQL/utPLSQL-cli

Is they any way we can get the UTPLSQL historical runs by using RUN ID and their coverage #192

New issue
Copy link
New issue
Copy link
Open
Open
Is they any way we can get the UTPLSQL historical runs by using RUN ID and their coverage#192
Copy link
Labels
question

Description

@venkat-kasula
venkat-kasula
opened on Feb 8, 2021
Issue body actions

Is they any way we can get the UTPLSQL historical runs by using RUN ID which gets generated automatically and their coverage using the inbuilt tables of UTPLSQL.

used the below query but could not find any data in the result of below query

select owner, name, type
from dbmspcc_runs r
join dbmspcc_units u
on r.run_id = u.run_id

Activity

  1. venkat-kasula commented on Feb 23, 2021

    @venkat-kasula
    venkat-kasula
    on Feb 23, 2021
    Author
    More actions

    @pesse can you please help me here

  2. pesse commented on Jun 10, 2021

    @pesse
    pesse
    on Jun 10, 2021
    Member
    More actions

    Hey @venkat-kasula - thanks for your patience. The last months have been a bit rough.

    There is no way to get data about historical runs in utPLSQL or the cli. This is a design decision, because storing the outcomes of a run is the task of the surrounding CI environment (e.g. Jenkins).
    There is a lightweight Apex solution you might be interested in: https://github.com/triologygmbh/utPLSQL-APEX

    There is also an even more lightweight way of storing your run results in the database, though you cannot do that via the cli right now (well, you could create your own reporter to do that, but that's a bit more effort):

    create table ut_runs ( 
      run_timestamp timestamp,
      output varchar2(4000)
    );
    
    insert into ut_runs
      select current_timestamp, column_value from table(ut.run());
  3. pesse
    added
    question
    on Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    question

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.