continuous

5 stories and discussions about continuous, aggregated from every source we track.

1.

<p>In the past I was using drone.io, which didn't require putting any configuration file in the repository. I simply logged into it, added repository (be it GitHub or BitBucket), configured it (choosing project language and setting triggering options), and finally provided my own build recipe (shell script). It wasn't the best service out there (had slightly outdated toolchains, etc.), but it was working fine. Wanted to look into it today, but it seems it's no longer there, or more precisely, something is there, but w/o stuff that was available before, so all links to builds, etc. are no longer valid (404). I hate when services where I have accounts vanish without any prior notice. But ad rem. So...</p> <p><strong>Are there any continuous integration services (for building and testing software) for open-source projects not requiring configuration file in the root of repository? I'm mostly interested in free ones for public projects.</strong></p> <p>Ideally I would prefer CI configuration outside of the project's git repository (let's call it <em>1st category</em>), but if it has to be in the repo yet doesn't have to placed in the root, then it's also an improvement (<em>2nd category</em>).</p> <p>Sadly, popular CI solutions (like Travis or Shippable) that support open-source projects (i.e. providing their service to them for free), require some <code>.yml</code> file in the root of repository that you want to run builds and tests on. Most people are apparently indifferent about it, and I may be in very small minority with my view on it, but I simply don't like polluting repository, especially the root of it, with stuff that could be avoided.</p> <p>Sometimes some services are not yet well-known, and sometimes some knobs are well-hidden, that's why I am reaching for collective Lobsters knowledge, hoping to be pointed to some solutions I possibly overlooked or not googled enough.</p>

9 points•przemoc•almost 9 years ago•51 comments
3.

My continuous journey into toolchains, in the first quarter of 2023

3 points•fcambus•over 3 years ago•1 comment
4.

Why think in words? A deep dive into Latent-GRPO, continuous thought recurrence (Coconut, SofT-GRPO, CoLaR, SLPO), policy gradients over continuous embeddings, and empirical benchmarks on Qwen3.6-27B.

2 points•gfactor_ai•7 days ago•0 comments•
5.
1 points•taivare•3 days ago•0 comments•

Related topics