Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added possibility to have multiple finders #47

Closed
wants to merge 3 commits into from

Conversation

judovana
Copy link

@judovana judovana commented Oct 9, 2019

Hi!

This is direct adaptation and rebase to tip of #23 , whic can be closed (unless merged first of course)

I had merged individual commits to single one - it still have sense, and to rebase it one by one was extremely painful.

Copy link
Contributor

@sparkoo sparkoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. However, you should address comments from review on original PR
#23 (comment)
#23 (comment)

@@ -244,6 +243,46 @@ private static Pattern compilePattern(PrintStream logger, String regexp) {
return pattern;
}

/** cut off first item as it is provided with getters */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this comment is no longer valid. I was using only list with 0th item as primary text finder. However, now there is primaryTextFinder and list for others.


// backward compatibility getters below
// all these getters are there for backward compatibility
// get first field from list which is used to store original config values
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, no longer valid comment. we're not getting 0th element, but values from primaryTextFinder

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comments removed. Wil now jump to the #23 (comment)

@sparkoo sparkoo mentioned this pull request Oct 9, 2019
@judovana
Copy link
Author

Adapted to pipelines. Now struggling with html view test... not much successfully.

@judovana
Copy link
Author

@basil hi! Major issues were fixed. I think you can start with review.
I'm now testing DSL api.
I would like to fix #23 (comment) as separate changeset. ty in advance.

@basil
Copy link
Member

basil commented Oct 11, 2019

@basil hi! Major issues were fixed. I think you can start with review.
I'm now testing DSL api.
I would like to fix #23 (comment) as separate changeset. ty in advance.

A promising start. Looks like my first concern from #23 (comment) was addressed.

Now we need to address the second and third concerns from #23 (comment) and the concern from #23 (comment).

@judovana
Copy link
Author

hi! Thank you for eyballing it.
I would say that also third concern is fixed, inst it?
As for #23 (comment) , please dont torture me. I'm going to fix it, but it can be separate PR.

From my point of view only DSL verification is missing. I'm working on that, but am currently stuck on it. It can be seen in dsl dynamic api view, but methods the dynamic api viewer is showing do not have sense. Was Textfinder plgin actually ever working with dsl, after the change from databound constructors to databoundsetters? Was it wolring on all proeject types?

@judovana
Copy link
Author

ping please?

@judovana
Copy link
Author

@basil Hi!

Do you mind to confirm that also third concern is fixed please?
Do you really insists on fixing the #23 (comment) in initial changeset? I would really like to dereffer it it to another changeset.

Can you please help with the dsl? I spent few days on it, ant it was not working before this changeset too, or I'm doing something really wrong.

Please do not let this change to rot, You could see, that there are at least four teams world wide using this feature, and so now pathcing the builds of yours on thirs own. Thanx!

@judovana
Copy link
Author

Dear maintainers, collaboration with this project is really painful
Do you mind if we publish our fork on jenkinsci as new plugin?

@judovana
Copy link
Author

@judovana
Copy link
Author

Hi Basil!

You have forced us to rework the fully backward comaptible PR to this one. And once we did it, and once we fixed even all other nits, you stopped to communicate. Do you have some final resolution?

Maybe we should for as jenkins/multitext-finder-plugin?

@judovana
Copy link
Author

We have one more improvement in our for. A field, whicch based on regex can change displayName of run. Not sure if you are interesting in any such change. If not, thane probably we really should stay forked.

@judovana
Copy link
Author

judovana commented Aug 4, 2021

Ok. We will continue to live in our fork, https://github.com/judovana/text-finders-plugin/ and will release it as separate plugind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants