[JIRA] (JENKINS-42336) Can't fail build if condition not met
Title: Message Title
Kent Granström created an issue
Jenkins / JENKINS-42336
Can't fail build if condition not met
Issue Type:
Bug
Assignee:
ikedam
Attachments:
Flex-publ-1.png
Components:
flexible-publish-plugin
Created:
2017/Feb/27 8:50 AM
Environment:
Jenkins: 2.44 Flexible publish: 0.15.2
Priority:
Minor
Reporter:
Kent Granström
Testing that a certain condition is met by running "Execute Shell" in the plugin. Have tried to return 0 and 1 through and the build never fails even though it is configured to do that. The condition per se works, meaning that if the condition is met, the specified action is executed. If the condition is NOT met, the action isn't executed, as expected. However, the build is never marked as failed whatever the outcome of the evaluation of the condition. This does NOT fail the build {{ 00:00:00.022 ++ find . -name dependency-check-report.xml 00:00:00.075 + RPT= 00:00:00.075 ++ test '!' -z '' 00:00:00.075 + exit 00:00:00.081 Run condition [Execute Shell] preventing perform for step [[Publish OWASP Dependency-Check analysis results]] 00:00:00.084 Files match condition: Matched [0] files 00:00:00.085 Run condition [Files match] preventing perform for step [[]] 00:00:00.086 Started calculate disk usage of build 00:00:00.087 Finished Calculation of disk usage of build in 0 seconds 00:00:00.089 Started calculate disk usage of workspace 00:00:00.092 Finished Calculation of disk usage of workspace in 0 seconds 00:00:00.094 Finished: SUCCESS }} Nor does this: {{00:00:00.023 ++ find . -name dependency_links.txt 00:00:00.075 + RPT=./info/depe
[JIRA] (JENKINS-42336) Can't fail build if condition not met
Title: Message Title
Kent Granström updated an issue
Jenkins / JENKINS-42336
Can't fail build if condition not met
Change By:
Kent Granström
Testing that a certain condition is met by running "Execute Shell" in the plugin. Have tried to return 0 and 1 through and the build never fails even though it is configured to do that. The condition per se works, meaning that if the condition is met, the specified action is executed. If the condition is NOT met, the action isn't executed, as expected. However, the build is never marked as failed whatever the outcome of the evaluation of the condition. *This does NOT fail the build*{{00:00:00.022 ++ find . -name dependency-check-report.xml00:00:00.075 + RPT=00:00:00.075 ++ test '!' -z ''00:00:00.075 + exit00:00:00.081 Run condition [Execute Shell] preventing perform for step [[Publish OWASP Dependency-Check analysis results]]00:00:00. 084 Files match condition: Matched [0] files00:00:00.085 Run condition [Files match] preventing perform for step [[]]00:00:00. 086 Started calculate disk usage of build00:00:00.087 Finished Calculation of disk usage of build in 0 seconds00:00:00.089 Started calculate disk usage of workspace00:00:00.092 Finished Calculation of disk usage of workspace in 0 seconds00:00:00.094 Finished: SUCCESS}}*Nor does this:*{{00:00:00.023 ++ find . -name dependency_links.txt00:00:00.075 + RPT=./info/dependency_links.txt00:00:00.076 ++ test '!' -z ./info/dependency_links.txt00:00:00.076 + exit00:00:00.082 Run condition [Execute Shell] enabling perform for step [[Publish OWASP Dependency-Check analysis results]]00:00:00.082 [DependencyCheck] Collecting Dependency-Check analysis files...00:00:00.085 [DependencyCheck] Finding all files that match the pattern **/dependency-check-report.xml00:00:00.088 [DependencyCheck] Computing warning deltas based on reference build #11600:00:00. 092 Files match condition: Matched [0] files00:00:00.092 Run condition [Files match] preventing perform for step [[]]00:00:00. 094 Started calculate disk usage of build00:00:00.095 Finished Calculation of disk usage of build in 0 seconds00:00:00.097 Started calculate disk usage of workspace00:00:00.101 Finished Calculation of disk usage of workspace in 0 seconds00:00:00.103 Finished: SUCCESS}}What do I have to do to fail the build if the condition per se is not met?
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title
Kent Granström updated an issue
Jenkins / JENKINS-40712
Exception when using mavenSettingsConfig
Change By:
Kent Granström
Comment:
Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log:{code:java}[Pipeline] }[Pipeline] // stage[Pipeline] withMaven00:00:16.758 $ /bin/sh -c "which mvn"[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variableFinished: FAILURE{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log: [Pipeline] } [Pipeline] // stage [Pipeline] withMaven 00:00:16.758 $ /bin/sh -c "which mvn" [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline ERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variable Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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...@goog
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Just to let you know the progress. Reverted back to 0.4 and had the same behaviour as before. Reinstalling the 0.5 version. Restarted the slave-machine. Restarted Jenkins on that slave and now it works For unknown reasons it now finds the installed maven... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Guys, I can't reproduce this anymore. It works like charm Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title
Kent Granström created an issue
Jenkins / JENKINS-40712
Exception when using mavenSettingsConfig
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin, pipeline-maven-plugin
Created:
2016/Dec/29 8:24 AM
Environment:
Jenkins 2.38, pipeline-maven-plugin 0.4 config-file-provider 2.15.1
Priority:
Major
Reporter:
Kent Granström
The usage of withMaven() and the mavenSettingsConfig appears to have been broken when I installed the 2.15.1 version of the config-file-provider. Had a perfectly working setup for a pipeline using 'withMaven' pointing to a configuration made in the config-file section of Jenkins using this simple test:
// Build the project.
stage("Build") {
withMaven( maven : 'maven333',
mavenLocalRepo : '.repo',
mavenSettingsConfig: 'my-settings-test')
{
sh "mvn -X clean -T2C"
}
}
After the updates of the plugins I get this exception:
08:55:42 Using Maven Installation maven333
08:55:42 Using maven exec: /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven333/bin/mvn
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timestamp
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Synchronization is the word here Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Off work now. Will a go on måndag. Hoppas new year to you all you guds doing suck a GREAT job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Will have a go on Monday... Arrrgggh K9... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-40712 Exception when using mavenSettingsConfig Change By: Kent Granström Comment: Will have a go on Monday... Arrrgggh K9... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström edited a comment on JENKINS-40712 Re: Exception when using mavenSettingsConfig Off work now. Will have a go on monday. Happy new year to you all you guys doing such a GREAT job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström edited a comment on JENKINS-40712 Re: Exception when using mavenSettingsConfig Off work now. Will a go on måndag monday . Hoppas Happy new year to you all you guds guys doing suck such a GREAT job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Kent Granström commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Have now set up an environment to be able to build the plugin. Once installed I could see a difference in the behaviour. First of all, the config files I have setup now appears in the "Snippet Generator" and it all looks good. However, when running the script it can't find 'mvn' any more. Despite one of the arguments being passed to 'withMaven(maven: 'maven333') ' for the maven version to use in Jenkins it can not find it anymore. I can see the workaround and just add the path to the $PATH and or manually set the $MAVEN_HOME but the question I ask myself is, why does it not find maven anymore? This is an excerpt from the log: [Pipeline] } [Pipeline] // stage [Pipeline] withMaven 00:00:16.758 $ /bin/sh -c "which mvn" [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline ERROR: Could not find maven executable, please set up a Maven Installation or configure MAVEN_HOME environment variable Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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...@goog
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title
Kent Granström created an issue
Jenkins / JENKINS-50187
build-blocker-plugin does not block on node level for pipeline projects
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-blocker-plugin
Created:
2018-03-15 08:27
Environment:
Jenkins 2.111
Priority:
Critical
Reporter:
Kent Granström
Have integrated Jenkins with Atlassian Bitbucket where I trigger what we call "pre-merge" builds. This means once pull-requests are reday for merge we start a job that checks that they are really ready for merge. A failed build will prevent the merge. Any change on the target branch, or the source branch will trigger a new build. Since there are several pull requests that wants to merge to the develop branch many jobs can be triggered simultanously causing 2-3 or even more build jobs to be queued at once. We have 2 build slaves/agents that I have given the same label so they can be used simultanously to balance the load so to speak. Now then, in the job, I have entered a restriction for where this job can execute in the "Label _expression_": 'label-that-sits-on-two-slaves'. I have also entered a "Blocking jobs" -name like ABC* and then selecting the "block on node level" which leads me to believe that this would allow one of the "pre-merge" builds to use one of our agents and a second one to use the other slave and this seems to work for NON-PIPELINE jobs. Doing the same for a pipeline job, where specifying:
agent { label: 'label-that-sits-on-two-slaves' }
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title
Kent Granström updated an issue
Jenkins / JENKINS-50187
build-blocker-plugin does not block on node level for pipeline projects
Change By:
Kent Granström
Have integrated Jenkins with Atlassian Bitbucket where I trigger what we call "pre-merge" builds. This means once pull-requests are reday ready for merge we start a job that checks that they are really ready for merge. A failed build will prevent the merge. Any change on the target branch, or the source branch will trigger a new build. Since there are several pull requests that wants to merge to the develop branch many jobs can be triggered simultanously causing 2-3 or even more build jobs to be queued at once. We have 2 build slaves/agents that I have given the same label so they can be used simultanously to balance the load so to speak.Now then, in the job, I have entered a restriction for where this job can execute in the "Label _expression_": 'label-that-sits-on-two-slaves'.I have also entered a "Blocking jobs" -name like ABC* and then selecting the "block on node level" which leads me to believe that this would allow one of the "pre-merge" builds to use one of our agents and a second one to use the other slave and this seems to work for NON-PIPELINE jobs. Doing the same for a pipeline job, where specifying:{code:java}agent { label: 'label-that-sits-on-two-slaves' }{code}does not work. What is required to be able to automatically distribute a build-job on two or more agents simultanously and prevent them from running at the same time on the same agent using pipeline scripts?
Add Comment
[JIRA] (JENKINS-54038) Jacoco creates multiple Coverage reports and trends grapphs
Title: Message Title Kent Granström created an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and trends grapphs Issue Type: Bug Assignee: Ognjen Bubalo Attachments: MultipleJacocoTrends.png Components: jacoco-plugin Created: 2018-10-12 06:54 Environment: Jenkins 2.146, jacoco-plugin 3.0.3 Priority: Minor Reporter: Kent Granström After yesterday's upgrade of Jenkins from 2.140 to 2.146 and several plugins, to many to enumerate, our pipeline jobs now generates loads of jacoco Coverage reports and Trends graphs. The jobs can hardly be opened probably due to the amount of data to load and they take forever to build. What has happened? I'am building at the moment so I'll add relevant data from the log files if I find any suspicous printouts. Add Comment
[JIRA] (JENKINS-54038) Jacoco creates multiple Coverage reports and trends grapphs
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and trends grapphs Change By: Kent Granström Priority: Minor Critical 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-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and Trends graphs Change By: Kent Granström Summary: Jacoco creates multiple Coverage reports and trends grapphs Trends graphs 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-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and Trends graphs Change By: Kent Granström After yesterday's upgrade of Jenkins from 2.140 to 2.146 and several plugins, to many to enumerate, our pipeline jobs now generates loads of jacoco Coverage reports and Trends graphs. The jobs can hardly be opened probably due to the amount of data to load and they take forever to build. What has happened? I'am building at the moment so I'll add relevant data from the log files if I find any suspicous printouts. Very similar to this issue:[http://jenkins-ci.361315.n4.nabble.com/jacoco-plugin-broken-after-update-of-Pipeline-Maven-Integration-plugin-td4948864.html] 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-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström commented on JENKINS-54038 Re: Jacoco creates multiple Coverage reports and Trends graphs Can someone who has the knowledge address this issue plz? 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-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and Trends graphs Change By: Kent Granström Comment: Can someone who has the knowledge address this issue plz? 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-37262) Notify Stash does not work with ssh keys
Title: Message Title Kent Granström commented on JENKINS-37262 Re: Notify Stash does not work with ssh keys Any progress in this matter? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35470) Restrict file access slave-to-master
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-35470 Restrict file access slave-to-master Change By: Kent Granström Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35470) Restrict file access slave-to-master
Title: Message Title Kent Granström created an issue Jenkins / JENKINS-35470 Restrict file access slave-to-master Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/08 12:43 PM Environment: Centos 7 Priority: Major Reporter: Kent Granström Hi Have an unsolvable problem regarding slave-to-master access which I can’t seem to find a solution for. Here is the big picture. We’re developing software where we assign certain parts to one contractor, other parts to other contractors and yet some other parts to a third or fourth contractor. They are not meant to share the code they develop with other contractors. Once they’re done they commit the code into our GIT where we have configured the access rights accordingly. Once the code is in GIT it’s pulled out by our Jenkins CI for building and testing activities. This is done in several jobs that we have set up. None of the jobs are actually built on the master node in Jenkins but GIT pulls all the code to the master. They all build and execute on our slaves/agents. The jobs are configured so that they just pull out the appropriate git repo hence we restrict access to the source code to this particular job only. The buildsteps include several shell-scripts doing all the making/building/tes
[JIRA] [core] (JENKINS-18800) Jenkins selects channel to wrong node for build job
Title: Message Title
Kent Granström commented on JENKINS-18800
Re: Jenkins selects channel to wrong node for build job
I think I can reproduce this in the latest Jenkins (2.7) Have a test-setup with a master and 2 slaves (byggslav labelled BS-1 and byggslav-2 labelled BS-2) Have set up a very simple MultiConfiguration job. The only thing the job does is to pull a git repo to the slave's workspace. Have also setup the Configuration Matrix to execute on label "BS-1" only.
Despite that, it tends to pull the repo to both slaves but in different locations
Started by user Me Building remotely on byggslav-2 (BS-2) in workspace /home/bb2/workspace/MultiConfigJob Cloning the remote Git repository Cloning repository ssh://g...@test.mysite.com/testing.git > git init /home/bb2/workspace/MultiConfigJob # timeout=10 Fetching upstream changes from ssh://g...@test.mysite.com/testing.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh://g...@test.mysite.com/testing.git +refs/heads/:refs/remotes/origin/ > git config remote.origin.url ssh://g...@test.mysite.com/testing.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > git config remote.origin.url ssh://g...@test.mysite.com/testing.git # timeout=10 Fetching upstream changes from ssh://g...@test.mysite.com/testing.git > git -c core.askpass=true fetch --tags --progress ssh://g...@test.mysite.com/testing.git +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/master^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit}
# timeout=10 Checking out Revision c650834025c6866b4fd244458b20a10e64e262cf (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c650834025c6866b4fd244458b20a10e64e262cf > git rev-list c650834025c6866b4fd244458b20a10e64e262cf # timeout=10 Triggering MultiConfigJob » BS-1 MultiConfigJob » BS-1 completed with result SUCCESS Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS
REPO found here: ls -ltr bb1/workspace/MultiConfigJob/label/BS-1/ total 28
rw-r
r
-. 1 bb1 jenkins 114 Jun 9 16:53 nyfil.txt
rw-r
r
-. 1 bb1 jenkins 0 Jun 9 16:53 Jenkinsfile
rw-r
r
-. 1 bb1 jenkins 34 Jun 9 16:53 d.txt
rw-r
r
-. 1 bb1 jenkins 34 Jun 9 16:53 c.txt
rw-r
[JIRA] [core] (JENKINS-18800) Jenkins selects channel to wrong node for build job
Title: Message Title
Kent Granström edited a comment on JENKINS-18800
Re: Jenkins selects channel to wrong node for build job
I think I can reproduce this in the latest Jenkins (2.7) (or a similar behaviour) Have a test-setup with a master and 2 slaves (byggslav labelled BS-1 and byggslav-2 labelled BS-2)Have set up a very simple MultiConfiguration job. The only thing the job does is to pull a git repo to the slave's workspace. Have also setup the Configuration Matrix to execute on label "BS-1" only.Despite that, it tends to pull the repo to both slaves but in different locationsStarted by user Me Building remotely on *byggslav-2 (BS-2)* in workspace /home/bb2/workspace/MultiConfigJobCloning the remote Git repositoryCloning repository ssh://g...@test.mysite.com/testing.git > git init /home/bb2/workspace/MultiConfigJob # timeout=10Fetching upstream changes from ssh://g...@test.mysite.com/testing.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh://g...@test.mysite.com/testing.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ssh://g...@test.mysite.com/testing.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ssh://g...@test.mysite.com/testing.git # timeout=10Fetching upstream changes from ssh://g...@test.mysite.com/testing.git > git -c core.askpass=true fetch --tags --progress ssh://g...@test.mysite.com/testing.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision c650834025c6866b4fd244458b20a10e64e262cf (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c650834025c6866b4fd244458b20a10e64e262cf > git rev-list c650834025c6866b4fd244458b20a10e64e262cf # timeout=10Triggering MultiConfigJob » BS-1MultiConfigJob » BS-1 completed with result SUCCESSStarted calculate disk usage of buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsFinished: SUCCESSREPO found here:ls -ltr *bb1/workspace/MultiConfigJob/label/BS-1/*total 28-rw-r--r--. 1 bb1 jenkins 114 Jun 9 16:53 nyfil.txt-rw-r--r--. 1 bb1 jenkins 0 Jun 9 16:53 Jenkinsfile-rw-r--r--. 1 bb1 jenkins 34 Jun 9 16:53 d.txt-rw-r--r--. 1 bb1 jenkins 34 Jun 9 16:53 c.txt-rw-r--r--. 1 bb1 jenkins 65 Jun 9 16:53 crb.txt-rw-r--r--. 1 bb1 jenkins 170 Jun 9 16:53 cra.txt-rw-r--r--. 1 bb1 jenkins 29 Jun 9 16:53 b.txt-rw-r--r--. 1 bb1 jenkins 87 Jun 9 16:53 a.txtand here: ls -ltr *bb2/workspace/MultiConfigJob/*total 28-rw-r--r--. 1 bb2 jenkins 114 Jun 9 16:53 nyfil.txt-rw-r--r--. 1 bb2 jenkins 0 Jun 9 16:53 Jenkinsfile-rw-r--r--. 1 bb2 jenkins 34 Jun 9 16:53 d.txt-rw-r--r--. 1 bb2 jenkins 34 Jun 9 16:53 c.txt-rw-r--r--. 1 bb2 jenkins 65 Jun 9 16:53 crb.txt-rw-r--r--. 1 bb2 jenkins 170 Jun 9 16:53 cra.txt-rw-r--r--. 1 bb2 jenkins 29 Jun 9 16:53 b.txt-rw-r--r--. 1 bb2 jenkins 87 Jun 9 16:53 a.txtRegards-- Kent
Add Comment
[JIRA] [core] (JENKINS-35566) Building on wrong slave
Title: Message Title Kent Granström created an issue Jenkins / JENKINS-35566 Building on wrong slave Issue Type: Bug Assignee: Unassigned Attachments: pic.png Components: core Created: 2016/Jun/10 10:22 AM Priority: Major Reporter: Kent Granström Have a strange behaviour with our builds. Have a test-setup with a master and 2 slaves (byggslav labelled BS-1 and byggslav-2 labelled BS-2) Have set up a very simple MultiConfiguration job. The only thing the job does is to pull a git repo to the slave's workspace. Have also setup the Configuration Matrix to execute on label "BS-1" only. Despite that, it tends to pull the repo to both slaves but in different locations Started by user Me Building remotely on byggslav-2 (BS-2) in workspace /home/bb2/workspace/MultiConfigJob Cloning the remote Git repository Cloning repository ssh://g...@test.mysite.com/testing.git > git init /home/bb2/workspace/MultiConfigJob # timeout=10 Fetching upstream changes from ssh://g...@test.mysite.com/testing.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh://g...@test.mysite.com/testing.git +refs/heads/:refs/remotes/origin/ > git config remote.origi
[JIRA] [core] (JENKINS-35566) Building on wrong slave
Title: Message Title Kent Granström reopened an issue I don't understand why you say that this is not an error? It check out the code in 2 slaves. The master is not bb1 nor bb2. I still would call this a bug since I specify that the execution is made on a particular slave and the code is cloned in two different slaves, on different locations. Jenkins / JENKINS-35566 Building on wrong slave Change By: Kent Granström Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35566) Building on wrong slave
Title: Message Title Kent Granström commented on JENKINS-35566 Re: Building on wrong slave Ok! I see. I thought the master was always the master where everything was initiated not som arbitrary slave/agent. Still confused of the reasoning behind this. If one is to restrict a build to a certain machine identified by name or label in the advanced tab to me that implies that the build is only going to be built on that particular machine. Adding som slaves in the matrix-configuration is more or less contradicting the first configuration Anyway. Keeping this behaviour in mind I now know what to do. I'll close the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35566) Building on wrong slave
Title: Message Title Kent Granström resolved as Not A Defect See comments Jenkins / JENKINS-35566 Building on wrong slave Change By: Kent Granström Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend I have now changed this one to major since it does, when working properly, provide important information regarding the builds. Am I the only one interested in having this bug fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Attachment: Build sizes back.png Attachment: Build sizes back.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Attachment: AllSizesVisible.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Have some more info: Just found one way to temporarily get the build sizes back and that is to go to the "Disk Usage" page by clicking the icon in the left hand pane and in there click the "Record Builds Disk Usage"-button Now then! Going back to a build-job and VOILA, the sizes are back! Note that they are only back until I click on the build. Once I have opened a certain build they are gone again Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström edited a comment on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Have some more info:Just found one way to temporarily get the build sizes back and that is to go to the "Disk Usage" page by clicking the icon in the left hand pane and in there click the "Record Builds Disk Usage"-button !Build sizes back.png|thumbnail!Now then ! . Going back to a build-job and VOILA, the sizes are back ... ! ! AllSizesVisible.png|thumbnail! Note that they are only back until I click on the build. Once I have opened a certain build they are gone again :( Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Environment: Jenkins : 1.574, 1.583, 1.619 , 1.622Disk-Usage plugin: 0.25 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Is this issue being addressed by anyone? Is it perhaps solved in a later version? Does anyone know? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Have now at last upgraded to 1.619. No change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Added all loggers I could think of but nothing came out in the log. Must be doing something wrong here Change By: Kent Granström Attachment: LoggersForDiskUsage.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström edited a comment on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Added all loggers I could think of but nothing came out in the log. Must be doing something wrong here :-( Not even sure I'm looking in the right place... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Re-reading Jenkins config from disk restores the build sizes but once I click on a build and go back, it is gone Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend As a side-note, ALL sizes dissapeard from builds made on previous version of Jenkins (1.583). They are now replaced by a dash Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Created a VERY simple project. All sizes for the builds are stored in the disk-usage.xml file found at the top level of the job. Executing a new build results in that the file is updated correctly. The UI for this new build is also updated. Clicking the build and then head back to the same screen results in that the size is gone. Looking in the disk-usage.xml again, the correct value is present for all builds. I'm lost Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Environment: Jenkins 1.574 , 1.583, 1.619 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28355) Project's Build History frame size is short for icons
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-28355 Project's Build History frame size is short for icons Change By: Kent Granström Component/s: disk-usage-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28355) Project's Build History frame size is short for icons
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-28355 Project's Build History frame size is short for icons Change By: Kent Granström Component/s: disk-usage-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström Component/s: disk-usage-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström edited a comment on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Created a VERY simple project. All sizes for the builds are stored in the disk-usage.xml file found at the top level of the job. Executing a new build results in that the file is updated correctly. The UI for this new build is also updated with the correct value . Clicking the build and then head back to the same screen results in that the size is gone.Looking in the disk-usage.xml again, the correct value is present for all builds. Is it perhaps cached somewhere? Is it read only once perhaps? *I'm lost* :-( Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Title: Message Title Kent Granström commented on JENKINS-24821 Re: Jenkins missing build size in Build History Trend Can confirm that the fix works Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22946) Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves
Kent Granström updated JENKINS-22946 Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves Change By: Kent Granström (13/May/14 9:54 AM) Description: After a Jenkins upgrade from 1.544 to 1.562 all multi-platform jobs started to abort themselves for no apparent reason. We have jobs configured to build on three platforms, Win, Mac and Linux. As soon as one of the platforms are ready all the others aborts themselves. This is an extract of the behaviour from the log:May 8, 2014 2:16:42 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=mac #1651 main build action completed: SUCCESSMay 8, 2014 2:21:17 PM hudson.model.Run executeINFO: AnApplication/Conf=Rel,label=mac #1651 main build action completed: SUCCESSMay 8, 2014 2:21:36 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=win #1651 abortedjava.lang.InterruptedExceptionat java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:146)at hudson.remoting.Channel.call(Channel.java:739)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)at $Proxy62.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951)at hudson.Launcher$ProcStarter.join(Launcher.java:362)at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:118)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)at hudson.model.Build$BuildExecution.build(Build.java:198)at hudson.model.Build$BuildExecution.doRun(Build.java:159)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)at hudson.model.Run.execute(Run.java:1704)at hudson.matrix.MatrixRun.run(MatrixRun.java:146)at hudson.model.ResourceController.execute(ResourceController.java:88)at hudson.model.Executor.run(Executor.java:231)May 8, 2014 2:21:36 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=linux #1651 abortedjava.lang.InterruptedExceptionat java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:146)at hudson.remoting.Channel.call(Channel.java:739)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)at $Proxy62.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951)at hudson.Launcher$ProcStarter.join(Launcher.java:362)at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:118)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)at hudson.model.Build$BuildExecution.build(Build.java:198)at hudson.model.Build$BuildExecution.doRun(Build.java:159)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)at hudson.model.Run.execute(Run.java:1704) Additional information:FATAL: tried to access method hudson.tasks.test.AggregatedTestResultAction.add(Lhudson/tasks/test/AbstractTestResultAction;)V from class hudson.tasks.test.TestResultAggregatorjava.lang.IllegalAccessError: tried to access method hudson.tasks.test.AggregatedTestResultAction.add(Lhudson/tasks/test/AbstractTestResultAction;)V from class hudson.tasks.test.TestResultAggregator at hudson.tasks.test.TestResultAggregator.endRun(TestResultAggregator.java:57) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:219) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:162) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:357) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1704) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)
[JIRA] [core] (JENKINS-22946) Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves
Kent Granström commented on JENKINS-22946 Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves Incompatibility between slave and master was the cause. Setting up matching slave.jar solved the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Kent Granström created JENKINS-24821 Jenkins missing build size in Build History Trend Issue Type: Bug Assignee: Unassigned Attachments: Missing_size.png Components: core Created: 23/Sep/14 8:43 AM Description: For each build you get an item in the Build History you get a build number, a date and finally the size of the build. As soon as I click on any item in the list and returns to the same page the size has disappeared. It seems to be gone forever. Is this a bug or a feature? Environment: Jenkins 1.574 Project: Jenkins Priority: Minor Reporter: Kent Granström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Kent Granström updated JENKINS-24821 Jenkins missing build size in Build History Trend Change By: Kent Granström (23/Sep/14 9:49 AM) Description: For each build you get an item in the Build History you . You get a build number, a date and finally the size of the build. As soon as I click on any item in the list and returns to the same page the size has disappeared. It seems to be gone forever. Is this a bug or a feature? :-) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Kent Granström commented on JENKINS-24821 Jenkins missing build size in Build History Trend Ver: 0.24 of the disk usage plugin No. Reloading the page doesn't change the outcome No. They are older. Added another pic to demonstrate this If I restart the computer, then I get them back. They will probably be visible if I restart the whole browser (Chrome). I'll test that in a minute This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Kent Granström updated JENKINS-24821 Jenkins missing build size in Build History Trend Older builds that disappear when I look into the build Change By: Kent Granström (24/Sep/14 5:22 AM) Attachment: Missing_size_2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24821) Jenkins missing build size in Build History Trend
Kent Granström commented on JENKINS-24821 Jenkins missing build size in Build History Trend No. They don't come back with a restart of the browser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström commented on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström edited a comment on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? Perhaps I am missing something in order to omit all these This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström edited a comment on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? Perhaps I am missing something in order to omit all these Solution: Add the DiskUsageProjectActionFactory to the "System configuration exclude file pattern" filtering and it is gone. Case closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström edited a comment on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? Perhaps I am missing something in order to omit all these - Solution: Add the DiskUsageProjectActionFactory to the "System configuration exclude file pattern" filtering and it is gone. Case closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström reopened JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Encountered this problem on 1.583 when installing v1.3 of jUnit. Tried v1.4, same result. Manually resinstalled v1.2 works. The problem is still in there somewhere ... Archiving artifacts Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Change By: Kent Granström (11/Feb/15 9:51 AM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Silly me RTFM before writing... Thanx Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström resolved JENKINS-24946 as Cannot Reproduce JUnit Tests Results fail to archive in V1.582 Reverting issue to its previous state since it is explained in the comments why it doesn't work with 1.583. The release-notes for the plugin however should perhaps state the incompatibility even though it is compatible with later versions of Jenkins. Change By: Kent Granström (11/Feb/15 10:56 AM) Status: Reopened Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
