Set up Semaphore v2 #230
Set up Semaphore v2 #230
Conversation
mrc0mmand
force-pushed
the
set-up-semaphore
branch
2 times, most recently
from
83ed9f1 to
255e032
Compare
mrc0mmand
force-pushed
the
set-up-semaphore
branch
5 times, most recently
from
ef55fa3 to
be2040e
Compare
Shouldn't be needed anymore, since the new Sempahore supports Ubuntu Bionic
mrc0mmand
force-pushed
the
set-up-semaphore
branch
from
07a3464 to
70ce130
Compare
|
The new pipeline seems to work pretty well. Anyway, I wanted to move it under |
|
@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! |
|
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. |
|
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. :-) |
|
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. |
That's actually a pretty good point, thank you. I'll look into this next week (or possibly even during this weekend). |
|
Superseded by #231 |
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)