Credentials

2020-07-19 Thread Gavin McDonald
Hi All,

There are a lot of credentials stored on builds.a.o - likely the majority
are now
not in use.

For those that need migrating to the new Master(s) - the majority of those
you
should be able to recreate on your own.

For the remainder, like role accounts etc, or for those which you
can't find the
secrets for, that are needed on the new Master(s), please either file an
INFRA Jira ticket or reply to this new thread.

Thanks

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread Christofer Dutz
Hi,

could you please create the folder for the Apache PLC4X project?

Thanks,

Chris

Am 18.07.20, 20:04 schrieb "Stefan Seelmann" :

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 
> 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/
>>
> 
> 




Re: [ci-builds] - New Project Folder requests

2020-07-19 Thread Christofer Dutz
Please create a folder for "PLC4X"

Thanks,
Chris

Am 18.07.20, 12:12 schrieb "Gavin McDonald" :

Hi All,

The Migrations thread is getting a bit large, so please any
new requests for Project Folder requests please either open
a new INFRA jira ticket or reply to this new thread

Thanks

-- 
*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team



Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread Christofer Dutz
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" :

Hi,

could you please create the folder for the Apache PLC4X project?

Thanks,

Chris

Am 18.07.20, 20:04 schrieb "Stefan Seelmann" :

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 

> 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/
>>
> 
> 





Re: Credentials

2020-07-19 Thread Dmytro Grinenko
I would need the credentials associated with Ambari tasks and if possible -
exported tasks as well. It should help me to restore them on new master

On Sun, Jul 19, 2020, 1:59 PM Gavin McDonald  wrote:

> Hi All,
>
> There are a lot of credentials stored on builds.a.o - likely the majority
> are now
> not in use.
>
> For those that need migrating to the new Master(s) - the majority of those
> you
> should be able to recreate on your own.
>
> For the remainder, like role accounts etc, or for those which you
> can't find the
> secrets for, that are needed on the new Master(s), please either file an
> INFRA Jira ticket or reply to this new thread.
>
> Thanks
>
> --
>
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team
>


Re: Credentials

2020-07-19 Thread Gavin McDonald
Hi,

On Sun, Jul 19, 2020 at 4:48 PM Dmytro Grinenko
 wrote:

> I would need the credentials associated with Ambari tasks and if possible -
> exported tasks as well. It should help me to restore them on new master
>

Do you know the names of these credentials? Or at least a link to the jobs
that currently
use them?

There are several hundred to go through otherwise.



>
> On Sun, Jul 19, 2020, 1:59 PM Gavin McDonald  wrote:
>
> > Hi All,
> >
> > There are a lot of credentials stored on builds.a.o - likely the majority
> > are now
> > not in use.
> >
> > For those that need migrating to the new Master(s) - the majority of
> those
> > you
> > should be able to recreate on your own.
> >
> > For the remainder, like role accounts etc, or for those which you
> > can't find the
> > secrets for, that are needed on the new Master(s), please either file an
> > INFRA Jira ticket or reply to this new thread.
> >
> > Thanks
> >
> > --
> >
> > *Gavin McDonald*
> > Systems Administrator
> > ASF Infrastructure Team
> >
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re[2]: Credentials

2020-07-19 Thread Dmitry Grinenko

Hi,

Unfortunate, i have no knowledge on all jobs existed, but have link to 
most important one:

-  https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/

Now it not working, but there is a job name as part of url. I guess, if 
there were another jobs, they should be prefixed as Ambari-* too



Thanks!


-- Original Message --
From: "Gavin McDonald" 
To: hadoop-migrati...@infra.apache.org
Cc: "builds" 
Sent: 7/19/2020 6:17:01 PM
Subject: Re: Credentials


Hi,

On Sun, Jul 19, 2020 at 4:48 PM Dmytro Grinenko
 wrote:


 I would need the credentials associated with Ambari tasks and if possible -
 exported tasks as well. It should help me to restore them on new master



Do you know the names of these credentials? Or at least a link to the jobs
that currently
use them?

There are several hundred to go through otherwise.





 On Sun, Jul 19, 2020, 1:59 PM Gavin McDonald  wrote:

 > Hi All,
 >
 > There are a lot of credentials stored on builds.a.o - likely the majority
 > are now
 > not in use.
 >
 > For those that need migrating to the new Master(s) - the majority of
 those
 > you
 > should be able to recreate on your own.
 >
 > For the remainder, like role accounts etc, or for those which you
 > can't find the
 > secrets for, that are needed on the new Master(s), please either file an
 > INFRA Jira ticket or reply to this new thread.
 >
 > Thanks
 >
 > --
 >
 > *Gavin McDonald*
 > Systems Administrator
 > ASF Infrastructure Team
 >




--

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team




Re: Re[2]: Credentials

2020-07-19 Thread Gavin McDonald
Hi ,

On Sun, Jul 19, 2020 at 5:24 PM Dmitry Grinenko
 wrote:

> Hi,
>
> Unfortunate, i have no knowledge on all jobs existed, but have link to
> most important one:
> -  https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/
>
> Now it not working, but there is a job name as part of url. I guess, if
> there were another jobs, they should be prefixed as Ambari-* too
>

Ok, so I found one credential (Github...asfbot) used by that job and copied
it over to
the new Master(s).



>
> Thanks!
>
>
> -- Original Message --
> From: "Gavin McDonald" 
> To: hadoop-migrati...@infra.apache.org
> Cc: "builds" 
> Sent: 7/19/2020 6:17:01 PM
> Subject: Re: Credentials
>
> >Hi,
> >
> >On Sun, Jul 19, 2020 at 4:48 PM Dmytro Grinenko
> > wrote:
> >
> >>  I would need the credentials associated with Ambari tasks and if
> possible -
> >>  exported tasks as well. It should help me to restore them on new master
> >>
> >
> >Do you know the names of these credentials? Or at least a link to the jobs
> >that currently
> >use them?
> >
> >There are several hundred to go through otherwise.
> >
> >
> >
> >>
> >>  On Sun, Jul 19, 2020, 1:59 PM Gavin McDonald 
> wrote:
> >>
> >>  > Hi All,
> >>  >
> >>  > There are a lot of credentials stored on builds.a.o - likely the
> majority
> >>  > are now
> >>  > not in use.
> >>  >
> >>  > For those that need migrating to the new Master(s) - the majority of
> >>  those
> >>  > you
> >>  > should be able to recreate on your own.
> >>  >
> >>  > For the remainder, like role accounts etc, or for those which you
> >>  > can't find the
> >>  > secrets for, that are needed on the new Master(s), please either
> file an
> >>  > INFRA Jira ticket or reply to this new thread.
> >>  >
> >>  > Thanks
> >>  >
> >>  > --
> >>  >
> >>  > *Gavin McDonald*
> >>  > Systems Administrator
> >>  > ASF Infrastructure Team
> >>  >
> >>
> >
> >
> >--
> >
> >*Gavin McDonald*
> >Systems Administrator
> >ASF Infrastructure Team
>
>

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread Gavin McDonald
Hi Chris,

On Sun, Jul 19, 2020 at 2:02 PM Christofer Dutz 
wrote:

> 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.
>

Please create a new INFRA ticket to have this VM set up as a dedicated
agent for the plc4x project


>
> Chris
>
>
>
> Am 19.07.20, 13:17 schrieb "Christofer Dutz" :
>
> Hi,
>
> could you please create the folder for the Apache PLC4X project?
>
> Thanks,
>
> Chris
>
> Am 18.07.20, 20:04 schrieb "Stefan Seelmann"  >:
>
> 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/
> >>
> >
> >
>
>
>
>

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread Gavin McDonald
I think these days Maxim you login to Sonarcloud.io with your github creds
and create a personal token

On Sat, Jul 18, 2020 at 1:36 PM Maxim Solodovnik 
wrote:

> The only credentials I can see in drop-down is GitHub PR Builder asf-ci
> Token
> no Sonar token :((
>
> On Sat, 18 Jul 2020 at 16:51, Gavin McDonald  wrote:
>
>> Hi Maxim,
>>
>> On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik 
>> wrote:
>>
>>> Hello Gavin,
>>>
>>> It seems sonar integration is missing (Credentials dropdown for sonar is
>>> missing)
>>>
>>
>> Try again please.
>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>
>>
>> --
>> *Gavin McDonald*
>> Systems Administrator
>> ASF Infrastructure Team
>>
>>
>
> --
> Best regards,
> Maxim
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [ci-infra] - Plugin Installations

2020-07-19 Thread P. Ottlinger
Hi,
not sure if it's a plugin but the new Jenkins seems to lack the
"Abort if build is stuck" option, the old one had.

Thanks,
Phil

Am 18.07.20 um 12:09 schrieb Gavin McDonald:
> Hi All,
> 
> The other thread is getting a bit large, lets try and stop posting there.
> 
> For new plugin installation requests please either file an INFRA Jira
> ticket or reply to this new thread.
> 
> Over the next couple of weeks, I will ensure plugins get installed timely
> so you can continue testing the new system and getting your jobs
> to work.
> 



Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread P. Ottlinger
Hi Gav,

Am 17.07.20 um 21:56 schrieb Gavin McDonald:
>> can you create a Creadur as well with the right to create jobs for all
>> PMC-members?
>>
> 
> Done, but I extended the scope slightly to all Creadur Committers - I dont
> see
> why this should just be PMC Members creating Jenkins jobs, please do let
> me know if I did the wrong thing there.

Everything is fine, thanks.

All older Creadur-jobs had the label to only run on "ubuntu" nodes - in
order to ease the setup I tried to not restrict where builds are
running, but this doesn't seem to speed up build time.

Should I add "ubuntu" to node restrictions or is the new Jenkins just
lacking build nodes?

Thanks,
Phil


Re: [ci-infra] - Plugin Installations

2020-07-19 Thread Olivier Lamy
Hi Gav
We need a plugin to scan gitbox repos and create projects based on git repo
names.
See https://issues.apache.org/jira/browse/INFRA-20544

On Mon, 20 Jul 2020 at 05:31, P. Ottlinger  wrote:

> Hi,
> not sure if it's a plugin but the new Jenkins seems to lack the
> "Abort if build is stuck" option, the old one had.
>
> Thanks,
> Phil
>
> Am 18.07.20 um 12:09 schrieb Gavin McDonald:
> > Hi All,
> >
> > The other thread is getting a bit large, lets try and stop posting there.
> >
> > For new plugin installation requests please either file an INFRA Jira
> > ticket or reply to this new thread.
> >
> > Over the next couple of weeks, I will ensure plugins get installed timely
> > so you can continue testing the new system and getting your jobs
> > to work.
> >
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: [ci-infra] - Plugin Installations

2020-07-19 Thread Gavin McDonald
Hi Phil,

On Sun, Jul 19, 2020 at 9:31 PM P. Ottlinger  wrote:

> Hi,
> not sure if it's a plugin but the new Jenkins seems to lack the
> "Abort if build is stuck" option, the old one had.
>

Fixed by adding the Build Timeout plugin :)



>
> Thanks,
> Phil
>
> Am 18.07.20 um 12:09 schrieb Gavin McDonald:
> > Hi All,
> >
> > The other thread is getting a bit large, lets try and stop posting there.
> >
> > For new plugin installation requests please either file an INFRA Jira
> > ticket or reply to this new thread.
> >
> > Over the next couple of weeks, I will ensure plugins get installed timely
> > so you can continue testing the new system and getting your jobs
> > to work.
> >
>
>

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [ci-infra] - Plugin Installations

2020-07-19 Thread Gavin McDonald
Hi Olivier,

On Sun, Jul 19, 2020 at 10:51 PM Olivier Lamy  wrote:

> Hi Gav
> We need a plugin to scan gitbox repos and create projects based on git repo
> names.
> See https://issues.apache.org/jira/browse/INFRA-20544


that ticket is for OpenMeetings - which project do you need it for ?

What type of 'project' are you creating for this (Organisation or something
else)

Can you link me the current version in builds.a.o

Thanks


>
>
> On Mon, 20 Jul 2020 at 05:31, P. Ottlinger  wrote:
>
> > Hi,
> > not sure if it's a plugin but the new Jenkins seems to lack the
> > "Abort if build is stuck" option, the old one had.
> >
> > Thanks,
> > Phil
> >
> > Am 18.07.20 um 12:09 schrieb Gavin McDonald:
> > > Hi All,
> > >
> > > The other thread is getting a bit large, lets try and stop posting
> there.
> > >
> > > For new plugin installation requests please either file an INFRA Jira
> > > ticket or reply to this new thread.
> > >
> > > Over the next couple of weeks, I will ensure plugins get installed
> timely
> > > so you can continue testing the new system and getting your jobs
> > > to work.
> > >
> >
> >
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: [IMPORTANT] - Migration to ci-builds.a.o

2020-07-19 Thread Gavin McDonald
Hi Phil,

On Sun, Jul 19, 2020 at 9:32 PM P. Ottlinger  wrote:

> Hi Gav,
>
> Am 17.07.20 um 21:56 schrieb Gavin McDonald:
> >> can you create a Creadur as well with the right to create jobs for all
> >> PMC-members?
> >>
> >
> > Done, but I extended the scope slightly to all Creadur Committers - I
> dont
> > see
> > why this should just be PMC Members creating Jenkins jobs, please do let
> > me know if I did the wrong thing there.
>
> Everything is fine, thanks.
>
> All older Creadur-jobs had the label to only run on "ubuntu" nodes - in
> order to ease the setup I tried to not restrict where builds are
> running, but this doesn't seem to speed up build time.
>

hm, I'd like to know more about what is happening here, what do you mean
by 'speed up build time' ? My wild guess is that by not limiting the pool
of
available exexutors by choosing a label means a shorter build time? Not
really, it may make grab an executor quicker if the conditions are right,
but
actual build time on an agent after that should be the same.

>
> Should I add "ubuntu" to node restrictions or is the new Jenkins just
> lacking build nodes?
>

Unless your build works on Windows then I would choose the 'ubuntu' label.
99% of all agents on the new ci-builds.a.o will be 'ubuntu'

Currently we have 4 agents totalling 8 executors, and I haven't see any
build
up of a queue yet, mostly they have been pretty much idle so lack of
build agents/nodes is not an issue currently.

HTH

>
> Thanks,
> Phil
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team


Re: Credentials

2020-07-19 Thread Akira Ajisaka
HI Gavin,

I would need JIRA_PASSWORD in the precommit job (
https://builds.apache.org/job/PreCommit-HADOOP-Build/) to be copied to the
new master.

Thanks,
Akira

On Sun, Jul 19, 2020 at 7:59 PM Gavin McDonald  wrote:

> Hi All,
>
> There are a lot of credentials stored on builds.a.o - likely the majority
> are now
> not in use.
>
> For those that need migrating to the new Master(s) - the majority of those
> you
> should be able to recreate on your own.
>
> For the remainder, like role accounts etc, or for those which you
> can't find the
> secrets for, that are needed on the new Master(s), please either file an
> INFRA Jira ticket or reply to this new thread.
>
> Thanks
>
> --
>
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team
>