Option to handle test reports by Artifact Manager

[olegmaiboroda-lab49]

Currently, the plugin copies Robot Framework output files to the build directory. The purpose of this change is to implement an option that allows the plugin to treat test report files as artifacts and delegate the task of saving them to a configured in the system Artifact Manager.

Testing done

A significant part is covered by existing and added automated tests.
Also the manual testing is done on my AWS machine.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
  1. useArtifactManager boolean option added
  2. RobotPublisher changed to archive test results by Artifact Manager if useArtifactManager == true. Otherwise original logic is intacted.
  3. Corresponded links are modified to point to artifactory location if useArtifactManager == true.
• Link to relevant issues in GitHub or Jira
  Not quite the same, but related request: https://issues.jenkins.io/browse/JENKINS-71096
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[olegmaiboroda-lab49]

Hi @asimell
Could you please review and share your ideas if this enhancement can be included into release. If yes, I would be appreciated if you could provide some ETA.

[asimell]

Hi @olegmaiboroda-lab49

I'm currently on parental leave, so I don't have that much free time to review PRs as I do when I'm at work. I asked @Tattoo if he could review this, but he's also busy for a few weeks. This PR also has quite a few changes, so the review and testing will take a bit more time. Especially since Artifact Manager is not something I actively use.

In general, I like the addition, but I need to squeeze in time for the review from somewhere somehow. I'm sorry I can't actually give an accurate ETA right now. I hope you understand. But just to give you an answer, I'll say I can try to review it during September.

[olegmaiboroda-lab49]

Hi @Tattoo and @asimell
Has there been any clarity regarding the timing of this issue?
Yes I understand that it's hard to find time. I'm not even asking for a review under any circumstances, but just to let us know that it's on the schedule and will be done by a certain date. This would help us planning. 2 weeks are gone and we need at least have an idea when this can be rolled out.

[asimell]

@olegmaiboroda-lab49 hi, sorry for the delay. I'll try to find time for this during this or next week. After it's merged it shouldn't take long to release.

[asimell]

LGTM!

@Tattoo any comments from you?

[olegmaiboroda-lab49]

Hi @asimell. Thanks for merging this FB!
What is estimated time of release that will include this feature?

[asimell]

Hi @olegmaiboroda-lab49, there's still #88 pending. CI build failed for that so I need to double check it's not related to the PR. I'll make the release when everything is merged and passing.

[olegmaiboroda-lab49]

I'm very sorry for being annoying. As I can see #88 is merged. How far we are from the release now?

[asimell]

6.2.0 was released last week.