Way to Force "Full Sync" in Jenkins Job Discovery

I encountered a case where there are still deleted tests (from GIT) in the Octane. So I tried to check in the Jenkins discovery job and found this statement in the ALM Octane UFT tests discovery

"By default, full sync is done for the first run of the job, and after that only ChangeSet sync is done. If you need to force full sync - define in the job a boolean parameter "Full Sync" and execute the job with this parameter is checked"

Where can I configure this "Full Sync" boolean parameter?

  • Verified Answer

    +1  
    Hello,

    This parameter should be defined directly in the job. To do this, open your Jenkins dashboard and navigate to the Jenkins job responsible for the ALM Octane UFT test discovery. Then, modify the job by adding the Boolean Parameter.

    I recommend contacting someone with Jenkins expertise to ensure it is done correctly, as Jenkins-related configuration is not part of our expertise. The name of the parameter is Full Sync.

    I hope this helps.

    Best regards,


    Bernal Salzar

    OpenText Customer Support Agent | ALM

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.

  • 0 in reply to   

    Yes, I have confirmed in the Jenkins Job, the Full Sync parameter is exist and already enabled. But still the Octane do not delete the deleted asset (in the GIT)

  • Verified Answer

    +1   in reply to 

    Hello,

    For case that UFT test has been deleted on repository we are not deleting the test on Octane so we will not loose the history of test and it's execution. what we are doing on this case is mark the test as not executable, you can find on test entity Yes/No field name executable and for deleted test it will set to 'No'

    Thanks,

    Nissim

  • 0 in reply to   

    Hi Nissim. Thank you for the info. That would explain a lot regarding Customer concern.

    I think about filtering the test in unassigned but the filter also affect/included in other modules but it will be another discussion.

    I will create another question for this.