Add: Build Script for salsa.debian.org

[codemonkeyrawks]

Hi There,

I don't want to cause any conflicts with using kicad-footprints if Travis-Cli is what everyone has chosen to use already. I have seen quite a few projects however move on Debian to salsa.debian.org using Gitlab while still keeping a branch on github and gitlab or in some cases gitlab only. I started to update this project over to using gitlab if this seems an option everyone would like to take however I don't want to create an issue if officially Travis-Cli is what is used.

There appears to be a project out there already: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints

This portion would mainly update the Repo to allow a Pipeline to run and build just like what Travis-Cli does - there would still need to be some tweaking.

I feel like if this can happen some of the debian developers may have more of a chance pulling into backports more releases being that the code can be pulled into the build server and deployment quicker. Again I am not trying to start an build war but trying to help on some simple updates where I can help out.

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

• Provide a URL to a datasheet for the footprint(s) you are contributing
• An example screenshot image is very helpful
• If there are matching symbol or 3D model pull requests, provide link(s) as appropriate
• Check the output of the Travis automated check scripts - fix any errors as required
• Give a reason behind any intentional library convention rule violation.

[codemonkeyrawks]

Please note that I am asking if the KiCad team is interested in using GitLab. I am not wanting to merge anything yet but if you decide a "yes" then I would try and help get this working.

A sample can be found here:
https://salsa.debian.org/codemonkeyrawks-guest/kicad-footprints/pipelines

[antoniovazquezblanco]

As far as I know, from the project mailing list, there is a desire to move the whole project to gitlab. I am not sure whether that would be a private instance, whether it will be on gitlab servers or where it will be hosted.

Some of us have started playing with Gitlab pipelines for source code and I was interested in moving the current tests to a gitlab based mirror in order to be ready when the transition order takes place. For this, we are using a mirror for the time being. It is located at https://gitlab.com/kicad-mirror

[codemonkeyrawks]

@antoniovazquezblanco : Let me know if the team needs any help: I will try my best. If not your more than welcome to close this. I am going to try and work with a few Debian members on setting up a few build rules however welcome to try and help.

[antoniovazquezblanco]

I am currently overloaded due to work constraints. I was working on a KiCad AppImage file but failed to get Python support working. If you have any knowledge about the issue it would be awesome if you could contribute. Also, it would be interesting to work on library checks and packaging.

As soon as I can I will be getting back to working on this.

Thanks for the interest!

[poeschlr]

I am uncertain if the footprint repo is the correct place to add platform specific build scripts. I thought this is done in separate repos and the footprint build scripts simply create a compressed file.

[poeschlr]

Regarding gitlab: I assume you reference the FOSDEM comments by wayne. To me it seemed that the long term goal would be to move all kicad assets to a CERN owned and managed gitlab server.
I would assume that such a server would be public. I hope it would be setup to easily allow our pull request model of contribution to continue (gitlab generally has something called merge request. I am uncertain if that would require users to have a public fork of the repo similar to how it works on github. If that is the case then users will need to be able to register at the server and at least fork repos without interaction with maintainers.)

[codemonkeyrawks]

Hi @poeschlr : gitlab works exactly like github it just has building also "Docker builds". The options for using gitlab I know are:

1. Use gitlab directly: (similar to what you have set up as a mirror)
   -- example project: https://gitlab.com/codemonkeyrawks/

2. Use: https://salsa.debian.org - Wayne would have more details than me being a Debian maintainer.

• User registration on Debian Salsa is really easy: you can see since last time I have cloned the branch and added a simple build script as a getting started. I am also getting my feet wet as we go.
  -- example project: https://salsa.debian.org/codemonkeyrawks-guest/kicad

Both projects should remain up for about 2 weeks: I may eventually move a few things around once I get a handle on building.

Again you can close this as needed: this was just to give an example build.

[codemonkeyrawks]

Closing!