Request hosting for plugin

[Andrei Tuicu]

Hello everyone,

I would like to request hosting for the following plugin that links Jira Issues to failing JUnit tests.

GitHub URL: https://github.com/andreituicu/JenkinsJiraPlugin

Repository Name: jira-issue-plugin

GitHub username: andreituicu

Jenkins username: andreituicu

Description: You can link issues to failing JUnit tests directly in the Jenkins interface and also create issues with one click based on a configured template. 

Thank you,

Andrei Tuicu

[Richard Bywater]

I'm wondering how your plugin differs from the other three Jira plugins that already exist including JiraTestResultReporter which appears to perform the same function?

If similar, would it make more sense to collaborate with one of the other plugin maintainers to enhance the existing plugin?

Richard

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/090535e9-2bee-4f20-9af6-1ba527c75c2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrei Tuicu]

Hello Richard,

There are a number of differences. First of all this plugin does not create issues for you, you decide if you want to create an issue for a specific test, but I think it's better if I show you (please, see photo attachment 1). The linking issue appears next to the failing test in the Jenkins UI (please, also see photo attachment 1). Also, you can define in the configuration  (please, see photo attachment 2) how each issue field will be completed and you can use here the environment variables defined by Jenkins, or variables that provide informations about the test result.

Thank you,

Andrei Tuicu

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/r65XTtLqxiU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945rT53LpHcLFAO5z46gzv5QMfw_Qs%2BTU7G8LBAO2p9JHA%40mail.gmail.com.

[Oleg Nenashev]

+1 for improving the existing plugin or adding a new mode there.

четверг, 20 августа 2015 г., 15:50:26 UTC+3 пользователь Andrei Tuicu написал:

[Catalin Luta]

Hey Guys,

I'm one of the contributors to this new plugin and I'd like to try and explain why we chose to file for hosting instead of extending the Result Publisher plugin.

First off, let me give you a bit of background info: We've been having trouble with mapping test fails to JIRA issues for over a year now and we've been looking into ways of fixing this in order to avoid the overhead of manually querying and searching for related builds/fails/issues. While the Test Result Publisher did meet some of our needs, it had major drawbacks:

- No relation visible in Jenkins to corresponding Issues

- No possibility of configuring the template for the newly created Issues

- High risk of flooding JIRA instance with many issues (we have roughly 3000 tests, which may fail randomly)

The main focus of our plugin is to offer the possibility of linking test fails to JIRA issues, be they existing or newly created. During its development we've realized that there are some other issues with the other plugins, like security and the connectors used (if any), so development just kept going. The main features the plugin currently has are:

- Ability to link existing JIRA issues with tests fails

- Ability to create new JIRA issues for new test fails

- Visual representation of the link in the Publisher page, with issue number/link and status

- Link persistency between builds

- Configuration of Issue template on a job level (including labels, components etc.)

- Thread-safety

- Uses the Atlassian JIRA rest Java library

- Supports multi-configuration projects

We do realize that some people would require the functionality that JIRA Test Result Publisher has, but there would be two options for that:

- use both plugins concurrently

- add the functionality of the Result Publisher plugin to our own

I, for one, would suggest adding the functionality to our infrastructure, because that would take less time to achieve and we have a more robust infrastructure. 

All in all, while we are advocates of reusing things and contributing to existing things, this current situation looks like an overly complicated approach to grafting, by tying the whole tree to a branch, rather than tying the branch to the tree.

Regards,

Catalin

[Christopher Orr]

On 21/08/15 12:44, Catalin Luta wrote:
> We do realize that some people would require the functionality that JIRA
> Test Result Publisher has, but there would be two options for that:
> - use both plugins concurrently
> - add the functionality of the Result Publisher plugin to our own

The second option could be possible — I believe there have been some
plugins that have replaced (or are intended to replace) existing
plugins, where the new plugin includes the existing plugin's features,
and takes over the existing plugin's artifact ID, allowing existing
users to upgrade.

But in this case, it needs to be made sure that the new plugin migrates
users' settings from the existing plugin correctly.

> I, for one, would suggest adding the functionality to our
> infrastructure, because that would take less time to achieve and we have
> a more robust infrastructure.

"Robust infrastructure" and a GitHub repository with zero tests in it
don't really go together IMO ;)

I'm sure adding the existing code to your plugin without replacing the
existing plugin would "take less time" for *you*, but it would be
terrible for everyone else, and that's why we want to prevent plugin
proliferation.

So (if you want to release the plugin via the Jenkins update centre),
taking over the existing plugin and including its functionality might be
the best solution.

Regards,
Chris

[Catalin Luta]

Hey Christopher,

I've contacted Stephan, the owner of the other plugin, to see what we can do about it.

I'm sure adding the existing code to your plugin without replacing the 
existing plugin would "take less time" for *you*, but it would be 
terrible for everyone else, and that's why we want to prevent plugin 
proliferation. 

Of course I was implying that it would take less time for us, considering we're the ones doing the work, right? We are using the plugin in our company, so from our point of view everything is good and done. We're just trying to give something back to the community, but we do have limited time to invest in this pursuit. We're also taking some responsibility on our shoulders by trying to maintain the plugin, so the least we've expected was better cooperation. Also, I do not see what would be terrible for everybody else. They would just use a new plugin which would replace the existing one. There would be only one new checkbox to fill and no other persistency problems. 

Granted, proliferation is to be avoided. But I do believe that individual cases may appear when the given rules only do harm, and this is one of them.

I'll come back with a reply from Stephan and we'll see what future course of action we can take.

Regards,

Catalin

[Catalin Luta]

Hello guys,

I've received a reply from Stephan. Due to lack of time he can no longer maintain the plugin (JiraTestResultReporter), so he would be happy if we could take it over. 

Is there a standard procedure of doing this?

Cheers,

Catalin

[Oleg Nenashev]

Hi Catalin,

What are your GitHub and JIRA accounts? Should we also add Andrei to the plugin developers?

Thanks in advance,

Oleg

понедельник, 14 сентября 2015 г., 14:45:34 UTC+3 пользователь Catalin Luta написал:

[Catalin Luta]

Hello Oleg,

My users are as follows:

GitHub username: catalinluta

Jenkins/Jira username: catalinluta

Yes, please, add Andrei as a plugin dev also.

Thanks for the help!

Regards,

Catalin

[Oleg Nenashev]

Hi,

Sorry for the delay. The permissions have been granted. You should get invitations to jenkinsci organization soon.

Hopefully everything goes well with the features integration. Good luck!

Best regards,
Oleg

пятница, 18 сентября 2015 г., 14:32:08 UTC+3 пользователь Catalin Luta написал: