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

Validate "new" Ansible scripts for Power and add step to update to Java8 #919

Closed
4 of 11 tasks
mhdawson opened this issue Oct 16, 2017 · 5 comments
Closed
4 of 11 tasks
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 16, 2017

We recently manually updated the Power machines so that they used java8. (See #775)

I'm also not sure we have validated the "new" ansible scripts on for the power machines we should:

  • create new PPC le machine
  • update "new" ansible sxripts to add step to add/use java8 for PPC le and be
  • test "new" ansible scripts
  • swap new machine in as test worker
  • destroy old worker
  • create new PPC be machine
  • update "new" ansible sxripts to add step to add/use java8 for PPC be and be
  • test "new" ansible scripts
  • test "new" ansible scripts
  • swap new machine in as test worker
  • destroy old worker
@mhdawson mhdawson changed the title Validate "new" sensible scripts for Power and add step to update to Java8 Validate "new" Ansible scripts for Power and add step to update to Java8 Oct 19, 2017
@maclover7
Copy link
Contributor

Just a note, this can be closed once #1075 and #1101 land.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 9, 2018

This should stay open a bit longer as once those land we still have BE to update the ansible scripts for.

As an update, new ansible script has landed and there is one new work in the CI that is setting the compiler level. Will leave over the weekend and if it looks ok then proceed to updating the other 2 workers and removing the logic in the job to only set the compiler level on the currently updated machine.

@maclover7
Copy link
Contributor

ping @mhdawson -- can you confirm we're good here?

@mhdawson
Copy link
Member Author

I tried to say in the last post that we will still need time to go through the other steps, these will take a while.

@sam-github
Copy link
Contributor

Closing as stale, but if anyone wants to take this up feel free to reopen.

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

4 participants