Hi Slide,

mstest plugin  is hosted on subversion not Github. I am not sure how to
send pull request for subversion in Github way.
For https://issues.jenkins-ci.org/browse/JENKINS-19360 , change required is
added as attachment.

Thats why checking in this forum if there are any active maintainers for
mstest plugin.

Thanks,
Suresh


On Mon, Nov 17, 2014 at 3:00 PM, Slide <[email protected]> wrote:

> The best way to do this would be to fork the repo on Github, make the
> changes in your fork and submit a pull request. It makes it MUCH easier to
> review changes.
>
> On Mon Nov 17 2014 at 3:42:53 PM Suresh Nallamilli <[email protected]>
> wrote:
>
>> Hi
>>
>>
>>
>> Are there any active maintainers for mstestplugin(
>> https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin)?
>>
>> If yes requesting to review the patch submitted for issue#
>> https://issues.jenkins-ci.org/browse/JENKINS-19360 ?
>>
>>
>>
>> I will wait for a week for someone to respond and if no one responds i
>> will request for write access to repo and see if I can release a new
>> version.
>>
>>
>>
>>
>>
>> *Issue:*
>>
>> When using the older Microsoft test running tool (MSTest), MSTest saved
>> the name of the each test in the following format:
>>
>> My.Type.Name, Version=1.0.0.0, Culture=neutral,
>> PublicKeyToken=1234567890ABCDEF
>>
>>
>>
>> Whereas the newer Microsoft test running tool (vstest.console.exe) uses
>> simpler format: My.Type.Name
>>
>>
>>
>> Previously, the .xsl file assumed there would always be a comma in the
>> test name, and it would substring the name to get the value “My.Type.Name
>> ”.
>>
>> With vstest.console.exe there is no comma, so XSL treats the substring
>> operation as ‘not a match’ and returns no value.
>>
>> *Resolution:*
>>
>>                 With the patch(
>> https://issues.jenkins-ci.org/browse/JENKINS-19360), there’s now an
>> <xsl:choose> with an <xsl:otherwise> clause that handles
>>
>> the no comma case (line 78). Thus supporting either naming scheme.
>>
>>
>>
>> We tested this in our environment and new change is working for us.
>>
>>
>>
>> Thanks,
>>
>> Suresh Nallamilli.
>>
>>
>>
>> --
>> 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].
>> 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].
> 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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to