Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Jenkins server for custom CI #1309

Open
martukas opened this issue Aug 21, 2022 · 3 comments
Open

Configure Jenkins server for custom CI #1309

martukas opened this issue Aug 21, 2022 · 3 comments
Assignees
Labels
Devops/CI Integration / testing / deployment Software Umbrella: GUI, Controller or CI

Comments

@martukas
Copy link
Member

martukas commented Aug 21, 2022

What has to be done
We have a server at the Oakland workshop that can be used to continuously test with hardware. We need to configure a Jenkins server for this.

  • Jenkins setup should be proxied and secure, with shttp
  • for starters, it should run similar tasks as CircleCI
  • minimal test with hardware would be:
    • deploy to unit
    • execute a couple of simple commands via debug interface to confirm data in/out
  • figure out what is needed for parallelization - to run multiple build processes and/or to deploy to multiple controllers simultaneously

How do you know it has to be done
Needed for all the different types of hardware-in-the-loop tests, such as

Starting points
Useful articles:
https://www.virtualizationhowto.com/2021/09/install-jenkins-on-ubuntu-21-04-with-self-signed-ssl-certificate/
https://www.digitalocean.com/community/tutorials/how-to-configure-jenkins-with-ssl-using-an-nginx-reverse-proxy-on-ubuntu-22-04

@martukas martukas added Devops/CI Integration / testing / deployment Software Umbrella: GUI, Controller or CI labels Aug 21, 2022
@martukas martukas self-assigned this Aug 21, 2022
@martukas
Copy link
Member Author

@martukas
Copy link
Member Author

So apparently we need a cert from here https://letsencrypt.org/
which should probably be managed by certbot, but a number of things are not clear to me:

  • do we need to have ports 80 and 443 open? Would be best if we could avoid that. There must be servers out there that use other ports and things still work?
  • can Cloudflare do the proxying for us? Or is that something different?
  • don't we already have some sort of cert for our main website and top level domain? Could we not reuse that one?

martukas added a commit that referenced this issue Jan 17, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 18, 2023
martukas added a commit that referenced this issue Jan 19, 2023
martukas added a commit that referenced this issue Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Devops/CI Integration / testing / deployment Software Umbrella: GUI, Controller or CI
Projects
None yet
Development

No branches or pull requests

1 participant