CIDuty/How To/How To Loan BD: Difference between revisions

From MozillaWiki
< CIDuty‎ | How To
Jump to navigation Jump to search
(Initial release)
 
m (Live preview of formating.)
Line 12: Line 12:
= OSX Yosemite r7 - Test - Build Bot =
= OSX Yosemite r7 - Test - Build Bot =
==  Find a server ==
==  Find a server ==
TBA
Head to SlaveAlloc, following this link: [https://secure.pub.build.mozilla.org/slavealloc/ui/#slaves] and in the top-right search for '''yosemite-r7''':
Look for a server that '''DOESN'T''' have a note to it, such as the note in the example below, keep in mind servers with "'''migration to taskcluster'''" are not good for loaning either:
[[File:Slavealloc-search-example.png|thumb]]
----
Take note of the server number, then lets find out if there is a task running on the server.
Follow [https://secure.pub.build.mozilla.org/buildapi/running THIS LINK] and in the top-right search for '''10.10.5''' (version of OSX yosemite). At this point there should be 2 things:
1) Nothing shows up. Make sure your search query is correct and if it is, it's safe to assume there are no tasks running on any of the selected servers, so feel free to pick whichever you find fancy.
Now if you have the server '''SKIP TO Connect to the server section'''.
----
2) There is stuff that shows up, which means we need to do some more investigation. If after the search you see anything (as shown below) click on all the '''Buildmaster''' column links:
[[File:Slavealloc-search-with-results.png|thumb]]
----
The link will lead you to the task-execution page which shows you what's happening on the slave. At this point (if there are more than 5 results) I would '''recommend''' you to open a text editor as we need to keep track of which server is running. You can extract the number from the textfield in the example below:
[[File:Slave-alloc-buildmaster-tasknumber.png|thumb]]
----
After you have a complete list of all the busy servers, see if there are servers that are free/idle. If not, come back again 30 minutes later and check again.


== Connect to the server ==
== Connect to the server ==

Revision as of 18:24, 9 April 2018

Introduction

Use this page if you want to loan a machine to a developer. This guide has been updated on 26 March 2018 and reflects the new changes/requirements on how you should approach the process.

The format will be as follows:

  • Finding a server
  • Cleaning it up
  • Activating and Testing the VNC connection to the server
  • Sending the credentials to the requester

Everything you need to do when loaning one of the two type of servers is on this page. You can safely click on the links when instructed too as you will be automatically scrolled to the next step (eg: Server Steps -> VNC -> Email).


OSX Yosemite r7 - Test - Build Bot

Find a server

Head to SlaveAlloc, following this link: [1] and in the top-right search for yosemite-r7: Look for a server that DOESN'T have a note to it, such as the note in the example below, keep in mind servers with "migration to taskcluster" are not good for loaning either:

Slavealloc-search-example.png

Take note of the server number, then lets find out if there is a task running on the server. Follow THIS LINK and in the top-right search for 10.10.5 (version of OSX yosemite). At this point there should be 2 things: 1) Nothing shows up. Make sure your search query is correct and if it is, it's safe to assume there are no tasks running on any of the selected servers, so feel free to pick whichever you find fancy. Now if you have the server SKIP TO Connect to the server section.


2) There is stuff that shows up, which means we need to do some more investigation. If after the search you see anything (as shown below) click on all the Buildmaster column links:

Slavealloc-search-with-results.png

The link will lead you to the task-execution page which shows you what's happening on the slave. At this point (if there are more than 5 results) I would recommend you to open a text editor as we need to keep track of which server is running. You can extract the number from the textfield in the example below:

Slave-alloc-buildmaster-tasknumber.png

After you have a complete list of all the busy servers, see if there are servers that are free/idle. If not, come back again 30 minutes later and check again.

Connect to the server

TBA

Cleaning up BuildBot and Puppet files

TBA

OSX Yosemite r7 - Test - TaskCluster

Find a server

TBA

Connect to the server

TBA

Terminate the TC Worker

TBA

Cleaning up TC files

TBA

Setup, test and grant VNC access

Activate VNC on the server

TBA

Test the VNC connection

TBA

Grant VNC access/rights to the requester

TBA

At this point all thats left if to send the credentials to the requester.

Send the credentials for the server to the requester