jenkins-job-builder configuration #59
Conversation
|
So currently we have 4.3 for python 2.6 and 2.7, there are some configuration that is not available on standard jenkins-job-builder but that we are using, we will need to either decided if we still want it or not. |
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
from
3a98ca8 to
5cfe6a0
Compare
|
Plone 5.0 (core and robot) are there, missing AT and all the tweaks on things that jjb does not provide by default. |
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
from
5cfe6a0 to
fa099f0
Compare
|
AT is there also, now "only" the missing parts. |
|
Awesome! Will have a look later today... |
|
I have quite a few more things done, will push them later... Still we have a bit of a problem with current JJB as it only allows to add more definitions (say xvfb) but not to extend/override already defined ones. I already send them a bug report, let's see... |
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
from
fa099f0 to
122da2a
Compare
|
Everything that I have is pushed, as you can see adding new things is quite easy: an entry on setup.py and a function is enough. |
gforcada
changed the title
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
3 times, most recently
from
4b80901 to
3c133b3
Compare
gforcada
changed the title
|
Updated once again. To try the current configuration one needs to have on virtualenv jenkins-job-builder from my fork. As it can be see on the TODO's entries on the config file, the only remaining configuration to be updated to match 1:1 the current setup is the email configuration. Once we decided what to do with it, this PR can be merged and start to be used. |
|
Some more work on it: I created another project that define as many PLIPs jobs as needed provided the PLIP has a config file on buildout.coredev branch 5.0 .) This way we can test all PLIPs as they move forward. Maybe we need to set a cron job to run them on a daily basis or so? And regarding that I created plone/buildout.coredev#64 |
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
3 times, most recently
from
2996f53 to
bbf13cb
Compare
gforcada
changed the title
There are some changes made on jenkins-job-builder that are still not upstream but that we need them. Unfortunately jjb doesn't have a way to override/extend their own definitions, so we can only fork by now.
Add Plone 4.3 {py26, py27} configuration based on jenkins-job-builder.
Add Plone 5.0 {core, robot and AT} configuration based on jenkins-job-builder
To create a job for a plip only two things are needed: - a short name (for display purposes) - the path to its cfg file on buildout.coredev
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
from
bbf13cb to
1e8a4b8
Compare
As it will be soon the real master, there's no need to call it test anymore.
gforcada
force-pushed
the
jenkins-job-builder-current-setup
branch
from
1e8a4b8 to
75a405c
Compare
jenkins-job-builder configuration
|
@tisto merged! we can now tweak it, I think the foundation is stable enough to not have to start rewriting things all over (hopefully). 🎉 |
|
Awesome! |
As discussed some time ago with @tisto, the idea here is to make a 1:1 translation of our current setup but using jenkins-job-builder.
As currently jenkins.plone.org has lots of jobs defined, only the core set will be recreated within this pull request. That means basically Plone 4.3 with both python 2.6 and 2.7 and Plone 5.0 with core tests, robot and AT, all in all just 5 jobs.
This is mostly a test ground so that once we get some experience with jjb and we decide how to proceed further with the testing workflow, we already have a clean and solid configuration to expand on.