Labeling with the TFS Plugin and Visual Studio Online

2014-12-31 Thread Rob D
Anyone who is using the TFS Plugin with Visual Studio Online (VSO), are you 
labeling your code? If you are, how are you doing that? A labeling feature 
was added to the TFS Plugin but so far I have not been able to get it to 
work with VSO. How do you apply labels in VSO with Jenkins?

Thanks,
Rob

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f145bfd3-6db7-48b5-b6a5-b586b9c21860%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Can't get log info with Groovy Postbuild Plugin

2014-12-10 Thread Rob D
I'm using the Groovy Postbuild Plugin in Jenkins on Windows 7. I was trying 
to match strings in a file but when that failed, I reduced it to the point 
where I am just searching for a string in another string. It will never 
find a match. I must be misunderstanding how Groovy works or else it just 
isn't working in this plugin. Please tell me what I am doing wrong.

def txt = slkd Cskk sdwo Csks swkdCsksl
def matcher = txt  =~ /Cs/ 
if(matcher.matches()){
   manager.addShortText(match)
}
else {
   manager.addShortText(no match)
}

Thanks,
Rob

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cbc1569e-959d-45a2-9ce2-f3acf3f021ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Tagging or labeling code

2014-12-03 Thread Rob D
We are using Visual Studio Online for source control and Jenkins to do 
builds, tests, etc. I have things working except nothing is getting tagged. 
Is there a plugin that integrates with Visual Studio Online or TFS to 
create tags (labels) and facilitates moving releases through the release 
process?

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2d643994-3f23-40e0-965d-b5de175484ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: ***NO_CI*** — Account Service??

2014-11-27 Thread Rob D
In case anyone else runs into this, I figured out what is going on. We are 
in the process of moving from using VSO for builds to Jenkins. We will 
still use VSO for version control. During the transition, both are running 
in parallel and gated-checkin in used in the VSO build definitions. When 
VSO checks in code after a gated checkin, it adds ***NO_CI*** to the 
comment. This is a code that tells VSO not to kick off yet another build. 
Since VSO is what actually checks in the code, the user is shown as Account 
Service, i.e., the original user who committed is not passed through. So, 
if the VSO build definitions are turned off, ***NO_CI*** disappears and 
the user name of the one who checks in the code shows up.

On Wednesday, November 26, 2014 10:52:38 AM UTC-6, Rob D wrote:

 I have Jenkins connected to Visual Studio Online. Builds are working 
 however when I click on changes and look at the list, all changes 
 show ***NO_CI*** — Account Service (account name). I believe it is saying 
 the account that made the code change is Account Service. Shouldn't it list 
 here the account name of the actual users that committed code? If so, any 
 suggestions on what I have set up incorrectly?

 Thanks,
 Rob


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/37b976c0-7e45-42af-809c-e393eb38a99b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


***NO_CI*** — Account Service??

2014-11-26 Thread Rob D
I have Jenkins connected to Visual Studio Online. Builds are working 
however when I click on changes and look at the list, all changes 
show ***NO_CI*** — Account Service (account name). I believe it is saying 
the account that made the code change is Account Service. Shouldn't it list 
here the account name of the actual users that committed code? If so, any 
suggestions on what I have set up incorrectly?

Thanks,
Rob

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4b888a35-fc74-4caa-813e-57d6c1794d83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Path to projects not working correctly.

2014-11-19 Thread Rob D
I am using Visual Studio Online for source control via the TFS Plugin. For 
Server URL, I am pointing to the DefaultCollection. The Project Path 
traverses from there down to the folder that contains all project folders. 
I am using the MSBuild Plugin and for the MSBuild Build File, I specify the 
project folder/project file. There are two different projects set up on two 
different Jenkins builds. When code is committed to one of the projects, 
i.e., in only one of the project folders, both Jenkins jobs kick off a 
build.

How does Jenkins determine when code has changed for a particular job? Is 
it based on the Project path in the TFS Plugin and everything below that 
location triggers a build?


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Publishing vstest results?

2014-11-11 Thread Rob D
Thanks Marton and Jeff. I was out for a few days and just now had a chance 
to work on this. Test results are now displaying.

Rob

On Thursday, November 6, 2014 8:54:53 AM UTC-6, Jeff Dege wrote:

 First - added a build action: run unit tests with VSTest.console
 Second - added a build-action: Execute Windows batch command to convert 
 the results from vstest to junit
 Third - added a post-build action: Publish JUnit test result report

 What VSTest.console outputs is XML, what the JUnit report publisher 
 expects is XML. But the schemas differ, and the filenames are different.

 The mstest-to-junit.xsl file, attached to 
 https://issues.jenkins-ci.org/browse/JENKINS-19360 is an XSL 
 transform,which will convert the an XML file from the VSTest.console schema 
 to the Junit schema. But how to run it from Jenkins?

 I installed Saxonica's xslt tools on the build machine: 
 http://www.saxonica.com/welcome/welcome.xml

 I created a directory in Jenkins_home for my own custom stuff, and in that 
 directory I placed the mstest-to-junit.xsl file, and a batch file:

 @ECHO OFF

 SET WORKINGDIR=%~1

 FOR %%t IN (%WORKINGDIR%\*.trx) DO (
 d:\Program Files\Saxonica\SaxonHE9.5N\bin\Transform.exe -s:%%t 
 -xsl:%JENKINS_HOME%\KorTerraStuff\mstest-junit.xsl -versionmsg:off 
 -o:%WORKINGDIR%\testresults.xml
 )

 DEL %WORKINGDIR%\*.trx


 Part of the problem is that VSTest.console outputs into a time-stamped 
 filename. The batchfile is wildcarded, and will convert any .trx file into 
 testresults.xml.

 The batch command, in Jenkins:

 ECHO Convert VSTest.console output to JUnit format

 CD %WORKSPACE%

 %JENKINS_HOME%\MyStuff\ConvertVsTest2Junit.bat %WORKSPACE%\TestResults








 On Wednesday, November 5, 2014 2:08:15 PM UTC-6, Rob D wrote:

 Jeff, did you get this working. I just ran into the same issue and 
 discovered your thread. I am very new to Jenkins so if you or anyone else 
 can explain how to display the results of the vstestrunner plugin so that a 
 beginner can understand it, I would be extremely grateful.

 Rob

 On Thursday, July 10, 2014 9:07:29 AM UTC-5, Glenn V wrote:

 The xslt does not transform to MsTest format, but to JUnit format. You 
 can import the resulting xml file with the publish junit test result 
 report post build task.

 Kind regards,
 Glenn

 On Monday, June 23, 2014 8:55:27 PM UTC+2, Jeff Dege wrote:

 OK, I have added a Windows Batch Command task, that's using Saxonica's 
 XLST transform to the VsTest .trx file to what is supposed to be an MsTest 
 .trx file that the Jenkins plug-in can handle, using the .xsl file 
 included 
 in Jenkins-19360.

 It's not working at all.

 Where the untransformed file would display the passed and failed tests, 
 but broke when you tried to display the results of a test, the plugin 
 parses the transformed file and reports no tests at all.

 I can't have been the first to deal with this.  Is there someplace else 
 on the net I should be asking for help?

 On Thursday, June 19, 2014 4:19:55 PM UTC-5, Jeff Dege wrote:

 I have a VS2013 project that I'm building with Jenkins. Now I'm trying 
 to get running the unit tests to be a part of the build process.

 I'm running the tests with the VSTest Runner plugin, and that's 
 working fine. But I've not figured out how to publish the results.

 Currently, I'm trying the MSTest plugin, but it's only sorta working.

 I have the VSTest Runner configured to log results to a trx file, and 
 the file shows up in the TestResults directory of the Jenkins workspace, 
 with a complicated, unpredictable name.

 And I have the MSTest plugin configured to look for TestResults\*.trx 
 - which I'm hoping will work for locating the file that the runner 
 generated.

 When I look at a build's Test Result, I a red/blue failure/success bar 
 (8 failures, 66 tests). And I see two grids below. The first is labeled 
 All Failed Tests, and has a row for each failed test. The second is 
 labeled All Tests, and has only one row, with a package of (root).

 When I try to expand any of the failed tests, (clicking on the blue 
 '+'), the row expands to show a pane displaying HTTP ERROR 404.

 So, the questions:


1. Does the MSTest plugin support vstest.console.exe's trx output?
2. If so, why am I only getting partial results? 
3. Is it because I'm not passing the filename correctly? 
4. If I'm not, how should I pass the filename between the two 
plugins?
5. And if the MSTest plugin does not support vstest.console.exe's 
trx output, what do I do?
6. Is there some other plugin I should be using? Some other tool?



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


System credentials for VSO

2014-11-11 Thread Rob D
If you are connecting to Visual Studio Online, have you found a way to use 
anything other than your personal Microsoft Live ID? I have tried the 
Credentials 
Viewer http://nakedalm.com/tfs-service-credential-viewer/ but it crashes 
as others describe in the comments there. I have things working in Jenkins 
so that I can connect and get the code but so far I have to use a personal 
Live ID to do it. Are you using a Live ID like that or have you figured out 
something else?

Thanks
Rob

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Publishing vstest results?

2014-11-05 Thread Rob D
Jeff, did you get this working. I just ran into the same issue and 
discovered your thread. I am very new to Jenkins so if you or anyone else 
can explain how to display the results of the vstestrunner plugin so that a 
beginner can understand it, I would be extremely grateful.

Rob

On Thursday, July 10, 2014 9:07:29 AM UTC-5, Glenn V wrote:

 The xslt does not transform to MsTest format, but to JUnit format. You can 
 import the resulting xml file with the publish junit test result report 
 post build task.

 Kind regards,
 Glenn

 On Monday, June 23, 2014 8:55:27 PM UTC+2, Jeff Dege wrote:

 OK, I have added a Windows Batch Command task, that's using Saxonica's 
 XLST transform to the VsTest .trx file to what is supposed to be an MsTest 
 .trx file that the Jenkins plug-in can handle, using the .xsl file included 
 in Jenkins-19360.

 It's not working at all.

 Where the untransformed file would display the passed and failed tests, 
 but broke when you tried to display the results of a test, the plugin 
 parses the transformed file and reports no tests at all.

 I can't have been the first to deal with this.  Is there someplace else 
 on the net I should be asking for help?

 On Thursday, June 19, 2014 4:19:55 PM UTC-5, Jeff Dege wrote:

 I have a VS2013 project that I'm building with Jenkins. Now I'm trying 
 to get running the unit tests to be a part of the build process.

 I'm running the tests with the VSTest Runner plugin, and that's working 
 fine. But I've not figured out how to publish the results.

 Currently, I'm trying the MSTest plugin, but it's only sorta working.

 I have the VSTest Runner configured to log results to a trx file, and 
 the file shows up in the TestResults directory of the Jenkins workspace, 
 with a complicated, unpredictable name.

 And I have the MSTest plugin configured to look for TestResults\*.trx - 
 which I'm hoping will work for locating the file that the runner generated.

 When I look at a build's Test Result, I a red/blue failure/success bar 
 (8 failures, 66 tests). And I see two grids below. The first is labeled 
 All Failed Tests, and has a row for each failed test. The second is 
 labeled All Tests, and has only one row, with a package of (root).

 When I try to expand any of the failed tests, (clicking on the blue 
 '+'), the row expands to show a pane displaying HTTP ERROR 404.

 So, the questions:


1. Does the MSTest plugin support vstest.console.exe's trx output?
2. If so, why am I only getting partial results? 
3. Is it because I'm not passing the filename correctly? 
4. If I'm not, how should I pass the filename between the two 
plugins?
5. And if the MSTest plugin does not support vstest.console.exe's 
trx output, what do I do?
6. Is there some other plugin I should be using? Some other tool?



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Beginner Question: Jenkins and Visual Studio tests

2014-11-05 Thread Rob D
Christoph,

I am also new to Jenkins and at the point of running tests on a Visual 
Studio project. I'm not sure what you mean by running the tests by hand. I 
am running unit tests and have found the VSTestRunner plugin useful there. 
However it does not display the test results. I am still trying to figure 
out how to do that. 

As jpd4nt says, if you want to run tests using vstestrunner, you will need 
to install Visual Studio.

On Wednesday, November 5, 2014 10:15:09 AM UTC-6, jpd4nt wrote:

 Hi.

 From the look you can only run VSTests in Visual Studio, or rip the msi 
 out of Visual Studio installer

 Otherwise you are going to have to install Visual Studio on the server as 
 that how VSTests work.




-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.