[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov edited a comment on JENKINS-49225 Re: Graph not generated on scheduled performance jobs Hello, Which plugin do use for Schedule Build? Also could you recheck that you haven't any errors messages in [http://your_host/log/all] If you refresh your page with report it doesn't display graphs again? Thanks,Artem 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-49455) Scroll up during input step causes Proceed not to respond in Blue Ocean
Title: Message Title
Pierre Lord created an issue
Jenkins / JENKINS-49455
Scroll up during input step causes Proceed not to respond in Blue Ocean
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
inputstep1.PNG, inputstep2.PNG
Components:
blueocean-plugin
Created:
2018-02-08 12:06
Environment:
Jenkins 2.89.3 BlueOcean 1.4.0 JDK 8u121 RHEL 5.11 Chrome 63.0.3239.84
Priority:
Major
Reporter:
Pierre Lord
In Blue Ocean, if the user scrolls up (or presses the up arrow key) during an input step, then clicks Proceed, the input forms remains and the lower half of the UI does not update. The pipeline graph updates, and the execution continues in the background. The user has to manually refresh the page to view the log of the next stage. This can be reproduced on any input step, however in practice this affects users when input forms contain choice parameters and/or enough parameters to require scrolling on the page. The _javascript_ code is catching these events, seemingly to stop auto-scrolling when displaying console output, so perhaps an exception needs to be made for input steps. Example pipeline used in the screenshots:
stage("Select version") {
input message: "Select from the list", parameters: [choice(name: "version", choices: "0.1\n0.2\n0.3\n0.4\n0.5\n0.6\n0.7", description: "Version")]
}
stage("Deploy") {
println "Deploying..."
sleep(10)
}
[JIRA] (JENKINS-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza commented on JENKINS-49263 Re: Determine minimal useful test case for running ATH for Jenkins Core Gathering data with my latest changes 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 Nicola Worthington commented on JENKINS-47026 Re: User not completely set in docker containers Manually modifying `/etc/passwd` like this feel quite wrong to me. I understand that this is intended to be a lightweight fix that doesn't rely on extraneous system maintenance packages, but who is to day that any given Docker container is even configured to perform a lookup using `/etc/passwd`? I think the root problem here is that Jenkins relies upon a shared volume model as the transport mechanism to get source into the contain, and the build artefacts back out. While this is arguably reasonable for the input vector (permissions of the files being injected can be left fairly open), we clearly see the problems when trying to get files back out. Would a better approach be to decouple container workspace filesystem from the host, and implement an RPC mechanism to deliver the build artefacts back to Jenkins. I believe GitLab CI does something similar with its job caching and artefact management, so running tasks inside the Docker container as root is not a problem. 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 Nicola Worthington edited a comment on JENKINS-47026 Re: User not completely set in docker containers Manually modifying ` /etc/passwd ` like this feel feels quite wrong to me. I understand that this is intended to be a lightweight fix that doesn't rely on extraneous system maintenance packages, but who is to day that any given Docker container is even configured to perform a lookup using ` /etc/passwd ` ?I think the root problem here is that Jenkins relies upon a shared volume model as the transport mechanism to get source into the contain, and the build artefacts back out. While this is arguably reasonable for the input vector (permissions of the files being injected can be left fairly open), we clearly see the problems when trying to get files back out.Would a better approach be to decouple container workspace filesystem from the host, and implement an RPC mechanism to deliver the build artefacts back to Jenkins.I believe GitLab CI does something similar with its job caching and artefact management, so running tasks inside the Docker container as root is not a problem. 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 Nicola Worthington edited a comment on JENKINS-47026 Re: User not completely set in docker containers Manually modifying /etc/passwd like this feels quite wrong to me. I understand that this is intended to be a lightweight fix that doesn't rely on extraneous system maintenance packages, but who is to day say that any given Docker container is even configured to perform a lookup using /etc/passwd?I think the root problem here is that Jenkins relies upon a shared volume model as the transport mechanism to get source into the contain container , and the build artefacts back out. While this is arguably reasonable for the input vector (permissions of the files being injected can be left fairly open), we clearly see the problems when trying to get files back out.Would a better approach be to decouple container workspace filesystem from the host, and implement an RPC mechanism to deliver the build artefacts back to Jenkins.I believe GitLab CI does something similar with its job caching and artefact management, so running tasks inside the Docker container as root is not a problem. 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-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Vincent Robert assigned an issue to Vincent Robert Jenkins / JENKINS-43106 pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) Change By: Vincent Robert Assignee: Vincent Robert 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-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title
Rein Achten edited a comment on JENKINS-47617
Re: CHANGE_BRANCH no longer reporting branch name, but instead PR
I've just pinpointed this to v2.2.4 of the bitbucket-branch-source-plugin. In v2.2.3, {{CHANGE_BRANCH}} is still set according to expectation. Looking through the diffs, it seems to be caused by the changes on context of [the following pull request|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63] (for JENKINS-45775). [~stephenconnolly] I'm not familiar with the plugin and don't completely understand the [rationale|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63/files#r129575824] behind using {{branchName}} instead of {{pull.getSource().getBranch().getName()}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/761fa289a13ff5750f7fdb8be0c980e688143197/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java#L65], but I reckon this is causing the problem. Can you shed your light on this?
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-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title
Rein Achten edited a comment on JENKINS-47617
Re: CHANGE_BRANCH no longer reporting branch name, but instead PR
I've just pinpointed this to v2.2.4 of the bitbucket-branch-source-plugin. In v2.2.3, {{CHANGE_BRANCH}} is still set according to expectation. Looking through the diffs, it seems to be caused by the changes on context of [the following pull request|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63] (for JENKINS-45775).[~stephenconnolly] I'm not familiar with the plugin and don't completely understand the [rationale|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63/files#r129575824] behind using {{branchName}} instead of {{pull.getSource().getBranch().getName()}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/761fa289a13ff5750f7fdb8be0c980e688143197/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java# L65 L657 ], but I reckon this is causing the problem. Can you shed your light on this?
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] (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 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 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 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 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-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Mark Waite commented on JENKINS-43106 Re: pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) Vincent Robert I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of possibly "blacklisting" Jira plugin 2.5.1. Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release. 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner edited a comment on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with [~abayer] about the problem right after you created the bug and he wanted to look into it but seems that he also has been forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case||https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java[]|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner edited a comment on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with [~abayer] about the problem right after you created the bug and he wanted to look into it but seems that this he also has been forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case||https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java[]|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner commented on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with Andrew Bayer about the problem right after you created the bug and he wanted to look into it but seems that this also has been forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case||https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java[]|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner edited a comment on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with [~abayer] about the problem right after you created the bug and he wanted to look into it but seems that he also has forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case| | https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java[]|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner edited a comment on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with [~abayer] about the problem right after you created the bug and he wanted to look into it but seems that he also has forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case|https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java [ ] |https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) 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-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner edited a comment on JENKINS-45774 Re: Cannot find files from reports generated in parallel Actually, I did not look into this issue since you reported it, sorry. I chatted with [~abayer] about the problem right after you created the bug and he wanted to look into it but seems that he also has forgotten it... A simple solution would be to make the parser more intelligent: the regular _expression_ should ignore that part of the message. (You need to write a small [test case|https://github.com/jenkinsci/warnings-plugin/blob/master/src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java] with your log file and adapt the [parser|https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java] accordingly.) Currently I'm converting all parsers to the [new API|https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/Pep8Parser.java], but that branch is not yet ready for a release. So maybe it makes sense to wait a little bit longer until this part is done. 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-30382) TFS plug-in 4.0.0 NumberFormatExceptions
Title: Message Title Stefan Drissen reopened an issue On Jenkins 2.104 / Team Foundation Server Plug-in 5.125.0 - this is rearing it's ugly head again: Started by upstream project "/build work" build number 271 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on (oe11.5.1.036 odbc-sql2014 oe11.6.3.005 odbc-sql2012) in workspace d:\jenkins\workspace\\work\build_bp-11.6 FATAL: java.lang.NumberFormatException: For input string: ".20182018E4.20182018E4" Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.103/10.2.33.103:54670 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:909) at hudson.plugins.tfs.model.Server.execute(Server.java:233) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) java.lang.NumberFormatException: For input string: ".20182018E4.20182018E4" at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source) at sun.misc.FloatingDecimal.parseDouble(Unknown Source) at java.lang.Double.parseDouble(Unknown Source) at java.text.DigitList.getDouble(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:285) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:365) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.(DateVersionSpec.java:51) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:197) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:60) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Unknown Source) Caused: java.lang.RuntimeException
[JIRA] (JENKINS-30382) TFS plug-in 4.0.0 NumberFormatExceptions
Title: Message Title
Stefan Drissen edited a comment on JENKINS-30382
Re: TFS plug-in 4.0.0 NumberFormatExceptions
On Jenkins 2.104 / Team Foundation Server Plug-in 5. 125 126 .0 - this is rearing it's ugly head again:{code:java}Started by upstream project "/build work" build number 271originally caused by:Started by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM changeStarted by an SCM change[EnvInject] - Loading node environment variables.Building remotely on (oe11.5.1.036 odbc-sql2014 oe11.6.3.005 odbc-sql2012) in workspace d:\jenkins\workspace\\work\build_bp-11.6FATAL: java.lang.NumberFormatException: For input string: ".20182018E4.20182018E4"Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.103/10.2.33.103:54670at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:909)at hudson.plugins.tfs.model.Server.execute(Server.java:233)at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1203)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at hudson.model.Run.execute(Run.java:1727)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.NumberFormatException: For input string: ".20182018E4.20182018E4"at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)at sun.misc.FloatingDecimal.parseDouble(Unknown Source)at java.lang.Double.parseDouble(Unknown Source)at java.text.DigitList.getDouble(Unknown Source)at java.text.DecimalFormat.parse(Unknown Source)at java.text.SimpleDateFormat.subParse(Unknown Source)at java.text.SimpleDateFormat.parse(Unknown Source)at java.text.DateFormat.parse(Unknown Source)at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:285)at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:365)at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.(DateVersionSpec.java:51)at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:197)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:60)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)at hudson.remoting.UserRequest.perform(UserRequest.java:210)at hudson.remoting.UserRequest.perform(UserRequest.java:53)at hudson.remoting.Request$2.run(Request.java:358)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)at java.util.concurrent.FutureTask.run(Unknow
[JIRA] (JENKINS-43573) Build form value different than parameter passed to the build
Title: Message Title Ioannis Moutsatsos commented on JENKINS-43573 Re: Build form value different than parameter passed to the build This issue is surfacing again in some of my complex builds. Kindly asking Bruno P. Kinoshita to review possible fixes. Currently the workaround is to pass this parameter to another Active Choices Reactive Reference (as in the example shown) and use that value in the build. Already complex job configuration become even more so (and features are build on bugs ) 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-49405) Create jenkins/evergreen Docker package
Title: Message Title R. Tyler Croy commented on JENKINS-49405 Re: Create jenkins/evergreen Docker package Submitted a draft design document as JEP-301 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-49456) Jenkins plugin update dashboard not updating correctly
Title: Message Title Alex Lombardi created an issue Jenkins / JENKINS-49456 Jenkins plugin update dashboard not updating correctly Issue Type: Bug Assignee: Unassigned Attachments: Plugin Update Dashboard.JPG Components: core Created: 2018-02-08 14:08 Environment: Jenkins 2.105 running on Windows 2K8 server as a service using Master-Agent setup. Labels: jenkins plugin configuration Priority: Minor Reporter: Alex Lombardi When I go to the plugin manager none of my plugins show up as requiring updates when I know all of them need updates from the "Installed" view. Available and Installed components dashboard renders fine, and I can test the connection successfully on the advanced setup page.
[JIRA] (JENKINS-49405) Create jenkins/evergreen Docker package
Title: Message Title R. Tyler Croy stopped work on JENKINS-49405 Change By: R. Tyler Croy Status: In Progress Open 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-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Mark Waite edited a comment on JENKINS-43106 Re: pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) [~vrobert78] I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of possibly "blacklisting" Jira plugin 2.5.1 and that has been implemented about a week ago in the Jenkins update center .Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release. 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-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Mark Waite edited a comment on JENKINS-43106 Re: pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) [~vrobert78] I don't think it is enough to disable the Jira plugin. I believe that you need to downgrade the Jira plugin from 2.5.1 to 2.5.0 or earlier. There was a discussion of "blacklisting" Jira plugin 2.5.1 and that has been implemented about a week ago in the [ Jenkins update center |https://github . com/jenkins-infra/backend-update-center2/commit/47580ef481d5c103bfcd5c9943d604029a151ebe]. Refer to JENKINS-48357 for the details of the types of damage done to critical libraries by the 2.5.1 release. 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-49438) I can't use selectedValue and useRepository for git parameter job-dsl-plugin
Title: Message Title Sreeni Gadila updated an issue Jenkins / JENKINS-49438 I can't use selectedValue and useRepository for git parameter job-dsl-plugin Change By: Sreeni Gadila Comment: I am not seeing these two methods here in https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/GitParamContext.groovy file. This could be an issue? 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-49438) I can't use selectedValue and useRepository for git parameter job-dsl-plugin
Title: Message Title Sreeni Gadila updated an issue Jenkins / JENKINS-49438 I can't use selectedValue and useRepository for git parameter job-dsl-plugin Change By: Sreeni Gadila Comment: Hi Daniel, Please review my last two comments, I have double checked and it is not working. 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-49438) I can't use selectedValue and useRepository for git parameter job-dsl-plugin
Title: Message Title Sreeni Gadila updated an issue Jenkins / JENKINS-49438 I can't use selectedValue and useRepository for git parameter job-dsl-plugin Change By: Sreeni Gadila Comment: Hello - This is not resolved, I can't use this in DSL and it is giving me the error No signature of method: javaposse.jobdsl.dsl.helpers.GitParamContext.useRepository() is applicable for argument types: (java.lang.String)for both below lines of groovy script.selectedValue() useRepository()Please advise If I am not using right method. 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-49438) I can't use selectedValue and useRepository for git parameter job-dsl-plugin
Title: Message Title Sreeni Gadila resolved as Fixed Use of gitParameterDefinition method resolved my issue. Jenkins / JENKINS-49438 I can't use selectedValue and useRepository for git parameter job-dsl-plugin Change By: Sreeni Gadila Status: Reopened Resolved Resolution: Fixed 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, vis
[JIRA] (JENKINS-41432) Perforce plugin doesn't always show changes in pipeline jobs
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.1 Jenkins / JENKINS-41432 Perforce plugin doesn't always show changes in pipeline jobs Change By: Paul Allen Status: Open Closed Resolution: Fixed 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-49457) Git Parameter does not work as input in a scripted pipeline
Title: Message Title Magnus Jungsbluth created an issue Jenkins / JENKINS-49457 Git Parameter does not work as input in a scripted pipeline Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2018-02-08 14:31 Environment: Jenkins ver. 2.89.1 Git Parameter Plugin 0.90 Priority: Major Reporter: Magnus Jungsbluth I tried to use the git parameter plugin in a pipeline script to fill an input (Target Branch to merge to in another repository). According to https://jenkins.io/doc/pipeline/steps/pipeline-input-step/ GitParameters should work for inputs, input( id: 'Proceed1', message: 'Specifiy QA Candiate Branch', parameters: [ [$class: 'GitParameterDefinition', name: 'candidateBranch', type: 'PT_BRANCH', ] ] ) This gets rendered but whatever I do the branch select stays empty (When refreshing I can see a brief spinner with "Retrieving..."). I also tried to capture related logs but couldn't get anything (From looking at the code only exceptional cases are logged). I also tried as documented in https://jenkins.io/doc/pipeline/steps/pipeline-input-step/ type: 'Branch' Just to validate that it works in general I added
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-47026 User not completely set in docker containers Change By: Nicolas De Loof Component/s: declarative-pipeline-when-conditions-plugin Component/s: docker 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 Nicolas De Loof updated an issue Jenkins / JENKINS-47026 User not completely set in docker containers Change By: Nicolas De Loof Component/s: docker-workflow-plugin Component/s: declarative-pipeline-when-conditions-plugin 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-49458) Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository
Title: Message Title Francisco Díaz Bayón created an issue Jenkins / JENKINS-49458 Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository Issue Type: Task Assignee: Francisco Díaz Bayón Components: elastest-plugin Created: 2018-02-08 14:37 Priority: Major Reporter: Francisco Díaz Bayón Hi, We need to add the user "elastestci" as a new member of the Jenkins organization and also as a new committer for the repository https://github.com/jenkinsci/elastest-plugin . The user elastestci is registered in Jira. This user will be the one who makes the releases of the plugin. Thank you! Regards. Add Comment
[JIRA] (JENKINS-49435) Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository
Title: Message Title Francisco Díaz Bayón closed an issue as Duplicate Jenkins / JENKINS-49435 Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository Change By: Francisco Díaz Bayón Status: Open Closed Resolution: Duplicate 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-49458) Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository
Title: Message Title Francisco Díaz Bayón assigned an issue to Unassigned Jenkins / JENKINS-49458 Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository Change By: Francisco Díaz Bayón Assignee: Francisco Díaz Bayón 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-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-49434) Multibranch pipeline doesn't trigger on Git submodule changes
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49434 Multibranch pipeline doesn't trigger on Git submodule changes Change By: Mark Waite Assignee: Mark Waite 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-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...'
Title: Message Title javydreamercsw commented on JENKINS-49413 Re: IllegalArgumentException : Cannot relativize '...' relatively to ...' I know it is downloading some external artifacts there. I guess the main issue is that running in Jenkins pipeline with the command it's just ignored. It works fine on my local tests. mvn test -Djava.io.tmpdir=/mypath/ 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-48727) Jenkins HP Plugin Unable to Connect to SaaS ALM Server
Title: Message Title Josh Privett commented on JENKINS-48727 Re: Jenkins HP Plugin Unable to Connect to SaaS ALM Server I can confirm thanks to Marlene that reverting to 5.2 solved the problem for us as well, we were running 5.3. It would be nice to not have to worry about the version though! 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-49459) New parametrization feature of PC Plugin affects the configuration of the job
Title: Message Title Daniel Danan created an issue Jenkins / JENKINS-49459 New parametrization feature of PC Plugin affects the configuration of the job Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-02-08 15:21 Environment: hp-application-automation-tools-plugin, version 5.3.2-beta-SNAPSHOT Labels: PerformanceCenter Priority: Critical Reporter: Daniel Danan Running parametrized job with Performance Center plugin works fine for the first time however it modifies the values in the configuration of the job (the parameters are actually replaced by the values in the configuration). Running once again the same job, will actually cause the job to use the injected values in the configuration and stop considering the parameters. Add Comment
[JIRA] (JENKINS-49459) New parametrization feature of PC Plugin affects the configuration of the job
Title: Message Title Daniel Danan assigned an issue to Daniel Danan Jenkins / JENKINS-49459 New parametrization feature of PC Plugin affects the configuration of the job Change By: Daniel Danan Assignee: Ofir Shaked Daniel Danan 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-49459) New parametrization feature of PC Plugin affects the configuration of the job
Title: Message Title Daniel Danan commented on JENKINS-49459 Re: New parametrization feature of PC Plugin affects the configuration of the job issue detected during self QA. 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-37974) WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException
Title: Message Title Adrian Wyssmann commented on JENKINS-37974 Re: WARNING: Caught exception evaluating: c.displayExecutors in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException Same issue here in Jenkins 2.89.3, running on Windows Feb 08, 2018 4:14:25 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.transientActions in /jenkins/job/PLAYGROUND-Pipeline/89/input/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor770.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(Cor
[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-49458) Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository
Title: Message Title Francisco Díaz Bayón closed an issue as Duplicate Jenkins / JENKINS-49458 Invite a new user to the jenkinsci organization and also as a new committer to the elastest-plugin repository Change By: Francisco Díaz Bayón Status: Open Closed Resolution: Duplicate 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-29235) p4jenksin not pickup latest changes
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Cleaning up old issue - closing Jenkins / JENKINS-29235 p4jenksin not pickup latest changes Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov commented on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally able to reproduce this in an isolated Jenkins installation running the following versions:
Jenkins 2.98
Docker Plugin 1.1.2
Here are the steps to reproduce:
Create a Cloud configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method.
Create a Pipeline job with the following code (adjust for image labels if needed):
def flavors = ['centos6','centos7','sles11','sles12','ubuntu']
def steps = [:]
flavors.each{def flavor ->
steps[flavor] = {
stage(flavor) {
timeout(1) {
echo "Allocating ${flavor}"
node("${flavor}&&dockerswarm") {
sh "date"
}
}
}
}
}
timestamps {
parallel steps
}
Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out.
Restart Jenkins.
Job will succeed again for a little while.
Add Comment
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-48490 Intermittently slow docker provisioning with no errors Change By: Alexander Komarov Attachment: .jenkins-log-provisioning-success.log.swp 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-48490 Intermittently slow docker provisioning with no errors Change By: Alexander Komarov Attachment: jenkins-log-provisioning-success.log Attachment: jenkins-log-provisioning-fail.log 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-48490 Intermittently slow docker provisioning with no errors Change By: Alexander Komarov Attachment: .jenkins-log-provisioning-success.log.swp Attachment: .jenkins-log-provisioning-fail.log.swp 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-48490 Intermittently slow docker provisioning with no errors Change By: Alexander Komarov Attachment: .jenkins-log-provisioning-fail.log.swp 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally *able to reproduce this* in an isolated Jenkins installation running the following versions: * Jenkins 2.98 * Docker Plugin 1.1.2h2. Here are the steps to reproduce: * Create a *Cloud* configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method. * Create a Pipeline job with the following code (adjust for image labels if needed): {code:java}def flavors = ['centos6','centos7','sles11','sles12','ubuntu']def steps = [:]flavors.each{def flavor -> steps[flavor] = {stage(flavor) { timeout(1) { echo "Allocating ${flavor}" node("${flavor}&&dockerswarm") { sh "date" } }} }}timestamps { parallel steps}{code} * Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out. * Restart Jenkins. * Job will succeed again for a little while. h2. Logs are attached:When provisioning hangs: [^jenkins-log-provisioning-fail.log]When provisioning succeeds: [^jenkins-log-provisioning-success.log]
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...@googlegroup
[JIRA] (JENKINS-26455) Removing .p4config file during force clean
Title: Message Title Paul Allen closed an issue as Won't Fix On the whole users should not use the Jenkins Workspaces. Open to ideas, but no plans to fix this issue. Jenkins / JENKINS-26455 Removing .p4config file during force clean Change By: Paul Allen Status: Open Closed Assignee: Paul Allen Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- Y
[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build
Title: Message Title Paul Allen closed an issue as Won't Fix Closing old issues - happy to take a PR, but no plan to fix this issue. Jenkins / JENKINS-36572 Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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 email
[JIRA] (JENKINS-37626) Clone pipeline job with "Poll SCM" use old polling settings
Title: Message Title Paul Allen closed an issue as Won't Fix Closing old issues - no plan to fix this, but happy to look at a PR if someone else wants to take this on. Jenkins / JENKINS-37626 Clone pipeline job with "Poll SCM" use old polling settings Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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...@go
[JIRA] (JENKINS-49434) Multibranch pipeline doesn't trigger on Git submodule changes
Title: Message Title Mark Waite commented on JENKINS-49434 Re: Multibranch pipeline doesn't trigger on Git submodule changes Can you provide more detail of what you mean when you say: one of the submodules changes For example, do you mean one (or more) of these scenarios: a single branch pipeline detects a case where a commit is submitted to a submodule repository without any commit being submitted to the parent repository. That would be unexpected (at least for me), since a submodule commit is not used unless a commit is made to the parent module to point it to the new commit in the submodule a single branch pipeline detects a case where a commit is submitted to a submodule repository and a commit is submitted to the parent repository. That should be detected as a new commit in the parent repository and should be detected by the single branch pipeline when it polls or is notified by a web hook and should be detected by the multi-branch pipeline when it scans the repository or is notified by a web hook 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 fr
[JIRA] (JENKINS-38886) Polling broken on Matrix configuration
Title: Message Title Paul Allen closed an issue as Won't Fix No plans to fix this. Jenkins has many limitations with environment variable especially around polling; custom Matrix variables only compounds this problem. Jenkins / JENKINS-38886 Polling broken on Matrix configuration Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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 je
[JIRA] (JENKINS-34062) Error with ResMerger in xcodebuild
Title: Message Title Paul Allen closed an issue as Won't Fix Closing old issues - no plan to fix, but happy to review a PR if someone wants to take this on. Jenkins / JENKINS-34062 Error with ResMerger in xcodebuild Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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, vi
[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Ken Rachynski commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS I did have a chance to speak with one of the updaters on IRC and he acknowledged this issue but is currently working on security tasks. The workaround for now is to downgrade. 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-49460) Connection error via PTC integrity plugin
Title: Message Title Saad Azam created an issue Jenkins / JENKINS-49460 Connection error via PTC integrity plugin Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 2018-02-08 16:29 Priority: Major Reporter: Saad Azam I am currently unable to successfully test mks connection using latest PTC integrity plugin version 2.1, with Jenkins 2.89.2. I get the following error message: java.lang.AbstractMethodError at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1368) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330) at com.mks.connect.UserApplicationSessionImpl.handleHTTPResponse(UserApplicationSessionImpl.java:309) at com.mks.connect.UserApplicationSessionImpl.getSession(UserApplicationSessionImpl.java:355) at com.mks.connect.UserApplicationSessionImpl.getSessionURI(UserApplicationSessionImpl.java:418) at com.mks.connect.HttpCmdRunnerImpl.getSessionURI(HttpCmdRunnerImpl.java:72) at com.mks.connect.HttpBlimpInputStream.getSessionURI(HttpBlimpInputStream.java:125) at com.mks.connect.HttpBlimpInputStream.blimpInitiate(HttpBlimpInputStream.java:152) at com.mks.connect.BlimpInputStream.getInputStream(BlimpInputStream.java:223) at com.mks.connect.BlimpInputStream.readNoEof(BlimpInputStream.java:704) at com.mks.connect.BlimpInputStream.handleNextBlimpCommand(BlimpInputStream.java:266) at com.mks.connect.BlimpInputStream.read(BlimpInputStream.java:190) at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) at sun.nio.cs.StreamDecoder.implRead(Unknown Source) at sun.nio.cs.StreamDecoder.read(Unknown So
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally *able to reproduce this* in an isolated Jenkins installation running the following versions: * Jenkins 2.98 * Docker Plugin 1.1.2h2. Here are the steps to reproduce: * Create a *Cloud* configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method. * Create a Pipeline job with the following code (adjust for image labels if needed): {code:java}def flavors = ['centos6','centos7','sles11','sles12','ubuntu']def steps = [:]flavors.each{def flavor -> steps[flavor] = {stage(flavor) { timeout(1) { echo "Allocating ${flavor}" node("${flavor}&&dockerswarm") { sh "date" } }} }}timestamps { parallel steps}{code} * Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out. * Restart Jenkins. * Job will succeed again for a little while.h2. Logs Jenkins logs are attached: When Job run when provisioning hangs: [^jenkins-log-provisioning-fail.log] When Job run when provisioning succeeds: [^jenkins-log-provisioning-success.log]
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
[JIRA] (JENKINS-49434) Multibranch pipeline doesn't trigger on Git submodule changes
Title: Message Title Chris Reffett commented on JENKINS-49434 Re: Multibranch pipeline doesn't trigger on Git submodule changes Sure, I'm referring to the former. In the single-branch pipeline, Jenkins was set to update the submodules to their tip, and that registered as an SCM change and triggered a build. In the multibranch pipeline, the same behavior is set, but the Scan Multibranch Pipe Log shows that Jenkins is only checking the top-level repo's commit ID for changes. Background on our configuration: My organization has several components in their own repos and then combines them as sub-modules of a "master" repository to build (with the master repository having a few other things, like a pom.xml and Jenkins config). Since we don't care about the submodules pointing to a specific commit on our develop branch, our .gitmodules config points to the develop branch and has ignore=all set. 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally *able to reproduce this* in an isolated Jenkins installation running the following versions: * Jenkins 2.98 * Docker Plugin 1.1.2h2. Here are the steps to reproduce: * Create a *Cloud* configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method. Ensure that there is enough capacity (instance limits, etc) so that this is not a bottleneck. * Create a Pipeline job with the following code (adjust for image labels if needed): {code:java}def flavors = ['centos6','centos7','sles11','sles12','ubuntu']def steps = [:]flavors.each{def flavor -> steps[flavor] = {stage(flavor) { timeout(1) { echo "Allocating ${flavor}" node("${flavor}&&dockerswarm") { sh "date" } }} }}timestamps { parallel steps}{code} * Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out. * Restart Jenkins. * Job will succeed again for a little while.h2. Jenkins logs are attached:Job run when provisioning hangs: [^jenkins-log-provisioning-fail.log]Job run when provisioning succeeds: [^jenkins-log-provisioning-success.log]
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 unsu
[JIRA] (JENKINS-30683) Perforce checkout occasionally fails with Unexpected termination of channel stack trace
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Closing old issues - unable to reproduce. Jenkins / JENKINS-30683 Perforce checkout occasionally fails with Unexpected termination of channel stack trace Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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 mor
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally *able to reproduce this* in an isolated Jenkins installation running the following versions: * Jenkins 2.98 * Docker Plugin 1.1.2h2. Here are the steps to reproduce: * Create a *Cloud* configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method. Ensure that there is enough capacity (instance limits, etc) so that this is not a bottleneck. * Create a Pipeline job with the following code (adjust for image labels if needed): {code:java}def flavors = ['centos6','centos7','sles11','sles12','ubuntu']def steps = [:]flavors.each{def flavor -> steps[flavor] = {stage(flavor) { timeout(1) { echo "Allocating ${flavor}" node("${flavor}&&dockerswarm") { sh "date" } }} }}timestamps { parallel steps}{code} * Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out. * Restart Jenkins. * Job will succeed again for a little while.h2. Jenkins logs are attached:Job run when provisioning hangs: [^jenkins-log-provisioning-fail.log]Job run when provisioning succeeds: [^jenkins-log-provisioning-success.log] *Note* that while Jenkins is blocked trying to allocate a node, I can manually allocate one using docker command-line, proving that the actual docker infrastructure is not the problem.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49461) Publish test results
Title: Message Title
Idan Bidani created an issue
Jenkins / JENKINS-49461
Publish test results
Issue Type:
Bug
Assignee:
Dhara Ghodasara
Components:
qmetry-for-jira-test-management-plugin
Created:
2018-02-08 16:37
Environment:
Jenkins 2.89.3 running on Windows 2012
Labels:
plugin
Priority:
Major
Reporter:
Idan Bidani
I'm really glad to see that you're working on Jenkins plugin, it is essential part of our testing framework. It seems like the "File URL"(probably should be named Test Results Location, it's not a URL) field doesn't accept relative paths. When running a build on an jenkins linux agent hwile the master Jenkins runs on windows, the plugin can't find results file see stack trace below.
INFO: Retrying request to {s}->https://issues.somewhere.com:443
java.io.FileNotFoundException: \opt\jenkins\jenkins-stg-slave\workspace\POC\SCM-JIRATest\target\surefire-reports\TEST-somepackage.xml (The system cannot find the path specified)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.apache.http.entity.mime.content.FileBody.writeTo(FileBody.java:116)
at org.apache.http.entity.mime.AbstractMultipartForm.doWriteTo(AbstractMultipartForm.java:134)
at org.apache.http.entity.mime.AbstractMultipartForm.writeTo(AbstractMultipartForm.java:157)
at org.apache.http.entity.mime.Mul
[JIRA] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Title: Message Title Paul Allen closed an issue as Won't Fix Closing old issues - No plans to fix this and there may now be alternatives with Pipeline. Jenkins / JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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.
[JIRA] (JENKINS-45897) Remoting Request classes should offer better toString(), which allow identifying them
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45897 Re: Remoting Request classes should offer better toString(), which allow identifying them Code changed in jenkins User: Oleg Nenashev Path: CHANGELOG.md http://jenkins-ci.org/commit/remoting/8a22d34106efd615279b138aac019330172d6b20 Log: Merge pull request #253 from oleg-nenashev/changelog/3.17_2 Changelog: Noting JENKINS-45897 in the 3.17 release + 3.18 heads-up Compare: https://github.com/jenkinsci/remoting/compare/1d5b0e5fee4c...8a22d34106ef 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-45897) Remoting Request classes should offer better toString(), which allow identifying them
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45897 Re: Remoting Request classes should offer better toString(), which allow identifying them Code changed in jenkins User: Oleg Nenashev Path: CHANGELOG.md http://jenkins-ci.org/commit/remoting/ea15ffdb1dad4de557f95ef599ac5c7062bf1d40 Log: Changelog: Noting JENKINS-45897 in the 3.17 release + 3.18 heads-up 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-36395) P4 Plugin not syncing when running job.
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Closing old issues - unable to reproduce. Jenkins / JENKINS-36395 P4 Plugin not syncing when running job. Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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/opt
[JIRA] (JENKINS-36243) ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds
Title: Message Title Paul Allen closed an issue as Postponed Closing old issues - issue may be fixed or not required. Jenkins / JENKINS-36243 ArrayIndexOutOfBoundsException with matrix and multiple simultaneous builds Change By: Paul Allen Status: In Progress Closed Resolution: Postponed 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 o
[JIRA] (JENKINS-34972) P4 plugin poll request cannot be done
Title: Message Title Paul Allen closed an issue as Won't Fix Unable to expand custom environment variables during polling. Jenkins / JENKINS-34972 P4 plugin poll request cannot be done Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48490
Re: Intermittently slow docker provisioning with no errors
I was finally *able to reproduce this* in an isolated Jenkins installation running the following versions: * Jenkins 2.98 * Docker Plugin 1.1.2h2. Here are the steps to reproduce: * Create a *Cloud* configuration with several docker image template definitions. Mine are custom built images, but the random nature of this issue suggests that this should happen with any images. Note: I am using JNLP but the problem also occurs with "Attached" method. Ensure that there is enough capacity (instance limits, etc) so that this is not a bottleneck. * Create a Pipeline job with the following code (adjust for image labels if needed): {code:java}def flavors = ['centos6','centos7','sles11','sles12','ubuntu']def steps = [:]flavors.each{def flavor -> steps[flavor] = {stage(flavor) { timeout(1) { echo "Allocating ${flavor}" node("${flavor}&&dockerswarm") { sh "date" } }} }}timestamps { parallel steps}{code} * Run this job a few times. Job will succeed at first, but after a few successful runs one or more of the image flavors will start to time out. * Restart Jenkins. * Job will succeed again for a little while. (UPDATE: restart does not always help, issue sometimes begins immediately after) h2. Jenkins logs are attached:Job run when provisioning hangs: [^jenkins-log-provisioning-fail.log]Job run when provisioning succeeds: [^jenkins-log-provisioning-success.log] *Note* that while Jenkins is blocked trying to allocate a node, I can manually allocate one using docker command-line, proving that the actual docker infrastructure is not the problem.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Closing old issues - presumed fixed in 1.8.x Jenkins / JENKINS-34924 p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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.
[JIRA] (JENKINS-39824) Plugin does not work with read-only perforce replica
Title: Message Title Paul Allen closed an issue as Won't Fix I am unable to fix this issue due to the behaviour of a read-only replica server. Jenkins / JENKINS-39824 Plugin does not work with read-only perforce replica Change By: Paul Allen Status: Reopened Closed Resolution: Won't Fix 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 op
[JIRA] (JENKINS-39564) 72cde84 introduced an issue where queued builds with different parameters were ignored when another queued build was present
Title: Message Title Paul Allen closed an issue as Won't Fix Closing old issues. I have no plans to fix this, but happy to review a PR if someone else want to take it on. Jenkins / JENKINS-39564 72cde84 introduced an issue where queued builds with different parameters were ignored when another queued build was present Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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 receiv
[JIRA] (JENKINS-37760) Not able to set p4 executable in configure tab after upgrading jenkins server to 2.7
Title: Message Title Paul Allen closed an issue as Not A Defect Closing - The P4 plugin uses P4Java and not the p4 executable (the old Perforce plugin used the p4 executable) Jenkins / JENKINS-37760 Not able to set p4 executable in configure tab after upgrading jenkins server to 2.7 Change By: Paul Allen Status: Open Closed Resolution: Not A Defect 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 emai
[JIRA] (JENKINS-43051) Jenkins Parameters/Variables are not expanded during Polling
Title: Message Title Paul Allen closed an issue as Won't Fix Closing - unable to fix. Jenkins has limitations with the visibility of environment variables during polling. Jenkins / JENKINS-43051 Jenkins Parameters/Variables are not expanded during Polling Change By: Paul Allen Status: In Progress Closed Resolution: Won't Fix 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+uns
[JIRA] (JENKINS-49462) Provide mechanisms to validate additions to the set of "key" ATH tests
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-49462 Provide mechanisms to validate additions to the set of "key" ATH tests Issue Type: Task Assignee: Raul Arabaolaza Components: acceptance-test-harness Created: 2018-02-08 17:01 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza We need to tag or categorize "key" test cases in ATH that all plugins should run, the tests that give us a high level of confidence that the plugin and/or core changes do not have severe side effects. Additionally those tests must be very trustworthy and without flakiness Add Comment
[JIRA] (JENKINS-49462) Provide mechanisms to validate additions to the set of "key" ATH tests
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-49462 Provide mechanisms to validate additions to the set of "key" ATH tests Change By: Raul Arabaolaza We need to tag or categorize "key" test cases in ATH that all plugins should run, After we have choose the initial set of tests that give us for essentials in JENKINS-49271 we need a high level "validation process" and tools to evaluate modifications of confidence that the plugin and/or core changes do not have severe side effects. Additionally those aforementioned set of tests must be very trustworthy and without flakiness in an easy way 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-48286) Using p4unshelve the change does no appear in the changes list
Title: Message Title Paul Allen closed an issue as Won't Fix Unable to fix this as the list is determined before the pipeline stage runs. We would need to read/parse and retrospectively add the extra shelve data into the changelog.xml. Happy to accept a PR if someone wants to take this on. Jenkins / JENKINS-48286 Using p4unshelve the change does no appear in the changes list Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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 I
[JIRA] (JENKINS-49041) clobber is always true
Title: Message Title Paul Allen closed an issue as Won't Do Intended by design. Jenkins / JENKINS-49041 clobber is always true Change By: Paul Allen Status: Open Closed Resolution: Won't Do 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-49223) Fix https://plugins.jenkins.io/p4
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49223 Fix https://plugins.jenkins.io/p4 Change By: Paul Allen Attachment: Screen Shot 2018-02-08 at 17.17.54.png 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-49223) Fix https://plugins.jenkins.io/p4
Title: Message Title
Paul Allen commented on JENKINS-49223
Re: Fix https://plugins.jenkins.io/p4
I updated the Wiki Markup to :
{jenkins-plugin-info:credentials|jiraComponent=credentials-plugin|sourceDir=credentials-plugin}
But the Plugin Information is not visible even though I based it on the Credentials plugin (see screen shot). Can You guys take a look Oleg Nenashev R. Tyler Croy Stephen Connolly
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-49223) Fix https://plugins.jenkins.io/p4
Title: Message Title
Paul Allen edited a comment on JENKINS-49223
Re: Fix https://plugins.jenkins.io/p4
I updated the Wiki Markup to :|\{jenkins-plugin-info: credentials p4 \|jiraComponent= credentials p4 -plugin\|sourceDir= credentials p4 -plugin}|But the Plugin Information is not visible even though I based it on the Credentials plugin (see screen shot). Can You guys take a look [~oleg_nenashev] [~rtyler] [~stephenconnolly]
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-41827) JenkinsRule mode to use realistic class loading
Title: Message Title Jesse Glick commented on JENKINS-41827 Re: JenkinsRule mode to use realistic class loading Durability tests turned out to be feasible with a simple addition to RestartableJenkinsRule. 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-49403) Pipeline method to get the log of a specific stage
Title: Message Title Sam Van Oort commented on JENKINS-49403 Re: Pipeline method to get the log of a specific stage Javier Raez Please provide a bit more detail – explain why you would like this, and what you hope it will do for 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-41622) Perforce unshelve command override local file without revision verification.
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-41622 Perforce unshelve command override local file without revision verification. Change By: Paul Allen Assignee: Paul Allen 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-41622) Perforce unshelve command override local file without revision verification.
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-41622 Perforce unshelve command override local file without revision verification. Change By: Paul Allen Labels: P4_B 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-49223) Fix https://plugins.jenkins.io/p4
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49223 Fix https://plugins.jenkins.io/p4 Change By: Paul Allen Labels: P4_B 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-41622) Perforce unshelve command override local file without revision verification.
Title: Message Title
Paul Allen commented on JENKINS-41622
Re: Perforce unshelve command override local file without revision verification.
Possible fix in UnshelveTask:
p4.unshelveFiles(shelf);
Populate populate = new AutoCleanImpl();
p4.syncFiles(new P4ChangeRef(shelf), populate);
p4.resolveFiles(resolve);
if(tidy) {
p4.revertAllFiles(true);
}
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-49463) jenkins needs a DRY mode which disables schedulers
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49463 jenkins needs a DRY mode which disables schedulers Issue Type: Epic Assignee: Unassigned Components: core Created: 2018-02-08 17:51 Priority: Major Reporter: Sorin Sbarnea At this moment is impossible to keep a hot-swap backup Jenkins instance running because all schedulers will start builds. The workaround of disabling jobs in order to prevent them from starting on a schedule does work only for the most basic deployments, ones that probably do not need a backup. production may have disabled jobs on normal use, disabling all on backup copy would prevent us from enabling back the correct ones if needed. disabled jobs cannot be manually triggered by users, it means that if they want to run them on the 2nd server, they need to enable them. The only safe way to enable this is to add a DRY option that tells Jenkins to: not trigger any timer based schedulers (just ignore them) not trigger on incoming SCM changes (silent skip) allow only manual job triggering skip sending emails As it can be seen some of these features depend on plugins and it would be up to the plugin authors to implement this feature. Still, the core Jenkins needs to be able to expose this "DRY" property. Ideally this property should be configurable without having to restart Jenkins so we can implement a failover service from main Jenkins master to
