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 "Michael Duffy (JIRA)" <ji...@apache.org> on 2013/08/16 02:00:49 UTC

[jira] [Commented] (KALUMET-36) Provide a Jenkins publisher

    [ https://issues.apache.org/jira/browse/KALUMET-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741812#comment-13741812 ] 

Michael Duffy commented on KALUMET-36:
--------------------------------------

Please assign this to me JB
                
> 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