Re: sh pipeline step started to fail after update to 2.42

[John Mellor]

Looking at your pipeline plugin version numbers, I assume that you are on 
Jenkins2.
I'm on Jenkins 1.656 and have been unable to move up to the exact pipeline 
plugin version numbers that you used.
However, I have the same problem, and unfortunately reverting to the 
previous version has not fixed the issue.

[Pipeline] {[Pipeline] stage[Pipeline] { (Fetch Dependencies)[Pipeline] 
deleteDir[Pipeline] sh[cb-automation-pipeline] Running shell script
nohup: failed to run command ‘sh’: No such file or directory[Pipeline] echoNo 
need to clear known_hosts.[Pipeline] sh[cb-automation-pipeline] Running shell 
script
nohup: failed to run command ‘sh’: No such file or directory[Pipeline] }

Now what?  All pipelines a inoperable at this point.

-- 
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/f7c01382-6be3-47b2-8bd1-89f071597dcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Jira plugin 2.3

[Slide]

Root of the problem looks to be:

JSONException: A JSONObject text must begin with '{' at character 19 of
 
  
   Wrong host!
  
  
   Please use a valid host.
  
 

Nothing in your setup changed other than the plugin version? Did you check
the change log of the plugin to see if there were any notes on config
updates you might need to do? It looks like your server is responding with
the data above, which is causing the exception.

On Fri, Feb 10, 2017, 08:01 vf  wrote:

> More information:
> Our Jira version: v6.3.1#6329-sha1:7df76f1
> issues.jenkins-ci.org: v7.1.7#71011-sha1:2526d7c
>
>
> Am Freitag, 10. Februar 2017 13:00:52 UTC+1 schrieb vf:
>
> Hi,
>
> I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working
> (see stack trace below).
> System:
>   Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
> Jira plugin configuration: (unchanged fo 3+ years)
>  url https://my.company.com/jira/
>  username + password
>  other fields are all default.
>
> I tested on a fresh installation: Jenkins 2.44, with only jira plugin 2.3
> installed.
>
> I can reproduce the stacktrace by validating my configuration on the
> configure screen.
>
> But, when I test https://issues.jenkins-ci,org/ with my account, it works
> without any problem.
>
> So I am very much stuck here, Can anyone give me a hint?
>
> thanks
> vf
>
>
> WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
> RestClientException{statusCode=Optional.absent(), errorCollections=[]}
> at
> com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
> at
> hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
> at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
> at
> hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
> at
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at 

Re: sh pipeline step started to fail after update to 2.42

[Daniel Beck]

> On 10.02.2017, at 21:40, John Mellor  wrote:
> 
> Now what?  All pipelines a inoperable at this point.

I linked to JENKINS-41339 earlier, which mentions solutions in the comments.

-- 
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/CA61940D-B454-4FDA-BC19-D6E77A3C232C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Multi Configuration Job Jenkinsfile

[Chris Denneen]

I'm looking for example to replace existing Multi Configuration Job with 
Jenkinsfile that handles X Y axis mapping.
Also needs to support Matrix Configuration (so which X:Y mappings to do) 
and Slave label to run that job on.
In the multi configuration job even if called from pipeline on node X... 
when it runs the child jobs it runs them on random nodes without a Slave 
Axis.

-- 
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/ea3da699-0199-42f4-b3cc-5aba19a370b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

println in "call()" in "vars/xx.groovy" shows in console, but println in defed method in class in "vars/xx.groovy" is just ignored

[David Karr]

I'm seeing some odd behavior with "println" calls in shared library 
methods, and a perhaps related issue with printing a shared library object 
in a Jenkinsfile.

I've been using https://jenkins.io/doc/book/pipeline/shared-libraries/ as 
my implementation guide.

I've been working on evolving a shared library.  I started with a 
Jenkinsfile with several methods that I've been copying to a handful of 
other Jenkinsfiles, so I decided it was time to remove duplication and move 
them to a shared library.  I first created a "vars/foo.groovy" with a 
"call()" method, with the body of my original "foo" method from the 
Jenkinsfile.  This worked fine, and I note that "println" calls within the 
"call" method resulted in that string in the Jenkins job console.

However, I found that the negative part of moving those methods to "vars" 
files was that I now had to pass several global variables ("params.." and 
"env..") as parameters to those methods (actually, I don't know for certain 
that I actually had to do that, but I don't think I would want to depend on 
that working).

So, I decided to try defining a class in a "vars" file, with several 
instance variables for for those "params." and "env." variables, and "def" 
methods for each of the methods that I used to have in standalone "vars" 
files.  So far, I've tested this a little bit, and functionally this 
appears to work.  However, what's very odd is that if I have a "println" 
call within one of the "def"ed methods in the class, when it's executed 
during the job, it's like it just skips over it.  The output from that line 
just doesn't appear in the console.

I also noticed another seemingly related behavior that might be something 
completely different.  The file I had created to store the class was 
"vars/uslutils.groovy" (with "class uslutils implements Serializable" in 
the file). I also implemented a "public String toString()" method in the 
defined class, which just returns a string containing all the instance 
variables in a gstring. In my Jenkinsfile, I referenced "uslutils.varname" 
and "uslutils.methodname", and that worked fine.  However, I also had a 
println call in the Jenkinsfile itself that just printed 
"uslutils[${uslutils}]".  Right after that line, I had another println call 
for "uslutils[${uslutils.toString()}]".  The output from the latter line 
appeared in the console.  The output from the former line did not appear.

-- 
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/f8037f10-15cc-4323-bf7e-cf56e9768f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch pipeline - source code present but .git file missing

[Sharan Basappa]

I am using multi-branch pipeline and I find that source code is present 
under {workspace}@script directory but .git files are missing in any of the 
directories.
So, when I try to stash so that I can move to another branch, I get error 
saying that, "it does not appear to be a git repository"

Let me know what the issue is?

The following are some additional information:
1) I am using Jenkinsfile that is at the root of my git repository
2) I have created a Jenkins job using multi-branch pipeline and have only 
given path to git and only option to pool SCM every minute
3) I am not checking out any repository explicitly in my Jenkinsfile - I 
still find source code in the workspace through

-- 
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/18112354-49a6-4852-8b3f-7724ff0211a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with docker agent (declarative syntax)

[R. Tyler Croy]

(replies inline)

On Thu, 09 Feb 2017, Bart??omiej Kruczyk wrote:

> Hi, I have problem with setting docker agent type for my pipeline.
> 
> Although something like this works:
> 
> 
> agent {
> docker 'myimage'
> 
> }
> 
> 
> This does not:
> 
> 
> agent {
> docker {
> image: 'myimage'
> 
> registry: 'localhost:5000'
> 
> }
> }


As far as I am aware, there is no supported "registry" value inside that
`docker` block.


See also https://jenkins.io/doc/book/pipeline/syntax/#agent



- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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/20170210093934.GC26439%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

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

[Carlos Sanchez]

On Saturday, January 28, 2017 at 6:36:55 PM UTC+1, Joe Rhaman wrote:
>
> 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. 
>


Considering that are over 1200 installations, I think it is safe to assume 
that it does work for most people.
There are examples at https://github.com/jenkinsci/kubernetes-plugin

As I mentioned in the previous mail, in order to see why pods can't connect 
to jenkins you need to get the pod logs in Kubernetes side: kubectl logs 
pods/{your pod id} jnlp
 

>
> 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/fa355e11-ec8d-4d75-8fb6-145bb710de31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins crashes with "Illegal character 0x0 for HttpChannelOverHttp" - Why?

[daniel . seebauer]

Hi,

- Ubuntu 16.04.1
- Jenkins 2.32.2

Since a few days I see crashes on Jenkins: (/var/log/jenkins/jenkins.log*)*

Feb 10, 2017 12:15:09 AM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /azenv.php. Returning 
403.

Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Illegal character 0x1 in state=START for buffer 
HeapByteBuffer@6de2eef2[p=1,l=256,c=16384,r=255]={\x01<<<\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01...\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01>>>.com/\r\nContent-Ty...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: badMessage: 400 Illegal character 0x1 for 
HttpChannelOverHttp@10d1bddb{r=0,c=false,a=IDLE,uri=}

Feb 10, 2017 4:35:15 AM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /azenv.php. Returning 
403.

Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Illegal character 0x0 in state=START for buffer 
HeapByteBuffer@5e57ec7c[p=1,l=1,c=16384,r=0]={\x00<<<>>>ET /login 
HTTP/1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: badMessage: 400 Illegal character 0x0 for 
HttpChannelOverHttp@1910d1bc{r=0,c=false,a=IDLE,uri=}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Illegal character 0x4 in state=START for buffer 
HeapByteBuffer@53c389d4[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>/m.sogou.com/?ran...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: badMessage: 400 Illegal character 0x4 for 
HttpChannelOverHttp@3e824b3e{r=0,c=false,a=IDLE,uri=}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Illegal character 0x4 in state=START for buffer 
HeapByteBuffer@64380bcf[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>
 
HTTP/1.1\r\nUser-A...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: badMessage: 400 Illegal character 0x4 for 
HttpChannelOverHttp@605ff7ac{r=0,c=false,a=IDLE,uri=}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Illegal character 0x5 in state=START for buffer 
HeapByteBuffer@53c389d4[p=1,l=3,c=16384,r=2]={\x05<<<\x01\x00>>>P\xC0c\xF660\x00/m.sogou.c...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: badMessage: 400 Illegal character 0x5 for 
HttpChannelOverHttp@59989f5a{r=0,c=false,a=IDLE,uri=}


Anyone can help or have ideas how to solve this? 

-- 
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/9aacc222-8133-4ca6-bb75-254ba142%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with pipeline

[Sharan Basappa]

Folks,

At this point, I am so confused.

My Jenkins file is kept at the root of Git directory. I am doing this in 
branches where I want to do Jenkins build.
I am using multibranch pipeline plug-in to define the build on Jenkins 
server.

As I am doing only mock set-up for now, the pipeline job is very simple and 
looks as follows. Can someone explain where I am going wrong?
The log below clearly reports that it is checking out test3 branch. So, I 
expect repository to be checked out correctly.

node {

stage 'build'

sh "pwd"

sh "ls ${workspace}@script"

sh "echo $PATH"

sh "cat  ${workspace}@script/simple.csh"

sh "csh  ${workspace}@script/simple.csh"

 

stage 'merge'

sh 'git stash'

sh 'git checkout master'

sh 'git merge test3'

sh 'git commit -am "Merged test3 branch to master"'

sh "git push origin master"

}

The script executes all the way till "git stash" and at this point, it 
reports error.
I have attached the entire log. 

Branch indexing
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to git@hd1:testing
> git config remote.origin.url git@hd1:testing # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/master
Seen branch in repository origin/test
Seen branch in repository origin/test1
Seen branch in repository origin/test2
Seen branch in repository origin/test3
Seen branch in repository origin/test4
Seen branch in repository origin/testx
Seen 7 remote branches
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git@hd1:testing # timeout=10
Fetching upstream changes from git@hd1:testing
> git --version # timeout=10
> git fetch --tags --progress git@hd1:testing 
+refs/heads/*:refs/remotes/origin/*
Checking out Revision f5eabd27c25242cc35d0b597537c3a3bcec8f54f (test3)
> git config core.sparsecheckout # timeout=10
> git checkout -f f5eabd27c25242cc35d0b597537c3a3bcec8f54f
> git rev-list 18552ecf03f27679cb0d88f28c096d5c7ec33d99 # timeout=10
[Pipeline] node Running on master in 
/var/lib/jenkins/workspace/an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A
[Pipeline] { [Pipeline] stage (build) Using the ‘stage’ step without a 
block argument is deprecated
Entering stage build
Proceeding
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ pwd
/var/lib/jenkins/workspace/an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ ls 
/var/lib/jenkins/workspace/an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A@script
avalon_asrts.sv
binding.sv
dir1
Jenkinsfile
Just_Checking
simple.csh
source.csh
tb_avalon_asrts.sv
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ echo /sbin:/usr/sbin:/bin:/usr/bin
/sbin:/usr/sbin:/bin:/usr/bin
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ cat 
/var/lib/jenkins/workspace/an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A@script/simple.csh
#!/bin/csh -f -e -x
echo "welcome to Jenkins from test2 branch"
\rm -f t
echo "junk" > t
exit 0
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ csh 
/var/lib/jenkins/workspace/an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A@script/simple.csh
welcome to Jenkins from test2 branch
[Pipeline] stage (merge) Using the ‘stage’ step without a block argument is 
deprecated
Entering stage merge
Proceeding
[Pipeline] sh 
[an_example_test3-26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] 
Running shell script
+ git stash
fatal: Not a git repository (or any of the parent directories): .git
[Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script 
returned exit code 128
*Finished* : FAILURE


On Tuesday, 7 February 2017 23:45:06 UTC+5:30, Sharan Basappa wrote:

> Hi All,
>
> I am having some trouble executing basic shell commands (highlighted in 
> red). I cant figure out the issue. Need some help. This is what I get:
>
> Branch indexing
>
> > git rev-parse --is-inside-work-tree # timeout=10
>
> Setting origin to git@hd1:testing
>
> > git config remote.origin.url git@hd1:testing # timeout=10
>
> Fetching origin...
>
> Fetching upstream changes from origin
>
> > git --version # timeout=10
>
> > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
>
> Seen branch in repository origin/master
>
> Seen branch in repository origin/test
>
> Seen branch in repository origin/test1
>
> Seen branch in repository origin/testx
>
> Seen 4 remote branches
>
> > git rev-parse 

freeipa + ldap plugin: "Invalid login information"

[Harri]

Problem with Jenkins 2.32.2 and FreeIPA (Centos 7.3):
I have configured Jenkin's LDAP plugin according to the documentation on 
the Wiki (https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin). 
Everything appears to be fine: anonymous ldap browsing is possible, user 
search base is given, etc. No warnings or errors in the System Log.

But if I try to login in Jenkins as a regular user (managed in Freeipa), 
then I get a message "Invalid login information" :-( On the command line 
the jenkins user can read the whole user and group base using ldapsearch, 
so I wonder wth?

Every helpful comment is highly appreciated
Harri

-- 
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/8bb4eb6a-5dff-4d0d-a9b4-395651281b6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with docker agent (declarative syntax)

[Christopher Orr]

Hi there,



On Thu, 9 Feb 2017, at 13:38, Bartłomiej Kruczyk wrote:

> agent {
> docker {
> image: 'myimage'

> registry: 'localhost:5000'



> }
> }
> 





A couple of points:



1. The syntax documentation is wrong at the moment: you should not add a
   colon after the key
2. The key you're looking for is "registryUrl"



Source: 
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/3222d5a/pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/AbstractDockerAgent.java#L33-L37


For example:

agent {

  docker {

image 'foo'

registryUrl 'registry.example.com'

  }

}



Regards,

Chris




-- 
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/1486726573.373537.876691200.05BF2406%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with docker agent (declarative syntax)

[Bartłomiej Kruczyk]

That worked like a charm. I had found issue 
https://issues.jenkins-ci.org/browse/JENKINS-39684, and source file you are 
referring but I didn't known what declarative syntax expression it should 
be.
Thank you!

W dniu piątek, 10 lutego 2017 13:02:33 UTC+1 użytkownik Christopher Orr 
napisał:
>
> Quick correction:
>
> On Fri, 10 Feb 2017, at 12:36, Christopher Orr wrote:
>
> Hi there,
>
> On Thu, 9 Feb 2017, at 13:38, Bartłomiej Kruczyk wrote:
>
> agent {
> docker {
> image: 'myimage'
>
> registry: 'localhost:5000'
>
> }
> } 
>
>
> A couple of points:
>
> 1. The syntax documentation is wrong at the moment: you should not add a 
> colon after the key
> 2. The key you're looking for is "registryUrl"
>
> Source: 
> https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/3222d5a/pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/AbstractDockerAgent.java#L33-L37
>
> For example:
> agent {
>   docker {
> image 'foo'
> registryUrl 'registry.example.com'
>   }
> }
>
>
> The 'registryUrl' value needs to be a proper URI, e.g. '
> https://registry.hub.docker.com'
>
> -Chris
>

-- 
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/0dfb81c8-8b07-4d4c-9d11-f02b925a7e6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with docker agent (declarative syntax)

[Bartłomiej Kruczyk]

Thanks for your reply, it's not yet documented but I found issue which 
asserted that this feature is implemented.
Christopher's solution works.

W dniu piątek, 10 lutego 2017 10:39:49 UTC+1 użytkownik R Tyler Croy 
napisał:
>
> (replies inline) 
>
> On Thu, 09 Feb 2017, Bart??omiej Kruczyk wrote: 
>
> > Hi, I have problem with setting docker agent type for my pipeline. 
> > 
> > Although something like this works: 
> > 
> > 
> > agent { 
> > docker 'myimage' 
> > 
> > } 
> > 
> > 
> > This does not: 
> > 
> > 
> > agent { 
> > docker { 
> > image: 'myimage' 
> > 
> > registry: 'localhost:5000' 
> > 
> > } 
> > } 
>
>
> As far as I am aware, there is no supported "registry" value inside that 
> `docker` block. 
>
>
> See also https://jenkins.io/doc/book/pipeline/syntax/#agent 
>
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

-- 
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/e4134c0a-fb70-453e-9a53-e47a7762d507%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Jira plugin 2.3

[vf]

More information:
Our Jira version: v6.3.1#6329-sha1:7df76f1
issues.jenkins-ci.org: v7.1.7#71011-sha1:2526d7c

Am Freitag, 10. Februar 2017 13:00:52 UTC+1 schrieb vf:
>
> Hi,
>
> I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working 
> (see stack trace below). 
> System:
>   Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
> Jira plugin configuration: (unchanged fo 3+ years)
>  url https://my.company.com/jira/
>  username + password
>  other fields are all default.
>
> I tested on a fresh installation: Jenkins 2.44, with only jira plugin 2.3 
> installed.
>
> I can reproduce the stacktrace by validating my configuration on the 
> configure screen.
>
> But, when I test https://issues.jenkins-ci,org/ with my account, it works 
> without any problem.
>
> So I am very much stuck here, Can anyone give me a hint?
>
> thanks
> vf
>
>
> WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
> RestClientException{statusCode=Optional.absent(), errorCollections=[]}
> at 
> com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
> at 
> hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
> at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
> at 
> hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at 
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
> at 
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
> at 
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
> at 
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
> at