Pavel, I think that script should be stored inside TeamCity task.
On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn <ptupit...@gridgain.com> wrote: > Anton, good idea, the script can be stored in git this way. Dmitriy, what > do you think? > > Another question is the email account to send from. Do we have something > suitable already? > > > > On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov <avinogra...@gridgain.com > > > wrote: > > > Folks, > > > > we can create TeamCity task with special trigger (eg. once a day). > > This task can contains any script. > > > > On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn <ptupit...@gridgain.com> > > wrote: > > > > > Raul, I'm not good with shell scripts. As a .net person I was thinking > > > about a scheduled C# script on one of our TeamCity win machines, but > > Dmitry > > > prefers Jenkins. > > > > > > > > > On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani <ra...@apache.org> > wrote: > > > > > > > I believe all we need is a shell script in our source tree that > queries > > > the > > > > JIRA API and produces an output on stdout. > > > > > > > > We can then schedule an overnight job with, e.g. a 0 23 * * * cron > > > > expression, and configure the output to be sent to the ML, as > indicated > > > > here: https://wiki.apache.org/general/Jenkins. > > > > > > > > @Pavel, would you like to work on the shell script? I can help you > > > > configure the JKS job. > > > > > > > > @Dmitriy, can you add both Pavel and me as job admins? > > > > > > > > > > > > > > https://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson#How_do_I_get_an_account > > > > > > > > Cheers, > > > > > > > > > >
