Hi developers, we agreed that current CI in jenkins have some problems and I would like to face it. But at first I would like to hear your opinions on current setup, what is weak points and what is nice features we like.
Few questions I have in my mind: testing: current it test only changes in master branch. How important for you if we automatic test also pull requests and maintenance branches? Related question is how important for us is to have generated <package>.spec file as it quite block more generic solutions. autosubmit: Are you satisfied with current autosubmit to Yast:Head? And what about automatic submit to factory? What is criteria to submit to Yast:Head and to factory? Do you want it automatic or some someautomatic or manual step is better from your POV? involvement: Do you want actively help with CI? ( current status is that usually I fix it myself when I see fail ) Do you have own idea what can be automatic or what can help with removing common task? openess: Problem of current status is that yast CI lives in suse network ( benefit is that we have direct access to our test machines and can easy modify it ). What about using http://ci.opensuse.org/ instance? where then must live workers? I see that cloud guys use it, so maybe we can discuss it with them (mvidner do you have closer information?)? Thanks for feedback, Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
