-
Notifications
You must be signed in to change notification settings - Fork 68
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
[ci] Added Power Support ppc64le #107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Travis is not working due to exhausted credits after they decided to change their pricing plan.
I tried sending a support request to travis as they recommend in their indications but to no avail (https://twitter.com/nemesisdesign/status/1334162938127642625 more info).
If the situation does not resolve we'll switch to another CI at some point.
@nemesisdesign Thank you for the info. Tagging @gerrith3. |
@nemesisdesign I'm escalating your request to Travis - I'll let you know if I get a response soon. They were swamped, I know they are getting close to catching up but there's always a chance that a request got lost in the system. |
BTW, @nemesisdesign did you file your request at support.travis-ci.com ? |
BTW, Travis support confirmed that you should have another 10k credits for openwisp now - not sure if you can verify that? |
Thanks @nagesh4193 and @gerrith3, I think I had filed it through their support page, I received the email confirmation from their zendesk notification system, but still haven't got a response so far. It looks like we got 10K credits, but they're not flagged as OSS only and are not recurring, I hope they can help us to get some monthly allotment of OSS only credit, so we can avoid having to request credits periodically. Anyway, I will now leave some feedback for this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not fully understood what is pushing you to send this PR, could you please expand on this a bit? Given the fact that we just ran out of credits on travis, I think we'll need to optimize our CI builds to save resources, regardless of the CI we use, since I guess other CI may do the same that travis did in the future.
jobs: | ||
exclude: | ||
- arch: ppc64le | ||
python: 3.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we want to run it only on python 3.6? This version of python will be EOL soonish.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the focal distribution, the power support architecture currently does not support python 3.7 version. Power support architecture currently supports 3.5 and 3.6 in focal distribution. Thanks.
@nemesisdesign how many credits do you think you need, keep in mind that it is about 10 credits per minute of Linux run time? As an open source developer you should be able to get whatever you need at this point. Other CIs are limiting to 2k minutes or so but currently Travis only requires that you request what you need. Also, how many repositories are part of the openwisp environment and about how many developers? If we need to request more than we should do so. Keep in mind that I run the budget for the ppc64le back end servers, so the only cost that Travis worries about there is for the front end that is shared across all architectures. So, ppc64le back end servers is our gift to the open source communities. ;) |
At the moment I count 25 active repositories and 22 members of the organization.
@gerrith3 that's great, thank you so much for your support to OSS. |
@nagesh4193 if you could rename the commit to |
@nemesisdesign I have updated the commit to the new name as requested. Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the record, can you now expand a bit more on this:
Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing.
What use case is pushing you to add ppc64le
to this build, where is it needed?
@nemesisdesign we took these projects as already being part of the ppc64le distros from debian/ubuntu. So this doesn't represent a specific user or use case, but the simple fact that this is viewed as a base/common package for Linux at this point and we enable all of these packages for Power. Our goal is to hit full parity with Intel in terms of application availability. I can't name a specific django/openwisp user, but usually ubuntu includes packages like this because they believe that they are the future or at least modern software and we piggy back on that decision. I know that's probably not an insightful "who are my users" answer that you are looking for but that's how we got here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation.
Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing.