me attention.
>> >>>>>>>>
>> >>>>>>>> There are two things basing on my research:
>> >>>>>>>>
>> >>>>>>>> data uploaded by performance and load tests by the jobs,
>> directly to the infl
ce and load tests by the jobs, directly
> to the influx DB - that should be handled automatically as new jobs will
> upload the same data in the same way
> >>>>>>>> data fetched using Jenkins API by the metrics tool
> (syncjenkins.py) - here the situation is a
>>>>>> the influx DB - that should be handled automatically as new jobs will
>>>>>>>> upload the same data in the same way
>>>>>>>> data fetched using Jenkins API by the metrics tool (syncjenkins.py) -
>>>>>>>> here
ns.py) - here the situation is a bit more complex as the
>>>>>>> script
>>>>>>>relies on the build number (it's used actually as a time reference
>>>>>>> and
>>>>>>>primary key in the DB is creat
ld
>>>>>> number I've
>>>>>>just "fast-forwarded" the numbers on the new
>>>>>>https://ci-beam.apache.org to follow current numbering from the
>>>>>>old CI. Therefore simple replacement of the Jenkins URL in the metrics
>
ry key in the DB is created from it). To avoid refactoring of the
>>>>>>script and database migration to use timestamp instead of build
>>>>>> number I've
>>>>>>just "fast-forwarded" the numbers on the new
>>>>>>
tps://ci-beam.apache.org to follow current numbering from the
>>>>>old CI. Therefore simple replacement of the Jenkins URL in the metrics
>>>>>scripts should do the trick to have continuous metrics data. I'll check
>>>>>that tomorrow on my local grafana instance
in the metrics
>>>> scripts
>>>>should do the trick to have continuous metrics data. I'll check that
>>>>tomorrow on my local grafana instance.
>>>>
>>>> Please let me know if there's anything that I missed.
>>>&
w on my local grafana instance.
>>>
>>> Please let me know if there's anything that I missed.
>>>
>>> Regards,
>>> Damian
>>>
>>> On Mon, Jun 15, 2020 at 8:05 PM Alexey Romanenko <
>>> aromanenko@gmail.com> wrote:
Please let me know if there's anything that I missed.
>>
>> Regards,
>> Damian
>>
>> On Mon, Jun 15, 2020 at 8:05 PM Alexey Romanenko <
>> aromanenko....@gmail.com> wrote:
>>
>>> Great! Thank you for working on this and letting us know.
>
tance.
>
> Please let me know if there's anything that I missed.
>
> Regards,
> Damian
>
> On Mon, Jun 15, 2020 at 8:05 PM Alexey Romanenko
> wrote:
>
>> Great! Thank you for working on this and letting us know.
>>
>> On 12 Jun 2020, at 16:58, Damia
u for working on this and letting us know.
>
> On 12 Jun 2020, at 16:58, Damian Gadomski
> wrote:
>
> Hello,
>
> During the last few days, I was preparing for the Beam Jenkins migration
> from builds.apache.org to ci-beam.apache.org. The new Jenkins Master will
> be dedica
Great! Thank you for working on this and letting us know.
> On 12 Jun 2020, at 16:58, Damian Gadomski wrote:
>
> Hello,
>
> During the last few days, I was preparing for the Beam Jenkins migration from
> builds.apache.org <http://builds.apache.org/> to ci-beam.
t 9:57 AM Tyson Hamilton wrote:
>
>> Very exciting! Thanks for the advanced notice Damian.
>>
>> On Fri, Jun 12, 2020 at 7:58 AM Damian Gadomski <
>> damian.gadom...@polidea.com> wrote:
>>
>>> Hello,
>>>
>>> During the last
AM Damian Gadomski <
> damian.gadom...@polidea.com> wrote:
>
>> Hello,
>>
>> During the last few days, I was preparing for the Beam Jenkins migration
>> from builds.apache.org to ci-beam.apache.org. The new Jenkins Master
>> will be dedicated only for Beam r
Very exciting! Thanks for the advanced notice Damian.
On Fri, Jun 12, 2020 at 7:58 AM Damian Gadomski
wrote:
> Hello,
>
> During the last few days, I was preparing for the Beam Jenkins migration
> from builds.apache.org to ci-beam.apache.org. The new Jenkins Master will
> be
Hello,
During the last few days, I was preparing for the Beam Jenkins migration
from builds.apache.org to ci-beam.apache.org. The new Jenkins Master will
be dedicated only for Beam related jobs, all Beam Committers will have
build configure access, and Beam PMC will have Admin (GUI) Access.
We
17 matches
Mail list logo
