It would be super useful agent and templates could come from workflow
libraries so that they could be shared
man. 2. des. 2019, 17:16 skrev Carlos Sanchez :
> No, It has to live in the same repo
>
> On Mon, Dec 2, 2019, 16:39 YD wrote:
>
>> Hi all
>>
>> in kubernetes plugin i want to use yaml
Yes, but
yamlFile './k8s/someyaml.yaml'
On Tue, Dec 3, 2019 at 11:41 AM YD wrote:
> thanks Carlos , it did work fine when i copy the file (someyaml.yaml) to
> the root of the repo
> can i put the file in some folder (same repo) and use something like below
> pipeline {
> agent {
>
thanks Carlos , it did work fine when i copy the file (someyaml.yaml) to
the root of the repo
can i put the file in some folder (same repo) and use something like below
pipeline {
agent {
kubernetes
{
yamlFile '/k8s/someyaml.yaml'
}
}
On Monday, December 2, 2019 at
No, It has to live in the same repo
On Mon, Dec 2, 2019, 16:39 YD wrote:
> Hi all
>
> in kubernetes plugin i want to use yaml that i managed in my git server
> (public repo)
>
> does something like that should work ?
>
> pipeline {
> agent {
> kubernetes
> {
> yamlFile
Hi all
in kubernetes plugin i want to use yaml that i managed in my git server
(public repo)
does something like that should work ?
pipeline {
agent {
kubernetes
{
yamlFile '/someyaml.yaml'
}
}
if not what are my options for using yamlFile method
thanks
Yair
--
arted/kubernetes/
>
> I try to configure the service account for k8s plugin and run a simple
> test but not sure which part I have done wrong the 1st run (when first
> download the image to the cluster) the jnlp pod will use jenkins user
>
> + id
> uid=1000(jenkins) gid=1000(jenkin
Think I found the issue, I had a much older version of the kube plugin
installed and since then, client caching was introduced, I am applying the
fix found here: https://github.com/jenkinsci/kubernetes-plugin/pull/429
On Thursday, July 18, 2019 at 9:41:24 AM UTC-4, Andres Galindo wrote:
>
> Hi
Hi all,
Currently we're using EKS (v1.13) with Jenkins (v2.176.1) and the
Kubernetes plugin (v1.17.2) and it seems like every 15 minutes (coincides
with how long the generated token is supposed last) there is an issue with
authorizing against the cluster.
Here is the error message:
to configure the service account for k8s plugin and run a simple test
but not sure which part I have done wrong the 1st run (when first download
the image to the cluster) the jnlp pod will use jenkins user
+ id
uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins)
+ ls -lh /home/jenkins
total 8
drwxr-sr
I don’t have any more ideas since I haven’t played with containers much :(
Feels like the NPM command is not being ran on the container. Does it work
if you remove the NPM stuff?
On Mon, Sep 17, 2018 at 03:57 Blau Gil wrote:
> Hi Jan,
>
> Thank you for assisting.
> Yes the container runs on
Hi Jan,
Thank you for assisting.
Yes the container runs on its own, only when I try to run the container
image with Jenkins it fails.
Any idea what I can do to resolve this?
Thanks,
--Gil.
On Thu, 23 Aug 2018 at 04:04, Jan Monterrubio
wrote:
> Does the container work on its own?
>
> Looks
Hi Jan,
Thank you for assisting.
Yes the container runs on its own, only when I try to run the container
image with Jenkins it fails.
Any idea what I can do to resolve this?
Thanks,
--Gil.
On 23 August 2018 at 04:03, Jan Monterrubio
wrote:
> Does the container work on its own?
>
> Looks like
Does the container work on its own?
Looks like you have this part in the container:
"RUN apk add --no-cache --virtual .gyp \
python \
make \
g++ \
git \
&& npm install --quit && npm cache clean --force \
&& apk del .gyp"
Which runs npm install
On Wed, Aug 22, 2018 at 6:08 AM gil wrote:
>
Anyone?
On Sunday, 12 August 2018 11:28:54 UTC+3, gil wrote:
>
> Trying to tun a podTemaplate with the following containerTemplate, we get
> the following error:
>
> npm ERR! path /home/jenkins/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent
Trying to tun a podTemaplate with the following containerTemplate, we get
the following error:
npm ERR! path /home/jenkins/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open
'/home/jenkins/package.json'
npm ERR! enoent
15 matches
Mail list logo
