[JIRA] (JENKINS-56798) Container name validation doesn't work with env variables
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-56798 Container name validation doesn't work with env variables Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.1.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57135) Favorite Plugin causes Exception : Caught exception evaluating: h.getIconFilePath(action)
Title: Message Title Dimas Rizky created an issue Jenkins / JENKINS-57135 Favorite Plugin causes Exception : Caught exception evaluating: h.getIconFilePath(action) Issue Type: Bug Assignee: James Dumay Components: favorite-plugin Created: 2019-04-22 06:50 Environment: Favorite : 2.3.2 Jenkins : 2.173 Priority: Minor Reporter: Dimas Rizky I got this error after updating my favorite plugins to the latest version, any clue ? I got this after updating my jenkins version, and thats makes me update my favorite-plugins too. Thus, this does not causing anything harmful on the jenkins, it's just showed lot of warning on log whenever I try to open the jobs that previously had favorite activated to it Apr 22, 2019 1:41:09 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: h.getIconFilePath(action) in /jenkins/job/Insuretech/view/Build/job/insuretech%20Build%20-%20Production/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.favorite.user.FavoriteUserProperty.isJobFavorite(FavoriteUserProperty.java:106) at hudson.plugins.favorite.Favorites.isFavorite(Favorites.java:45) at hudson.plugins.favorite.project.FavoriteProjectAction.isFavorite(FavoriteProjectAction.java:94) at hudson.plugins.favorite.project.FavoriteProjectAction.getIconFileName(FavoriteProjectAction.java:30) at hudson.Functions.getIconFilePath(Functions.java:1071) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.inv
[JIRA] (JENKINS-57134) Passing test parameters from Jenkins to ALM for API tests
Title: Message Title Anda Sorina Laakso updated an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM for API tests Change By: Anda Sorina Laakso Summary: Passing test parameters from Jenkins to ALM does not work for API Tests tests Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57134) Passing test parameters from Jenkins to ALM does not work for API Tests
Title: Message Title Anda Sorina Laakso updated an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM does not work for API Tests Change By: Anda Sorina Laakso Issue Type: Bug Story Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57134) Passing test parameters from Jenkins to ALM does not work for API Tests
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM does not work for API Tests Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:32 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso [Jenkins][Test Parameters][API] Passing test parameters from Jenkins to ALM does not work for API Tests Steps to reproduce the defect : 1. Add a parametrized API test in ALM 2. Create a job of type "Execute Micro Focus functional tests from Micro Focus ALM" 3. Add test parameters for the API tests e.g: Root\Jenkins_TestParameters\TestSet "ParamAPI1": "7", "RequestParam1" : "978910134" 4. Execute the job Expected Result : Parameters are not taken into account when running the test in ALM. Parameters set in Jenkins should override the actual values set in ALM. Actual Result : Actual parameters set in ALM are used instead Detected in build: ++ Jenkins 5.7 Regression from version\build (if applicable): Additional Notes: Only for API tests. API test used attached
[JIRA] (JENKINS-57133) Test result link to ALM is pointing to wrong module
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57133 Test result link to ALM is pointing to wrong module Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:31 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Run any test from ALM in Jenkins 2. Open Console and check run output 3. Find link to jenkins result Expected Result : The link should be able to open target result Actual Result : The link is point to Test lab but it should point to Test runs module. So it cannot open target result Detected in build: Add Comment
[JIRA] (JENKINS-57132) Not userfriendly grouping of test results for running from file system
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57132 Not userfriendly grouping of test results for running from file system Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:31 Labels: plugin UFT Priority: Minor Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Create job, on build step select: "Execute HP tests from file system" 2. In field test put path to mtbx file, and direct pathes to tests 3. Build the job Detected in build: 4.5.0-SNAPSHOT (private-cd8b870c-kazaky) Expected Result : If confugured to run tests directly from file system, not group results to class Actual Result : Not userfriendly grouping of test results for running from file system (see attached snapshot) 4.5.0-SNAPSHOT (private-cd8b870c-kazaky) Add Comment
[JIRA] (JENKINS-57131) Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57131 Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:30 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Install plugin version 4.5 or 5.0 2. Create job for run test from ALM 3. Create simple API test and save in ALM 4. Add created test to test set 5. Run job 6. Now set up timeout to 1 second. 7. Run job 8. Remove timeout and try run job again Expected Result : job running Actual Result : UFT cant start and job failed ++ Add Comment
[JIRA] (JENKINS-57130) Multiple issues
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57130 Multiple issues Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:20 Priority: Major Reporter: Anda Sorina Laakso [Jenkins][Test Parameters][API] Passing test parameters from Jenkins to ALM does not work for API Tests [Jenkins][UI] Configuration view issues when scrolling at the bottom of the page Jenkins plugin : Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout [Jenkins CI Plugin]: Not userfriendly grouping of test results for running from file system [Jenkins Plugin] Test result link to ALM is pointing to wrong module Add Comment
[JIRA] (JENKINS-56716) Add unit tests for LogHandler
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56716 Add unit tests for LogHandler Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56790) using pyLint results to an NPE
Title: Message Title Ulli Hafner resolved as Cannot Reproduce Please provide some detailed steps on how to reproduce. Jenkins / JENKINS-56790 using pyLint results to an NPE Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56815) Make "note" lines availabl in warning details
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56815 Make "note" lines availabl in warning details Change By: Ulli Hafner Labels: help-wanted newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56892) Add support for include what you use (IWYU)
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-56892 Add support for include what you use (IWYU) Change By: Ulli Hafner Component/s: analysis-model Labels: help-wanted Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56815) Make "note" lines availabl in warning details
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-56815 Make "note" lines availabl in warning details Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56915) Clang-Tidy reporting does not work for errors without line dependency
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-56915 Clang-Tidy reporting does not work for errors without line dependency Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57083) Mouse over in diagrams only works for first diagram
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-57083 Mouse over in diagrams only works for first diagram Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-43322) Nested view should be also searchable by name
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-43322 Nested view should be also searchable by name Change By: Daniel Beck Released As: jenkins-2. 17 174 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-43322) Nested view should be also searchable by name
Title: Message Title Daniel Beck updated JENKINS-43322 Jenkins / JENKINS-43322 Nested view should be also searchable by name Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: jenkins-2.17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/abcd[Pipeline] {[Pipeline] sh+ docker inspect -f . xxx.[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkings jenkins check its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03831:name=systemd:/dock
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/abcd[Pipeline] {[Pipeline] sh+ docker inspect -f . abcd xxx .[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkings check its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03831:name=systemd:/docker/
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/abcd[Pipeline] {[Pipeline] sh+ docker inspect -f . image_wlpbuild abcd .[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkings check its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03831:name=syste
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/ bus_master abcd [Pipeline] {[Pipeline] sh+ docker inspect -f . image_wlpbuild.[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkings check its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03831:name=
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/bus_master[Pipeline] {[Pipeline] sh+ docker inspect -f . image_wlpbuild.[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code} Is the following process Does jenkings check it ' s own cgroup checked ?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/bus_master[Pipeline] {[Pipeline] sh+ docker inspect -f . image_wlpbuild.[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkings check it's its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat /proc/1310/cgroup12:memory:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service11:pids:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service10:rdma:/9:hugetlb:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03838:blkio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03837:perf_event:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03836:freezer:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03835:cpuset:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03834:cpu,cpuacct:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03833:devices:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service2:net_cls,net_prio:/docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e03831:name
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax
Title: Message Title
werner hans created an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2019-04-21 09:45
Environment:
RHEL 8 beta Jenkins 2.173 (rpm based installation, running as service, running as docker container) docker 18.09.2 Jenkins container/Docker host on same machine - using shared binary, socket via bind mounts
Labels:
plugin docker-slaves
Priority:
Minor
Reporter:
werner hans
Hi, following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change https://github.com/jenkinsci/docker-workflow-plugin/pull/169 might be too restrictive. Szenario, cf. Field Environment with the following configuration in Jenkins: - pipeline script (tried both with groovy sandbox unchecked and checked):
pipeline {
agent {
docker {
image 'xxx'
}
}
stages {
stage('Build') {
steps {
sh 'echo "abc"'
}
}
}
}
console output of a build:
[JIRA] (JENKINS-57128) Builds array is not created in version 4
Title: Message Title Michael S created an issue Jenkins / JENKINS-57128 Builds array is not created in version 4 Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-04-21 09:05 Priority: Major Reporter: Michael S After accidental upgrading to version 4 (rc) our internal scripts stopped working. The script used "/api/python?tree=jobs[name,scm[userRemoteConfigs[url]],builds[changeSet[items[paths[file]]],actions[lastBuiltRevision[SHA1]],result,building,number,duration,estimatedDuration, url]]" to get information from Jenkins. The "SHA1" is not available anymore. The "build" is not created and I don't see how I can get the commit ID now. Add Comment
