[Gluster-infra] [gluster.org_salt_states] Want to refactor jenkins.slave
Niels de Vos
ndevos at redhat.com
Mon Nov 23 21:17:00 UTC 2015
On Mon, Nov 23, 2015 at 04:39:04PM +0530, Kaushal M wrote:
> Hi all
> Now that we have public access to the gluster-infra salt states , (thank
> you Misc) I'd like to start contributing to it. I'd like to begin by
> refactoring the `jenkins.slave` state.
> My aim with the refactoring is to pull out the general test environment
> configuration, from the gluster infra specific configuration. The reason to
> do this is mainly two fold,
> 1. To make it easier for developers to contribute changes to the GlusterFS
> testing environment.
> 2. To make it easier to deploy local testing environments.
> I need some questions on which I'd like feedback.
> 1. How do I contribute changes back? As I understand the github repos of
> the salt-states and salt-pillar are just mirrors.
> 2. I'd like to have this test environment state separate from gluster.org
> infra states, ie., outside the current salt-states tree, in a separate
> repo, or within the glusterfs repo. This would help developers contribute
> to it, without hurting the infra states. Would this be okay? If yes, which
> repo should this be put into.
We already keep some of the scripts that are used by Jenkins jobs in a
repository. It would probably be good to use that:
At least on build.gluster.org this is checked out (manually) in /opt/qa.
I guess this should be done on the other slaves as well if that is not
the case yet. I think it would be nice to have very simple Jenkins jobs
that only execute scripts from this repository.
> : https://github.com/gluster/gluster.org_salt_states
> Gluster-infra mailing list
> Gluster-infra at gluster.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the Gluster-infra