[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Waldek M edited a comment on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
[~jinzoo] Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ? Also, you did specify "-u root" in run args, which is exactly what you got.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.5976.1583971981289%40Atlassian.JIRA.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Waldek M commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
john dow Have you given the example you wanted here? The Jenkinsfile you posted doesn't use dir () . Also, did you mean to use `sh "echo $PWD"` ?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168928.1457906095000.5899.1583971801425%40Atlassian.JIRA.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers Depends on your setup; it won't work if you're using LDAP or any other external authentication service. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185407.1506000559000.2059.1573894020339%40Atlassian.JIRA.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers Just for the record: Dockerfile workaround worked fine. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Waldek M commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
I took the liberty to link JENKINS-38331 - per-stage `agent` declarations are also affected.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Waldek M commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Nicolas De Loof sure, I hear what you're saying. There's a lot of features Jenkins users take for granted (which they wouldn't like to use) and general design of agents stand in the way too. I've had a couple of discussions with my colleagues on the subject of sharing files between a host and a container and the bottom line was: the alternatives may be inconvenient (or complicated, or come with performance trade-off), but using a simple volume mount just isn't clean and versatile enough and IMO the only clean way to transfer files back and forth is some sort of RPC (as Nicola Worthington has suggested in JENKINS-47026), be it directly via SSH/SFTP/what have you or e.g. https://github.com/vieux/docker-volume-sshfs..] otherwise the design is always going to make assumptions on the image or Docker host setup. Just my £0.02. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M edited a comment on JENKINS-47026
Re: User not completely set in docker containers
Thanks for sharing the workaround, [~aliusmiles]! Interestingly, passing such arguments to the prebuilt image with a `docker` closure did *not* work for me{{ }}{ { agent \{ code:java } } agent { { docker \ { }} {{ image 'foo' }} {{ args '--env USER_ID= }}{{ $(id -u) }} {{ --env GROUP_ID=$(id -g)' }} {{ } }} } { { code } }} The values passed were literally "{{$(id -u)}}" (not interpreted.I'll give it a go and see.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M commented on JENKINS-47026
Re: User not completely set in docker containers
Thanks for sharing the workaround, Taras Bondarchuk! Interestingly, passing such arguments to the prebuilt image with a `docker` closure did not work for me {{ agent {}} docker { image 'foo' args '--env USER_ID=$(id -u){{ --env GROUP_ID=$(id -g)'}} {{ }}} {{ }}} The values passed were literally "$(id -u)" (not interpreted. I'll give it a go and see.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Waldek M commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Hello, I'm wondering - would the new implementation be also solving problems like https://issues.jenkins-ci.org/browse/JENKINS-47026 ? I.e. would it also honor the isolation of Docker container from host (processes running within and outside of Docker container with different UID/GID)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers I took the liberty to link issue JENKINS-49416 which is also a consequence of how is spinning Docker containers with an arbitrary user / group / entry point script. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers Related to what the Original Poster mentioned about SSH problems in this setup, there are general problems with using plain Git commands within the container (as initiated by Jenkins). a) Over SSH: $ docker run -u 1223:1223 -it weakcamel/centos-python2-build:3 bash-4.2$ cd /tmp bash-4.2$ git clone g...@github.com:k-bx/python-semver.git Cloning into 'python-semver'... No user exists for uid 1223 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. b) over HTTPS as well: bash-4.2$ git clone https://github.com/k-bx/python-semver.git Cloning into 'python-semver'... remote: Counting objects: 534, done. remote: Total 534 (delta 0), reused 0 (delta 0), pack-reused 534 Receiving objects: 100% (534/534), 89.52 KiB | 0 bytes/s, done. Resolving deltas: 100% (285/285), done. fatal: unable to look up current user in the passwd file: no such user Unexpected end of command stream bash-4.2$ echo $? 128 bash-4.2$ ls -al python-semver ls: cannot access python-semver: No such file or directory Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-31944) Docker commandline passed wrong user id when executing.
Title: Message Title Waldek M commented on JENKINS-31944 Re: Docker commandline passed wrong user id when executing. Just for the record: a sample has been provided in https://issues.jenkins-ci.org/browse/JENKINS-47026 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M updated an issue Jenkins / JENKINS-47026 User not completely set in docker containers Change By: Waldek M Attachment: Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M edited a comment on JENKINS-47026
Re: User not completely set in docker containers
I've prepared an example of how using this fixed, non-root user breaks RPM builds, using: * a sample Docker image based on Centos ([https://hub.docker.com/r/weakcamel/centos-python2-build/)] * a (picked at almost random) simple PyPI package: [https://github.com/k-bx/python-semver.git] to use as source code baseI'll attach the content of Jenkinsfile and output log (slightly redacted) shortly; example failure: {{[docker-build-weeps] Running shell script}} {{+ . /tmp/venv/bin/activate}} {{[...]}} {{+ python setup.py bdist_rpm}} {{running bdist_rpm}} {{running egg_info}} {{writing semver.egg-info/PKG-INFO}} {{writing top-level names to semver.egg-info/top_level.txt}} {{writing dependency_links to semver.egg-info/dependency_links.txt}} {{reading manifest file 'semver.egg-info/SOURCES.txt'}} {{reading manifest template 'MANIFEST.in'}} {{writing manifest file 'semver.egg-info/SOURCES.txt'}} {{creating build/bdist.linux-x86_64}} {{creating build/bdist.linux-x86_64/rpm}} {{creating build/bdist.linux-x86_64/rpm/SOURCES}} {{creating build/bdist.linux-x86_64/rpm/SPECS}} {{creating build/bdist.linux-x86_64/rpm/BUILD}} {{creating build/bdist.linux-x86_64/rpm/RPMS}} {{creating build/bdist.linux-x86_64/rpm/SRPMS}} {{writing 'build/bdist.linux-x86_64/rpm/SPECS/semver.spec'}} {{running sdist}} {{running check}} {{creating semver-2.7.9}} {{creating semver-2.7.9/semver.egg-info}} {{making hard links in semver-2.7.9...}} {{hard linking MANIFEST.in -> semver-2.7.9}} {{hard linking README.rst -> semver-2.7.9}} {{hard linking semver.py -> semver-2.7.9}} {{hard linking setup.py -> semver-2.7.9}} {{hard linking semver.egg-info/PKG-INFO -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/SOURCES.txt -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/dependency_links.txt -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/top_level.txt -> semver-2.7.9/semver.egg-info}} {{Writing semver-2.7.9/setup.cfg}} {{creating dist}} {{Creating tar archive}} {{removing 'semver-2.7.9' (and everything under it)}} {{copying dist/semver-2.7.9.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES}} {{building RPMs}} {{rpmbuild -ba --define _topdir /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm --clean build/bdist.linux-x86_64/rpm/SPECS/semver.spec}} {{error: Bad owner/group: /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm/SOURCES/semver-2.7.9.tar.gz}} {{error: command 'rpmbuild' failed with exit status 1}} Pipeline to reproduce the behaviour is pretty simple: {{pipeline \{}}{{ agent \{}}{{ docker \{}}{{ image "weakcamel/centos-python2-build:3"}}{{ label 'cam1'}}{{ }}}{{ }}}{{ stages \{}}{{ stage('build and unit test') \{}}{{ steps \{}}{{ git changelog: false, poll: false, url: 'https://github.com/k-bx/python-semver.git'}}{{ script \{}}{{ sh('virtualenv /tmp/venv')}}{{ // sh('. /tmp/venv/bin/activate && pip install nosetests')}}{{ sh '. /tmp/venv/bin/activate && python setup.py build'}}{{ sh('. /tmp/venv/bin/activate && python setup.py bdist_rpm')}}{{ }}}{{ }}}{{ }}}{{ } //stages}}{{}}}
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M edited a comment on JENKINS-47026
Re: User not completely set in docker containers
I've prepared an example of how using this fixed, non-root user breaks RPM builds, using: * a sample Docker image based on Centos ([https://hub.docker.com/r/weakcamel/centos-python2-build/)] * a (picked at almost random) simple PyPI package: [https://github.com/k-bx/python-semver.git] to use as source code baseI'll attach the content of Jenkinsfile and output log (slightly redacted) shortly; example failure: {{[docker-build-weeps] Running shell script}} {{+ . /tmp/venv/bin/activate}} {{[...]}} {{+ python setup.py bdist_rpm}} {{running bdist_rpm}} {{running egg_info}} {{writing semver.egg-info/PKG-INFO}} {{writing top-level names to semver.egg-info/top_level.txt}} {{writing dependency_links to semver.egg-info/dependency_links.txt}} {{reading manifest file 'semver.egg-info/SOURCES.txt'}} {{reading manifest template 'MANIFEST.in'}} {{writing manifest file 'semver.egg-info/SOURCES.txt'}} {{creating build/bdist.linux-x86_64}} {{creating build/bdist.linux-x86_64/rpm}} {{creating build/bdist.linux-x86_64/rpm/SOURCES}} {{creating build/bdist.linux-x86_64/rpm/SPECS}} {{creating build/bdist.linux-x86_64/rpm/BUILD}} {{creating build/bdist.linux-x86_64/rpm/RPMS}} {{creating build/bdist.linux-x86_64/rpm/SRPMS}} {{writing 'build/bdist.linux-x86_64/rpm/SPECS/semver.spec'}} {{running sdist}} {{running check}} {{creating semver-2.7.9}} {{creating semver-2.7.9/semver.egg-info}} {{making hard links in semver-2.7.9...}} {{hard linking MANIFEST.in -> semver-2.7.9}} {{hard linking README.rst -> semver-2.7.9}} {{hard linking semver.py -> semver-2.7.9}} {{hard linking setup.py -> semver-2.7.9}} {{hard linking semver.egg-info/PKG-INFO -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/SOURCES.txt -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/dependency_links.txt -> semver-2.7.9/semver.egg-info}} {{hard linking semver.egg-info/top_level.txt -> semver-2.7.9/semver.egg-info}} {{Writing semver-2.7.9/setup.cfg}} {{creating dist}} {{Creating tar archive}} {{removing 'semver-2.7.9' (and everything under it)}} {{copying dist/semver-2.7.9.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES}} {{building RPMs}} {{rpmbuild -ba --define _topdir /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm --clean build/bdist.linux-x86_64/rpm/SPECS/semver.spec}} {{error: Bad owner/group: /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm/SOURCES/semver-2.7.9.tar.gz}} {{error: command 'rpmbuild' failed with exit status 1}} Pipeline to reproduce the behaviour is pretty simple: { { quote} pipeline \{ }} {{ agent \{ }} {{ docker \{ }} {{ image "weakcamel/centos-python2-build:3" }} {{ label 'cam1' }} {{ } }} {{ } }} {{ stages \{ }} {{ stage('build and unit test') \{ }} {{ steps \{ }} {{ git changelog: false, poll: false, url: 'https://github.com/k-bx/python-semver.git' }} {{ script \{ }} {{ sh('virtualenv /tmp/venv') }} {{ // sh ( '. /tmp/venv/bin/activate && pip install nosetests')}}{{ sh '. /tmp/venv/bin/activate && python setup.py build' }} {{ sh('. /tmp/venv/bin/activate && python setup.py bdist_rpm') }} {{ } }} {{ } }} {{ } }} {{ } //stages } } { { quote } }}
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M edited a comment on JENKINS-47026
Re: User not completely set in docker containers
I've prepared an example of how using this fixed, non-root user breaks RPM builds, using: * a sample Docker image based on Centos ([https://hub.docker.com/r/weakcamel/centos-python2-build/)] * a (picked at almost random) simple PyPI package: [https://github.com/k-bx/python-semver.git] to use as source code baseI'll attach the content of Jenkinsfile and output log (slightly redacted) shortly; example failure: {{[docker-build-weeps] Running shell script}}{{+ . /tmp/venv/bin/activate}}{{[...]}}{{+ python setup.py bdist_rpm}}{{running bdist_rpm}}{{running egg_info}}{{writing semver.egg-info/PKG-INFO}}{{writing top-level names to semver.egg-info/top_level.txt}}{{writing dependency_links to semver.egg-info/dependency_links.txt}}{{reading manifest file 'semver.egg-info/SOURCES.txt'}}{{reading manifest template 'MANIFEST.in'}}{{writing manifest file 'semver.egg-info/SOURCES.txt'}}{{creating build/bdist.linux-x86_64}}{{creating build/bdist.linux-x86_64/rpm}}{{creating build/bdist.linux-x86_64/rpm/SOURCES}}{{creating build/bdist.linux-x86_64/rpm/SPECS}}{{creating build/bdist.linux-x86_64/rpm/BUILD}}{{creating build/bdist.linux-x86_64/rpm/RPMS}}{{creating build/bdist.linux-x86_64/rpm/SRPMS}}{{writing 'build/bdist.linux-x86_64/rpm/SPECS/semver.spec'}}{{running sdist}}{{running check}}{{creating semver-2.7.9}}{{creating semver-2.7.9/semver.egg-info}}{{making hard links in semver-2.7.9...}}{{hard linking MANIFEST.in -> semver-2.7.9}}{{hard linking README.rst -> semver-2.7.9}}{{hard linking semver.py -> semver-2.7.9}}{{hard linking setup.py -> semver-2.7.9}}{{hard linking semver.egg-info/PKG-INFO -> semver-2.7.9/semver.egg-info}}{{hard linking semver.egg-info/SOURCES.txt -> semver-2.7.9/semver.egg-info}}{{hard linking semver.egg-info/dependency_links.txt -> semver-2.7.9/semver.egg-info}}{{hard linking semver.egg-info/top_level.txt -> semver-2.7.9/semver.egg-info}}{{Writing semver-2.7.9/setup.cfg}}{{creating dist}}{{Creating tar archive}}{{removing 'semver-2.7.9' (and everything under it)}}{{copying dist/semver-2.7.9.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES}}{{building RPMs}}{{rpmbuild -ba --define _topdir /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm --clean build/bdist.linux-x86_64/rpm/SPECS/semver.spec}}{{error: Bad owner/group: /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm/SOURCES/semver-2.7.9.tar.gz}}{{error: command 'rpmbuild' failed with exit status 1}} Pipeline to reproduce the behaviour is pretty simple: {{pipeline \{}}{{ agent \{}}{{ docker \{}}{{ image "weakcamel/centos-python2-build:3"}}{{ label 'cam1'}}{{ }}}{{ }}}{{ stages \{}}{{ stage('build and unit test') \{}}{{ steps \{}}{{ git changelog: false, poll: false, url: 'https://github.com/k-bx/python-semver.git'}}{{ script \{}}{{ sh('virtualenv /tmp/venv')}}{{ // sh('. /tmp/venv/bin/activate && pip install nosetests')}}{{ sh '. /tmp/venv/bin/activate && python setup.py build'}}{{ sh('. /tmp/venv/bin/activate && python setup.py bdist_rpm')}}{{ }}}{{ }}}{{ }}}{{ } //stages}}{{}}}
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Waldek M edited a comment on JENKINS-47026
Re: User not completely set in docker containers
Note also that in case you try and use Python's `pip` command, there's a warning as well related to not fully set up user: {{ }} {{ + pip install virtualenv }} {{ The directory '/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. }} {{ The directory '/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. }} {{ Requirement already satisfied: virtualenv in /usr/lib/python2.7/site-packages }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers Note also that in case you try and use Python's `pip` command, there's a warning as well related to not fully set up user: + pip install virtualenv The directory '/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. The directory '/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. Requirement already satisfied: virtualenv in /usr/lib/python2.7/site-packages Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M updated an issue Jenkins / JENKINS-47026 User not completely set in docker containers Change By: Waldek M Attachment: build_log.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers I've prepared an example of how using this fixed, non-root user breaks RPM builds, using: a sample Docker image based on Centos (https://hub.docker.com/r/weakcamel/centos-python2-build/) a (picked at almost random) simple PyPI package: https://github.com/k-bx/python-semver.git to use as source code base I'll attach the content of Jenkinsfile and output log (slightly redacted) shortly; example failure: [docker-build-weeps] Running shell script + . /tmp/venv/bin/activate [...] + python setup.py bdist_rpm running bdist_rpm running egg_info writing semver.egg-info/PKG-INFO writing top-level names to semver.egg-info/top_level.txt writing dependency_links to semver.egg-info/dependency_links.txt reading manifest file 'semver.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'semver.egg-info/SOURCES.txt' creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/rpm creating build/bdist.linux-x86_64/rpm/SOURCES creating build/bdist.linux-x86_64/rpm/SPECS creating build/bdist.linux-x86_64/rpm/BUILD creating build/bdist.linux-x86_64/rpm/RPMS creating build/bdist.linux-x86_64/rpm/SRPMS writing 'build/bdist.linux-x86_64/rpm/SPECS/semver.spec' running sdist running check creating semver-2.7.9 creating semver-2.7.9/semver.egg-info making hard links in semver-2.7.9... hard linking MANIFEST.in -> semver-2.7.9 hard linking README.rst -> semver-2.7.9 hard linking semver.py -> semver-2.7.9 hard linking setup.py -> semver-2.7.9 hard linking semver.egg-info/PKG-INFO -> semver-2.7.9/semver.egg-info hard linking semver.egg-info/SOURCES.txt -> semver-2.7.9/semver.egg-info hard linking semver.egg-info/dependency_links.txt -> semver-2.7.9/semver.egg-info hard linking semver.egg-info/top_level.txt -> semver-2.7.9/semver.egg-info Writing semver-2.7.9/setup.cfg creating dist Creating tar archive removing 'semver-2.7.9' (and everything under it) copying dist/semver-2.7.9.tar.gz -> build/bdist.linux-x86_64/rpm/SOURCES building RPMs rpmbuild -ba --define _topdir /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm --clean build/bdist.linux-x86_64/rpm/SPECS/semver.spec error: Bad owner/group: /var/spool/jenkins/workspace/docker-build-weeps/build/bdist.linux-x86_64/rpm/SOURCES/semver-2.7.9.tar.gz error: command 'rpmbuild' failed with exit status 1 Add Comment
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title
Waldek M edited a comment on JENKINS-28155
Re: Job fails with [An existing connection was forcibly closed by the remote host]
*UPDATE*:Itturnedoutmyissuewasrelatedtotherecentswitchtohttps(soprobablynotrelatedtothisone).AfterprovidingJavatrustStorewithRootCAandIntermediateCA-issueresolved. Samehere-althoughreasonmightbedifferent.SlavestartedonWIndows7,onanADaccount,asaservice.Dropsalmostimmediately.{noformat}java.io.IOException:Connectionaborted:org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave] atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:java.io.IOException:Connectionresetbypeer atsun.nio.ch.FileDispatcherImpl.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) atsun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) atsun.nio.ch.IOUtil.read(IOUtil.java:197) atsun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) atorg.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) atorg.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ...6more{noformat}Foundsomemoreinslave'slog.MymasterinstanceisusinghttpsandalthoughthecertificateisinstalledinWindowsandbrowsersrecognizeit,slavecomplainsaboutit-asbelow.Anyideaswouldbewelcome.{noformat}Exceptioninthreadmainjava.io.IOException:Failedtovalidateaservercertificate.Ifyouareusingaself-signedcertificate,youcanusethe-noCertificateCheckoptiontobypassthischeck. athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327) athudson.remoting.Launcher.run(Launcher.java:219) athudson.remoting.Launcher.main(Launcher.java:192)Causedby:javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.ssl.Alerts.getSSLException(UnknownSource) atsun.security.ssl.SSLSocketImpl.fatal(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.ClientHandshaker.serverCertificate(UnknownSource) atsun.security.ssl.ClientHandshaker.processMessage(UnknownSource) atsun.security.ssl.Handshaker.processLoop(UnknownSource) atsun.security.ssl.Handshaker.process_record(UnknownSource) atsun.security.ssl.SSLSocketImpl.readRecord(UnknownSource) atsun.security.ssl.SSLSocketImpl.performInitialHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.net.www.protocol.https.HttpsClient.afterConnect(UnknownSource) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(UnknownSource) atsun.net.www.protocol.https.HttpsURLConnectionImpl.connect(UnknownSource) athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269) ...2moreCausedby:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.validator.PKIXValidator.doBuild(UnknownSource) atsun.security.validator.PKIXValidator.engineValidate(UnknownSource) atsun.security.validator.Validator.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.validate(UnknownSource)
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title
Waldek M edited a comment on JENKINS-28155
Re: Job fails with [An existing connection was forcibly closed by the remote host]
Samehere -althoughreasonmightbedifferent .SlavestartedonWIndows7,onanADaccount,asaservice. Dropsalmostimmediately. {noformat}java.io.IOException:Connectionaborted:org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave] atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:java.io.IOException:Connectionresetbypeer atsun.nio.ch.FileDispatcherImpl.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) atsun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) atsun.nio.ch.IOUtil.read(IOUtil.java:197) atsun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) atorg.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) atorg.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ...6more{noformat}Foundsomemoreinslave'slog.MymasterinstanceisusinghttpsandalthoughthecertificateisinstalledinWindowsandbrowsersrecognizeit,slavecomplainsaboutit-asbelow.Anyideaswouldbewelcome.{noformat}Exceptioninthreadmainjava.io.IOException:Failedtovalidateaservercertificate.Ifyouareusingaself-signedcertificate,youcanusethe-noCertificateCheckoptiontobypassthischeck. athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327) athudson.remoting.Launcher.run(Launcher.java:219) athudson.remoting.Launcher.main(Launcher.java:192)Causedby:javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.ssl.Alerts.getSSLException(UnknownSource) atsun.security.ssl.SSLSocketImpl.fatal(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.ClientHandshaker.serverCertificate(UnknownSource) atsun.security.ssl.ClientHandshaker.processMessage(UnknownSource) atsun.security.ssl.Handshaker.processLoop(UnknownSource) atsun.security.ssl.Handshaker.process_record(UnknownSource) atsun.security.ssl.SSLSocketImpl.readRecord(UnknownSource) atsun.security.ssl.SSLSocketImpl.performInitialHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.net.www.protocol.https.HttpsClient.afterConnect(UnknownSource) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(UnknownSource) atsun.net.www.protocol.https.HttpsURLConnectionImpl.connect(UnknownSource) athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269) ...2moreCausedby:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.validator.PKIXValidator.doBuild(UnknownSource) atsun.security.validator.PKIXValidator.engineValidate(UnknownSource) atsun.security.validator.Validator.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.checkTrusted(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.checkServerTrusted(UnknownSource)
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Waldek M commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] Same here. Slave started on WIndows 7, on an AD account, as a service. java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 6 more Found some more in slave's log. My master instance is using https and although the certificate is installed in Windows and browsers recognize it, slave complains about it - as below. Any ideas would be welcome. Exception in thread main java.io.IOException: Failed to validate a server certificate. If you are using a self-signed certificate, you can use the -noCertificateCheck option to bypass this check. at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327) at hudson.remoting.Launcher.run(Launcher.java:219) at hudson.remoting.Launcher.main(Launcher.java:192) Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker.process_record(Unknown Source) at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source) at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269) ... 2 more Caused by:
[JIRA] [role-strategy-plugin] (JENKINS-29333) role-based security: edit existing role
Title: Message Title Waldek M commented on JENKINS-29333 Re: role-based security: edit existing role Ouch! The field doesn't look editable is my only defence. Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-29333) role-based security: edit existing role
Title: Message Title Waldek M closed an issue as Not A Defect Not an issue. Jenkins / JENKINS-29333 role-based security: edit existing role Change By: Waldek M Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-29333) role-based security: edit existing role
Title: Message Title Waldek M created an issue Jenkins / JENKINS-29333 role-based security: edit existing role Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 10/Jul/15 8:13 AM Priority: Minor Reporter: Waldek M It would be extremely helpful to be able to edit existing pattern in a role. Currently the only way to update it is to remove the role entirely and add it back. And lately I observe that removing the role removes also the assignments - so for a large group of people it's necessary to re-assign them again, which is quite error prone. Add Comment
[JIRA] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Waldek M commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Thanks, Oleg! I appreciate it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Waldek M commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Ah, I see. Thanks, and too bad. I do hope it would, soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Waldek M commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Hello, I'm afraid I was able to reproduce this issue again on core 1.601 and 1.90 of EnvInject. Or more precisely, I reproduced duplicated https://issues.jenkins-ci.org/browse/JENKINS-22577 As a user with job configuration permissions I've un-checked the "Prepare environment" option, and while saving, I was greeted with the following stacktrace. javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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.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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
[JIRA] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Waldek M reopened JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Re-occurence on 1.601 core, EnvInject 1.90 Change By: Waldek M (05/Mar/15 1:31 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 You may want to upgrade core version. I was on 1.586 and upgrade finally solved it for me, as advised by Daniel Beck above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M resolved JENKINS-9703 as Fixed Find changes on a branch not working correctly with CC multisite The behavior is known and the Multi-site poll buffer configuration can be used to adjust polling. Added a small documentation improvement (under the buffer option) to clarify. Change By: Waldek M (19/Dec/14 5:31 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25657) JUnit crashes during recording of test results in 1.580.1
Waldek M commented on JENKINS-25657 JUnit crashes during recording of test results in 1.580.1 Or maybe https://issues.jenkins-ci.org/browse/JENKINS-24946 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M commented on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M edited a comment on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. Update: As advised by colleague, using "Multisite poll buffer" from Advanced options. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M edited a comment on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. Update: As advised by colleague, using "Multisite poll buffer" option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 I see. Yes, probably version of core might be the issue. I did upgrade to the latest core, however that one contains another critical bug (related to losing slave restrictions in a job), so I had to revert. I missed the upgrade to 1.2, so can't confirm. I can see a similar https://issues.jenkins-ci.org/browse/JENKINS-25657 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M commented on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Submitted documentation patch. https://github.com/jenkinsci/clearcase-plugin/pull/32 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M assigned JENKINS-9703 to Waldek M Find changes on a branch not working correctly with CC multisite Change By: Waldek M (18/Dec/14 11:01 AM) Assignee: VincentLatombe WaldekM This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M started work on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Change By: Waldek M (18/Dec/14 11:01 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M updated JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Updated severity - actually, Junit plugin 1.3 is a complete blocker of the whole Jenkins instance. Change By: Waldek M (17/Dec/14 2:45 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Similar issue with 1.3 Junit plugin, Jenkins 1.586. Reverting to Junit 1.1 solved it. Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M edited a comment on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Similar issue with 1.3 Junit plugin, Jenkins 1.586. Reverting to Junit 1.1 solved it. Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser] (JENKINS-7490) console-parser should get the parsing rules directly from a textbox in the project config
Waldek M commented on JENKINS-7490 console-parser should get the parsing rules directly from a textbox in the project config Seems like Sudulai gave up. Wish I knew how to work with the plugins enough to help out here... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser] (JENKINS-7490) console-parser should get the parsing rules directly from a textbox in the project config
Waldek M edited a comment on JENKINS-7490 console-parser should get the parsing rules directly from a textbox in the project config Seems like Sudulai gave up . Wish I knew how to work with the plugins enough to help out here... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [klocwork] (JENKINS-21866) Klocwork plugin does not show new issues
Waldek M created JENKINS-21866 Klocwork plugin does not show new issues Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: kw_plugin.png Components: klocwork Created: 19/Feb/14 8:35 AM Description: On 1.15 plugin, new issues are not listed (with KW 10.0.1). Graph is generated correctly. Environment: Klocwork 10.0.1 RHEL 5.5 Project: Jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Waldek M commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Yes, it still is. And recently, when accessing e.g. job site, users aren't even redirected to login page - they just get an error message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21100) Parametrize config spec configuration
Waldek M commented on JENKINS-21100 Parametrize config spec configuration I concur. Currently it's possible to get the build parameters and generate a config spec, and then set it on the view as a build preparation step. But this way, most of the plugin's benefits are gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21538) Update the plugin website - screenshots and documentation
Waldek M created JENKINS-21538 Update the plugin website - screenshots and documentation Issue Type: Improvement Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 28/Jan/14 9:10 PM Description: The screenshot on https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin is a bit outdated and especially the Advanced configuration is different under 1.4 plugin. Since the website (and the inline help) is the only source of plugin documentation, it would be really great to have it up to date. Project: Jenkins Priority: Minor Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
Waldek M commented on JENKINS-18929 OutOfMemoryError: PermGen space Same here. Since a few recent versions, I'm also getting PermGen very often (like every few days). I'll see how it works with MaxPermSize. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-2293) ssh slave doesn't detect correctly java installation
Waldek M commented on JENKINS-2293 ssh slave doesnt detect correctly java installation I've raised the ticket: https://issues.jenkins-ci.org/browse/JENKINS-18767 If some more details are needed, please let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-18767) Checking java version fails - SSH slave not connecting
Waldek M created JENKINS-18767 Checking java version fails - SSH slave not connecting Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 16/Jul/13 11:35 AM Description: I've seen the issue as resolved (at least twice), but it still occurs for me. Despite having Java binary on slave and master, the SSH Slave plugin fails to find Java version. Error log: 07/16/13 10:48:00 SSH Opening SSH connection to ...:22. 07/16/13 10:48:00 SSH Authentication successful. 07/16/13 10:48:00 SSH The remote users environment is: 07/16/13 10:48:00 SSH Checking java version of java Couldn't figure out the Java version of java 07/16/13 10:48:00 SSH Checking java version of /usr/bin/java Couldn't figure out the Java version of /usr/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/java/default/bin/java Couldn't figure out the Java version of /usr/java/default/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/java/latest/bin/java Couldn't figure out the Java version of /usr/java/latest/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/local/bin/java Couldn't figure out the Java version of /usr/local/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/local/java/bin/java Couldn't figure out the Java version of /usr/local/java/bin/java 07/16/13 10:48:00 SSH Checking java version of /bin/java Couldn't figure out the Java version of /bin/java hudson.util.IOException2: Could not find any known supported java version in java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /bin/java, and we also failed to install JDK as a fallback at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:557) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:493) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Failed to detect the environment for automatic JDK installation. Please report this to jenkinsci-us...@googlegroups.com: at hudson.plugins.sshslaves.SSHLauncher.attemptToInstallJDK(SSHLauncher.java:654) at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:555) ... 7 more 07/16/13 10:48:00 SSH Connection closed. Environment: Linux (RHEL master + Ubuntu slave) Project: Jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Waldek M commented on JENKINS-16234 Plugin does not currently work for Clearcase Base I'm looking forward to the resolution, too Currently using the -vws workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes I've finally found some time to verify the fix. Well - it works Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for Clearcase SCM changes
Waldek M created JENKINS-15718 Failed to record SCM polling (again) while polling for Clearcase SCM changes Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Nov/12 11:18 AM Description: I saw similar issues, but with a bit different stack trace. Captured on Jenkins 1.489 and ClearCase plugin 1.3.11, however CC doesn't appear in the stack trace. ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@103f0bc0XYZ_R5.0_Integration java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(Unknown Source) at hudson.Launcher.inherit(Launcher.java:1068) at hudson.Launcher.access$100(Launcher.java:80) at hudson.Launcher$LocalLauncher.launch(Launcher.java:756) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Project: Jenkins Labels: jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Waldek M commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Same here, Jenkins on Linux and different browsers on Win7. Is there a chance to have it fixed? Thanks if advance for your response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12794) Occasional crash of plugin
Waldek M commented on JENKINS-12794 Occasional crash of plugin Thanks, Kohsuke, for your comment. I'll hope for clearcase plugin, then This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes Is there a chance for a fix for this one? This would be great, because without it, users of dynamic views (and some users of snapshots) are stuck with 1.3.8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema OK, so let me rephrase it; perhaps I wasn't too clear, indeed. Is there a way that I could gather some more detailed logs from the Klocwork plugin? Waldek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12794) Occasional crash of plugin
Waldek M commented on JENKINS-12794 Occasional crash of plugin Still failing, I'm afraid. Is there something I could do to have it fixed? ERROR: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:236) at hudson.FilePath.resolvePathIfRelative(FilePath.java:221) at hudson.FilePath.init(FilePath.java:217) at hudson.FilePath.child(FilePath.java:1053) at hudson.plugins.clearcase.AbstractClearCaseScm.getModuleRoot(AbstractClearCaseScm.java:345) at hudson.scm.SCM.getModuleRoots(SCM.java:543) at hudson.model.AbstractBuild.getModuleRoots(AbstractBuild.java:290) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:314) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12794) Occasional crash of plugin
Waldek M updated JENKINS-12794 Occasional crash of plugin Change By: Waldek M (28/Sep/12 8:55 AM) Environment: RHEL.Jenkins1.451andthelatestversionsofplugins-clearcaseandcobertura Alsopresentonlatest1.482 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema I'll give it a try. Thank you! BTW, could you please write what logger should I subscribe to to gather some more kw plugin debug information in future? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema Hello, It doesn't seem to work fine with 1.12 I'm using KW 9.5.3, and that's what I got in build log: == Starting the klocwork analysis. Version 9.6 or later of Klocwork detected. Only Klocwork review is available. Parse_errors.log and build.log can be accessed on the review ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:186) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) xUnit INFO - Starting to record. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema Well, I'd like a release for sure I'm using plugin 1.10 with KW 9.5.3 and the following stack trace appears (see below). Is it perhaps this issue? ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:101) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) xUnit INFO - Starting to record. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes Hi, Vincent I do understand that this is open source, and I do appreciate your work. Perhaps because the plugin has been so useful and robust, I got to expect it always to be perfect I'll try to be only constructive in the future. And, thanks! Waldek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes Hello, Well, perhaps the "plenty" was an overstatement. Sorry, I was a bit emotional, because those 2 existing issues have blocked a team of ~20 persons for a day. I'm simply concerned: if just after upgrade I've discovered 2 issues that have broken long-existing functionality, I'm not really eager to take the risk again and upgrade. As for the automatic time rules: their description is in Advanced section of plugin configuration: Use time rule in config spec If checked, Hudson will use a time rule in the dynamic view's config spec, locking the view contents in as of the beginning of the build, even if files are changed on the branch during the build. When using CC dynamic view, it's actually an essential option. Otherwise, content of the build may change during its compilation - which is very likely for team with a CI branch, the more probable, the bigger the team is. I must though say that I like the new feature that allows setting config spec from file (I guess that was also part of the pull request?). I'm just very cautious and a bit afraid that perhaps there are some other changes that might not have been tested well enough: on snapshot and dynamic views, in standalone and master-slave, with Linux/Unix. Waldek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M edited a comment on JENKINS-15202 Permanent building / consider removing latest changes Hello, Well, perhaps the "plenty" was an overstatement. Sorry, I was a bit emotional, because those 2 existing issues have blocked a team of ~20 persons for a day. I'm simply concerned: if just after upgrade I've discovered 2 issues that have broken long-existing functionality, I'm not really eager to take the risk again and upgrade. As for the automatic time rules: their description is in Advanced section of plugin configuration: Use time rule in config spec If checked, Hudson will use a time rule in the dynamic view's config spec, locking the view contents in as of the beginning of the build, even if files are changed on the branch during the build. When using CC dynamic view, it's actually an essential option. Otherwise, content of the build may change during its compilation - which is very likely for team with a CI branch, the more probable, the bigger the team is. It's mostly about adding a time rule at when updating the view's CS, eg: time 17-sep-12.11:53:51utc+ [... config spec set by user - the original from Jenkins UI ] end time Please note also that the original CS may contain time rules, too. I must though say that I like the new feature that allows setting config spec from file (I guess that was also part of the pull request?). I'm just very cautious and a bit afraid that perhaps there are some other changes that might not have been tested well enough: on snapshot and dynamic views, in standalone and master-slave, with Linux/Unix. Waldek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15196) Plugin uses cleartool.cmd instead of cleartool.exe for Windows slave
Waldek M created JENKINS-15196 Plugin uses cleartool.cmd instead of cleartool.exe for Windows slave Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 17/Sep/12 12:51 PM Description: Actually, issue captured on 1.3.9. After upgrade, it seems that plugin assumes cleartool binary to be "cleartool.cmd" instead of cleartool.exe. In at least clearcase 7.0.1.12, it results crashes of the plugin (see stacktrace below), even when trying to poll for changes. What's also interesting is that the build continues to be triggered all the time, so with eg. 1 minute "quiet period", every 1 minut there is a failed build. Building remotely on BarSlave in workspace D:\JenkinsData\workspace\FOO_RELEASE_Integration FOO_RELEASE_Integration $ "C:\Program Files\Rational\ClearCase\\bin\cleartool.cmd" lsview FOO_jenkins_integration_release INFO computeChangeLogBeforeCheckout = false INFO computeChangeLogAfterCheckout = false FOO_RELEASE_Integration $ "C:\Program Files\Rational\ClearCase\\bin\cleartool.cmd" startview FOO_jenkins_integration_release java.io.IOException: Cannot run program "C:\Program Files\Rational\ClearCase\\bin\cleartool.cmd" (in directory "D:\JenkinsData\workspace\FOO_RELEASE_Integration"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:934) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more xUnit INFO - Starting to record. xUnit INFO - Processing NUnit-Version N/A (default) Environment: Windows slave Clearcase client 7.0.1.12 Project: Jenkins Priority: Blocker Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M created JENKINS-15202 Permanent building / consider removing latest changes Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 17/Sep/12 2:46 PM Description: There seems to be a feature that re-builds a job whenever the config spec has changed. It's very troublesome; it's not always desired. User may want to prepare a config spec that he/she wants to be run later, not just instantly. Moreover, there's a bug in this functionality: when using automated time rules, current set CS is constantly different that the one configured. So the result is rebuilding constantly . After those 2 latest issues, I strongly recommend to remove the latest pull request at all https://github.com/jenkinsci/clearcase-plugin/pull/11 since it creates plenty of blocking issues. With these many breaking changes, I'm afraid that my project and I would need to stay with the 1.3.8 indefinitely. === This page captures the polling log that triggered this build. Started on Sep 17, 2012 2:39:01 PM get view CSPEC *** workspace $ cleartool catcs -tag my_view time 17-sep-12.11:53:51utc+ Removed ... config spec rules element * /main/LATEST end time ** WARNING CSPEC configured != catcs (view) REASON: New config spec detected. Done. Took 58 ms Changes found Environment: Jenkins 1.480 Plugin 1.3.9 Project: Jenkins Priority: Critical Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M updated JENKINS-15202 Permanent building / consider removing latest changes Change By: Waldek M (17/Sep/12 2:50 PM) Description: Thereseemstobea new feature (since1.3.9) thatre-buildsajobwhenevertheconfigspechaschanged.Itsverytroublesome;itsnotalwaysdesired.Usermaywanttoprepareaconfigspecthathe/shewantstoberunlater,notjustinstantly.Moreover,theresabuginthisfunctionality:whenusingautomatedtimerules,currentsetCSisconstantlydifferentthattheoneconfigured.Sotheresultisrebuildingconstantly(!).Afterthose2latestissues,Istronglyrecommendtoremovethelatestpullrequestatallhttps://github.com/jenkinsci/clearcase-plugin/pull/11sinceitcreatesplentyofblockingissues.Withthesemanybreakingchanges,ImafraidthatmyprojectandIwouldneedtostaywiththe1.3.8indefinitely.===Thispagecapturesthepollinglogthattriggeredthisbuild.StartedonSep17,20122:39:01PM***getviewCSPEC***[workspace]$cleartoolcatcs-tagmy_viewtime17-sep-12.11:53:51utc+#Removed[...]configspecruleselement*/main/LATESTendtime**[WARNING]CSPECconfigured!=catcs(view)REASON:Newconfigspecdetected.Done.Took58msChangesfound This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ
Waldek M commented on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ Same here. And it's a serious security issue; some plugins show much more information than they should (eg. Cobertura presents the source code under this "General read"), so the Anonymous access may be dangerous. But revoking this access is preventing from using master-slave architecture of Jenkins at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ
Waldek M edited a comment on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ It seems that after some latest changes to permissions of Jenkins, giving just Read access prevents from seeing anything useful. If this is so, enabling the "General Read" permissions for Anonymous should be fine. Can anyone confirm that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13743) Jenkins 1.463 + Klocwork plugin - crashes when saving configuration
Waldek M created JENKINS-13743:
--
Summary: Jenkins 1.463 + Klocwork plugin - crashes when saving
configuration
Key: JENKINS-13743
URL: https://issues.jenkins-ci.org/browse/JENKINS-13743
Project: Jenkins
Issue Type: Bug
Components: klocwork
Affects Versions: current
Environment: RHEL 5.5, master node on Linux
Reporter: Waldek M
Assignee: Gregory Boissinot
Priority: Blocker
Attachments: jenkins_fail.txt
After upgrade of Jenkins to 1.463, I'm having crashes each time I try to edit
configuration of jobs.
This didn't stop when downgraded Klocwork plugin from 1.7 to 1.2.
Issue disappeared when downgraded Jenkins from 1.463 to 1.462
Attaching the full stacktrace as file.
===
Stacktrace:
java.lang.IllegalArgumentException: Failed to instantiate class
com.thalesgroup.hudson.plugins.klocwork.config.KloConfig from
{buildXSize:0,buildYSize:0,displayAllError:false,displayHighSeverity:false,displayLowSeverity:false,displayMedSeverity:false,existing:false,failureThreshold:,fixed:false,healthy:,highSeverity:false,interval:1,kind:com.thalesgroup.hudson.plugins.klocwork.KloPublisher,klocworkReportPattern:,linkBuildLog:false,linkParseLog:false,linkReview:true,lowSeverity:false,newFailureThreshold:,newThreshold:,neww:false,publishBuildGraph:false,publishProjectGraph:false,stapler-class:com.thalesgroup.hudson.plugins.klocwork.KloPublisher,threshold:,trendNum:0,trendXSize:0,trendYSize:0,unHealthy:}
at
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
at
com.thalesgroup.hudson.plugins.klocwork.KloPublisher$KloDescriptor.newInstance(KloPublisher.java:253)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13633) Linux master + Windows slave: problem with polling when global configuration for Clearcase is set
Waldek M created JENKINS-13633: -- Summary: Linux master + Windows slave: problem with polling when global configuration for Clearcase is set Key: JENKINS-13633 URL: https://issues.jenkins-ci.org/browse/JENKINS-13633 Project: Jenkins Issue Type: Bug Components: clearcase Environment: master: RHEL 5.5 slave: MS Windows XP SP3 Reporter: Waldek M Assignee: Vincent Latombe Priority: Minor My configuration was: - general settings: Clearcase path set to /usr/atria - Windows node slave settings: Clearcase path set to C:\Program Files\Rational\Clearcase The log from clearcase polling showed that even on Windows slave, the cleartool with path from global settings was used, and showed nothing. Started on Apr 27, 2012 4:58:22 PM [my_view] $ /usr/atria/bin/cleartool pwv -root [MyJob] $ /usr/atria/bin/cleartool lsview my_view Done. Took 15 ms No changes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue
[ https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160947#comment-160947 ] Waldek M commented on JENKINS-12994: Same here. In case of many scheduled builds, this may cause them never to happen. Quiet period is blocking other jobs in queue Key: JENKINS-12994 URL: https://issues.jenkins-ci.org/browse/JENKINS-12994 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Platform: All, OS: All Reporter: teetoivo Starting from version 1.452, a job in queue waiting for the quiet period to pass is blocking all other jobs that have been queued after it. Example: # Job A has quiet period set to 10 seconds # Job B has quiet period set to 300 seconds # Job C has quiet period set to 100 seconds # Jobs get queued in A-B-C order. # Job A starts executing after 10 seconds # After 100 seconds, status of job C changes to pending - Waiting for next available executor even if free executors are available # After 300 seconds both jobs B and C start executing This problem is hardly visible when short quiet periods are used but becomes problematic with longer quiet periods or plugins like Naginator that will increase the quiet period to hours if the builds fail enough. Version 1.451 is the last release where this problem isn't visible. From public releases, at least 1.452 and 1.454 are affected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12794) Occasional crash of plugin
Waldek M created JENKINS-12794: -- Summary: Occasional crash of plugin Key: JENKINS-12794 URL: https://issues.jenkins-ci.org/browse/JENKINS-12794 Project: Jenkins Issue Type: Bug Components: clearcase, cobertura Affects Versions: current Environment: RHEL. Jenkins 1.451 and the latest versions of plugins - clearcase and cobertura Reporter: Waldek M Assignee: Vincent Latombe Priority: Minor Occasionally, the cobertura plugin crashes with the trace as follows. I'm afraid I'm not able to tell whether this is really releated to the cobertura, or clearcase plugins, because both appear on the trace. Publishing Cobertura coverage report... ERROR: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:226) at hudson.FilePath.init(FilePath.java:214) at hudson.FilePath.child(FilePath.java:926) at hudson.plugins.clearcase.AbstractClearCaseScm.getModuleRoot(AbstractClearCaseScm.java:345) at hudson.scm.SCM.getModuleRoots(SCM.java:543) at hudson.model.AbstractBuild.getModuleRoots(AbstractBuild.java:287) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:216) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:675) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:653) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:622) at hudson.model.Run.run(Run.java:1434) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
