search

systemd / casync

Content-Addressable Data Synchronization Tool
1.49k stars 117 forks source link

Set up Semaphore v2 #230

Closed mrc0mmand closed 4 years ago

mrc0mmand commented 4 years ago

The new version of Semaphore supports newer Ubuntu versions (like Bionic), which should fix the outstanding Python 3.6 issue which was being workarounded by (now broken) custom PPA.

(Sorry for the branch location, but that's how the initial Semaphore setup works)

mrc0mmand commented 4 years ago

The new pipeline seems to work pretty well. Anyway, I wanted to move it under systemd organization on the new Semaphore, but apparently it's taken - maybe @evverx already started playing around with it?

evverx commented 4 years ago

@mrc0mmand I'm afraid I have no idea what's going on on Semaphore 2.0. I've never tried to set it up. It must have been somebody else.

mrc0mmand commented 4 years ago

@mrc0mmand I'm afraid I have no idea what's going on on Semaphore 2.0. I've never tried to set it up. It must have been somebody else.

I see, thanks for the heads up though!

evverx commented 4 years ago

I think the only way to take the organization over from its current owner is to contact the support and complain :-) On the other hand, it seems it would probably be a little bit easier (and certainly faster) to just activate the casync repository on Travis CI and use Ubuntu Bionic there.

mrc0mmand commented 4 years ago

I just sent out an email asking if it's indeed used by somebody else or if it was me creating it the first time I was playing around with the new Semaphore. Not just for this particular case, rather than for the other repositories (systemd, mkosi), as I guess the current Semaphore will get replaced with the new version eventually. :-)

evverx commented 4 years ago

I agree the organization on Semaphore 2.0 should be returned to its rightful owner so that it can be utilized when needed but I'd choose Travis anyway to make it easier to test casync on different plataforms. As far as I know, Semaphore 2.0 isn't going to support arm for example in the foreseeable future.

mrc0mmand commented 4 years ago

I'd choose Travis anyway to make it easier to test casync on different plataforms. As far as I know, Semaphore 2.0 isn't going to support arm for example in the foreseeable future.

That's actually a pretty good point, thank you. I'll look into this next week (or possibly even during this weekend).

mrc0mmand commented 4 years ago

Superseded by #231