Re: Jenkins Pipeline - fail a stage but continue the build

2018-02-22 Thread Baptiste Mathus 
Andrew was referring to adding code into Blue Ocean itself, not something
doable for end users.

Le 22 févr. 2018 08:55, "Cameron Jeffries"  a écrit :

> Can you please link to the syntax for the Blue Ocean metadata to use?  I'm
> having trouble finding it.
>
> On Tuesday, January 3, 2017 at 11:15:12 AM UTC-8, Andrew Bayer wrote:
>>
>> There's no *easy* way to do this - in Declarative + Blue Ocean, we now
>> have this capability, but it relies on adding some additional metadata to
>> the "failed" stage that Blue Ocean reads. That said, if you don't care
>> about the visualization (i.e., the stage is marked as passed in Blue Ocean
>> or the Stage View, the build continues, but at the end of the build the
>> whole build is marked as failed), catchError will do the trick -
>> https://jenkins.io/doc/pipeline/steps/workflow-basic-steps
>> /#code-catcherror-code-catch-error-and-set-build-result
>>
>> A.
>>
>> On Tue, Jan 3, 2017 at 8:10 AM, 'Stefan Golas' via Jenkins Users <
>> jenkins...@googlegroups.com> wrote:
>>
>>> Hello,
>>> I would like to fail a stage in a pipeline job without aborting the
>>> build (pipeline). Is there a way?
>>>
>>> regards Stefan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/6cfbefd9-99da-40a1-afe2-5005c72a5b5f%
>>> 40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/d162304a-f064-4fb3-8cfd-8728ea283025%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7E4LzyVfC9_y%3DMhORTA0u6xaDX-Em-Yv8FJ7D1jrr_Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Installation - No Plugin

2018-02-22 Thread 江南 
When I run the jenkins.war file I'm getting this error:




On Thursday, 22 February 2018 12:46:00 UTC, 江南 wrote:
>
> Hi,
>
> I have installed Jenkins on my C drive but when I try to install suggested 
> plugins I'm getting this error:
>
>
> 
> Please help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/67a0e4ab-a3e2-4362-a330-225c32c785db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tfs-plugin: error when TFS Project name has a space "Retrieved 0 resources"

2018-02-22 Thread Shai Hirsch 
We use Jenkins ver. 2.89.4 with the tfs plugin 5.126.0
One of our TFS team projects has a space in its name.
We cannot change its name in TFS, unfortunately

When running a build, Jenkins connects to our TFS server successfully.
It also recognizes the specific changeset we are querying for.
However, it retrieves 0 resources and erros out that the Jenkins file is 
not found.

The same exact configuration on a project without a space in its name ran 
successfully.

Is there a way to configure a project with a whitespace in it?
Is there another workaround we can follow?

We tried html encoding the project: $/Space%20Inside
as well as wrapping the name with double quotes: $/"Space Inside"
but with no success.

Thank you,
Shai Hirsch

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/07e6b6d2-d538-4a15-a2a0-f95be0dd74a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Installation - No Plugin

2018-02-22 Thread 江南 
Hi,

I have installed Jenkins on my C drive but when I try to install suggested 
plugins I'm getting this error:


Please help.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/50c34af3-2294-4965-9ef0-f48bc3992529%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

2018-02-22 Thread Carlos Sanchez 
OOMKilled has nothing to do with the host resources, but the process in the
container using more memory than available.
Try increasing the memory limits and read
https://blog.csanchez.org/2017/05/31/running-a-jvm-in-a-container-without-getting-killed/

On Thu, Feb 22, 2018 at 10:19 AM,  wrote:

> Disk space and memory are all at an extremely low utilization for all of
> my hosts. So it's not real resource exhaustion. I'm thinking timeline wise
> it seems that OOMkilled state is possibly a result of kubernetes
> terminating the pod due to disconnection.
>
>
> INFO: Excess workload after pending Spot instances: 1
> Feb 22, 2018 9:05:10 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud
> provision
> INFO: Template: Kubernetes Pod Template
> Feb 22, 2018 9:05:10 AM okhttp3.internal.platform.Platform log
> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot
> class path?
> Feb 22, 2018 9:05:10 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl
> apply
> INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1
> executors. Remaining excess workload: 0
> Feb 22, 2018 9:05:20 AM hudson.slaves.NodeProvisioner$2 run
> INFO: Kubernetes Pod Template provisioning successfully completed. We have
> now 2 computer(s)
> Feb 22, 2018 9:05:20 AM okhttp3.internal.platform.Platform log
> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot
> class path?
> Feb 22, 2018 9:05:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Created Pod: jnlp-t2c36 in namespace jenkins-test
> Feb 22, 2018 9:05:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (0/100): jnlp-t2c36
> Feb 22, 2018 9:05:26 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (1/100): jnlp-t2c36
> Feb 22, 2018 9:05:32 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (2/100): jnlp-t2c36
> Feb 22, 2018 9:05:38 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (3/100): jnlp-t2c36
> Feb 22, 2018 9:05:44 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (4/100): jnlp-t2c36
> Feb 22, 2018 9:05:47 AM hudson.model.Descriptor verifyNewInstance
> WARNING: Father of ContainerEnvVar [getValue()=http://jenkins-
> test-jenkins:8080, getKey()=JENKINS_URL] and its getDescriptor() points
> to two different instances. Probably malplaced @Extension. See
> http://hudson.361315.n4.nabble.com/Help-Hint-needed-
> Post-build-action-doesn-t-stay-activated-td2308833.html
> Feb 22, 2018 9:05:50 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (5/100): jnlp-t2c36
> Feb 22, 2018 9:05:56 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (6/100): jnlp-t2c36
> Feb 22, 2018 9:06:02 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (7/100): jnlp-t2c36
> Feb 22, 2018 9:06:08 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (8/100): jnlp-t2c36
> Feb 22, 2018 9:06:14 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (9/100): jnlp-t2c36
> Feb 22, 2018 9:06:20 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (10/100): jnlp-t2c36
> Feb 22, 2018 9:06:26 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (11/100): jnlp-t2c36
> Feb 22, 2018 9:06:32 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (12/100): jnlp-t2c36
> Feb 22, 2018 9:06:38 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (13/100): jnlp-t2c36
> Feb 22, 2018 9:06:44 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (14/100): jnlp-t2c36
> Feb 22, 2018 9:06:50 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (15/100): jnlp-t2c36
> Feb 22, 2018 9:06:56 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (16/100): jnlp-t2c36
> Feb 22, 2018 9:07:02 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (17/100): jnlp-t2c36
> Feb 22, 2018 9:07:08 AM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher
> launch
> INFO: Waiting for Pod to be scheduled (18/100): jnlp-t2c36
> Feb 22, 2018

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

2018-02-22 Thread brandon 
Disk space and memory are all at an extremely low utilization for all of my 
hosts. So it's not real resource exhaustion. I'm thinking timeline wise it 
seems that OOMkilled state is possibly a result of kubernetes terminating 
the pod due to disconnection.


INFO: Excess workload after pending Spot instances: 1
Feb 22, 2018 9:05:10 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Template: Kubernetes Pod Template
Feb 22, 2018 9:05:10 AM okhttp3.internal.platform.Platform log
INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot 
class path?
Feb 22, 2018 9:05:10 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl 
apply
INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 
executors. Remaining excess workload: 0
Feb 22, 2018 9:05:20 AM hudson.slaves.NodeProvisioner$2 run
INFO: Kubernetes Pod Template provisioning successfully completed. We have 
now 2 computer(s)
Feb 22, 2018 9:05:20 AM okhttp3.internal.platform.Platform log
INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot 
class path?
Feb 22, 2018 9:05:20 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Created Pod: jnlp-t2c36 in namespace jenkins-test
Feb 22, 2018 9:05:20 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (0/100): jnlp-t2c36
Feb 22, 2018 9:05:26 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (1/100): jnlp-t2c36
Feb 22, 2018 9:05:32 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (2/100): jnlp-t2c36
Feb 22, 2018 9:05:38 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (3/100): jnlp-t2c36
Feb 22, 2018 9:05:44 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (4/100): jnlp-t2c36
Feb 22, 2018 9:05:47 AM hudson.model.Descriptor verifyNewInstance
WARNING: Father of ContainerEnvVar 
[getValue()=http://jenkins-test-jenkins:8080, getKey()=JENKINS_URL] and its 
getDescriptor() points to two different instances. Probably malplaced 
@Extension. See 
http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html
Feb 22, 2018 9:05:50 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (5/100): jnlp-t2c36
Feb 22, 2018 9:05:56 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (6/100): jnlp-t2c36
Feb 22, 2018 9:06:02 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (7/100): jnlp-t2c36
Feb 22, 2018 9:06:08 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (8/100): jnlp-t2c36
Feb 22, 2018 9:06:14 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (9/100): jnlp-t2c36
Feb 22, 2018 9:06:20 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (10/100): jnlp-t2c36
Feb 22, 2018 9:06:26 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (11/100): jnlp-t2c36
Feb 22, 2018 9:06:32 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (12/100): jnlp-t2c36
Feb 22, 2018 9:06:38 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (13/100): jnlp-t2c36
Feb 22, 2018 9:06:44 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (14/100): jnlp-t2c36
Feb 22, 2018 9:06:50 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (15/100): jnlp-t2c36
Feb 22, 2018 9:06:56 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (16/100): jnlp-t2c36
Feb 22, 2018 9:07:02 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (17/100): jnlp-t2c36
Feb 22, 2018 9:07:08 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (18/100): jnlp-t2c36
Feb 22, 2018 9:07:14 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (19/100): jnlp-t2c36
Feb 22, 2018 9:07:20 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (20/100): jnlp-t2c36
Feb 22, 2018 9:07:26 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (21/100): jnlp-t2c36
Feb 22, 2018 9:07:32 AM 
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

2018-02-22 Thread brandon 
I'm actually seeing now that the workers are being OOMkilled at some point. 
Which doesn't make any sense because all of my kubernetes workers have 
>50gb free and this pod only requires 256mb.

Name: jnlp-1sh50
Namespace:jenkins-test
Node: kubeworker-rwva1-prod-10/10.0.0.217
Start Time:   Thu, 22 Feb 2018 01:08:20 -0800
Labels:   jenkins=slave
  jenkins/jenkins-test-jenkins-slave=true
Annotations:  
Status:   Failed
IP:   10.233.115.31
Containers:
  jnlp:
Container ID:  
docker://4cf893a70ad3d074b9708f076baef9600b0abfa9d5726d41711ccb39adcc9814
Image: jenkins/jnlp-slave:3.10-1
Image ID:  
docker-pullable://jenkins/jnlp-slave@sha256:db1cb9e803fe2aeb440435cf0da4195b63685664c5976d2fefead839631d070e
Port:  
Args:
  2200e9b3a7435e57a10c48570b0afe4210cbc87a910766503b5eace2d4f32a86
  jnlp-1sh50
State:  Terminated
  Reason:   OOMKilled
  Exit Code:137
  Started:  Thu, 22 Feb 2018 01:08:21 -0800
  Finished: Thu, 22 Feb 2018 01:09:10 -0800
Ready:  False
Restart Count:  0
Limits:
  cpu: 200m
  memory:  256Mi
Requests:
  cpu: 200m
  memory:  256Mi
Environment:
  JENKINS_SECRET:  
2200e9b3a7435e57a10c48570b0afe4210cbc87a910766503b5eace2d4f32a86
  JENKINS_TUNNEL:  jenkins-test-jenkins-agent:5
  JENKINS_NAME:jnlp-1sh50
  JENKINS_URL: http://jenkins-test-jenkins:8080
  HOME:/home/jenkins
Mounts:
  /home/jenkins from workspace-volume (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from 
default-token-dtwdj (ro)
Conditions:
  Type   Status
  InitializedTrue
  Ready  False
  PodScheduled   True
Volumes:
  workspace-volume:
Type:EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
  default-token-dtwdj:
Type:Secret (a volume populated by a Secret)
SecretName:  default-token-dtwdj
Optional:false
QoS Class:   Guaranteed
Node-Selectors:  
Tolerations: 
Events:
  TypeReason Age   From  
 Message
  --     
 ---
  Normal  Scheduled  2mdefault-scheduler  
Successfully assigned jnlp-1sh50 to kubeworker-rwva1-prod-10
  Normal  SuccessfulMountVolume  2mkubelet, kubeworker-rwva1-prod-10  
MountVolume.SetUp succeeded for volume "workspace-volume"
  Normal  SuccessfulMountVolume  2mkubelet, kubeworker-rwva1-prod-10  
MountVolume.SetUp succeeded for volume "default-token-dtwdj"
  Normal  Pulled 2mkubelet, kubeworker-rwva1-prod-10  
Container image "jenkins/jnlp-slave:3.10-1" already present on machine
  Normal  Created2mkubelet, kubeworker-rwva1-prod-10  
Created container
  Normal  Started2mkubelet, kubeworker-rwva1-prod-10  
Started container



On Thursday, February 22, 2018 at 12:04:31 AM UTC-8, Carlos Sanchez wrote:
>
> That log suggests that the slave is not "online" for jenkins. If you go to 
> the jenkins nodes page under /computer/ what do you see? maybe the slave is 
> offline for some reason, lack of space or something
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5507122d-833a-422f-9461-7290ec92fc9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

2018-02-22 Thread Carlos Sanchez 
That log suggests that the slave is not "online" for jenkins. If you go to
the jenkins nodes page under /computer/ what do you see? maybe the slave is
offline for some reason, lack of space or something

On Wed, Feb 21, 2018 at 9:25 PM,  wrote:

> I've downgraded to the 1.2 version of the plugin and gone through the
> debug steps listed here https://github.com/jenkinsci/kubernetes-plugin
>
> No luck.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/b17a41a6-25f2-4aff-906d-b53879d33f0e%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6MJrNTgpkJwXLEMT38F-ULZm%2B9Z5QrXSUB2GppU-EQZqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.