Hasn’t Kohskue already provided a solution that could be leveraged?
http://groovy-sandbox.kohsuke.org/ would need some work to also ask
DSLExtensions what they need to run.
Short term I am working on limiting concurrent execution of jobs in a flow
to prevent exhaustion (there is no point pulling myjob#2 from the queue
when myjob#3 is in the queue as well - think parameterised jobs and
build("myjob", upstream:build; other:fred) ). This is as a sepated plugin
for the DSL - but I have some simple fixes for JENKINS-15966, typos and
extend the DSL help (so that extensions can also display some help) that
are for the flow plugin. Hopefully I should have clearance for these
sometime next week.
/James
On Wednesday, 21 August 2013 11:03:02 UTC+1, nicolas de loof wrote:
>
>
> 2013/8/21 teilo <[email protected] <javascript:>>
>
>> Excellent - I was hoping for GPLv2 but MIT should streamline being able
>> to push patches back!
>>
>
> I've documented short term plan on
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin in case you
> have some clever solution to existing limitations ;)
>
>
>>
>> BTW - the pom.xml still references LGPL v3
>>
>> <licenses>
>> <license>
>>
>>
>>
>> <name>LGPL 3</name>
>> <url>http://www.gnu.org/licenses/lgpl.html</url>
>>
>>
>> <distribution>repo</distribution>
>> </license>
>>
>>
>> </licenses>
>>
>>
> fixed.
>
>
>>
>>
>>
>>
>>
>> On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote:
>>
>>> The plugin was initially created under AGPL, but I got approval to
>>> relicense it under MIT.
>>> https://github.com/jenkinsci/**build-flow-plugin/commit/**
>>> 022b40b86383ef678184bf6fe6497b**e033254555<https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555>
>>>
>>>
>>> 2013/8/20 teilo <[email protected]>
>>>
>>>> Hi Nicolas/Cloudbees/other buildflow contributors.
>>>>
>>>> Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3
>>>> (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3.
>>>>
>>>> Is this just an oversight when the plugin was re-licensed - or is this
>>>> really a mix?
>>>>
>>>> (also any chance of changing it to something without the GPL v3 patent
>>>> issues to make it more company friendly - even if it is dual licenced with
>>>> the Jenkins enterprise plugins) I don't ask for much do I ;-)
>>>>
>>>> /James
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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 jenkinsci-de...@**googlegroups.com.
>>>>
>>>> For more options, visit
>>>> https://groups.google.com/**groups/opt_out<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] <javascript:>.
>> 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.
