#2462 closed enhancement (fixed)
Change Debbie and winnie scripts to be matrix driven
| Reported by: | robe | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | Website Management, Bots |
| Component: | QA/buildbots | Version: | master |
| Keywords: | Cc: |
Description
I've started changing the GEOS scripts to be matrix driven.
Easy enough with sh scripts. Since matrixes just define a permutation of variables that become environment variables that control the branching of sh script.
IT doesn't work as far as I can tell if I don't want a permutation.
So for example for builds gcc 4.8 I only do cmake builds of geos, so I still need to have 2 matrixes one for cmake and one for libtool. Does solve teh OS_BUILD 32 vs. 64 and gcc though.
Change History (5)
comment:1 by , 11 years ago
| Component: | postgis → buildbots |
|---|---|
| Owner: | changed from to |
comment:2 by , 11 years ago
comment:4 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
did this a while ago for newer jobs anyway
Note:
See TracTickets
for help on using tickets.
started building geos as a matrix. On further inspection, jenkins has a matrix property called Combination filter which allows you to stuff a groovy condition to skip a matrix combination thus achieving a sparse matrix. So in case of geos I can skip if matrix has combo (gcc48 and libtool). Wonder if travis has a similar thing for their matrix.