Remove .gitlab-ci.yaml From Installed Module

Description

Leaving the .gitlab-ci.yaml file in the module's git repo causes simp repos to start CI runners when using a remote gitlab. Suggest having the simp rpm helper script remove that file from the local git repo.

simp_rpm_helper: Line #204
copy_cmd = %(#{@rsync} -a --force --exclude='.git' --exclude '.gitlab-ci.yaml' --delete)

or

copy_cmd = %(#{@rsync} -a --force --exclude='.git*' --delete)

Acceptance Criteria

None

Activity

Show:
Trevor Vaughan
November 1, 2019, 2:00 PM

I took a look through things and I don't think that this is a change that should be made across the board.

We really do want users to have a full copy of the base repository so that they can reproduce our testing scenarios and infrastructure if possible.

I would recommend modifying your GitLab settings to not trigger CI runners on updates to these modules if you are importing them into a GitLab server.

Alternatively, you could exclude those files from being uploaded but I think that simply disabling the runners on those repositories would be best.

In general, for an internal corporate infrastructure, you're not going to want to trigger CI jobs on any imported repositories since you don't necessarily know what actions the tests may take (some could be dangerous).

Labels

Epic Link

None

Story Points

4

Sprint

None

Affects versions

Priority

Medium
Configure