incubator-kalumet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KALUMET-36) Provide a Jenkins publisher
Date Mon, 03 Dec 2012 12:45:58 GMT

     [ 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

Mime
View raw message