So, as some of you know we have a non-official CI designed to do test on packages in progress.
Available here https://jenkins-apps.nohost.me/jenkins/
But, this CI is set on one of my server and need many manual operations.
So, I thought about one another way to give an official non-official CI for all the packagers who want to use it.
Let me explain that.
- For a packager,
You can have an access to this CI by ssh with your private key. (And obviously everyone can see the results on jenkins.)
With your ssh connection, you gonna access to your private directory in this server. Where you can put all your apps.
For each app you add to your directory, a new job will be created in jenkins.
And, if you update an app in its directory, a new test for this app will begin.
To update or add a new app, you’ll can use a dedicated script which perform a rsync on your apps, from your computer.
For a member of apps group
To have a account, a packager have to ask you.
Your access to this server will not be restricted to your personnal directory.
A script have to be used to add a new packager, with his directory and all the stuff he need.
And the same if you want to remove an user.
Normally, you shouldn’t have something else to do.
But why ?
To give to all packagers more autonomy.
To prevent the coding by commits, as we can see with the current CI. (I mean add a new commit to start a new test. And so on…)
Do not use my personnal server to do that. It’s my fallback, so sometimes, it can be offline for you.
And allow to more packagers to have tests, even if they do not want (or can’t) use package check on their own.
So, if you’re interrested by this idea, let me know. I have to work in these scripts in this case, though it shouldn’t be too long.
But, if it’s possible, it can be nice if someone else than me can rent a vps to this purpose.
Désolé pas la force de réécrire ça une deuxième fois en français…