search

AndyReifman / ArseneWenger

1 stars 12 forks source link

Holding - Create CI/CD pipeline #32

Closed ingenium21 closed 2 years ago

ingenium21 commented 2 years ago

This is an issue to hold and track any progress we've made in the CI/CD pipeline.

ingenium21 commented 2 years ago

from eric: full disclosure i just set up the pipelines, i don’t manage it other than some light troubleshooting here and there. i don’t like that a lot of functionality is plugin based. don’t like that since we don’t use our own gitlab’s ci, the jenkins jobs are triggered via gitlab webhooks, this one isn’t jenkins fault obviously. i don’t like jenkinsfiles or groovy and prefer yaml don’t like the UI

AndyReifman commented 2 years ago

Before we get to the pipeline I think we need to come up with some base tests that we expect to pass any time a change is committed. Even if I'm executing those by hand for the time being, I think that's a better place to start. Choose a tool based on what we are doing, don't do stuff based on the tool we choose.

ash663 commented 2 years ago

To start with, our tests can simply check for expected <object> Example: !next outputs Next match is Burnley (H) in 15 hours, 6 minutes Strip out Next match is and check Burnley (H) in 15 hours, 6 minutes is a non-empty string.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.