I want to put an end to the pulp-qpid deadlock, AKA
https://bugzilla.redhat.com/show_bug.cgi?id=1377195
https://issues.apache.org/jira/browse/QPID-7317
but I am still having trouble reproducing it in a controlled
environment. I'm launching an appeal to anyone with ideas about how to
reproduce thi
I went ahead and created this PR [1] it is covering installing the base
packages like gcc, git, etc.
[1] https://github.com/pulp/pulp_packaging/pull/270
On Tue, Jan 3, 2017 at 4:33 PM, Elyezer Rezende wrote:
> It also seems that we can remove the ci/deploy [1] directory entirely. I
> tried to f
It also seems that we can remove the ci/deploy [1] directory entirely. I
tried to find a place where any of those scripts were called and at least
on the jobs they are not being called. I used git grep to help me with that
so I may be missing something.
[1] https://github.com/pulp/pulp_packaging/t
The only puppet apply is for the pulp-unittest [1] puppet module. Looking
on its source code it seems to be just setting up some packages depending
on the slave OS.
We can either install them on the prepare_node.sh or create an ansible
playbook for it. Or even have both, for example I think it is
+1 to pulling out puppet to unblock the builds.
+1 to replacing any puppet usage with Ansible, which is consistent with the
current direction[0].
After digging around in git some, it looks like those puppet lines were
originally added in 2015 with this commit[1]. That commit both installs
puppet a
On 01/02/2017 09:58 AM, Elyezer Rezende wrote:
> The prepare_node script is responsible to prepare the nodepool nodes we use
> on Jenkins. Other than installing basic packages and the machinery to make
> the node a Jenkins slave it installs puppet [1].
>
> I am wondering why setting up puppet is n
