Re: Does docker-slaves-plugin with pipeline assume Linux?

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description? On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote: > > This plugin has never been

Re: Cannot find the binary path of the firefox

org.openqa.selenium.WebDriverException: Cannot find firefox binary in PATH. Make sure firefox is installed. OS appears to be: LINUX This the one i am getting On Friday, August 11, 2017 at 2:11:47 AM UTC-7, Arthi Pargunan wrote: > > Hi > > I am new to jenkins.. I configured my project

Re: Does docker-slaves-plugin with pipeline assume Linux?

This plugin has never been tested for Windows containers, so I can't tell if they can work without changes. Le 11 août 2017 9:04 AM, "Geoff Bache" a écrit : > > I removed the extra slash in global configuration, but it still fails and > there are still Linux-style paths

Cannot find the binary path of the firefox

Hi I am new to jenkins.. I configured my project via Github and when giving Build now i am getting Cannot find the binary path of the firefox.. can we run the simply initiated firefox driver test in jenkins? or do i need to go with headless compulsorily .. help me on this please

Re: Does docker-slaves-plugin with pipeline assume Linux?

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below. I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error. /Geoff Start Docker container to

Re: How to use podTemplate in a declarative pipeline with the kubernetes-plugin.

I'm not familiar with declarative pipeline, but looking at what Andrew did in KubernetesDeclarativeAgent.java I assume you need to add the pod

Re: Image name and version of containerTemplate by variable created during execution of pipeline?

Have you tried? On Fri, Aug 11, 2017, 12:14 WANG, YAN-HONG wrote: > Hello all, > > I saw the tutorial with jenkins-kubernetes-plugin. > https://github.com/jenkinsci/kubernetes-plugin > > The examples of containerTemplate are all created in the *beginning *of > groovy

Image name and version of containerTemplate by variable created during execution of pipeline?

Hello all, I saw the tutorial with jenkins-kubernetes-plugin. https://github.com/jenkinsci/kubernetes-plugin The examples of containerTemplate are all created in the *beginning *of groovy file. And the *image name with version number *are *fixed*, too. Example like this below.

Re: Cannot find the binary path of the firefox

In your case, it looks like the firefox binary is not installed in that particular agent. Therefore you need to prepare the context/configuration where that particular project/job/pipeline runs. The same setup as you do in your local environment. -- You received this message because you are

Re: Image name and version of containerTemplate by variable created during execution of pipeline?

Hello Carlos, I tried it already with all *plain hard code*. And insert in the execution of pipeline. Something like this below: podTemplate( label: "pod", containers: [ containerTemplate( name: "*worker*", image: "myregistry:5000/jenkins-worker:latest", envVars:[

How to build several tagged versions

Hi, I'd like to test our program against different versions of dependent libraries, so I want to set up something like a matrix build (version, cpu, debug/release). Can I use a matrix parameter in selecting the version to build? Can I somehow communicate the list of tags from one common place,

Re: Does docker-slaves-plugin with pipeline assume Linux?

That is very sad.. I have slaves for windows and linux, and I was begining a migration of my machine slaves to containers =( Is there a JIRA feature created for that cause? Em 11/08/2017 04:52:49, Geoff Bache escreveu: > OK, I think we can conclude from my evidence that it doesn't yet work on

Pipeline - how to have a global config that's accessible from every step?

I'm putting together a jenkins global library and am struggling with creating a true global configuration. My Jenkinsfiles are pretty flat, and mostly just load the global library, set some build specific configuration values, and then calls a step that contains most of the build logic (calls

Re: The format of key of containerEnvVar within Jenkins Kubernetes Plugin

Hello Carlos, Thanks for hint. But, something interesting is if I set this *environment variable *into Dockerfile. That's worked. Looks like: ENV *data.source.url* SomeWhere_A I could see *data.source.url* existed when this Docker container run. That environment variable even could be saw