3 ms·

There was a major push for development back in 2015-2016, back before it was open sourced, but AFAIK it went dead pretty soon as internal funding dried up.. Loo

by p_l 2y ago

There was a major push for development back in 2015-2016, back before it was open sourced, but AFAIK it went dead pretty soon as internal funding dried up.. Looking at github commit log, it seems it died by mid 2018. First time I had to setup CI on a Mac, and what a horrible experience it was (Windows was comparatively easy, though finding out that starting with Windows Core wasn't best option took some time to learn)

LorenDB 2y ago
Did you work for the parent company?
- p_l 2y ago
  There was no "parent company" per se - codisec was a team inside CodiLime, starting out as an initiative to build more cybersecurity presence, including being the name we participated in various CTF contests. (This is all public info, you can find codisec at various CTF participation trackers too). And yes, I was there (worked at CodiLime late 2014 - early 2017), including in the early days of Veles (those who know my full name can easily find me in credits in the github repo, direct link with my account was lost when the repo was migrated into current one). With regards to Veles, I mostly did infrastructure and tooling for CI/CD - so including the CMake stuff and making Jenkins setup for the builds. I think it was actually the first project on which I used Jenkinsfile, which was then very fresh thing. I was never much of a C++ fan so I didn't participate much in the editor code itself, especially with another project taking lion share of my attention later on.
self_awareness 2y ago
> First time I had to setup CI on a Mac, and what a horrible experience it was Could you share some details what was horrible? I've created pipelines for Linux, macOS and Windows, and think that Windows is by far the worst of all three to setup anything related to CI.
- p_l 2y ago
  One of the issues was making builds that worked on OS versions older than the build host, general annoyances of admining macOS, fragility of the environment (this was before image based upgrades)

by p_l 2y ago

LorenDB 2y ago

Did you work for the parent company?

p_l 2y ago
There was no "parent company" per se - codisec was a team inside CodiLime, starting out as an initiative to build more cybersecurity presence, including being the name we participated in various CTF contests. (This is all public info, you can find codisec at various CTF participation trackers too). And yes, I was there (worked at CodiLime late 2014 - early 2017), including in the early days of Veles (those who know my full name can easily find me in credits in the github repo, direct link with my account was lost when the repo was migrated into current one). With regards to Veles, I mostly did infrastructure and tooling for CI/CD - so including the CMake stuff and making Jenkins setup for the builds. I think it was actually the first project on which I used Jenkinsfile, which was then very fresh thing. I was never much of a C++ fan so I didn't participate much in the editor code itself, especially with another project taking lion share of my attention later on.

self_awareness 2y ago

> First time I had to setup CI on a Mac, and what a horrible experience it was Could you share some details what was horrible? I've created pipelines for Linux, macOS and Windows, and think that Windows is by far the worst of all three to setup anything related to CI.

p_l 2y ago
One of the issues was making builds that worked on OS versions older than the build host, general annoyances of admining macOS, fragility of the environment (this was before image based upgrades)