On 2016-11-22 17:14, R. Tyler Croy wrote:
That said, this[0] Jenkinsfile was clearly written for some Jenkins which is
not ci.jenkins.io or anything that the Jenkins project runs.
* The labels it binds to are not labels we support[1]
* The Xvnc plugin isn't/won't be installed
* It requires an authenticated clone of [email protected]:jenkinsci/a-t-h which
won't work in ci.jenkins.io
* The CopyArtifact plugin is being used for unclear reasons, which also won't
work
* There are no Sauce OnDemand credentials in ci.jenkins.io, so the current
invocations of Selenium won't work
Thanks. How do you propose to address these? It should be possible to
run ATH in container and run docker fixtures in sibling containers. Is
there any image/Dockerfile we can reuse or it needs to be written from
scratch?
Thanks
--
oliver
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/6616f6a6-312e-0df3-92f2-431cad408f24%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
