Hi Prabha, you can add a downstream job plugin in your .ci.yml . It is kind of an undocumented feature, I have it in my todo list to update the docs.
plugins: - downstream_job: orgName/repoName: BRANCH: $DOTCI_BRANCH SHA: $DOTCI_SHA DOTCI_STEP: 'smoke tests' On Tuesday, May 19, 2015 at 2:50:09 AM UTC-5, Prabaharan Gopalan wrote: > > Has anyone ever implemented a DotCi build in a pipeline? I am setting out > to create a pipeline for our projects which would ideally result in a build > being promoted via downstream jobs. If my understanding is right, since > DotCi is using Mongo all the configuration for a particular job is stored > in Mongo. (and i don't see any build specific config.xml inside my > JENKINS_HOME directory), > > If I want to add a downstream job (say using the Parameterized Trigger > plugin ) and configure it to be triggered upon successful run of a DotCi > build, how would I do that? From the docs, I understand that I should be > taking a look at the plugin starter pack (and/or use the DotCiExtension) > where needed, but is that the only option to go? (and there aren't may > plugins in that list). > > Is this even possible? One of the common way is we'd use the job-dsl > plugin to dynamically create the downstream jobs which will let us play > around with the job configuration and jenkins will know what it needs to > know from the config xml. Since DotCi by-passes the xml, is the onus on us > to manually write code to trigger the downstream jobs? > > Any help would be appreciated (and apologies if this is to novice-y). > > Thank you > Praba. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/94142e13-acda-431f-ae69-be3f620dd3dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
