Re: [OpenStack-Infra] Upcoming changes now that Jenkins has retired
Hey Steve, Yes. The user "jenkins" in gerrit has actually been controlled by zuul for some years now. This rename is basically to reflect that and includes an 1st party CI comments (so check and gate). Cheers, Josh On Sat, Jun 18, 2016 at 3:26 PM, Steven Dake (stdake) wrote: > > > On 6/16/16, 6:13 PM, "James E. Blair" wrote: > > >Now that we have retired Jenkins, we have some upcoming changes: > > > >* Console logs are now available via TCP > > > > The status page now has "telnet" protocol links to running jobs. If > > you connect to the host and port specified in that link, you will be > > sent the console log for that job up to that point in time and it > > will continue to stream over that connection in real time. If your > > browser doesn't understand "telnet://" URLs, just grab the host and > > port and type "telnet " or better yet, "nc > > " into your terminal. You can also grep through in progress > > console logs with "nc | grep ". > > > >* Console logs will soon be available over the WWW > > > > Netcatting to Grep is cool, but sometimes if you're already in a > > browser, it may be easier to click on a link and have that just open > > up in your existing browser. Monty has been working on a websocket > > interface to the console log stream that we hope to have in place > > soon. > > > >* Zuul will stop using the name "Jenkins" > > > > There is a new user in Gerrit named "Zuul". Zuul has been > > masquerading as Jenkins for the past few years, but now that we no > > longer run any software named "Jenkins" it is the right time to > > change the name to Zuul. If you have any programs, scripts, > > dashboards, etc, that look for either the full name "Jenkins" or > > username "jenkins" from Gerrit, you should immediately update them > > to also use the full name "Zuul" or username "zuul" in order to > > prepare for the change. > > Jim, > > Apologies for the confusion on my end, but does this also apply to the > gate jenkins user? > > Thanks > -steve > > > > >-Jim > > > >___ > >OpenStack-Infra mailing list > >OpenStack-Infra@lists.openstack.org > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Upcoming changes now that Jenkins has retired
On 6/16/16, 6:13 PM, "James E. Blair" wrote: >Now that we have retired Jenkins, we have some upcoming changes: > >* Console logs are now available via TCP > > The status page now has "telnet" protocol links to running jobs. If > you connect to the host and port specified in that link, you will be > sent the console log for that job up to that point in time and it > will continue to stream over that connection in real time. If your > browser doesn't understand "telnet://" URLs, just grab the host and > port and type "telnet " or better yet, "nc > " into your terminal. You can also grep through in progress > console logs with "nc | grep ". > >* Console logs will soon be available over the WWW > > Netcatting to Grep is cool, but sometimes if you're already in a > browser, it may be easier to click on a link and have that just open > up in your existing browser. Monty has been working on a websocket > interface to the console log stream that we hope to have in place > soon. > >* Zuul will stop using the name "Jenkins" > > There is a new user in Gerrit named "Zuul". Zuul has been > masquerading as Jenkins for the past few years, but now that we no > longer run any software named "Jenkins" it is the right time to > change the name to Zuul. If you have any programs, scripts, > dashboards, etc, that look for either the full name "Jenkins" or > username "jenkins" from Gerrit, you should immediately update them > to also use the full name "Zuul" or username "zuul" in order to > prepare for the change. Jim, Apologies for the confusion on my end, but does this also apply to the gate jenkins user? Thanks -steve > >-Jim > >___ >OpenStack-Infra mailing list >OpenStack-Infra@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request help for ICLA error
On 6/17/16, 3:37 PM, "Anita Kuno" wrote: >On 06/17/2016 06:22 PM, Steven Dake (stdake) wrote: >> Soffie, >> >> I'm happy to spend 15 minutes on a google hangout or webex where you >>can screen share and I can walk you through getting your environment >>setup. I know every combination of problems related to ICLA setup >>helping my good friends at Red Hat and Cisco get a basic setup going in >>their environment. >> >> Ping me sdake on channel #openstack-kolla on freenode, and I'll provide >>a link to webex. You will need a mac or windows machine to use webex. >>Google hangouts also has a screen sharing feature if you can set it up. >>I am usually around all the time. :) >> >> Regards >> -steve > >This is a generous offer, Steve. > >I'd just like to make it clear to users that the infra team doesn't >support windows questions. So if this user goes to great efforts to get >access to windows to use webex, the use of that tool only goes as far as >Steve's offer, it is not indicative of what kind of support users can >expect from the infra team. > >Thanks, >Anita. Thanks Anita, Yes just to be clear: I am not a member of the infra team and don't offer other people's time (including the infrastructure team) to bring up their gerrit environment. I have helped 30+ people in kolla land learn how to contribute to Kolla, and make this offer because I want OpenStack to grow and enjoy mentoring. And to be more clear (thanks Anita!) you will need to be able to ssh from your windows machine to your linux dev environment where you intend to git review from for my offer to work :) Regards -steve > >> >> >> From: Soffie Huang >>mailto:soffie.hu...@falconstor.com>> >> Date: Wednesday, June 15, 2016 at 3:58 AM >> To: openstack-infra >>mailto:openstack-infra@lists.opensta >>ck.org>> >> Subject: [OpenStack-Infra] Request help for ICLA error >> >> >> Hello Infra Team, >> >> I am trying to push the code changes for sanbox. But while initiating >>the >> review I am getting the following Error. >> >> --- >> fatal: ICLA contributor agreement requires current contact information. >> Please review your contact information: >> https://review.openstack.org/#/settings/contact >> fatal: Could not read from remote repository. >> >> Please make sure you have the correct access rights >> and the repository exists. >> - >> >> I have signed the ICLA by providing my email address and also I tried to >> update my contact details at the link given above. While updating the >> details I am getting server error. >> >> Could you help me with this issue? >> >> >> Here is my detail information: >> >> >> >> >> >> Thanks, >> >> Soffie >> >> >> >> ___ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > > >___ >OpenStack-Infra mailing list >OpenStack-Infra@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request help for ICLA error
On 06/17/2016 06:22 PM, Steven Dake (stdake) wrote: > Soffie, > > I'm happy to spend 15 minutes on a google hangout or webex where you can > screen share and I can walk you through getting your environment setup. I > know every combination of problems related to ICLA setup helping my good > friends at Red Hat and Cisco get a basic setup going in their environment. > > Ping me sdake on channel #openstack-kolla on freenode, and I'll provide a > link to webex. You will need a mac or windows machine to use webex. Google > hangouts also has a screen sharing feature if you can set it up. I am > usually around all the time. :) > > Regards > -steve This is a generous offer, Steve. I'd just like to make it clear to users that the infra team doesn't support windows questions. So if this user goes to great efforts to get access to windows to use webex, the use of that tool only goes as far as Steve's offer, it is not indicative of what kind of support users can expect from the infra team. Thanks, Anita. > > > From: Soffie Huang > mailto:soffie.hu...@falconstor.com>> > Date: Wednesday, June 15, 2016 at 3:58 AM > To: openstack-infra > mailto:openstack-infra@lists.openstack.org>> > Subject: [OpenStack-Infra] Request help for ICLA error > > > Hello Infra Team, > > I am trying to push the code changes for sanbox. But while initiating the > review I am getting the following Error. > > --- > fatal: ICLA contributor agreement requires current contact information. > Please review your contact information: > https://review.openstack.org/#/settings/contact > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > - > > I have signed the ICLA by providing my email address and also I tried to > update my contact details at the link given above. While updating the > details I am getting server error. > > Could you help me with this issue? > > > Here is my detail information: > > > > > > Thanks, > > Soffie > > > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request help for ICLA error
Soffie, I'm happy to spend 15 minutes on a google hangout or webex where you can screen share and I can walk you through getting your environment setup. I know every combination of problems related to ICLA setup helping my good friends at Red Hat and Cisco get a basic setup going in their environment. Ping me sdake on channel #openstack-kolla on freenode, and I'll provide a link to webex. You will need a mac or windows machine to use webex. Google hangouts also has a screen sharing feature if you can set it up. I am usually around all the time. :) Regards -steve From: Soffie Huang mailto:soffie.hu...@falconstor.com>> Date: Wednesday, June 15, 2016 at 3:58 AM To: openstack-infra mailto:openstack-infra@lists.openstack.org>> Subject: [OpenStack-Infra] Request help for ICLA error Hello Infra Team, I am trying to push the code changes for sanbox. But while initiating the review I am getting the following Error. --- fatal: ICLA contributor agreement requires current contact information. Please review your contact information: https://review.openstack.org/#/settings/contact fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. - I have signed the ICLA by providing my email address and also I tried to update my contact details at the link given above. While updating the details I am getting server error. Could you help me with this issue? Here is my detail information: Thanks, Soffie ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] Upcoming changes now that Jenkins has retired
We can update those without any trouble. We just need to also update the tests that check the usernames. You should be able to make all of the changes (as per your first patchset) and then find where the tests also need changing. Happy to help you on the review if you need more guidance. To clarify though, these are just usernames used in the testing. They can be anything arbitrarily. And as mentioned by James, it is still possible to run Jenkins with zuul (in v2.5). So the tests aren't necessarily incorrect. There are still some places in infra that do still use jenkins though. For example, when uploading logs or assets zuul ssh's into the log server as the user 'jenkins'. We could create a new user for zuul to use in these cases. On Fri, Jun 17, 2016 at 6:08 PM, Will Zhou wrote: > Hi James, > > I submitted a fix to openstack-infra/zuul via > https://review.openstack.org/#/c/330853/. I found that username could not > be changed from 'jenkins' to 'zuul' like > > > https://github.com/openstack-infra/zuul/blob/master/tests/fixtures/layouts/good_require_approvals.yaml#L11 > review_gerrit: > - event: comment-added > require-approval: > * - username: jenkins* > older-than: 48h > - event: comment-added > require-approval: > - email: jenk...@example.com > newer-than: 48h > It seems that it might be a little early for the fix? > > Thanks. > > On Fri, Jun 17, 2016 at 9:15 AM James E. Blair > wrote: > >> Now that we have retired Jenkins, we have some upcoming changes: >> >> * Console logs are now available via TCP >> >> The status page now has "telnet" protocol links to running jobs. If >> you connect to the host and port specified in that link, you will be >> sent the console log for that job up to that point in time and it >> will continue to stream over that connection in real time. If your >> browser doesn't understand "telnet://" URLs, just grab the host and >> port and type "telnet " or better yet, "nc >> " into your terminal. You can also grep through in progress >> console logs with "nc | grep ". >> >> * Console logs will soon be available over the WWW >> >> Netcatting to Grep is cool, but sometimes if you're already in a >> browser, it may be easier to click on a link and have that just open >> up in your existing browser. Monty has been working on a websocket >> interface to the console log stream that we hope to have in place >> soon. >> >> * Zuul will stop using the name "Jenkins" >> >> There is a new user in Gerrit named "Zuul". Zuul has been >> masquerading as Jenkins for the past few years, but now that we no >> longer run any software named "Jenkins" it is the right time to >> change the name to Zuul. If you have any programs, scripts, >> dashboards, etc, that look for either the full name "Jenkins" or >> username "jenkins" from Gerrit, you should immediately update them >> to also use the full name "Zuul" or username "zuul" in order to >> prepare for the change. >> >> -Jim >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] Upcoming changes now that Jenkins has retired
Hi James, I submitted a fix to openstack-infra/zuul via https://review.openstack.org/#/c/330853/. I found that username could not be changed from 'jenkins' to 'zuul' like https://github.com/openstack-infra/zuul/blob/master/tests/fixtures/layouts/good_require_approvals.yaml#L11 review_gerrit: - event: comment-added require-approval: * - username: jenkins* older-than: 48h - event: comment-added require-approval: - email: jenk...@example.com newer-than: 48h It seems that it might be a little early for the fix? Thanks. On Fri, Jun 17, 2016 at 9:15 AM James E. Blair wrote: > Now that we have retired Jenkins, we have some upcoming changes: > > * Console logs are now available via TCP > > The status page now has "telnet" protocol links to running jobs. If > you connect to the host and port specified in that link, you will be > sent the console log for that job up to that point in time and it > will continue to stream over that connection in real time. If your > browser doesn't understand "telnet://" URLs, just grab the host and > port and type "telnet " or better yet, "nc > " into your terminal. You can also grep through in progress > console logs with "nc | grep ". > > * Console logs will soon be available over the WWW > > Netcatting to Grep is cool, but sometimes if you're already in a > browser, it may be easier to click on a link and have that just open > up in your existing browser. Monty has been working on a websocket > interface to the console log stream that we hope to have in place > soon. > > * Zuul will stop using the name "Jenkins" > > There is a new user in Gerrit named "Zuul". Zuul has been > masquerading as Jenkins for the past few years, but now that we no > longer run any software named "Jenkins" it is the right time to > change the name to Zuul. If you have any programs, scripts, > dashboards, etc, that look for either the full name "Jenkins" or > username "jenkins" from Gerrit, you should immediately update them > to also use the full name "Zuul" or username "zuul" in order to > prepare for the change. > > -Jim > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
