Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collect a list of resources #51

Closed
jbergstroem opened this issue Feb 19, 2015 · 4 comments
Closed

Collect a list of resources #51

jbergstroem opened this issue Feb 19, 2015 · 4 comments
Labels

Comments

@jbergstroem
Copy link
Member

In order to get some things done, it'd be good to get a full list of what resources are available (and where). Based on that, I'd like to:

  • update the main readme.md (platforms and builders)
  • start digging into access redundancy (ref last meeting about 1+ access to all resources)
  • look at how which resources would be better suited for certain things (performance tracking, tests for all PR's, etc)

I can create a list from what @rvagg mentioned on the meeting, but think it'd be even better if @rvagg perhaps kicked this list off? How about:

  • hostname, location (sponsored by), hardware/vm assigned resources
@rvagg
Copy link
Member

rvagg commented Feb 20, 2015

actually a lot of it is here already: https://jenkins-iojs.nodesource.com/computer/

all of the connected hosts are being used in some way and their names should indicate what they do and who is sponsoring them. I can tweak if you come up with an initial list. Unfortunately I don't have much time for this at the moment as I'm preparing for a flight tomorrow and full week (at least) ahead of me.

@jbergstroem
Copy link
Member Author

Ok, I'll use that as a baseline.

@kenperkins kenperkins added the doc label Feb 26, 2015
@jbergstroem
Copy link
Member Author

I think what we want to do here is an ansible script that collects info (through gather_facts) and updates the README.md programatically.

@gibfahn
Copy link
Member

gibfahn commented Oct 22, 2017

I think this can/should be closed. We have a basic list, and if we want more info we should open a more targeted issue.

@gibfahn gibfahn closed this as completed Oct 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants