|
Gazpacho posted:i have never seen any other build tool that demanded more developer attention and babysitting than maven. even the build system developed for windows NT (a boatload of cmd scripts driven by nmake) managed to be more intuitive ive been begging you to post yoru pom.xml for years i want to see this heinous thing that tortures you
|
#
¿
Jan 11, 2020 20:00
|
|
|
|
| # ¿ May 9, 2024 13:59 |
|
|
Gazpacho posted:even if i had it it wouldn't be mine to post, and anyway we both know that your response would be "why are you doing the dumb things" while ignoring the answer I have always given, that the management mandated the use of maven while also imposing requirements (esp. variant builds) that conflict with maven's "opinions" you have to admit, your situation is pretty funny hope you have taken the opportunity to go on a rant in the xml comments every time you have to fight maven
|
|
#
¿
Jan 11, 2020 21:52
|
|
|
thats interesting gazpacho i would have said "any kind of mutation of code you want to do at build-time needs to happen prior to invoking maven" but when i think about it, i bet they did this insane bullshit the way you describe in order to have one maven process on one build host spit out N artifacts (where N is the number of customers your compiling for) whereas i would have probably set it up such that N executors each produce one artifact
|
|
#
¿
Jan 11, 2020 22:03
|
|
|
animist posted:re: build servers, anybody used gitlab CI? that looks okay i have used it it's good for testing and building in docker containers, which makes it easy to get repeatable builds. but ironically, it's not so good at actually building docker images because in order to do a docker build in gitlab ci, you have to either run outside of docker (shell executor on some dedicated build host) or do docker-in-docker (disgusting, but it can be done) if you can stomach running docker builds in one kind of environment and everything else in a docker container, it works well. i actually suspect this exact same quandary is present in most CI systems that involve docker.
|
|
#
¿
Jan 14, 2020 21:38
|
|
|
i've used a lot of jenkins instances, and no two are completely alike. there are lots of plugins to make it do exactly what you want. but they almost always become abandoned, and then you are stuck when you have to upgrade. gitlab ci has a much more limited feature set and no plugins afaik. but its very easy to keep up to date (if it actually meets your needs in the first place) so i recommend trying to make it work with gitlab ci if its already serving your git repos. jenkins is always there for you if you have some specific needs that aren't served by gitlab ci
|
|
#
¿
Jan 14, 2020 22:01
|
|
|
Poopernickel posted:it's pretty easy to have a dockerfile and think that your builds are reproducible, except: hard to argue with this, because almost every Dockerfile fetches stuff from a repo or package manager. you're supposed to use nexus or something to ensure that all that stuff remains available and consistent. if you do, all these problems go away (except for the one where dockerhub vanishes one day) but almost nobody does this, because using docker is all about taking shortcuts and doing the bare minimum to get poo poo working
|
|
#
¿
Jan 15, 2020 06:06
|
|
|
but its cool to use a docker image to provide an environment for CI, because THAT actually does make your builds more repeatable the problem shows up when you go to update that image, and the Dockerfile refers to an apt repo that doesn't exist anymore. then you're back to janitoring linux again
|
|
#
¿
Jan 15, 2020 06:20
|
|
|
|
| # ¿ May 9, 2024 13:59 |
|
|
CRIP EATIN BREAD posted:artifactory rules but their pricing is outrageous. at my old job, the NPM guys wanted to charge us 90k per year to run our own NPM mirror on-site we got artifactory instead lol
|
|
#
¿
Jan 16, 2020 00:21
|
|