On Tue, Mar 31, 2015 at 6:54 PM, Konstantin Boudnik <c...@apache.org> wrote:

> Thanks - that's great: not I'd be able to finish up the commenting part of
> the
> patch validation!
>

Cos, I think some meaning was lost due to typos. Do you mean that you will
be able to finish it or will not?


>
> Cos
>
> On Wed, Apr 01, 2015 at 12:00AM, Sergey Bachinskiy wrote:
> >    Hello Konstantin.
> >    I've installed lira-cli on all agents (7) - path of cli is
> >    /opt/jira-cli-3.9.0
> >    On Wed, Mar 25, 2015 at 10:16 PM, Konstantin Boudnik <c...@apache.org>
> >    wrote:
> >
> >      I believe this is a different jira cli tools. The one I am using is
> 100%
> >      java
> >      - no Python nonsense (god forbids). I am talking about this
> particular
> >      version
> >
> >      A
> >
> https://bobswift.atlassian.net/wiki/download/attachments/16285777/jira-cli-3.9.0-distribution.zip?version=1&modificationDate=1401618313091&api=v2
> >
> >      It seems to be the last official atlassian version of the tools that
> >      still
> >      works with out-of-stock JIRA server. Can we get it installed?
> >
> >      Thanks,
> >      A  Cos
> >      On Wed, Mar 25, 2015 at 11:15AM, Sergey Bachinskiy wrote:
> >      >A  A  Hello Konstantin!
> >      >A  A  As I've seen jira cli tools need python 2.7 to run?
> >      >A  A  Should we have jira-cli on all build nodes?
> >      >A  A  On Wed, Mar 25, 2015 at 1:07 AM, Dmitriy Setrakyan
> >      <dsetrak...@apache.org>
> >      >A  A  wrote:
> >      >
> >      >A  A  A  Sergey B (CC'ed) is admitting these boxes. Sergey, can you
> >      please
> >      >A  A  A  respond here?
> >      >A  A  A  D.
> >      >A  A  A  On Tue, Mar 24, 2015 at 3:03 PM, Konstantin Boudnik
> >      <c...@apache.org>
> >      >A  A  A  wrote:
> >      >
> >      >A  A  A  A  Guys,
> >      >
> >      >A  A  A  A  is there any chance we can add jira-cli tools to the TC
> >      agent nodes?
> >      >A  A  A  A  It seems
> >      >A  A  A  A  that OAuth setup doesn't move anywhere yet and I want
> to
> >      finish this
> >      >A  A  A  A  patch
> >      >A  A  A  A  validation work ASAP. jira-cli tools allow an external
> >      process to
> >      >A  A  A  A  comm. with
> >      >A  A  A  A  JIRA without any fancy SOAP/REST stuff.
> >      >
> >      >A  A  A  A  Can anyone who's admin'ing these boxes ping me
> off-line so
> >      we can
> >      >A  A  A  A  complete it?
> >      >
> >      >A  A  A  A  Thanks,
> >      >A  A  A  A  AA  Cos
> >      >
> >      >A  A  A  A  On Sat, Feb 28, 2015 at 05:22AM, Konstantin Boudnik
> wrote:
> >      >A  A  A  A  > Y'all
> >      >A  A  A  A  >
> >      >A  A  A  A  > I have put together an initial version of the TC job
> that
> >      pulls in
> >      >A  A  A  A  JIRAs in PA
> >      >A  A  A  A  > state and find the latest attachment by date. It also
> >      creates and
> >      >A  A  A  A  artifact
> >      >A  A  A  A  > where all earlier processed attachments are listed to
> >      avoid
> >      >A  A  A  A  duplicated
> >      >A  A  A  A  > test runs. The job is here
> >      >A  A  A  A  >A
> >      >A  A  A  A  A
> >
> http://204.14.53.152/viewType.html?buildTypeId=Ignite_PatchValidation_Main
> >      >A  A  A  A  >
> >      >A  A  A  A  > Now, I need some advice from TC experts, as I have no
> >      experience
> >      >A  A  A  A  with it,
> >      >A  A  A  A  > really. The issue I have as this (perhaps, coming
> from my
> >      ignorance
> >      >A  A  A  A  about TC):
> >      >A  A  A  A  >AA  1. it seems that TC builds can be triggered by
> >      creating a special
> >      >A  A  A  A  remote
> >      >A  A  A  A  >AA  AA  A branch in git. That would require a job to
> do
> >      pushed to the
> >      >A  A  A  A  git, which I
> >      >A  A  A  A  >AA  AA  A am no fan of...
> >      >A  A  A  A  >AA  2. there might be a way to use some sort of
> >      meta-runner that can
> >      >A  A  A  A  fetch the
> >      >A  A  A  A  >AA  AA  A repo, create a branch using provided patch,
> and
> >      then trigger
> >      >A  A  A  A  the test-run.
> >      >A  A  A  A  >AA  AA  A I have no idea how to do it.
> >      >A  A  A  A  >AA  3. Some other unknown-unknown functionality, that
> I am
> >      evidently
> >      >A  A  A  A  missing?
> >      >A  A  A  A  >
> >      >A  A  A  A  > I would really like someone on this list with TC
> >      expertise to tell
> >      >A  A  A  A  me what's
> >      >A  A  A  A  > the preferred way of performing such workflow? E.g.
> in
> >      Jenkins I can
> >      >A  A  A  A  trigger a
> >      >A  A  A  A  > remote job with a parameter (JIRA #), which then will
> >      download the
> >      >A  A  A  A  latest
> >      >A  A  A  A  > attachment from it (7 lines of Groovy), apply it to
> the
> >      fresh repo
> >      >A  A  A  A  clone and
> >      >A  A  A  A  > run the tests. How we can do something like that in
> TC?
> >      Looking for
> >      >A  A  A  A  the
> >      >A  A  A  A  > guidance and help from this list.
> >      >A  A  A  A  >
> >      >A  A  A  A  > --
> >      >A  A  A  A  > Thanks in advance. Regards,
> >      >A  A  A  A  >AA  A Cos
> >      >A  A  A  A  >
>

Reply via email to