|
|
Home » Developing U++ » U++ Developers corner » UppHub - new package registration (How do we want to solve this problem?)
Re: UppHub - new package registration [message #56260 is a reply to message #56256] |
Mon, 15 February 2021 06:12 |
Novo
Messages: 1358 Registered: December 2006
|
Ultimate Contributor |
|
|
mirek wrote on Sun, 14 February 2021 17:56The branch to be installed is there since the beginning - check the docs
Actually, it is hard to spot in the docs.
IMHO, it would be much better (for tooling) to have branch as a separate key-value pair.
I'm currently have a lot of problems because this pair is missing.
Regards,
Novo
|
|
|
Re: UppHub - new package registration [message #56265 is a reply to message #56094] |
Mon, 15 February 2021 09:48 |
Oblivion
Messages: 1091 Registered: August 2007
|
Senior Contributor |
|
|
Hi,
Quote:I think for most projects master/main is unstable. If it is stable enough and certain features are present then the master became release via tagging. If it requires more polishing then release branch is created and then tagged if everything is fine.
I agree with Mirek here. git-based development is meant to be done via branches. Development should be done in developmental branches and the changes should be merged to master/main after they are streamlined and tested. Only then the package main branch is tagged a milestone or release.
I believe, however, it would be inappropriate to force this scheme to developers.
By the way, maybe the branching issue should be fixed in a more geneal way, via our repo tool. So that we can switch branches without manually cloning the package elsewhere or disrupting the upphub scheme.
Best regards,
Oblivion
Github page: https://github.com/ismail-yilmaz
upp-components: https://github.com/ismail-yilmaz/upp-components
Bobcat the terminal emulator: https://github.com/ismail-yilmaz/Bobcat
|
|
|
|
|
Re: UppHub - new package registration [message #56292 is a reply to message #56285] |
Wed, 17 February 2021 23:36 |
Novo
Messages: 1358 Registered: December 2006
|
Ultimate Contributor |
|
|
mirek wrote on Wed, 17 February 2021 03:07Novo wrote on Tue, 02 February 2021 15:58
That includes my build automation system.
BTW, I was thinking: Would it be in perspective possible to commit (automatically) your results to UppHub as some Json in some form? Probably only if changed to keep number of commits low.
It is just an idea, but I think this could definitely allow us to do some thing automatically, like OS support, detecting broken packages etc... UppHub code could refer directly to your files.
Mirek
My build automation system is based on Buildbot (for historical reasons).
Buildbot is used by almost all major IT companies. Example: LLVM/Clang.
Buildbot has a concept of "reporters". Most useful reporters in case of U++ are email, Telegram, and GitHubStatusPush.
I've already set up a Telegram bot, which can report results of U++ builds. It is currently down because U++ builds and my own builds share same setup. I need to separate them first.
I guess you do not want to get spammed by emails from Buildbot.
Another useful thing is GitHubStatusPush, which is using GitHub Status API to report build result directly to GitHub.
I do not want to develop custom reporters to produce JSON files or something else. At least right now.
My current goal is to make osxcross work to get rid of an always running MacOS VM, which is using 8GB of RAM and keeps one CPU busy all the time.
And Buildbot requires explicit branch name ...
Regards,
Novo
|
|
|
Re: UppHub - new package registration [message #56294 is a reply to message #56292] |
Thu, 18 February 2021 00:25 |
Novo
Messages: 1358 Registered: December 2006
|
Ultimate Contributor |
|
|
This is how current situation with builds looks like at the moment.
"l" stands for Linux (Ubuntu)
"al" stands for Alpine Linux.
"m" - MacOS 10.13
"m11" - MacOS 11.1
"mingw" - mingw-clang (cross-compiler for Windows)
Regards,
Novo
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri Mar 29 01:20:34 CET 2024
Total time taken to generate the page: 0.03125 seconds
|
|
|