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

[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

[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

[brandon]

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.

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

[brandon]

-- 
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/d5e1e22c-1119-4198-aaa4-21a683dec3b0%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

[brandon]

<http://cloud.rabb.it/2h0y1T0z1A2M/Image%202018-02-19%20at%2011.08.48%20PM.png>


On Monday, February 19, 2018 at 9:02:22 PM UTC-8, Brandon wrote:
>
> Hello, I am trying to use the community helm chart for Jenkins and the 
> Kubernetes plugin 1.2 so that agents can be dynamically provisioned 
> according to build needs.
>
> Ultimately, builds are failing because the  agents are not able to connect 
> to the master. However, I am seeing that in both the agents and master log 
> that they believe they have established a connection. What is going on? How 
> can I debug this further.
>
> This is using the default agent container and doing service discovery for 
> a Jenkins URL and tunnel according to the services in the jenkins namespace.
>
> k get svc -n jenkins
> NAMETYPECLUSTER-IP  EXTERNAL-IP   
> PORT(S)  AGE
> jenkins-jenkins NodePort10.233.45.129   
> 8080:32080/TCP   7d
> jenkins-jenkins-agent   ClusterIP   10.233.11.112   
> 5/TCP7d
>
>
> #master log
> INFO: Created Pod: default-37fj9 in namespace jenkins
> Feb 12, 2018 11:16:32 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for Pod to be scheduled (0/100): default-37fj9
> Feb 12, 2018 11:16:38 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (0/100): default-37fj9
> Feb 12, 2018 11:16:39 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (1/100): default-37fj9
> Feb 12, 2018 11:16:40 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (2/100): default-37fj9
> Feb 12, 2018 11:16:41 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (3/100): default-37fj9
> Feb 12, 2018 11:16:42 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
> *INFO: Accepted JNLP4-connect connection #3 from /10.233.108.132:38682 
> <http://10.233.108.132:38682>*
> Feb 12, 2018 11:16:42 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (4/100): default-37fj9
> Feb 12, 2018 11:16:43 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (5/100): default-37fj9
> Feb 12, 2018 11:16:44 PM 
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
> INFO: Waiting for agent to connect (6/100): default-37fj9
>
>
>
> #agent logs
> INFO: Locating server among [
> http://jenkins-jenkins.jenkins.svc.cluster.local:8080/]
> Feb 12, 2018 11:16:41 PM 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
> INFO: Remoting server accepts the following protocols: [JNLP4-connect, 
> JNLP-connect, Ping, JNLP2-connect]
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Agent discovery successful
>   Agent address: jenkins-jenkins-agent.jenkins.svc.cluster.local
>   Agent port:5
>   Identity:  5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Handshaking
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Connecting to jenkins-jenkins-agent.jenkins.svc.cluster.local:5
> Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Trying protocol: JNLP4-connect
> Feb 12, 2018 11:16:43 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Remote identity confirmed: 
> 5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
> Feb 12, 2018 11:16:55 PM hudson.remoting.jnlp.Main$CuiListener status
> * INFO: Connected*
>
> -- 
> Brandon Pinske
> Site Reliability Engineer
> Rabb.it
>
>

-- 
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/e88fad60-b5f2-4f83-82c2-5e0900743839%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon]

Hello, I am trying to use the community helm chart for Jenkins and the
Kubernetes plugin 1.2 so that agents can be dynamically provisioned
according to build needs.

Ultimately, builds are failing because the  agents are not able to
connect to the master. However, I am seeing that in both the agents and
master log that they believe they have established a connection. What is
going on? How can I debug this further.

This is using the default agent container and doing service discovery
for a Jenkins URL and tunnel according to the services in the jenkins
namespace.

k get svc -n jenkins
NAME    TYPE    CLUSTER-IP  EXTERNAL-IP  
PORT(S)  AGE
jenkins-jenkins NodePort    10.233.45.129      
8080:32080/TCP   7d
jenkins-jenkins-agent   ClusterIP   10.233.11.112      
5/TCP    7d


#master log
INFO: Created Pod: default-37fj9 in namespace jenkins
Feb 12, 2018 11:16:32 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (0/100): default-37fj9
Feb 12, 2018 11:16:38 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (0/100): default-37fj9
Feb 12, 2018 11:16:39 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (1/100): default-37fj9
Feb 12, 2018 11:16:40 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (2/100): default-37fj9
Feb 12, 2018 11:16:41 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (3/100): default-37fj9
Feb 12, 2018 11:16:42 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
*INFO: Accepted JNLP4-connect connection #3 from /10.233.108.132:38682
<http://10.233.108.132:38682>*
Feb 12, 2018 11:16:42 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (4/100): default-37fj9
Feb 12, 2018 11:16:43 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (5/100): default-37fj9
Feb 12, 2018 11:16:44 PM
org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (6/100): default-37fj9



#agent logs
INFO: Locating server among
[http://jenkins-jenkins.jenkins.svc.cluster.local:8080/]
Feb 12, 2018 11:16:41 PM
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect,
JNLP-connect, Ping, JNLP2-connect]
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: jenkins-jenkins-agent.jenkins.svc.cluster.local
  Agent port:    5
  Identity:  5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-jenkins-agent.jenkins.svc.cluster.local:5
Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Feb 12, 2018 11:16:43 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed:
5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a
Feb 12, 2018 11:16:55 PM hudson.remoting.jnlp.Main$CuiListener status
*INFO: Connected*

-- 
Brandon Pinske
Site Reliability Engineer
Rabb.it

-- 
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/aae360a9-e14f-4e9e-94cf-63f75ad5d468%40rabb.it.
For more options, visit https://groups.google.com/d/optout.

Re: How to set global quiet period automatically on Jenkins startup

[Brandon Fryslie]

I just wanted to respond.  I have automated pretty much everything related 
to Jenkins lately, and looking through the source code and then using that 
to write a groovy script is exactly how it is supposed to be done.  Jenkins 
was never designed to be automated (which is strange considering it is an 
automation tool), so using the source code to write groovy scripts is 
pretty much the only workable technique.  

On Wednesday, February 8, 2017 at 2:32:37 AM UTC-7, Barry Laffoy wrote:
>
> By digging into the source code, I found an answer myself.
>
> import jenkins.model.Jenkins
> instance = Jenkins.getInstance()
> instance.setQuietPeriod(0)
>
> As always, I'm left to wonder if this is how it's supposed to be done, or 
> have I just completely misunderstood Jenkins?
>
> On Wednesday, 8 February 2017 09:18:46 UTC, Barry Laffoy wrote:
>>
>> In my never-ending quest to create a deployment script for Jenkins (why 
>> is this so difficult?), I would like to be able to configure the quiet 
>> period on startup, *without needing to configure it through the UI*.
>>
>> Is there a way of configuring this through groovy? Ideally I would like 
>> to place a script in my init.groovy.d/ so that it will be triggered 
>> automatically.
>>
>> In the class files, I found jenkins.model.GlobalQuietPeriodConfiguration, 
>> but this only exposes a method to get the quiet period
>>
>> gqpc = new jenkins.model.GlobalQuietPeriodConfiguration()
>> gqpc.getQuietPeriod()
>>
>> Result: 5
>>>
>>>
>> There is a method boolean configure(org.kohsuke.stapler.StaplerRequest 
>> req, net.sf.json.JSONObject json), but this appears to be designed 
>> solely to be called from the UI.
>>
>> Is there some standard pattern by which I could construct a dummy 
>> StaplerRequest so I can run configuration in my groovy script?
>>
>> Alternatively, is there some other public method I could or should be 
>> using?
>>
>> Thanks.
>>
>

-- 
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/28ff01c4-fe6f-471f-9fc7-36105a1ff661%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

We offer high quality COUNTERFEIT NOTES for the following currencies;

[brandon homan]

This bills are not home made but industrial and professional manufacturing. 
>From High
Quality IT techinicians from US,Russia,Korea and China We offer high 
quality COUNTERFEIT NOTES for the following currencies;

EUR - Euro
USD - US Dollar
DNR - DINAR
GBP - British Pound
INR - Indian Rupee
AUD - Australian Dollar
CAD - Canadian Dollar
AED - Emirati Dirham
ZAR - Rand
CHF - Swiss Franc
CNY - Chinese Yuan Renminbi
MYR - Malaysian Ringgit
THB - Thai Baht
NZD - New Zealand Dollar
SAR - Saudi Arabian Riyal
QAR - Qatari Riya

Email-:brandonhoma...@gmail.com
whats app.+1 (518) 823-3800  

-- 
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/a7b7ef60-ef24-457c-ac9b-ae0c62a0ac29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I use the Jenkins CLI commands for Credentials Plugin?

[Brandon R]

I've been looking into this as well and made a little progress by digging 
around https://github.com/jenkinsci/credentials-plugin

For store, I used "system::system::jenkins" like in their tests.  For 
domain I tried variations on the word "global" but none worked.  I then 
tried underscore '_' as a wild guess and that worked.  I tried that because 
it's in the url when you hover on (global) on the credentials page.

Anyway, I haven't tried creating creds yet, but I can at least get them 
like:

java -jar /usr/share/jenkins/jenkins-cli.jar -s http://localhost:8080 -i 
~jenkins/.ssh/id_rsa list-credentials system::system::jenkins

and

java -jar /usr/share/jenkins/jenkins-cli.jar -s http://localhost:8080 -i 
~jenkins/.ssh/id_rsa get-credentials-as-xml system::system::jenkins _ 
somecredname

(note that I require auth hence the -i. This might not be relevant in your 
case)

Hope this helps some.

On Saturday, August 6, 2016 at 12:32:22 AM UTC-7, Vishwanath V wrote:
>
> Hi all,
>
> I need to *automatedly* load sets of credentials to a Jenkins instance, 
> so that my jobs can pick up these credentials. 
>
> For this purpose I am using the Jenkins CLI, specifically the set of 
> commands provided by the Credentials Provider plugin:
>
>   create-credentials-by-xml
> Create Credential by XML
>   create-credentials-domain-by-xml
> Create Credentials Domain by XML
>   get-credentials-as-xml
> Get a Credentials as XML (secrets redacted)
>   get-credentials-domain-as-xml
> Get a Credentials Domain as XML
>   list-credentials
> Lists the Credentials in a specific Store
>   list-credentials-context-resolvers
> List Credentials Context Resolvers
>   list-credentials-providers
> List Credentials Providers
>update-credentials-by-xml
> Update Credentials by XML
>   update-credentials-domain-by-xml
> Update Credentials Domain by XML
>
> I am trying to understand how to use them, but there is literally no 
> documentation on this beyond the actual code (which I unfortunately am 
> unable to understand). 
>
> *Question 1. What is the "Store ID"?* 
>
> Based on the error messages, I understand it is 
> list-credentials [Store ID]
>
> I am unable to understand what the Store ID is. Another error message says 
> it should be in the format Provider::Resolver::ContextPath.
> But where would I get this information from?
>
> *Question 2: How do I load an XML for "create-credentials-by-xml"?*
>
> When I use the create-credentials-by-xml, I assume I need to provide an 
> XML file. How do I provide this ? i.e would it be as follows
> create-credentials-by-xml [Store ID] [Path to XML]
> ??
>
>

-- 
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/a3137f6b-9753-455d-871b-6e564bf9452f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[Brandon Wagner]

If I'm understanding correctly, I would mount the docker.sock to the slave
container? I created an image extended from the jenkinsci/jnlp-slave that
does a wget for the docker CLI.

However, I don't see a place to mount the docker.sock through the ECS
configuration options.


-Brandon Wagner

On Sat, Jan 23, 2016 at 1:08 PM, nicolas de loof <nicolas.del...@gmail.com>
wrote:

> You could use docker-custom-build-environment-plugin for this exact
> scenario, with bind mounted /var/run/docker.sock so you can run containers
> side by side (vs "in-docker"). Would need some tests on my side to ensure
> this scenario is supported, I have this on my TOD for a while but never
> took time to setup a test environment for it...
>
> 2016-01-22 21:01 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>
>> I would like to run Docker containers for all of my software projects and
>> dynamically allocate build slaves via ECS (so that I can have a core
>> cluster that can do builds quickly; in contrast to spinning up an EC2
>> instance).
>>
>>  For example, I have a Java application which is completely contained in
>> a Docker container (I can build it, run tests, and run the actual
>> application with Tomcat all within the container). I want to use this for a
>> variety of different purposes (dev, testing, qa, and production). In order
>> to make it reusable like that, I don't want to include Jenkins Slave
>> packages and expose ports. I'd rather deploy out a Jenkins-Slave container
>> to my ECS cluster, and then have that slave handle running my application's
>> docker container which also performs tests.
>>
>> I also support other team applications which are already running docker
>> container builds in Jenkins (locally on the Jenkins Master). I want it to
>> be transparent to them that I'm "outsourcing" build slaves to ECS. It
>> shouldn't matter to them that I'm changing the way Jenkins is performing
>> builds.
>>
>> Let me know if you (or anyone else) have suggestions based on my goals.
>>
>> -Brandon Wagner
>>
>>
>> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>> privileged flag has been added to development build (
>>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>>> anyway, DinD is probably not a good idea (there's really few docker
>>> usages to actually require it). What's your actual need ?
>>>
>>> 2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>
>>>> So I ended up figuring my issue out. I think there were a couple of
>>>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>>>> Docker Container I was using was mapping to the host port 5000. And my Load
>>>> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
>>>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>>>> ECS.
>>>>
>>>> My next problem: I want to use docker-in-docker to run docker builds on
>>>> my docker jenkins slaves. I'm trying to use
>>>> https://github.com/tehranian/dind-jenkins-slave which looks good, but
>>>> I don't see an option on the Jenkins ECS plugin to run the slave as
>>>> privileged which is necessary for docker-in-docker.
>>>>
>>>>
>>>> -Brandon Wagner
>>>>
>>>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>
>>>>> First look into jenkins logs.
>>>>> Also check on ECS a task definition has been created for
>>>>> jenkins-slaves.
>>>>> Also double check ECS nodes can ping your jenkins master URL.
>>>>>
>>>>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>>>
>>>>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin
>>>>>> to deploy Jenkins Slave Containers for builds. I have an ECS cluster 
>>>>>> setup,
>>>>>> and I have it configured in my Jenkins Configuration. Everything appears 
>>>>>> to
>>>>>> be good until I try to build a job, restricting to the ecs cloud label I
>>>>>> setup, and it just comes back with "(pending—
>>>>>> Jenkins-Container-Cloud-456...164
>>>>>> <https://jenkins.itsec.aolcloud.net/computer/Jenkins-Container-Cloud-456b6d1601164>is
>>>>>> offlin

Re: AWS ECS Plugin

[Brandon Wagner]

Ok, I've made progress. I'm able to run a docker container along side the
slave container on ECS. However, I just used the amazon-ecs-plugin. When I
tried using the CloudBees Docker Custom build Environment Plugin, I kept
getting "Cannot start container  System error: no such file or
directory"

If I just do a shell script "docker pull java && docker run java java
-version" it works.

Is there any advantage in using the CloudBees Docker Custom build
Environment Plugin rather than shell scripts? I'm hesitant in using shell
scripts since people may see shell commands and start plugging in other
commands rather than just using the Docker CLI commands.


-Brandon Wagner

On Mon, Jan 25, 2016 at 10:51 AM, nicolas de loof <nicolas.del...@gmail.com>
wrote:

> Latest development build for ECS plugin do let you define bind mounts, see
> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/
>
> 2016-01-25 16:33 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>
>> If I'm understanding correctly, I would mount the docker.sock to the
>> slave container? I created an image extended from the jenkinsci/jnlp-slave
>> that does a wget for the docker CLI.
>>
>> However, I don't see a place to mount the docker.sock through the ECS
>> configuration options.
>>
>>
>> -Brandon Wagner
>>
>> On Sat, Jan 23, 2016 at 1:08 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>> You could use docker-custom-build-environment-plugin for this exact
>>> scenario, with bind mounted /var/run/docker.sock so you can run containers
>>> side by side (vs "in-docker"). Would need some tests on my side to ensure
>>> this scenario is supported, I have this on my TOD for a while but never
>>> took time to setup a test environment for it...
>>>
>>> 2016-01-22 21:01 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>
>>>> I would like to run Docker containers for all of my software projects
>>>> and dynamically allocate build slaves via ECS (so that I can have a core
>>>> cluster that can do builds quickly; in contrast to spinning up an EC2
>>>> instance).
>>>>
>>>>  For example, I have a Java application which is completely contained
>>>> in a Docker container (I can build it, run tests, and run the actual
>>>> application with Tomcat all within the container). I want to use this for a
>>>> variety of different purposes (dev, testing, qa, and production). In order
>>>> to make it reusable like that, I don't want to include Jenkins Slave
>>>> packages and expose ports. I'd rather deploy out a Jenkins-Slave container
>>>> to my ECS cluster, and then have that slave handle running my application's
>>>> docker container which also performs tests.
>>>>
>>>> I also support other team applications which are already running docker
>>>> container builds in Jenkins (locally on the Jenkins Master). I want it to
>>>> be transparent to them that I'm "outsourcing" build slaves to ECS. It
>>>> shouldn't matter to them that I'm changing the way Jenkins is performing
>>>> builds.
>>>>
>>>> Let me know if you (or anyone else) have suggestions based on my goals.
>>>>
>>>> -Brandon Wagner
>>>>
>>>>
>>>> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <
>>>> nicolas.del...@gmail.com> wrote:
>>>>
>>>>> privileged flag has been added to development build (
>>>>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>>>>> anyway, DinD is probably not a good idea (there's really few docker
>>>>> usages to actually require it). What's your actual need ?
>>>>>
>>>>> 2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>>>
>>>>>> So I ended up figuring my issue out. I think there were a couple of
>>>>>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>>>>>> Docker Container I was using was mapping to the host port 5000. And my 
>>>>>> Load
>>>>>> Balancer in front of Jenkins was not forwarding port 5000 to the host 
>>>>>> (only
>>>>>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>>>>>> ECS.
>>>>>>
>>>>>> My next problem: I want to use docker-in-docker to run docker builds
>>>>>>

Re: AWS ECS Plugin

[Brandon Wagner]

I would like to run Docker containers for all of my software projects and
dynamically allocate build slaves via ECS (so that I can have a core
cluster that can do builds quickly; in contrast to spinning up an EC2
instance).

 For example, I have a Java application which is completely contained in a
Docker container (I can build it, run tests, and run the actual application
with Tomcat all within the container). I want to use this for a variety of
different purposes (dev, testing, qa, and production). In order to make it
reusable like that, I don't want to include Jenkins Slave packages and
expose ports. I'd rather deploy out a Jenkins-Slave container to my ECS
cluster, and then have that slave handle running my application's docker
container which also performs tests.

I also support other team applications which are already running docker
container builds in Jenkins (locally on the Jenkins Master). I want it to
be transparent to them that I'm "outsourcing" build slaves to ECS. It
shouldn't matter to them that I'm changing the way Jenkins is performing
builds.

Let me know if you (or anyone else) have suggestions based on my goals.

-Brandon Wagner


On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <nicolas.del...@gmail.com>
wrote:

> privileged flag has been added to development build (
> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
> anyway, DinD is probably not a good idea (there's really few docker usages
> to actually require it). What's your actual need ?
>
> 2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>
>> So I ended up figuring my issue out. I think there were a couple of
>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>> Docker Container I was using was mapping to the host port 5000. And my Load
>> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>> ECS.
>>
>> My next problem: I want to use docker-in-docker to run docker builds on
>> my docker jenkins slaves. I'm trying to use
>> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
>> don't see an option on the Jenkins ECS plugin to run the slave as
>> privileged which is necessary for docker-in-docker.
>>
>>
>> -Brandon Wagner
>>
>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>> First look into jenkins logs.
>>> Also check on ECS a task definition has been created for jenkins-slaves.
>>> Also double check ECS nodes can ping your jenkins master URL.
>>>
>>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>
>>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
>>>> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
>>>> and I have it configured in my Jenkins Configuration. Everything appears to
>>>> be good until I try to build a job, restricting to the ecs cloud label I
>>>> setup, and it just comes back with "(pending—
>>>> Jenkins-Container-Cloud-456...164
>>>> <https://jenkins.itsec.aolcloud.net/computer/Jenkins-Container-Cloud-456b6d1601164>is
>>>> offline)" .
>>>>
>>>> Does anyone know how to fix this, or have suggestions on debugging
>>>> steps?
>>>>
>>>> --
>>>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.goog

Re: AWS ECS Plugin

[Brandon Wagner]

So I ended up figuring my issue out. I think there were a couple of issues.
My JNLP port was set to 50,000 instead of 5,000 which the Jenkins Docker
Container I was using was mapping to the host port 5000. And my Load
Balancer in front of Jenkins was not forwarding port 5000 to the host (only
443). Anyways, all of that is fixed and I can now run builds on slaves in
ECS.

My next problem: I want to use docker-in-docker to run docker builds on my
docker jenkins slaves. I'm trying to use
https://github.com/tehranian/dind-jenkins-slave which looks good, but I
don't see an option on the Jenkins ECS plugin to run the slave as
privileged which is necessary for docker-in-docker.


-Brandon Wagner

On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <nicolas.del...@gmail.com>
wrote:

> First look into jenkins logs.
> Also check on ECS a task definition has been created for jenkins-slaves.
> Also double check ECS nodes can ping your jenkins master URL.
>
> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>
>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
>> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
>> and I have it configured in my Jenkins Configuration. Everything appears to
>> be good until I try to build a job, restricting to the ecs cloud label I
>> setup, and it just comes back with "(pending—
>> Jenkins-Container-Cloud-456...164
>> <https://jenkins.itsec.aolcloud.net/computer/Jenkins-Container-Cloud-456b6d1601164>is
>> offline)" .
>>
>> Does anyone know how to fix this, or have suggestions on debugging steps?
>>
>> --
>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CAKgdMg-%2Bs99MCNpwJz99QBs0NTke7EV2Tt%3DWPEj5NZBzjkJaHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

AWS ECS Plugin

[Brandon Wagner]

I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to 
deploy Jenkins Slave Containers for builds. I have an ECS cluster setup, 
and I have it configured in my Jenkins Configuration. Everything appears to 
be good until I try to build a job, restricting to the ecs cloud label I 
setup, and it just comes back with "(pending—
Jenkins-Container-Cloud-456...164 
is
 
offline)" .  

Does anyone know how to fix this, or have suggestions on debugging steps? 

-- 
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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SCM Sync Configuration Plugin

[Brandon Koepke]

Hey,

Has anyone been able to get the scm sync configuration plugin working in 
the last 6-12 months? The plugin that is in the official jenkinsci jobs is 
completely non-functional for me, and I had to make many changes in order 
to get it to compile.

From there the best I've been able to do is get it to 'git add' files, but 
the 'git commit  git push' seems to never occur (and there isn't anything 
in the logs to indicate a problem). I also tried the pull request from 
here: https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/31 
and that one gets me further, but I have the same lack of 'git commit  
git push'. Does anyone have this plugin working in a newer version of 
jenkins?

If not does a plugin exist where you can have separate git repositories 
that store job configurations?

Any word on this would be greatly appreciated.


-- 
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/7193538c-086d-41e0-abf4-3a980c3bb9af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.