Hi Wamboo,
We use the embedded Jenkins Code Source Management .
It means we add the repository ("Gestion de code source" in french with the screenshot) by this way :
"We test adding a GIT Code source Management and see that Jenkins use a G Drive for that."
Sorry, but I don't understand this problem with the "G" drive. Where does Jenkins use this drive?
To retrieve data from the source code?
Yes, I think so Wamboo .
When we add our GIT repository as describe upper and run the test,
we can observe that the pluggin Testcomplete for Jenkins download the
code source on G created "itself" , I understand that it is done by TestComplete pluggin.
code source is placed on too separate drives. G an D drive like this : AQ stand for QA in french 🙂
I wondering who managed this ?
because my tests have parameters design for D : drive , and not for G: drive
Maybe I can use a config file ?
I don't know how for the moments...
Nicolas
