[JIRA] [dynamicparameter] (JENKINS-18972) About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0)
Dirk Haun commented on JENKINS-18972 About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0) Looks like we ran into the same problem: Jul 23, 2014 10:24:17 AM SEVERE com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition executeScript Error during executing script for parameter 'CPLIB_REVISION' hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script1.groovy: 52: unable to resolve class hudson.scm.SubversionSCM @ line 52, column 18. def newscm = new hudson.scm.SubversionSCM(newSvnPaths, job.scm.workspaceUpdater, job.scm.browser, job.scm.excludedRegions, ^ 1 error Any chance the pull request from Nicolas De Loof could make it into the plugin? 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] [matrix] (JENKINS-8205) Matrix Build result display problem
Dirk Haun commented on JENKINS-8205 Matrix Build result display problem I see this issue still exists in Jenkins ver. 1.554.2.2 (Jenkins Enterprise). Any chance this will be addressed some day? I realise it's purely a cosmetic thing, but sometimes you just need a Matrix job with only one active configuration, just for consistency. It would be nice if those would still be displayed as an actual matrix, with borders and all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-13514) Matrix Reloaded should trigger the same combination in downstream matrix job
[ https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162308#comment-162308 ] Dirk Haun commented on JENKINS-13514: - Thanks for looking into this. There's one detail I left out of the original description: Not all out downstream matrix jobs have exactly the same two axis. We have a few base libraries that need to be built for all combinations of platforms but further down the tree, we have products that are built on fewer platforms. For example, we have products that are Windows-only (due to ties with the Windows API). So if, say, the build for the base library for Windows failed, we would still like to be able to re-trigger that build and also the Windows-only builds further down the tree. So I'd like to rephrase the perfect match requirement to something like If the downstream matrix has any of the selected combinations, then build those that are available. In other words, we may have cases where we trigger, say, Solaris and Windows builds at the top, but further down the tree, there are Matrix jobs without the Solaris option, but we would still like it to trigger the Windows option in that Matrix (obviously, any downstream jobs from those matrix jobs won't have a Solaris option either). Does that make sense? Matrix Reloaded should trigger the same combination in downstream matrix job Key: JENKINS-13514 URL: https://issues.jenkins-ci.org/browse/JENKINS-13514 Project: Jenkins Issue Type: Improvement Components: matrix-reloaded Affects Versions: current Reporter: Dirk Haun Priority: Minor Attachments: 01-jobA.png, 02-jobB.png When rebuilding parts of a matrix job (using the matrix reloaded plugin), the build will then trigger all downstream jobs. In our case, the downstream jobs are also matrix jobs and we would like that in this case, the downstream jobs are also reloaded, i.e. only the parts that were rebuilt in the upstream job should be built there as well. To reproduce, I've used a setup that somewhat resembles what we have: - 2 matrix jobs, jobA and jobB - jobA has jobB as its downstream job - each job consists of a 3x3 matrix with the axis labelled compiler and os respectively - the compiler axis has values FORTE, GCC, MSC - the os axis has values solaris, linux, windows - the build step is just a echo hello world We're using the Parameterized Build plugin, http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to trigger downstream builds but this can also be reproduced with the standard Build other projects option. The two screenshots show the matrix and which parts are supposed to be rebuild. The second screenshot shows that jobB, when triggered by rebuilding only parts of the jobA matrix, is actually building all 9 combinations, not just the 2 of the upstream job. P.S. I mentioned this problem at the Jenkins User Conference in Paris, in case you remember :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13514) Matrix Reloaded should trigger the same combination in downstream matrix job
[ https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162308#comment-162308 ] Dirk Haun edited comment on JENKINS-13514 at 5/2/12 9:06 AM: - Thanks for looking into this. There's one detail I left out of the original description: Not all our downstream matrix jobs have exactly the same two axis. We have a few base libraries that need to be built for all combinations of platforms but further down the tree, we have products that are built on fewer platforms. For example, we have products that are Windows-only (due to ties with the Windows API). So if, say, the build for the base library for Windows failed, we would still like to be able to re-trigger that build and also the Windows-only builds further down the tree. So I'd like to rephrase the perfect match requirement to something like If the downstream matrix has any of the selected combinations, then build those that are available. In other words, we may have cases where we trigger, say, Solaris and Windows builds at the top, but further down the tree, there are Matrix jobs without the Solaris option, but we would still like it to trigger the Windows option in that Matrix (obviously, any downstream jobs from those matrix jobs then won't have a Solaris option either). Does that make sense? was (Author: dhaun): Thanks for looking into this. There's one detail I left out of the original description: Not all out downstream matrix jobs have exactly the same two axis. We have a few base libraries that need to be built for all combinations of platforms but further down the tree, we have products that are built on fewer platforms. For example, we have products that are Windows-only (due to ties with the Windows API). So if, say, the build for the base library for Windows failed, we would still like to be able to re-trigger that build and also the Windows-only builds further down the tree. So I'd like to rephrase the perfect match requirement to something like If the downstream matrix has any of the selected combinations, then build those that are available. In other words, we may have cases where we trigger, say, Solaris and Windows builds at the top, but further down the tree, there are Matrix jobs without the Solaris option, but we would still like it to trigger the Windows option in that Matrix (obviously, any downstream jobs from those matrix jobs won't have a Solaris option either). Does that make sense? Matrix Reloaded should trigger the same combination in downstream matrix job Key: JENKINS-13514 URL: https://issues.jenkins-ci.org/browse/JENKINS-13514 Project: Jenkins Issue Type: Improvement Components: matrix-reloaded Affects Versions: current Reporter: Dirk Haun Priority: Minor Attachments: 01-jobA.png, 02-jobB.png When rebuilding parts of a matrix job (using the matrix reloaded plugin), the build will then trigger all downstream jobs. In our case, the downstream jobs are also matrix jobs and we would like that in this case, the downstream jobs are also reloaded, i.e. only the parts that were rebuilt in the upstream job should be built there as well. To reproduce, I've used a setup that somewhat resembles what we have: - 2 matrix jobs, jobA and jobB - jobA has jobB as its downstream job - each job consists of a 3x3 matrix with the axis labelled compiler and os respectively - the compiler axis has values FORTE, GCC, MSC - the os axis has values solaris, linux, windows - the build step is just a echo hello world We're using the Parameterized Build plugin, http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to trigger downstream builds but this can also be reproduced with the standard Build other projects option. The two screenshots show the matrix and which parts are supposed to be rebuild. The second screenshot shows that jobB, when triggered by rebuilding only parts of the jobA matrix, is actually building all 9 combinations, not just the 2 of the upstream job. P.S. I mentioned this problem at the Jenkins User Conference in Paris, in case you remember :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13514) Matrix Reloaded should trigger the same combination in downstream matrix job
Dirk Haun created JENKINS-13514: --- Summary: Matrix Reloaded should trigger the same combination in downstream matrix job Key: JENKINS-13514 URL: https://issues.jenkins-ci.org/browse/JENKINS-13514 Project: Jenkins Issue Type: Improvement Components: matrix-reloaded Affects Versions: current Reporter: Dirk Haun Priority: Minor Attachments: 01-jobA.png, 02-jobB.png When rebuilding parts of a matrix job (using the matrix reloaded plugin), the build will then trigger all downstream jobs. In our case, the downstream jobs are also matrix jobs and we would like that in this case, the downstream jobs are also reloaded, i.e. only the parts that were rebuilt in the upstream job should be built there as well. To reproduce, I've used a setup that somewhat resembles what we have: - 2 matrix jobs, jobA and jobB - jobA has jobB as its downstream job - each job consists of a 3x3 matrix with the axis labelled compiler and os respectively - the compiler axis has values FORTE, GCC, MSC - the os axis has values solaris, linux, windows - the build step is just a echo hello world We're using the Parameterized Build plugin, http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to trigger downstream builds but this can also be reproduced with the standard Build other projects option. The two screenshots show the matrix and which parts are supposed to be rebuild. The second screenshot shows that jobB, when triggered by rebuilding only parts of the jobA matrix, is actually building all 9 combinations, not just the 2 of the upstream job. P.S. I mentioned this problem at the Jenkins User Conference in Paris, in case you remember :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
