Project

General

Profile

Actions

Task #644

closed

Task #621: Create LongRunningTask detail page

Dry Run

Added by Marek Klement over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marek Klement
Category:
Long running task
Target version:
Start date:
08/10/2017
Due date:
% Done:

100%

Estimated time:
Owner:

Description

Implement demo process of the LongRunningTask which will predict what will run and how the result will look like.

Actions #1

Updated by Marek Klement over 6 years ago

  • Status changed from New to Needs feedback
  • Assignee changed from Marek Klement to Radek Tomiška

Technical design for:
Dry Run
backend

Implement process which won’t run. It will only pretend running and than will show which entities will be affected by this LRT.

1. Class IdmScheduledTask is already prepared for DryRun, so it is needed to cut running a process and just take the entities which it will change.
2. In class AbstractSchedulableStatefulExecutor function processCandidate will be edited. It will also get boolean dryRun which will be used when making result. If dryRun than new State result DRY_RUN else it will run process.
3. In function executeProcess will be added boolean dryRun by scheduledTaskService

frontend

1. When someone will be making new Scheduled Task, there will be checkbox in popover where you select if dryRun.
2. LRT dryRun detail will show table of entities which will be affected by this process.

Actions #2

Updated by Radek Tomiška over 6 years ago

  • Status changed from Needs feedback to In Progress
  • Assignee changed from Radek Tomiška to Marek Klement
Actions #3

Updated by Marek Klement over 6 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Marek Klement to Radek Tomiška

What I was thinking was that on page Scheduled Tasks there will be checkbox (or something similar) wheter it should be runned like dryrun or not. As soon as you hit run or add it will save it already with dryrun. After this when you go to All tasks page, you just simply can run it and than look into possible results.

Actions #4

Updated by Radek Tomiška over 6 years ago

I removed my last comment, because flag and new state DRY_RUN is needed as you says.

I am not sure, about this dry run mechanism, we will need to talk about it at first.

Actions #5

Updated by Radek Tomiška over 6 years ago

  • Status changed from Needs feedback to In Progress
  • Assignee changed from Radek Tomiška to Marek Klement

The design is ok, you can continue .)

Actions #6

Updated by Vít Švanda over 6 years ago

  • Target version changed from Diamond (7.4.0) to Emerald (7.5.0)
Actions #7

Updated by Radek Tomiška over 6 years ago

  • Target version deleted (Emerald (7.5.0))
Actions #8

Updated by Radek Tomiška over 6 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Marek Klement to Radek Tomiška
Actions #9

Updated by Radek Tomiška over 6 years ago

  • Status changed from Needs feedback to In Progress
  • Assignee changed from Radek Tomiška to Marek Klement
  • Target version set to Garnet (7.7.0)
  • % Done changed from 0 to 90

I did review, see review notes in #621.

Dry run is merged into develop and work now. Add please documentation and you can close this ticket.

Actions #10

Updated by Radek Tomiška about 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF