These are chat archives for mojotech/pioneer

10th
May 2015
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:16
@samccone I started using PioneerJS with Sauce Labs, however, I had to do a small change in the selenium-webdriver's builder.js to support it.
Apparently Sauce Labs doesn’t support the http://<username>:<accessKey>@<url> format… I made it possible to connect by adding the access data to the capabilities to do it.
I am now searching the place where you actually change the selenium-webdriver’s builder.js
Tom Hicks
@tomhicks
May 10 2015 14:24
This message was deleted
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:24
yeah?
Tom Hicks
@tomhicks
May 10 2015 14:24
Oops! Look at pioneer docs about globals
There is a bit there for providing your own function to build your driver
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:25
yup ...
gotcha ;) :) just create the ‘saucelabs’ driver with my configuration
good good :) thanks m8 … never thought about it :)
Tom Hicks
@tomhicks
May 10 2015 14:26
Use that to provide your own builder 'usingServer' and 'withCapabilities' and you're done
We have been using pioneer with sauce labs for some time now
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:26
Ideally would be great to have that straight away from pioneer
Tom Hicks
@tomhicks
May 10 2015 14:27
What, a sauce labs driver builder?
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:27
Yeah, a driver configurable via process.env vars :)
With my change I just need to use the existing Selenium Remote, with 2 more env vars
Tom Hicks
@tomhicks
May 10 2015 14:28
Yeah just use process.env.SAUCE_ACCESS_KEY or whatever. Nothing more to it than that really
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:28
yeah :)
Tom Hicks
@tomhicks
May 10 2015 14:29
Although there is the business of setting up the test name, build number, etc and also sending the pass/fail result when the test completes
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:30
true
but the build number is normally provided by the CI, as well as the ‘tunnel-identifier'
just needs to be added to the capabilities
is not really correct. The URL format as I said, is not supported
Tom Hicks
@tomhicks
May 10 2015 14:32
Yeh but we could make it easier to plug pioneer into a 3rd party by providing things like the job name to the builder callback
Ricardo Machado
@mAiNiNfEcTiOn
May 10 2015 14:32
yup, true.
Currently we have a machine running that continuously as the repo’s master changes. But we will move it to the CI agents, of course
Let me rephrase that… The URL is supported, just ignores the auth via url… you have to use the capabilities anyway :)
Tom Hicks
@tomhicks
May 10 2015 14:35
Right.
Sam Saccone
@samccone
May 10 2015 18:34
hey guys :wave: