You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kalumet-dev@incubator.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/06/08 07:33:27 UTC
[jira] [Created] (KALUMET-36) Provide a Jenkins publisher
Jean-Baptiste Onofré created KALUMET-36:
-------------------------------------------
Summary: Provide a Jenkins publisher
Key: KALUMET-36
URL: https://issues.apache.org/jira/browse/KALUMET-36
Project: Kalumet
Issue Type: New Feature
Components: agent
Reporter: Jean-Baptiste Onofré
Fix For: 0.6-incubating
It can be great to "synchronize" the Jenkins continuous integration tool.
Currently, it's asynchronous: the continuous integration tool build an artifact and Kalumet deploys it at one time (when the user request an update or when the scheduler launch an update).
Providing a Jenkins publisher, Jenkins can fire update on an environment or an application. So the deployment is synchronized (chained) with the build chain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Updated] (KALUMET-36) Provide a Jenkins publisher
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Mike,
thanks for the update. I'm preparing Kalumet 0.6-incubating release, and
I moved most of the Jira to 0.7-incubating version.
So, we can commit your code on trunk just after the release.
Regards
JB
On 12/03/2012 10:37 PM, Michael Duffy wrote:
> JB,
>
> I have something I can contribute for this that allows you to choose an
> environment from inside Jenkins / Hudson which then can be used as a "build
> step" to initiate a deploy of a Kalumet environment.
>
> Will send to u this evening.
>
> Regards,
>
> Mike.
>
> On Mon, Dec 3, 2012 at 11:45 PM, Jean-Baptiste Onofré (JIRA) <
> jira@apache.org> wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/KALUMET-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Jean-Baptiste Onofré updated KALUMET-36:
>> ----------------------------------------
>>
>> Fix Version/s: (was: 0.6-incubating)
>> 0.7-incubating
>>
>>> Provide a Jenkins publisher
>>> ---------------------------
>>>
>>> Key: KALUMET-36
>>> URL: https://issues.apache.org/jira/browse/KALUMET-36
>>> Project: Kalumet
>>> Issue Type: New Feature
>>> Components: agent
>>> Reporter: Jean-Baptiste Onofré
>>> Fix For: 0.7-incubating
>>>
>>>
>>> It can be great to "synchronize" the Jenkins continuous integration tool.
>>> Currently, it's asynchronous: the continuous integration tool build an
>> artifact and Kalumet deploys it at one time (when the user request an
>> update or when the scheduler launch an update).
>>> Providing a Jenkins publisher, Jenkins can fire update on an environment
>> or an application. So the deployment is synchronized (chained) with the
>> build chain.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [jira] [Updated] (KALUMET-36) Provide a Jenkins publisher
Posted by Michael Duffy <mi...@gmail.com>.
JB,
I have something I can contribute for this that allows you to choose an
environment from inside Jenkins / Hudson which then can be used as a "build
step" to initiate a deploy of a Kalumet environment.
Will send to u this evening.
Regards,
Mike.
On Mon, Dec 3, 2012 at 11:45 PM, Jean-Baptiste Onofré (JIRA) <
jira@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/KALUMET-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Jean-Baptiste Onofré updated KALUMET-36:
> ----------------------------------------
>
> Fix Version/s: (was: 0.6-incubating)
> 0.7-incubating
>
> > Provide a Jenkins publisher
> > ---------------------------
> >
> > Key: KALUMET-36
> > URL: https://issues.apache.org/jira/browse/KALUMET-36
> > Project: Kalumet
> > Issue Type: New Feature
> > Components: agent
> > Reporter: Jean-Baptiste Onofré
> > Fix For: 0.7-incubating
> >
> >
> > It can be great to "synchronize" the Jenkins continuous integration tool.
> > Currently, it's asynchronous: the continuous integration tool build an
> artifact and Kalumet deploys it at one time (when the user request an
> update or when the scheduler launch an update).
> > Providing a Jenkins publisher, Jenkins can fire update on an environment
> or an application. So the deployment is synchronized (chained) with the
> build chain.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
[jira] [Updated] (KALUMET-36) Provide a Jenkins publisher
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KALUMET-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KALUMET-36:
----------------------------------------
Fix Version/s: (was: 0.6-incubating)
0.7-incubating
> Provide a Jenkins publisher
> ---------------------------
>
> Key: KALUMET-36
> URL: https://issues.apache.org/jira/browse/KALUMET-36
> Project: Kalumet
> Issue Type: New Feature
> Components: agent
> Reporter: Jean-Baptiste Onofré
> Fix For: 0.7-incubating
>
>
> It can be great to "synchronize" the Jenkins continuous integration tool.
> Currently, it's asynchronous: the continuous integration tool build an artifact and Kalumet deploys it at one time (when the user request an update or when the scheduler launch an update).
> Providing a Jenkins publisher, Jenkins can fire update on an environment or an application. So the deployment is synchronized (chained) with the build chain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira