Hello Konstantin!
As I've seen jira cli tools need python 2.7 to run?
Should we have jira-cli on all build nodes?

On Wed, Mar 25, 2015 at 1:07 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Sergey B (CC'ed) is admitting these boxes. Sergey, can you please respond
> here?
>
> D.
>
> On Tue, Mar 24, 2015 at 3:03 PM, Konstantin Boudnik <c...@apache.org>
> wrote:
>
>> Guys,
>>
>> is there any chance we can add jira-cli tools to the TC agent nodes? It
>> seems
>> that OAuth setup doesn't move anywhere yet and I want to finish this patch
>> validation work ASAP. jira-cli tools allow an external process to comm.
>> with
>> JIRA without any fancy SOAP/REST stuff.
>>
>> Can anyone who's admin'ing these boxes ping me off-line so we can
>> complete it?
>>
>> Thanks,
>>   Cos
>>
>> On Sat, Feb 28, 2015 at 05:22AM, Konstantin Boudnik wrote:
>> > Y'all
>> >
>> > I have put together an initial version of the TC job that pulls in
>> JIRAs in PA
>> > state and find the latest attachment by date. It also creates and
>> artifact
>> > where all earlier processed attachments are listed to avoid duplicated
>> > test runs. The job is here
>> >
>> http://204.14.53.152/viewType.html?buildTypeId=Ignite_PatchValidation_Main
>> >
>> > Now, I need some advice from TC experts, as I have no experience with
>> it,
>> > really. The issue I have as this (perhaps, coming from my ignorance
>> about TC):
>> >  1. it seems that TC builds can be triggered by creating a special
>> remote
>> >     branch in git. That would require a job to do pushed to the git,
>> which I
>> >     am no fan of...
>> >  2. there might be a way to use some sort of meta-runner that can fetch
>> the
>> >     repo, create a branch using provided patch, and then trigger the
>> test-run.
>> >     I have no idea how to do it.
>> >  3. Some other unknown-unknown functionality, that I am evidently
>> missing?
>> >
>> > I would really like someone on this list with TC expertise to tell me
>> what's
>> > the preferred way of performing such workflow? E.g. in Jenkins I can
>> trigger a
>> > remote job with a parameter (JIRA #), which then will download the
>> latest
>> > attachment from it (7 lines of Groovy), apply it to the fresh repo
>> clone and
>> > run the tests. How we can do something like that in TC? Looking for the
>> > guidance and help from this list.
>> >
>> > --
>> > Thanks in advance. Regards,
>> >   Cos
>> >
>>
>
>

Reply via email to