date:20170128

Re: Example of a working pod with the kubernetes-ci plugin

2017-01-28 Thread Joe Rhaman

Carlos,

This Plugin clearly doesn't work Please provide a detailed how to at 
least rather on how this works.

This is turning out to be a complete waste of time. 

Joe

On Monday, December 19, 2016 at 7:44:43 AM UTC, Carlos Sanchez wrote:
>
>
>
> On Tue, Dec 6, 2016, 22:37 Daniel Serodio  
> wrote:
>
>> Hi Carlos,
>>
>> I'm trying to understand how composing multiple containers (one with the 
>> JNLP slave, another with Maven) in a Pod Template but I can't get the 
>> example pipeline to work. The Jenkins logs show that it's "Waiting for 
>> slave to connect", and after 100 tries it gives up, deletes the Pod and 
>> creates a new one ad infinitum.
>>
>> Using "kubectl get pods" I can see that the 2 containers have been 
>> created and the Pod is running, but it won't connect to the Jenkins master.
>>
>
> You need to get the pod logs to see why it is not connecting. kubectl logs 
> pods/... jnlp
>
>
>> The example pipeline uses a maven and a golang images, but none of them 
>> knows how to connect to Jenkins using JNLP. The README says that "The jnlp 
>> agent image used can be customized by adding it to the template", but it 
>> seems that I need to include a JNLP image in the pod template so that it 
>> can talk to Jenkins.
>>
>>
>> On Wednesday, November 23, 2016 at 7:12:24 PM UTC-2, Carlos Sanchez wrote:
>>>
>>> You can't just jump from a container to another,  can only share through 
>>> network or shared filesystem.
>>> http://kubernetes.io/docs/user-guide/pods/
>>>
>>> I suggest using the Kubernetes Jenkins plugin that can do exactly what 
>>> you want using pipeline
>>>
>>> https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#pipeline-support
>>>
>> -- 
>> 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/khpG2-6NBNI/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/9ff5076f-b06e-428f-a43e-5c9d2e4b0094%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/f551c818-89b7-4e9e-89e8-5432898637bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: wildcard for branch name

2017-01-28 Thread Sharan Basappa

Mark,

I cant use freestyle job for the simple reason that, what we are doing 
would become a sort of best practice for many projects.
Gui based approach is, in my view,  not a good way to share the best 
practice.

I will check out multi branch pipeline. Thanks a lot

On Saturday, 28 January 2017 19:27:56 UTC+5:30, Mark Waite wrote:

> The freestyle job is a single job which would build each branch that 
> matches as part of that single job.
>
> The multi-branch pipeline will automatically create a job per branch which 
> matches the wildcard and has a Jenkinsfile.  That's where you ultimately 
> want to go.
>
> Mark Waite
>
> On Sat, Jan 28, 2017 at 5:29 AM Sharan Basappa  > wrote:
>
>> Hi Mark, Indra,
>>
>> If I use wildcard as a branch specifier then what would happen if there 
>> are multiple matches?
>> I would like to know this because my requirement is take each branch and 
>> then build each of them separately.
>>
>>
>> On Thursday, 26 January 2017 20:21:13 UTC+5:30, Indra Gunawan (ingunawa) 
>> wrote:
>>
>>> HI Sharan,
>>>
>>>  
>>>
>>> I sent this already:
>>>
>>>  
>>>
>>>  
>>>
>>> You can’t use the simple git pipeline command if you want to be fancy
>>>
>>>  
>>>
>>> You should use the form where you can specify more options like 
>>> configuring Git SCM:
>>>
>>>  
>>>
>>> checkout scm: [$class: 'GitSCM', branches: [[name: '*/test*']], 
>>> userRemoteConfigs: [[url: 'git@hd1:testing']]]
>>>
>>>  
>>>
>>>  
>>>
>> *From: * on behalf of Sharan Basappa <
>>> sharan@gmail.com>
>>> *Reply-To: *"jenkins...@googlegroups.com" 
>>>
>>
>>> *Date: *Thursday, January 26, 2017 at 4:03 AM
>>>
>> *To: *Jenkins Users 
>>>
>>
>>> *Subject: *Re: Pipeline: wildcard for branch name
>>>
>>  
>>>
>>> Hi David,
>>>
>>>  
>>>
>>> I am new to continuous integration and Jenkins, so I need inputs to go 
>>> in the right direction.
>>>
>>> My requirement is that users push branches with name test_id1/test_id2 
>>> etc.
>>>
>>> I would like to build only when users have created branches with the 
>>> above name.
>>>
>>>  
>>>
>>> So, after seeing the responses, it looks like I have to:
>>>
>>> 1)  first checkout the repository
>>>
>>> 2)  list out the branches, 
>>>
>>> 3)  if branch name matches test* then I checkout the corresponding 
>>> branch and do rest of the build
>>>
>>>  
>>>
>>> I need inputs here ...
>>>
>>>
>>> On Wednesday, 25 January 2017 04:53:20 UTC+5:30, David Karr wrote:
>>>
>>> On Monday, January 23, 2017 at 9:37:01 AM UTC-8, Sharan Basappa wrote: 
>>>
>>> Hi,
>>>
>>>  
>>>
>>> I am trying to create pipeline script such that it only a certain 
>>> branches following a naming style are built.
>>>
>>> However, pipeline bails out when I use the wildcard.
>>>
>>>  
>>>
>>> The code snippet is below:
>>>
>>>  
>>>
>>> stage 'build'
>>>
>>> node {
>>>
>>> git url: 'git@hd1:testing', branch: test*
>>>
>>> sh "pwd"
>>>
>>> sh "cat simple.csh"
>>>
>>> sh "echo $PATH"
>>>
>>> sh "csh simple.csh"
>>>
>>> echo("end of pipeline")
>>>
>>> }
>>>
>>>  
>>>
>>> I see the following output from the above script:
>>>
>>>  
>>>
>>>  
>>>
>>> Started by user User
>>>
>>>  
>>>
>>> [Pipeline] stage (build)
>>>
>>>  
>>>
>>> Using the ‘stage’ step without a block argument is deprecated
>>>
>>>  
>>>
>>> Entering stage build
>>>
>>>  
>>>
>>> Proceeding
>>>
>>>  
>>>
>>> [Pipeline] node
>>>
>>>  
>>>
>>> Running on master in /var/lib/jenkins/workspace/test_build_3
>>>
>>>  
>>>
>>> [Pipeline] {
>>>
>>>  
>>>
>>> [Pipeline] }
>>>
>>>  
>>>
>>> [Pipeline] // node
>>>
>>>  
>>>
>>> [Pipeline] End of Pipeline
>>>
>>>  
>>>
>>> groovy.lang.MissingPropertyException: No such property: test for class: 
>>> WorkflowScript
>>>
>>>  
>>>
>>> at 
>>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
>>>
>>>  
>>>
>>> at 
>>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
>>>
>>>  
>>>
>>> at 
>>> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
>>>
>>>  
>>>
>>> at 
>>> com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
>>>
>>>  
>>>
>>> at WorkflowScript.run(WorkflowScript:6)
>>>
>>>  
>>>
>>> at ___cps.transform___(Native Method)
>>>
>>>  
>>>
>>> at 
>>> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
>>>
>>>  
>>>
>>> at 
>>> com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
>>>
>>>  
>>>
>>> at 
>>> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
>>>
>>>  
>>>
>>> at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
>>>
>>>  
>>>
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>>  
>>>
>>>

Re: Pipeline: wildcard for branch name

2017-01-28 Thread Mark Waite

The freestyle job is a single job which would build each branch that
matches as part of that single job.

The multi-branch pipeline will automatically create a job per branch which
matches the wildcard and has a Jenkinsfile.  That's where you ultimately
want to go.

Mark Waite

On Sat, Jan 28, 2017 at 5:29 AM Sharan Basappa 
wrote:

> Hi Mark, Indra,
>
> If I use wildcard as a branch specifier then what would happen if there
> are multiple matches?
> I would like to know this because my requirement is take each branch and
> then build each of them separately.
>
>
> On Thursday, 26 January 2017 20:21:13 UTC+5:30, Indra Gunawan (ingunawa)
> wrote:
>
> HI Sharan,
>
>
>
> I sent this already:
>
>
>
>
>
> You can’t use the simple git pipeline command if you want to be fancy
>
>
>
> You should use the form where you can specify more options like
> configuring Git SCM:
>
>
>
> checkout scm: [$class: 'GitSCM', branches: [[name: '*/test*']],
> userRemoteConfigs: [[url: 'git@hd1:testing']]]
>
>
>
>
>
> *From: * on behalf of Sharan Basappa <
> sharan@gmail.com>
> *Reply-To: *"jenkins...@googlegroups.com" 
>
>
> *Date: *Thursday, January 26, 2017 at 4:03 AM
>
> *To: *Jenkins Users 
>
>
> *Subject: *Re: Pipeline: wildcard for branch name
>
>
>
> Hi David,
>
>
>
> I am new to continuous integration and Jenkins, so I need inputs to go in
> the right direction.
>
> My requirement is that users push branches with name test_id1/test_id2 etc.
>
> I would like to build only when users have created branches with the above
> name.
>
>
>
> So, after seeing the responses, it looks like I have to:
>
> 1)  first checkout the repository
>
> 2)  list out the branches,
>
> 3)  if branch name matches test* then I checkout the corresponding branch
> and do rest of the build
>
>
>
> I need inputs here ...
>
>
> On Wednesday, 25 January 2017 04:53:20 UTC+5:30, David Karr wrote:
>
> On Monday, January 23, 2017 at 9:37:01 AM UTC-8, Sharan Basappa wrote:
>
> Hi,
>
>
>
> I am trying to create pipeline script such that it only a certain branches
> following a naming style are built.
>
> However, pipeline bails out when I use the wildcard.
>
>
>
> The code snippet is below:
>
>
>
> stage 'build'
>
> node {
>
> git url: 'git@hd1:testing', branch: test*
>
> sh "pwd"
>
> sh "cat simple.csh"
>
> sh "echo $PATH"
>
> sh "csh simple.csh"
>
> echo("end of pipeline")
>
> }
>
>
>
> I see the following output from the above script:
>
>
>
>
>
> Started by user User
>
>
>
> [Pipeline] stage (build)
>
>
>
> Using the ‘stage’ step without a block argument is deprecated
>
>
>
> Entering stage build
>
>
>
> Proceeding
>
>
>
> [Pipeline] node
>
>
>
> Running on master in /var/lib/jenkins/workspace/test_build_3
>
>
>
> [Pipeline] {
>
>
>
> [Pipeline] }
>
>
>
> [Pipeline] // node
>
>
>
> [Pipeline] End of Pipeline
>
>
>
> groovy.lang.MissingPropertyException: No such property: test for class:
> WorkflowScript
>
>
>
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
>
>
>
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
>
>
>
> at
> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
>
>
>
> at
> com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
>
>
>
> at WorkflowScript.run(WorkflowScript:6)
>
>
>
> at ___cps.transform___(Native Method)
>
>
>
> at
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
>
>
>
> at
> com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
>
>
>
> at
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
>
>
>
> at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
>
>
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
>
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
>
>
> at
> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
>
>
>
> at
> com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
>
>
>
> at com.cloudbees.groovy.cps.Next.step(Next.java:58)
>
>
>
> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
>
>
>
> at
> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
>
>
>
> at
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)
>
>
>
> at
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
>
>
>
> at
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
>
>
>
> at
>

sonarqube quality gates with jenkinsfile

2017-01-28 Thread Ruchir Brahmbhatt

Hi,

I tried to 
follow https://gist.github.com/vdupain/832964527b4b8d7d4c648169dae8c656 
without maven for a test php project in bitbucket team repository. It gives 
me below error after sonarqube analysis stage.

Unable to process url: 
http://localhost:9000/api/ce/task?id=AVnksRksMwjM7SNQESTh

Any idea what could be wrong?

-- 
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/8b235bd6-810a-4877-974a-6fb4ff3377ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: wildcard for branch name

2017-01-28 Thread Sharan Basappa

Hi Mark, Indra,

If I use wildcard as a branch specifier then what would happen if there are 
multiple matches?
I would like to know this because my requirement is take each branch and 
then build each of them separately.


On Thursday, 26 January 2017 20:21:13 UTC+5:30, Indra Gunawan (ingunawa) 
wrote:

> HI Sharan,
>
>  
>
> I sent this already:
>
>  
>
>  
>
> You can’t use the simple git pipeline command if you want to be fancy
>
>  
>
> You should use the form where you can specify more options like 
> configuring Git SCM:
>
>  
>
> checkout scm: [$class: 'GitSCM', branches: [[name: '*/test*']], 
> userRemoteConfigs: [[url: 'git@hd1:testing']]]
>
>  
>
>  
>
> *From: * on behalf of Sharan 
> Basappa 
> *Reply-To: *"jenkins...@googlegroups.com " <
> jenkins...@googlegroups.com >
> *Date: *Thursday, January 26, 2017 at 4:03 AM
> *To: *Jenkins Users 
> *Subject: *Re: Pipeline: wildcard for branch name
>
>  
>
> Hi David,
>
>  
>
> I am new to continuous integration and Jenkins, so I need inputs to go in 
> the right direction.
>
> My requirement is that users push branches with name test_id1/test_id2 etc.
>
> I would like to build only when users have created branches with the above 
> name.
>
>  
>
> So, after seeing the responses, it looks like I have to:
>
> 1)  first checkout the repository
>
> 2)  list out the branches, 
>
> 3)  if branch name matches test* then I checkout the corresponding branch 
> and do rest of the build
>
>  
>
> I need inputs here ...
>
>
> On Wednesday, 25 January 2017 04:53:20 UTC+5:30, David Karr wrote:
>
> On Monday, January 23, 2017 at 9:37:01 AM UTC-8, Sharan Basappa wrote: 
>
> Hi,
>
>  
>
> I am trying to create pipeline script such that it only a certain branches 
> following a naming style are built.
>
> However, pipeline bails out when I use the wildcard.
>
>  
>
> The code snippet is below:
>
>  
>
> stage 'build'
>
> node {
>
> git url: 'git@hd1:testing', branch: test*
>
> sh "pwd"
>
> sh "cat simple.csh"
>
> sh "echo $PATH"
>
> sh "csh simple.csh"
>
> echo("end of pipeline")
>
> }
>
>  
>
> I see the following output from the above script:
>
>  
>
>  
>
> Started by user User
>
>  
>
> [Pipeline] stage (build)
>
>  
>
> Using the ‘stage’ step without a block argument is deprecated
>
>  
>
> Entering stage build
>
>  
>
> Proceeding
>
>  
>
> [Pipeline] node
>
>  
>
> Running on master in /var/lib/jenkins/workspace/test_build_3
>
>  
>
> [Pipeline] {
>
>  
>
> [Pipeline] }
>
>  
>
> [Pipeline] // node
>
>  
>
> [Pipeline] End of Pipeline
>
>  
>
> groovy.lang.MissingPropertyException: No such property: test for class: 
> WorkflowScript
>
>  
>
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
>
>  
>
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
>
>  
>
> at 
> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:33)
>
>  
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
>
>  
>
> at WorkflowScript.run(WorkflowScript:6)
>
>  
>
> at ___cps.transform___(Native Method)
>
>  
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
>
>  
>
> at 
> com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
>
>  
>
> at 
> com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
>
>  
>
> at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
>
>  
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
>  
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
>  
>
> at 
> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
>
>  
>
> at 
> com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
>
>  
>
> at com.cloudbees.groovy.cps.Next.step(Next.java:58)
>
>  
>
> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
>
>  
>
> at 
> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
>
>  
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>
>  
>
> at 
>

Re: Pipeline & Git branch

2017-01-28 Thread Sharan Basappa

Thanks. I do have conceptual questions. I will continue that thread ...

On Saturday, 28 January 2017 10:35:09 UTC+5:30, Mark Waite wrote:

> Did you try the steps I described earlier?  
> https://groups.google.com/d/msg/jenkinsci-users/jiwtA088sXc/BjL-X6DjCwAJ 
>
> On Friday, January 27, 2017 at 9:12:38 PM UTC-7, Sharan Basappa wrote:
>>
>>
>> I would like to list out all branches in Git with a specific naming 
>> convention (feature_*) and then start a build process (compile, test and 
>> publish) for each of those branches.
>> Can someone, please, give me some directions on this?
>>
>> 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/7626d8e7-808a-461a-869a-109cd9905abd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: html for the system message

2017-01-28 Thread Daniel Beck


> On 27.01.2017, at 19:26, Richard Ginga  wrote:
> 
> is there some over-riding style sheet at work here?

Check your browser's developer tools to see which rules apply, and why.

-- 
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/639572C9-79AC-47E9-826E-9049E9DBC0D3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Example of a working pod with the kubernetes-ci plugin

Re: Pipeline: wildcard for branch name

Re: Pipeline: wildcard for branch name

sonarqube quality gates with jenkinsfile

Re: Pipeline: wildcard for branch name

Re: Pipeline & Git branch

Re: html for the system message

7 matches

Site Navigation

Mail list logo

Footer information