[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#659908: marked as done (RFP: jenkins-parametrized-trigger-plugin -- Triggers new Jenkins builds when a build has completed)

Your message dated Tue, 10 Jul 2018 16:20:31 +0000
with message-id <E1fcvNP-0000X9-Lp@quantz.debian.org>
and subject line closing RFP: jenkins-parametrized-trigger-plugin -- Triggers new Jenkins builds when a build has completed
has caused the Debian Bug report #659908,
regarding RFP: jenkins-parametrized-trigger-plugin -- Triggers new Jenkins builds when a build has completed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
659908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659908
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org

--- Please fill out the fields below. ---

   Package name: jenkins-parametrized-trigger-plugin
        Version: 2.13
Upstream Author: Kohsuke Kawaguchi and others
        License: MIT
    Description: Triggers new Jenkins builds when a build has completed

 This plugin lets you trigger new builds when your build has completed, with
 various ways of specifying parameters for the new build.
 .
 You can add multiple configurations: each has a list of projects to trigger,
 a condition for when to trigger them (based on the result of the current
 build), and a parameters section.
 .
 The parameters section can contain a combination of one or more of
 the following:
 .
  * a set of predefined properties
  * properties from a properties file read from the workspace of the triggering
    build
  * the parameters of the current build
  * "Subversion revision": makes sure the triggered projects are built with the
    same revision(s) of the triggering build. You still have to make sure those
    projects are actually configured to checkout the right Subversion URLs.
 .
 The parameter section is itself pluggable, and other plugins can contribute
 other sources of parameters.
 .
 This triggering mechanism can be used both as a post-build step or as a build
 step, in which case you can also block for the completion of the triggered
 builds. This lets you create a "function call" like semantics.

--- End Message ---
--- Begin Message --- 
RFP 659908 has no visible progress for a long time, so closing.

--- End Message ---
Reply to: