|
alright so i'm at the end of my wits and i want to take an automatic rifle and fire 30 rounds into our bamboo server because it's such a steaming poo poo pile of trash that was suggested and approved behind my back years ago. however, i'm in the position to have complete control of all tech decisions at my company, and i'm going to force everyone to learn something new here because bamboo sucks. it's slow as poo poo, it can't handle project dependencies in a sane way, and everything about it is just horrible. i know there's gotta be something good out there (lol) so if you had your way, with complete control over the decision, what build system would YOU use?
|
# ¿ Dec 11, 2019 19:19 |
|
|
# ¿ May 9, 2024 04:32 |
|
i guess the title should have been "build servers" not "build systems" but whatever i just need to be freed from this prison i looked at ovh's CDS: https://ovh.github.io/cds/ which seems kinda cool but i've never heard of it before.
|
# ¿ Dec 11, 2019 19:28 |
|
rotor posted:i used travis once and it seemed not awful but also seemed like it had too much magic in it travis got sold to a company that immediately fired almost all the engineers and then it had multiple day downtime
|
# ¿ Dec 11, 2019 19:32 |
|
yeah i would never use off-premise stuff, plus, we can't, due to requirements dictated by certain global powers
|
# ¿ Dec 11, 2019 19:52 |
|
we use maven but its currently invoked by bamboo
|
# ¿ Dec 11, 2019 20:23 |
|
i had to write a bamboo plugin that let me define a static file to drop into the build directory of a project right before it builds. for whatever reason the suggested mechanism in bamboo is to write a bash script that generates the file.
|
# ¿ Dec 12, 2019 21:27 |
|
Plorkyeran posted:jenkins pipelines are a big improvement over the old approach of configuring things in the bad web ui, but the fact that they're a pipeline rather than a dependency graph is awful and makes a lot of our builds take 2-3x longer than they would otherwise. thats the one reason why i was interested in that CDS server because it does builds and deployments as a dependency graphs with gates that block the flow until something triggers it. and the build can be defined in the code itself.
|
# ¿ Dec 13, 2019 21:57 |
|
Shaggar posted:maven hatred boils down to 2 groups: shaggar was right 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 you are an embarrassment to your profession
|
# ¿ Dec 22, 2019 04:55 |
|
Captain Foo posted:lmao if you have to build code lmao if you dont
|
# ¿ Dec 30, 2019 04:43 |
|
dads friend steve posted:I have no good answer to the question above, but I do have a question of my own: how is it that you have PRs all to the same repo and at such a frequency that you have that problem to begin with? Like how is that happening so often you need automation? I just want to say one word to you. Just one word. Are you listening? Agile!
|
# ¿ Jan 14, 2020 19:26 |
|
this week im going to take the plunge and experiment with CDS https://ovh.github.io/cds
|
# ¿ Jan 14, 2020 21:07 |
|
oh? perfect
|
# ¿ Jan 14, 2020 22:06 |
|
using docker images from a hash instead of a tag to build your poo poo is so much nicer than any other mechanism
|
# ¿ Jan 15, 2020 06:29 |
|
I can understand why generic public hub images don't do that, but if you are doing any stuff internally you better have your own set of images. Just because the docker hub sucks sometimes doesn't mean the whole stack is bad, the technology and tool work just fine if you are willing to put a few hours aside to set up your base build images. You really should have your Dockerfiles start like this: code:
|
# ¿ Jan 15, 2020 18:33 |
|
|
# ¿ May 9, 2024 04:32 |
|
artifactory rules but their pricing is outrageous. having to buy the most expensive license @ ~$15k/year just to get S3 storage support is ridiculous.
|
# ¿ Jan 15, 2020 21:56 |