Dne 15.2.2017 v 12:44 Jiri Srain napsal(a):
Right. On the other hand, now it is "only" about CASP, later it may be about SLE12 vs. SLE13 (insert your favorite service pack number here ;-)
If SLE12 will be developed in master then there is no change... Another possibility is to use this rule: Whenever you create the CASP branch in Git craete the respective Jenkins Job. That's really trivial: - Go to https://ci.suse.de/view/YaST/ - Press "Login" in the right top corner, use the credentials from https://wiki.microfocus.net/index.php/YaST/jenkins#SUSE_.28internal.29 - In the left menu select "New" - Enter the new job name (e.g. "yast-foo-CASP"), in the "Copy from' field select the existing master job, e.g. "yast-foo-master". - Leave the "Add to current view" option checked, press "OK" - Change "Branches to build" from "master" to "SLE-12-SP2-CASP" - "Save" and that's it! -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org