definitions migration to gitlab (was Re: Proposal: gitlab.com/baserock/definitions as definitions canonical source)
by Javier Jardón
Hi all,
On 28 October 2016 at 17:45, Javier Jardón <jjardon(a)gnome.org> wrote:
> On 27 October 2016 at 16:59, Javier Jardón <jjardon(a)gnome.org> wrote:
>> Hi all,
>>
> <snip>
>>
>> Since I presented this demo in July, I've improved the CI pipeline a
>> little so now we have elastic runners; this means that we will
>> generate build machines on demand, while keeping the free runners
>> offered by gitlab.com as a backup.
>>
>> This will save us resources and we can adjust the capabilities of the
>> machines as we wish (the machines are generated from a DigitalOcean
>> account)
>>
>> We also have a ARM runner but I've had to disable it at the moment
>> because some problems cloning git repos [1]
>>
>> Therefore, and after some people have been playing with the system for
>> a while with mostly positive feedback, I'd like to propose
>> gitlab.com/baserock/definitions as the canonical source for
>> definitions.
>> By doing so we will have the most important feature we were wanting for a
>> long time (and one of the main reason we switched to gerrit):
>>
>> - Pre-merge testing of all the system we are interested on
>>
>> There are myriad other gitlab features we can use (issue
>> tracker... ), but I think this is the most important one for this
>> discussion
>>
>> Let me know what you think
>>
>> Cheers,
>> Javier
>>
>> [1] https://gitlab.com/baserock/definitions/commit/e2255bd601a12c9f6924874f2d...
>
> To clarify this a little more, the only change I'm requesting here is
> to stop mirroring the g.b.o definitions repo into
> gitlab.com/baserock/definitions
> So to make a change in definitions, the process would as simple as:
>
> - Create branch in gitlab.com/baserock/definition -> test branch in
> the gitlab ci -> Create Merge request -> review -> patch is applied to
> master
>
> (currently the patches have to be send to gerrit and then wait for the
> change to be mirrored in gitlab)
>
> I'd like to do this change on a week counting from today (so next
> Friday 4th of October)
> Let me know if you have any objection for this to not happen
Seems nobody has any big problem with the migration, so
gitlab.com/baserock/definitions will stop mirroring
git.baserock.org/baserock/baserock/definitions tomorrow at some point
I've already migrated the active merge request to the new location
[1], and I will try to edit the wiki over the weekend
To mirror back definitions to
https://git.baserock.org/delta/definitions I need the trove
credentials (user/pass) so gitlab can push there; can anyone give me
them in private? (or join the gitlab.com/baserock/definitions project
, and configure the mirror here [2] :))
Cheers,
Javier
[1] https://gitlab.com/baserock/definitions/merge_requests
[2] https://gitlab.com/baserock/definitions/mirror
6 years, 10 months
- 3
- 5
Proposal: gitlab.com/baserock/definitions as definitions canonical source (was Re: RFC: Gitlab Implementation)
by Javier Jardón
Hi all,
On 4 July 2016 at 17:35, Javier Jardón <jjardon(a)gnome.org> wrote:
> On 3 July 2016 at 14:20, Javier Jardón <jjardon(a)gnome.org> wrote:
>> I personally like gitlab for its simplicity so this morning I went
>> ahead and I setup a ci/cd pipeline in a mirror of definitions in
>> gitlab.com [1]
>> To make things easier it would be great if you can review this patch
>> [2] to add .gitlab-ci.yml in the master branch of definitions.
>> In this way the ci pipeline will be automatically triggered after any change.
> <snip>
>> [1] https://gitlab.com/jjardon/baserock-definitions/pipelines/3636171
>> [2] https://gerrit.baserock.org/#/c/2194/
>
> This is merged now, thanks for the quick reviews!
>
> Pipelines will be automatically generated here [1] with any change in
> master of definitions
> If you want to give a try to this ci system: the only thing you have
> to do is create a branch from master of definitions in gitlab,
> make your changes and push it. A pipeline will be automatically created
>
> Cheers,
> Javier
>
> [1] https://gitlab.com/baserock/definitions/pipelines
Since I presented this demo in July, I've improved the CI pipeline a
little so now we have elastic runners; this means that we will
generate build machines on demand, while keeping the free runners
offered by gitlab.com as a backup.
This will save us resources and we can adjust the capabilities of the
machines as we wish (the machines are generated from a DigitalOcean
account)
We also have a ARM runner but I've had to disable it at the moment
because some problems cloning git repos [1]
Therefore, and after some people have been playing with the system for
a while with mostly positive feedback, I'd like to propose
gitlab.com/baserock/definitions as the canonical source for
definitions.
By doing so we will have the most important feature we were wanting for a
long time (and one of the main reason we switched to gerrit):
- Pre-merge testing of all the system we are interested on
There are myriad other gitlab features we can use (issue
tracker... ), but I think this is the most important one for this
discussion
Let me know what you think
Cheers,
Javier
[1] https://gitlab.com/baserock/definitions/commit/e2255bd601a12c9f6924874f2d...
6 years, 10 months
- 3
- 5
- ← Newer
- 1
- Older →