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

Support new Workflow runners #249

Open
cheeseplus opened this issue Nov 14, 2016 · 4 comments
Open

Support new Workflow runners #249

cheeseplus opened this issue Nov 14, 2016 · 4 comments

Comments

@cheeseplus
Copy link

Push jobs is no longer needed for the new runners which use SSH. As this is dope, we should use it.

@ricardolupo
Copy link

the new runners also have no dependency on chef server, so build cookbooks may break if they are dependent on chef server search

@andrewelizondo
Copy link

we still need push, but we should still implement the new runner setup

@NickRycar
Copy link

NOTE: On newer versions of automate, it doesn't look like deploys show up in the trend graphs, nor do the build nodes show up in their respective aggregate views. Hypothesizing that this is what things look like when using v1 builders in a runner-capable automate server. Will update once I've had a chance to confirm (unless someone's already done so)

@scarolan
Copy link
Contributor

Let's prioritize this. I really liked showing off the purple markers for each change.

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

5 participants