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

четверг, 20 августа 2015 г., 15:50:26 UTC+3 пользователь 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
>
> 2015-08-20 14:43 GMT+03:00 Richard Bywater <[email protected] <javascript:>
> >:
>
>> 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
>>
>> On Thu, 20 Aug 2015 at 23:36 Andrei Tuicu <[email protected] 
>> <javascript:>> wrote:
>>
>>> 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
>>>
>>> -- 
>>> 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 [email protected] <javascript:>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/090535e9-2bee-4f20-9af6-1ba527c75c2f%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/090535e9-2bee-4f20-9af6-1ba527c75c2f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> 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 
>> [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945rT53LpHcLFAO5z46gzv5QMfw_Qs%2BTU7G8LBAO2p9JHA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945rT53LpHcLFAO5z46gzv5QMfw_Qs%2BTU7G8LBAO2p9JHA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/700a0ba1-8ca3-4b1e-bf14-127325e87720%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to