On 25 September 2013 15:22, Vincent Latombe <[email protected]>wrote:
> Hi Stephen, > > as you have noticed, I started to play with the plugin, I totally agree > that it has tremendous potential and this will be the foundation for many > improvements in Jenkins. > > I have an open question concerning how to handle several 'ways' of > building the same project. In the given examples, there are 'build' and > 'release' mentioned. > > Well there are three aspects I see to this: 1. The "tasks" aspect. Wherein the job says "We support the following 'task' sections: ..." this will result in essentially build promotions being available for each branch 2. The marker file aspect. Since each job can define a different marker file base-name, you could use different marker files for different build flavours. 3. I have yet to add the UI, but you can change the keyword(s) for the "environments" and "build" sections, so you could have a "integration test environment" section and a "integration test" section in a separate job. I am open to suggestions for other alternatives. > On a broader perspective, for a given project, you could have a build, > test, integration-test jobs. These seem different from the 'environments' > which relate to what is done with matrix jobs. > > How do you think this could be done with literate? I have seen build > profiles, but these seem to apply only to defined agents, I don't think > they are mentioned in build definition. There is also a chaining problem > (usually you'd like build -> test -> integration-test in sequence) > w.r.t. the chaining problem, I believe that the interrelationship between Jenkins jobs is not something that should be maintained in the source code SCM... (now if you get into complex build pipelines, the pipeline should be in SCM, but not the SCM of any one "node" in the pipeline) Thus I think that the interrelationship between Jenkins jobs should be expressed within Jenkins itself. I see Branch Properties to support the traditional upstream/downstream relationship between jobs (only reflecting the branch and (since we have it with multi-branch) the SCM revision) > > In any case, this is really great stuff, this will be a revolution when > this hits mainstream ;) > Yes, that is my belief too, but you can see that it has a few small rough edges right now! > > > Vincent > > > 2013/9/21 Jesse Glick <[email protected]> > >> On Fri, Sep 20, 2013 at 7:38 PM, Stephen Connolly >> <[email protected]> wrote: >> > This update center: >> > >> > http://updates.jenkins-ci.org/experimental/ >> > >> > contains the alpha and beta releases >> >> In case it was not clear, there are already beta releases of the five >> aforementioned plugins on this UC, so you do not need to build from >> source if you just want to play around. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" 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. >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" 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. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
