[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: DeployConfig and Jobs



Deployment hooks *could* be abused to do this.  We've certainly had
requests to run jobs when an image change happens.  We could allow the
upcoming ScheduledJobs to be triggered by images.

On Tue, Jan 26, 2016 at 4:34 PM, Philippe Lafoucrière
<philippe lafoucriere tech-angels com> wrote:
> Hi,
>
> I'm wondering if deploying a Job with a DC is something planned in the
> future?
> We have some one-shot tasks (db migrations, cache flush, etc.) to execute
> based on ImageChange trigger, and apparently, there's no way to achieve
> that.
> Creating a job is basically creating a new resource, so the policy needed
> for that is at least system:deployment-controller (or something similar).
> I'm not fond of letting a CI server create / delete resources directly, so
> I'd like to stick to system:image-builder only.
> Currently, I'm thinking of running the job with a non-exit option, which
> would allow the process to be shipped with builds, or ImageChanges.
> Is there a simpler way to to do that?
>
> Thanks,
> Philippe
>
> _______________________________________________
> users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]