Re: Jenkins and Jacoco and multiple jobs...
Thanks for the reply... Seems to be that the directory I had for "Use custom workspace" didn't have the project name in there, but rather just "D:\workspaces". This worked fine for my source control system, though the mapping was doubled. So now, I use "D:\workspaces\job01" and Jacoco looks only there. My source control system (Perforce), had a the project name twice and now it's only once (\\job01\job01\src... -> \\job01\src...) so that makes more sense too. Thanks again. Mark Wilhelm On Wednesday, July 30, 2014 6:11:16 PM UTC-5, Mark Waite wrote: > > That is quite surprising. I have many different Jacoco based jobs running > on master and on slaves and on Windows and Linux and have never seen it > "wandering" outside its own directory path to find coverage data. > > Could there be a symbolic link (or the Windows equivalent of it) inside > the workspace directory which is causing the matcher to look "one directory > above" the workspace? > > Could there be a directory definition somewhere in the system > configuration (like the path to the C:\workspaces directory) which would > benefit from a trailing slash to stop the matcher from somehow looking > outside the workspace? > > Mark Waite > > > On Wed, Jul 30, 2014 at 4:40 PM, Mark Wilhelm > wrote: > >> Hello, >> >> I'm running a Jenkins server with multiple jobs. Part of one of the jobs >> is to run Jacoco for code coverage metrics. I am using the latest Jacoco >> plugin. What is happening is that the Jacoco run is going into every job >> and searching for Jacoco artifacts (classes, exec,etc...) and with each new >> job, the build is taking longer and longer. >> >> How do I limit Jacoco from traversing all the paths? Is it with >> exclusions? If so, how do I enter the paths to exclude? >> >> Sorry if this is in the wrong group, but thought this could be Jenkins >> issue (default workspaces?) >> >> Thank you. >> >> For example: >> >> C:\Program Files (x86)\Jenkins\jobs\job01 >> \job02 >> \job03 <- has >> Jacoco plugin task >> \job04 >> \jobn... >> >> C:\workspaces\job01\src >> \job02\src >> \job03\src >> \job04\src >> \jobn... >> >> *Jacoco coverage example:* >> [JaCoCo plugin] Collecting JaCoCo coverage data... >> [JaCoCo plugin] **/**.exec;**/classes;**/src/main/java; locations are >> configured >> [JaCoCo plugin] Number of found exec files: 4+n >> [JaCoCo plugin] Saving matched execfiles: >> C:\workspaces\job01\src\jacoco-unit.exec >> C:\workspaces\job02\src\jacoco-unit.exec >> C:\workspaces\job03\src\jacoco-unit.exec >> C:\workspaces\job04\src\jacoco-unit.exec >> C:\workspaces\jobn\src\jacoco-unit.exec >> [JaCoCo plugin] Saving matched class directories: >> C:\workspaces\job01\src\classes >> C:\workspaces\job02\src\classes >> C:\workspaces\job03\src\classes >> C:\workspaces\job04\src\classes >> C:\workspaces\jobn\src\classes >> [JaCoCo plugin] Saving matched source directories: >> C:\workspaces\job01\src\java >> C:\workspaces\job02\src\java >> C:\workspaces\job03\src\java >> C:\workspaces\job04\src\java >> C:\workspaces\jobn\src\java >> [JaCoCo plugin] Loading inclusions files.. >> [JaCoCo plugin] inclusions: [] >> [JaCoCo plugin] exclusions: [**/*Test*.class] >> [JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, >> maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, >> maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, >> maxComplexity=0] >> [JaCoCo plugin] Publishing the results.. >> [JaCoCo plugin] Loading packages.. >> [JaCoCo plugin] Done. >> Sending e-mails to: m...@example.com >> Finished: SUCCESS >> >> >> -- >> 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-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Thanks! > Mark Waite > -- 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.
Jenkins and Jacoco and multiple jobs...
Hello, I'm running a Jenkins server with multiple jobs. Part of one of the jobs is to run Jacoco for code coverage metrics. I am using the latest Jacoco plugin. What is happening is that the Jacoco run is going into every job and searching for Jacoco artifacts (classes, exec,etc...) and with each new job, the build is taking longer and longer. How do I limit Jacoco from traversing all the paths? Is it with exclusions? If so, how do I enter the paths to exclude? Sorry if this is in the wrong group, but thought this could be Jenkins issue (default workspaces?) Thank you. For example: C:\Program Files (x86)\Jenkins\jobs\job01 \job02 \job03 <- has Jacoco plugin task \job04 \jobn... C:\workspaces\job01\src \job02\src \job03\src \job04\src \jobn... *Jacoco coverage example:* [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] **/**.exec;**/classes;**/src/main/java; locations are configured [JaCoCo plugin] Number of found exec files: 4+n [JaCoCo plugin] Saving matched execfiles: C:\workspaces\job01\src\jacoco-unit.exec C:\workspaces\job02\src\jacoco-unit.exec C:\workspaces\job03\src\jacoco-unit.exec C:\workspaces\job04\src\jacoco-unit.exec C:\workspaces\jobn\src\jacoco-unit.exec [JaCoCo plugin] Saving matched class directories: C:\workspaces\job01\src\classes C:\workspaces\job02\src\classes C:\workspaces\job03\src\classes C:\workspaces\job04\src\classes C:\workspaces\jobn\src\classes [JaCoCo plugin] Saving matched source directories: C:\workspaces\job01\src\java C:\workspaces\job02\src\java C:\workspaces\job03\src\java C:\workspaces\job04\src\java C:\workspaces\jobn\src\java [JaCoCo plugin] Loading inclusions files.. [JaCoCo plugin] inclusions: [] [JaCoCo plugin] exclusions: [**/*Test*.class] [JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0] [JaCoCo plugin] Publishing the results.. [JaCoCo plugin] Loading packages.. [JaCoCo plugin] Done. Sending e-mails to: m...@example.com Finished: SUCCESS -- 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: Perforce: merge files from a continuous directory to an integration directory...
Thanks, I'll give it a go. For #4, are you putting these into a "Execute Windows batch command" build step"? On Wednesday, May 7, 2014 2:18:57 PM UTC-5, Stuart Rowe wrote: > > Try this approach (there may be typos / gotchas - it's completely untested) > > 1) Enable Perforce SCM on your integration project in Jenkins > - set up the client spec 'myclientspec' to use the mapping: >//project/dev/... //myclientspec/dev/... >//project/int/... //myclientspec/int/... > > 2) Enable 'Use View Mask', but just for polling (I haven't tried this > feature yet so I'm just guessing it will work for you) > - set the view mask to be //project/dev/... > > 3) Under Build Triggers, check Poll SCM > - any submitted changes under the //project/int/... branch should now > trigger your integration project in Jenkins > - since we're NOT using the view mask for syncing, both branches will > be synced to head when the build starts (this is good for continuous > integration) > - perforce plugin stores the changelist it sync'd to in the > environment variable 'P4_CHANGELIST' (this is the latest changelist in the > Dev branch that triggered the build!) > > 4) Now we want to integrate from the Dev banch to the integration branch: > >p4 integrate -d -i -t //project/dev/...@%P4_CHANGELIST% > //project/int/... >p4 resolve -a > >// test the build > > p4 submit -f revertunchanged -d "Integration Build" > > On Wednesday, 7 May 2014 11:09:17 UTC-7, Mark Wilhelm wrote: >> >> ok, some more "work"... >> >> I put these commands in the "EWbc" window and it works: >> "C:\Program Files\Perforce\"p4 -u build-user -P xxx change -o >> "C:\Program Files\Perforce\"p4 -u build-user -P xxx integrate -d -i -t >> //Project/dev... //Workspace/Project/int... >> "C:\Program Files\Perforce\"p4 -u build-user -P xxx resolve -a >> "C:\Program Files\Perforce\"p4 -u build-user -P xxx submit -f >> revertunchanged -d "Integration Build" >> >> BUT, if I run it again, it fails: >> "No files to submit from the default changelist. >> >> D:\workspaces>exit 1" >> >> While this makes sense, is there: 1) a way to suppress the submit from >> returning a non-zero (i.e. an error) or 2) A better way altogether? >> >> >> Thanks... >> >> On Wednesday, May 7, 2014 9:01:04 AM UTC-5, Mark Wilhelm wrote: >>> >>> Just a basic setup: >>> depot/project/dev/src >>> depot/project/int/src >>> >>> I have a continuous build running on the "dev" structure every few >>> minutes. I have a nightly build that runs on the "int" structure. When you >>> ask "why don't you want to merge?", are you asking from a manual >>> perspective? >>> >>> I would like my "dev" build to run. When the "int" build runs, I would >>> like it to check if there were any changes on the "dev" branch/directory >>> and move them over. Then build what's there. >>> >>> I have used some of the commands in a "Execute Windows batch command" >>> build step, but thought that the "Source Code Management" plugin would be >>> where I would want to do that. >>> >>> In the window I used the following commands: >>> "C:\Program Files\Perforce\"p4 -u build-user -P xxx change -o >>> "C:\Program Files\Perforce\"p4 -u build-user -P xxx integrate -i -d -t >>> //project/dev... //JenkinsJob/workspace/int... >>> "C:\Program Files\Perforce\"p4 -u build-user -P xxx submit -f >>> revertunchanged -d "Integration Build" >>> >>> On the integrate I get: - all revision(s) already integrated. >>> On the integrate I get: No files to submit from the default changelist. >>> and the "Execute Windows batch command" fails the build "Build step >>> 'Execute Windows batch command' marked build as failure. Even though there >>> was a change list listed by Jenkins. >>> >>> I'm all for changing my direction if there is a more standard/better way >>> of implementing this. >>> >>> Thoughts? >>> >>> >>> >>> On Wednesday, May 7, 2014 2:58:51 AM UTC-5, Stuart Rowe wrote: >>>> >>>> Can you describe your branch structure a little more? >>>> >>>> Ho
Re: Perforce: merge files from a continuous directory to an integration directory...
ok, some more "work"... I put these commands in the "EWbc" window and it works: "C:\Program Files\Perforce\"p4 -u build-user -P xxx change -o "C:\Program Files\Perforce\"p4 -u build-user -P xxx integrate -d -i -t //Project/dev... //Workspace/Project/int... "C:\Program Files\Perforce\"p4 -u build-user -P xxx resolve -a "C:\Program Files\Perforce\"p4 -u build-user -P xxx submit -f revertunchanged -d "Integration Build" BUT, if I run it again, it fails: "No files to submit from the default changelist. D:\workspaces>exit 1" While this makes sense, is there: 1) a way to suppress the submit from returning a non-zero (i.e. an error) or 2) A better way altogether? Thanks... On Wednesday, May 7, 2014 9:01:04 AM UTC-5, Mark Wilhelm wrote: > > Just a basic setup: > depot/project/dev/src > depot/project/int/src > > I have a continuous build running on the "dev" structure every few > minutes. I have a nightly build that runs on the "int" structure. When you > ask "why don't you want to merge?", are you asking from a manual > perspective? > > I would like my "dev" build to run. When the "int" build runs, I would > like it to check if there were any changes on the "dev" branch/directory > and move them over. Then build what's there. > > I have used some of the commands in a "Execute Windows batch command" > build step, but thought that the "Source Code Management" plugin would be > where I would want to do that. > > In the window I used the following commands: > "C:\Program Files\Perforce\"p4 -u build-user -P xxx change -o > "C:\Program Files\Perforce\"p4 -u build-user -P xxx integrate -i -d -t > //project/dev... //JenkinsJob/workspace/int... > "C:\Program Files\Perforce\"p4 -u build-user -P xxx submit -f > revertunchanged -d "Integration Build" > > On the integrate I get: - all revision(s) already integrated. > On the integrate I get: No files to submit from the default changelist. > and the "Execute Windows batch command" fails the build "Build step > 'Execute Windows batch command' marked build as failure. Even though there > was a change list listed by Jenkins. > > I'm all for changing my direction if there is a more standard/better way > of implementing this. > > Thoughts? > > > > On Wednesday, May 7, 2014 2:58:51 AM UTC-5, Stuart Rowe wrote: >> >> Can you describe your branch structure a little more? >> >> How are your integration builds triggered? If you're trying to move >> changes from your development branch to another branch why don't you want >> to merge? >> >> Conceptually I would approach this as: >> >> 1) start an integration of your Dev branch up to some changelist to the >> target branch >> >> (look up "p4 integrate") >> >> >> 2) now you have a pending integration changelist with the changes from >> your Dev branch applied to your target branch. (assuming there were no >> conflicts that couldn't be resolved). >> >> Run whatever builds/tests you have set up to verify the changes >> >> 3) a) if the builds and tests were successful, submit the changelist >> >> (look up "p4 submit") >> >> b) if anything failed, revert the changelist and make the appropriate >> fixes in your Dev branch >> >> -- 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: Perforce: merge files from a continuous directory to an integration directory...
Just a basic setup: depot/project/dev/src depot/project/int/src I have a continuous build running on the "dev" structure every few minutes. I have a nightly build that runs on the "int" structure. When you ask "why don't you want to merge?", are you asking from a manual perspective? I would like my "dev" build to run. When the "int" build runs, I would like it to check if there were any changes on the "dev" branch/directory and move them over. Then build what's there. I have used some of the commands in a "Execute Windows batch command" build step, but thought that the "Source Code Management" plugin would be where I would want to do that. In the window I used the following commands: "C:\Program Files\Perforce\"p4 -u build-user -P xxx change -o "C:\Program Files\Perforce\"p4 -u build-user -P xxx integrate -i -d -t //project/dev... //JenkinsJob/workspace/int... "C:\Program Files\Perforce\"p4 -u build-user -P xxx submit -f revertunchanged -d "Integration Build" On the integrate I get: - all revision(s) already integrated. On the integrate I get: No files to submit from the default changelist. and the "Execute Windows batch command" fails the build "Build step 'Execute Windows batch command' marked build as failure. Even though there was a change list listed by Jenkins. I'm all for changing my direction if there is a more standard/better way of implementing this. Thoughts? On Wednesday, May 7, 2014 2:58:51 AM UTC-5, Stuart Rowe wrote: > > Can you describe your branch structure a little more? > > How are your integration builds triggered? If you're trying to move > changes from your development branch to another branch why don't you want > to merge? > > Conceptually I would approach this as: > > 1) start an integration of your Dev branch up to some changelist to the > target branch > > (look up "p4 integrate") > > > 2) now you have a pending integration changelist with the changes from > your Dev branch applied to your target branch. (assuming there were no > conflicts that couldn't be resolved). > > Run whatever builds/tests you have set up to verify the changes > > 3) a) if the builds and tests were successful, submit the changelist > > (look up "p4 submit") > > b) if anything failed, revert the changelist and make the appropriate > fixes in your Dev branch > > -- 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.
Perforce: merge files from a continuous directory to an integration directory...
I have continuous and integration build jobs. I would like to run my integration build so that it runs Perforce to automatically move files (not merge) from the dev branch/directory into the int branch/directory and then run the integration build. How or what are the commands for Perforce/Jenkins to do that. Thanks -- 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: Perforce Client View Type - View Map with multiple lines...
Well it appears to be working now. I "hand" modified the config.xml for the job, and made sure they were on different lines and spacing wasn't an issue. Now the multi view mapping is working as described. Thank you for the feedback rginga. On Wednesday, April 16, 2014 9:31:46 AM UTC-5, Mark Wilhelm wrote: > > That example was mostly to depict leveling, the named example shows the > different "actual" directories - so no conflict. I'm wondering if there is > a line ending issue? Jenkins is just not working when the second/third > lines are added. When you look at the config.xml under the scm element > () what do you see? > > thanks again for your help. > > On Wednesday, April 16, 2014 8:59:11 AM UTC-5, rginga wrote: >> >> Well you certainly can map multiple lines. We do it all the time. >> Admittedly most are one line and almost all simply do not use the second >> mapping. >> >> >> >> Is your example accurate for what you want to do? Isn’t your second line >> negate your first line? using the – is correct to eliminate folder >> structures. >> >> >> >> //DepotName/dir_level1/dir_level2... >> //WorkspaceName/Workspace_dir/dir_level1... >> >> -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... >> >> //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... >> >> >> >> >> >> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On >> Behalf Of *Mark Wilhelm >> *Sent:* Tuesday, April 15, 2014 6:29 PM >> *To:* jenkins...@googlegroups.com >> *Subject:* Re: Perforce Client View Type - View Map with multiple >> lines... >> >> >> >> Thanks for the reply. I don't think that's it though. I have a number >> of builds, and they don't have that ending slash. It won't run with my >> extra lines in there. I took out the subsequent two lines, and it runs. >> But that's not what I need. >> >> >> >> When I've been looking at examples, most (all but one) only have one line >> in the view map. But I have to believe that multiples are allowed - it >> would seem to be limiting without that. Having said that, how do I do it? >> How do I also negate inclusion? >> >> >> >> >> >> On Tuesday, April 15, 2014 1:39:57 PM UTC-5, rginga wrote: >> >> Try putting the last slash on: >> >> >> >> //DepotName/dir_level1/dir_level2/... >> //WorkspaceName/Workspace_dir/dir_level1/... >> >> >> >> >> >> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On >> Behalf Of *Mark Wilhelm >> *Sent:* Tuesday, April 15, 2014 1:30 PM >> *To:* jenkins...@googlegroups.com >> *Subject:* Perforce Client View Type - View Map with multiple lines... >> >> >> >> Hi, >> >> >> >> I'm trying to select different levels of directories out of a Perforce >> Depot with the Jenkins Plugin for Perforce.It seems that only one statement >> is allowed (or works) unless I'm missing something. >> >> >> >> For example... >> >> >> >> essence: >> >> //DepotName/dir_level1/dir_level2... >> //WorkspaceName/Workspace_dir/dir_level1... >> >> -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... >> >> //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... >> >> >> >> example: >> >> //Foo/Star/dev... //Foo_bld/Foo_bld/Star... >> >> -//Foo/dev/bar... //Foo_bld/Foo_bld... >> >> //Foo/dev... //Foo_bld/Foo_bld... >> >> >> >> Directory: Use custom workspace = D:\workspaces >> >> Workspace (client) = Foo_bld >> >> >> >> The directories don't seem to be created (only one, and it seems only the >> first one). >> >> >> >> What am I doing wrong? >> >> >> >> >> >> -- >> 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-use...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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-use...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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: Perforce Client View Type - View Map with multiple lines...
That example was mostly to depict leveling, the named example shows the different "actual" directories - so no conflict. I'm wondering if there is a line ending issue? Jenkins is just not working when the second/third lines are added. When you look at the config.xml under the scm element () what do you see? thanks again for your help. On Wednesday, April 16, 2014 8:59:11 AM UTC-5, rginga wrote: > > Well you certainly can map multiple lines. We do it all the time. > Admittedly most are one line and almost all simply do not use the second > mapping. > > > > Is your example accurate for what you want to do? Isn’t your second line > negate your first line? using the – is correct to eliminate folder > structures. > > > > //DepotName/dir_level1/dir_level2... > //WorkspaceName/Workspace_dir/dir_level1... > > -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... > > //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... > > > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Mark Wilhelm > *Sent:* Tuesday, April 15, 2014 6:29 PM > *To:* jenkins...@googlegroups.com > *Subject:* Re: Perforce Client View Type - View Map with multiple lines... > > > > Thanks for the reply. I don't think that's it though. I have a number of > builds, and they don't have that ending slash. It won't run with my extra > lines in there. I took out the subsequent two lines, and it runs. But > that's not what I need. > > > > When I've been looking at examples, most (all but one) only have one line > in the view map. But I have to believe that multiples are allowed - it > would seem to be limiting without that. Having said that, how do I do it? > How do I also negate inclusion? > > > > > > On Tuesday, April 15, 2014 1:39:57 PM UTC-5, rginga wrote: > > Try putting the last slash on: > > > > //DepotName/dir_level1/dir_level2/... > //WorkspaceName/Workspace_dir/dir_level1/... > > > > > > *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On > Behalf Of *Mark Wilhelm > *Sent:* Tuesday, April 15, 2014 1:30 PM > *To:* jenkins...@googlegroups.com > *Subject:* Perforce Client View Type - View Map with multiple lines... > > > > Hi, > > > > I'm trying to select different levels of directories out of a Perforce > Depot with the Jenkins Plugin for Perforce.It seems that only one statement > is allowed (or works) unless I'm missing something. > > > > For example... > > > > essence: > > //DepotName/dir_level1/dir_level2... > //WorkspaceName/Workspace_dir/dir_level1... > > -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... > > //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... > > > > example: > > //Foo/Star/dev... //Foo_bld/Foo_bld/Star... > > -//Foo/dev/bar... //Foo_bld/Foo_bld... > > //Foo/dev... //Foo_bld/Foo_bld... > > > > Directory: Use custom workspace = D:\workspaces > > Workspace (client) = Foo_bld > > > > The directories don't seem to be created (only one, and it seems only the > first one). > > > > What am I doing wrong? > > > > > > -- > 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-use...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > 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-use...@googlegroups.com . > For more options, visit https://groups.google.com/d/optout. > -- 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: Perforce Client View Type - View Map with multiple lines...
Thanks for the reply. I don't think that's it though. I have a number of builds, and they don't have that ending slash. It won't run with my extra lines in there. I took out the subsequent two lines, and it runs. But that's not what I need. When I've been looking at examples, most (all but one) only have one line in the view map. But I have to believe that multiples are allowed - it would seem to be limiting without that. Having said that, how do I do it? How do I also negate inclusion? On Tuesday, April 15, 2014 1:39:57 PM UTC-5, rginga wrote: > > Try putting the last slash on: > > > > //DepotName/dir_level1/dir_level2/... > //WorkspaceName/Workspace_dir/dir_level1/... > > > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Mark Wilhelm > *Sent:* Tuesday, April 15, 2014 1:30 PM > *To:* jenkins...@googlegroups.com > *Subject:* Perforce Client View Type - View Map with multiple lines... > > > > Hi, > > > > I'm trying to select different levels of directories out of a Perforce > Depot with the Jenkins Plugin for Perforce.It seems that only one statement > is allowed (or works) unless I'm missing something. > > > > For example... > > > > essence: > > //DepotName/dir_level1/dir_level2... > //WorkspaceName/Workspace_dir/dir_level1... > > -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... > > //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... > > > > example: > > //Foo/Star/dev... //Foo_bld/Foo_bld/Star... > > -//Foo/dev/bar... //Foo_bld/Foo_bld... > > //Foo/dev... //Foo_bld/Foo_bld... > > > > Directory: Use custom workspace = D:\workspaces > > Workspace (client) = Foo_bld > > > > The directories don't seem to be created (only one, and it seems only the > first one). > > > > What am I doing wrong? > > > > > > -- > 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-use...@googlegroups.com . > For more options, visit https://groups.google.com/d/optout. > -- 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.
Perforce Client View Type - View Map with multiple lines...
Hi, I'm trying to select different levels of directories out of a Perforce Depot with the Jenkins Plugin for Perforce.It seems that only one statement is allowed (or works) unless I'm missing something. For example... essence: //DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir/dir_level1... -//DepotName/dir_level1/dir_level2... //WorkspaceName/Workspace_dir... //DepotName/dir_level1/... //WorkspaceName/Workspace_dir... example: //Foo/Star/dev... //Foo_bld/Foo_bld/Star... -//Foo/dev/bar... //Foo_bld/Foo_bld... //Foo/dev... //Foo_bld/Foo_bld... Directory: Use custom workspace = D:\workspaces Workspace (client) = Foo_bld The directories don't seem to be created (only one, and it seems only the first one). What am I doing wrong? -- 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.
