Feature #1152

Finish new jenkins install and decide what build routines to run

Added by Joel Palmius almost 2 years ago. Updated over 1 year ago.

Status:NewStart date:03/16/2017
Priority:NormalDue date:
Assignee:Joel Palmius% Done:

50%

Category:Jenkins
Target version:MakeHuman 1.1.2

Description

I have a new jenkins up and running at http://jenkins2.makehumancommunity.org (requires login).

We still need slave machines for at least windows, but preferably also OSX. Windows, I plan to get up and running next week.

Remains to decide what build routines to run for nightly, and what is superfluous. I'm currently thinking:

  • No point in running any linux builds. It's easy enough to run from source on linux, and it's a nuisance with PPA uploads.
  • Windows should have nightlies for at least
    • stable
    • default
    • python3 port
  • ... but I'm thinking maybe we could try a stable-community build where the latest everything of the plugins is prebundled too.
  • Nightly lint runs for active branches

I'll PM logins to the jenkins machine via the forum.

viewlint.png (88.3 KB) Joel Palmius, 03/16/2017 02:55 PM

1361

Related issues

Related to MakeHuman - Feature #994: Resume nightly builds Fix exists, needs testing 02/15/2016

History

#1 Updated by Joel Palmius almost 2 years ago

#2 Updated by Joel Palmius almost 2 years ago

  • Tracker changed from Bug to Feature

#3 Updated by Joel Palmius almost 2 years ago

And oh, the reason I start from scratch is because I'm migrating virtualization solution from KVM to LXC and the old jenkins machine is a stone-age debian 6 installation.

#4 Updated by Joel Palmius almost 2 years ago

Now the pylint3 job is running once a day (although jenkins decide exactly when). To view the lint log, go to the job and click view.

#5 Updated by Joel Palmius over 1 year ago

  • % Done changed from 0 to 50

The new jenkins system is able to build a functional zip now.

Also available in: Atom