Am 23.08.17 um 01:44 schrieb Eric D Helms:
I would like to propose the following:
1) We drop sqlite3 entirely
2) We test all rubies on postgresql only
3) We pick the most widely used Ruby version and test mysql with that
I think, Jenkins pipelines are a good thing and can make the Job
configuration a lot easier. I'd like to to pitch some ideas. First of
all I would propose putting the Jenkinsfile(s) in the repos alongside
the code so it's more visible what happens and the job configuration
follows the code lifecycle.
I've also grown fond of the Docker Plugin for Jenkins. With that you can
easily run tests under different ruby versions. I found that easier to
setup then rvm. If you'd like, I can share the code snippets. But it's
rather trivial to connfigure.
You could also try to put the databases in a container. While I usually
don't recommend this, it might be a good architectural choice for a CI
system as you don't really need to persist data. It could also greatly
decouple the jobs from the jenkins system. But first things first.
One more thing: If we have more capacity, we could start replacing
HoundCI by our own linting again.
Timo
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
