Another question.
As I was asked to setup and check plc4x-vm2.apache.org ... could this be simply
be setup as PLC4X' build agent for ci-builds.apache.org?
I think then I'll be really able to setup things correctly and then we can just
turn off the old.
Chris
Am 19.07.20, 13:17 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
Hi,
could you please create the folder for the Apache PLC4X project?
Thanks,
Chris
Am 18.07.20, 20:04 schrieb "Stefan Seelmann" <m...@stefan-seelmann.de>:
Done: https://issues.apache.org/jira/browse/INFRA-20545
On 7/18/20 7:25 PM, Gavin McDonald wrote:
> Thanks Stefan,
>
> Can you create an INFRA jira ticket for this one please.
>
> On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann
<m...@stefan-seelmann.de>
> wrote:
>
>> On 7/17/20 8:41 PM, Gavin McDonald wrote:
>>>> Right now there seem to be no executors running Windows or am I
>>>> overlooking something? I assume they will be added later.
>>>>
>>>
>>> There are 2 configured as 'floating agents' meaning they are
available
>> for
>>> ci-builds and
>>> all the other project specific masters we have. Use the 'Windows'
label.
>>
>> I tried to use the in two jobs [1],[2] however it doesn't work.
>>
>> In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when
>> starting a job the state of the nodes changes to " Node on lease to
>> Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but
the
>> job never starts and the node also doesn't show up in the executors
>> list. After about one minute the status changes back to "Node
returned
>> from lease" to "Node being de-provisioned" to "Available for lease"
again.
>>
>> Kind Regards,
>> Stefan
>>
>> [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/
>> [2]
https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/
>>
>
>
