bump. On Monday, August 29, 2016 at 2:59:16 PM UTC-7, Matt Hauck wrote: > > Clarification: "artifacts and output get intermingled" is confusing. I > meant to say that standard output for all the various parallel nodes gets > intermingled. Something like this: > > [ windowsNode ] Doing some stuff >> [ linuxNode ] Doing different stuff >> [ macNode ] yet more stuff > > > It also seems that artifacts (whether files or test results) also get > intermingled and centralized rather than kept separate in connection to the > node they were built on. This point I am less clear on though. > > On Monday, August 29, 2016 at 2:46:55 PM UTC-7, Matt Hauck wrote: >> >> Hello! My team is looking to move to jenkins2 and struggling a bit with >> how to do a multip-platform build. I'm really excited about the direction >> it is moving in with the pipline builds -- I implemented something like >> this myself (github.com/tanium/pyjenkins), but glad to see something >> better being built directly into the platform. >> >> One difficulty I've run into so far is the less-than-ideal for >> multi-platform builds with pipelines. We have a build that needs to run in >> windows, linux, mac, etc. Right now we have this setup with a matrix job. >> The only way I can see to do this with the pipeline plugin is using >> `parallel` (i.e. >> https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#creating-multiple-threads >> ) >> >> However, there is one rather large setback of doing it this way: *artifacts >> and output get intermingled.* >> >> It is pretty crucial to us to be able to quickly and clearly tell which >> platform the build failed on, as well as to distinguish the artifacts from >> platform from the artifacts from another platform. I have the build >> currently running with `parallel` steps, but I find it really really >> difficult to find out what the build is doing either while running or after >> it finishes. >> >> Also, there does not appear to be an option to setup an older-style >> matrix build that uses the Jenkinsfile for its execution (for >> understandable reasons), so I don't even see a way to move forward >> incrementally until multi-platform builds have better support. >> >> I should also say that the matrix job is a really awesome feature of >> jenkins that, from a survey of other build systems I did once, is kinda >> unique to jenkins. Support for having the exact same build definition >> across that executes across multiple platforms does not really exist >> outside the matrix job definition in Jenkins, as far as I could tell. It >> would be sad to see this great feature become a second-class citizen that >> can't use all the cool shiny new toys. >> >> Are there plans to add better support for multi-platform builds / matrix >> jobs? Is there something I'm missing? >> >
-- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/590bc49a-1f19-467c-8246-80b8a09ef8ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
