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

Access to z/OS machines for @ miladfarca #1686

Closed
mhdawson opened this issue Feb 11, 2019 · 8 comments
Closed

Access to z/OS machines for @ miladfarca #1686

mhdawson opened this issue Feb 11, 2019 · 8 comments

Comments

@mhdawson
Copy link
Member

Milad Farazmand works at IBM with me and need access to the z/OS machines in order to investigate: #1685,

I think he meets the requirements for temporary access in: https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md based on this subset of the criteria:

Consequences to the individual in case of mis-bahaviour. For example, would they potentially lose their job if they were reported as mis-behaving to their employer? Would being banned from involvement in the Node.js community negatively affect them personally in some other way

  • He works at IBM in the Node.js Runtime technologies group. Being banned would
    definitely have an impact

Are there collaborators who work with the individual and can vouch for them.

  • I'll vouch for him

@nodejs/build can I get an approver?

@refack
Copy link
Contributor

refack commented Feb 11, 2019

+1

@mhdawson
Copy link
Member Author

@refack I'm travelling this week. Once we have enough approvals could you help get Milad's key onto the machine?

@Trott
Copy link
Member

Trott commented Feb 11, 2019

+1 SGTM

@refack
Copy link
Contributor

refack commented Feb 11, 2019

@miladfarca I've added your GitHub public keys to https://ci.nodejs.org/computer/test-marist-zos13-s390x-2/
(a.k.a. Unix1@test-marist-zos13-s390x-2)

Please stop the jenkins service while doing testing, and restart when finished.
Note: the CI runs as the iojs user, so either su as it, or make sure file permissions are intact when done.

Happy debugging 🎏

@refack refack self-assigned this Feb 11, 2019
@mhdawson
Copy link
Member Author

@refack thanks again for helping with this:)

@targos
Copy link
Member

targos commented Apr 17, 2023

Do we need to keep this open?

@miladfarca
Copy link

We should be able to close it.

@richardlau
Copy link
Member

z/OS VMs in question no longer exist -- they were shut down as they needed updating to be able to continue to build libuv and the host machine was being updated to a newer version of z/OS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants