incubator-kalumet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Duffy <micdu...@gmail.com>
Subject Re: [jira] [Updated] (KALUMET-36) Provide a Jenkins publisher
Date Mon, 03 Dec 2012 21:37:33 GMT
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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message