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