Hi, Have you been able to solve this problem? I am facing the same challenge too. I have tried to use copy-to-slave plugin to copy the properties file back to the Master. The file did copy back into Master, but it is located under .jenkins/jobs/<job name>/configurations/<axis>/<axis value>/<depends on how many axis you have>/workspace. The job itself on Master doesn't actually have a "workspace" created.
The only way I currently can think of is to create another upstream job to pre-determine the job name and then pass that as a parameter down to the matrix job... Let me know if you have a better solution :) Jeannie On Monday, November 5, 2012 12:17:49 PM UTC-8, Masariello wrote: > > Hi there > > I'm using the Build Name Setter plugin with a Matrix project to pick up a > version string from a build.properties file. > The right value of the version string is generated by my build script. > > This is because we keep the MAJOR and MINOR version numbers in svn. The > build scripts make sure those numbers get propagated to every file where > the build needs them. The version that ends up in the build.properties file > is really just MAJOR_VERSION.MINOR_VERSION.SOME_OTHER_VERSION.SVN_REVISION. > > The problem is that the build scripts are not run at all for the master > project of a Matrix job (multi-config), so the master does not get sensible > names for the list of builds. > > Is there any way to have the master project pick up the build.properties > of one of the config-specific jobs or some other sensible value? (e.g. just > use the Jenkins build nr for that) > > Thanks in advance! > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
