chef-boneyard / opscode-pushy-server

Chef Push Jobs Server

https://docs.chef.io/push_jobs.html

chef-boneyard/opscode-pushy-server Issues

push job cookbook is not getting deployed
Updated 3 years ago
Push-jobs is not getting installed
Updated 4 years ago
push jobs error
Updated 4 years ago
Parameterized push job commands
Updated 4 years ago
Push jobs server returning 504 on all requests, no further info
Closed 5 years ago2
push job log retention policy
Updated 4 years ago
chef push jobs not wokring
Closed 4 years ago1
Execute a recipe on multiple nodes sequentially
Closed 4 years ago3
Do not consider a job 'crashed' when a reboot is invoked by a cookbook resource
Updated 4 years ago2
Chef Push jobs
Closed 4 years ago3
push job output not captured on postgres
Updated 5 years ago
opscode-pushy-server 1.* and Chef-server >= 12.10 do not work oob
Updated 5 years ago3
Incompatible with Chef HA (etcd) clusters
Updated 5 years ago
We build ZMQ locally to the erlang zmq library instead of using libzmq as built by omnibus.
Updated 5 years ago1
Server gives 500s when polled for job status
Updated 6 years ago
Improve support for purging older job info
Updated 6 years ago1
Duplicate node names in submitted jobs cause server to fail with 500
Updated 6 years ago
Seeing 500 issues related to SSL connection issues
Closed 8 years ago12
pushy-server gives 400 errors with no further information
Closed 8 years ago3
v2.0.1 is missing in packagecloud stable and current
Closed 8 years ago1
Can't install with systemd, due to `cookbooks/enterprise/recipes/runit.rb`
Closed 8 years ago1
Job cancellation logic not wired up in webmachine
Updated 9 years ago
Add global timeout configuration
Updated 9 years ago