|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Sorry for shutting you down too soon.
It looks like you are trying to implement a divide-and-conquer strategy for a huge job that's controlled by FinalBuilder. The easiest way to have Jenkins break it down, is to hand the responsibility of the execution over to Jenkins.
Your first suggestion, to add a prefix to each line in the console output based on the current project being compiled makes me think that in order to do that Jenkins would have to know what project is being compiled - but since your using FinalBuilder - which is then creating the output for that particular compilation, makes me think that it's really FinalBuilder that should do the pre-fix.
Where does the Project name you want in the pre-fix come from?
You second suggestion, to update the job description during runtime with the project being build would require a plugin, that knew the
name of the project - But isn't it FinalBuilder who knows what is currently being build?
The way I see it, wrapping it all up in one-big-FinalBuilder job is really what needs to be broken down.
Maybe I'm missing your points. If you thing I am, then please throw some examples (screen shorts, logs, configurations) to clarify, what you are trying to achieve.