Why do we need to add useless comments from tc_commenter to JIRA issues?
They look like: tc_commenter added a comment - 2 days ago There was triggered next test builds for last attached patch-file: 01. http://204.14.53.152/viewQueued.html?itemId=88180 - Ignite AOP 02. http://204.14.53.152/viewQueued.html?itemId=88181 - Ignite AWS 03. http://204.14.53.152/viewQueued.html?itemId=88182 - Ignite Basic 04. http://204.14.53.152/viewQueued.html?itemId=88183 - Ignite Cache And if you click on provided link you will get: Queued build does not exist: 88180 Could someone fix this? -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
Why do you consider them useless?
Cos On Mon, Jun 08, 2015 at 03:44PM, Alexey Kuznetsov wrote: > Why do we need to add useless comments from tc_commenter to JIRA issues? > > They look like: > > tc_commenter added a comment - 2 days ago > There was triggered next test builds for last attached patch-file: > 01. http://204.14.53.152/viewQueued.html?itemId=88180 - Ignite AOP > 02. http://204.14.53.152/viewQueued.html?itemId=88181 - Ignite AWS > 03. http://204.14.53.152/viewQueued.html?itemId=88182 - Ignite Basic > 04. http://204.14.53.152/viewQueued.html?itemId=88183 - Ignite Cache > > And if you click on provided link you will get: > > Queued build does not exist: 88180 > > > Could someone fix this? > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com |
This comment could be a one-liner (build triggered, for example) instead of
big bunch of links that lead nowhere. On Mon, Jun 8, 2015 at 3:59 PM, Konstantin Boudnik <[hidden email]> wrote: > Why do you consider them useless? > > Cos > > On Mon, Jun 08, 2015 at 03:44PM, Alexey Kuznetsov wrote: > > Why do we need to add useless comments from tc_commenter to JIRA issues? > > > > They look like: > > > > tc_commenter added a comment - 2 days ago > > There was triggered next test builds for last attached patch-file: > > 01. http://204.14.53.152/viewQueued.html?itemId=88180 - Ignite AOP > > 02. http://204.14.53.152/viewQueued.html?itemId=88181 - Ignite AWS > > 03. http://204.14.53.152/viewQueued.html?itemId=88182 - Ignite Basic > > 04. http://204.14.53.152/viewQueued.html?itemId=88183 - Ignite Cache > > > > And if you click on provided link you will get: > > > > Queued build does not exist: 88180 > > > > > > Could someone fix this? > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
Ah, I see. So basically pointing to the umbrella build, instead of all of its
components? Yeah, I think it be nice. Don't know much about TC to make any comment on feasibility of it. Cos On Tue, Jun 09, 2015 at 06:21AM, Alexey Kuznetsov wrote: > This comment could be a one-liner (build triggered, for example) instead of > big bunch of links that lead nowhere. > > > On Mon, Jun 8, 2015 at 3:59 PM, Konstantin Boudnik <[hidden email]> wrote: > > > Why do you consider them useless? > > > > Cos > > > > On Mon, Jun 08, 2015 at 03:44PM, Alexey Kuznetsov wrote: > > > Why do we need to add useless comments from tc_commenter to JIRA issues? > > > > > > They look like: > > > > > > tc_commenter added a comment - 2 days ago > > > There was triggered next test builds for last attached patch-file: > > > 01. http://204.14.53.152/viewQueued.html?itemId=88180 - Ignite AOP > > > 02. http://204.14.53.152/viewQueued.html?itemId=88181 - Ignite AWS > > > 03. http://204.14.53.152/viewQueued.html?itemId=88182 - Ignite Basic > > > 04. http://204.14.53.152/viewQueued.html?itemId=88183 - Ignite Cache > > > > > > And if you click on provided link you will get: > > > > > > Queued build does not exist: 88180 > > > > > > > > > Could someone fix this? > > > > > > -- > > > Alexey Kuznetsov > > > GridGain Systems > > > www.gridgain.com > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com |
Free forum by Nabble | Edit this page |