Replies: 5 comments 28 replies
-
binary release for testing will be great! |
Beta Was this translation helpful? Give feedback.
-
Binary builds are currently availableDo NOT use them until you read this ENTIRE postWe have a CI system that does builds and uploads them we currently do not have a "release" step. You can still access the built binaries for every CI Action that was run. Each Action triggers two job for every Look at our Actions tab in the repo to view all ci buildsEach job is named after action that caused it. This is either a Pull Request's title or a Merge of a Pull Request #### .." Each of our action events triggers two different jobs with different artifacts produced. The jobs name is visible Just below the Actions Name
Once you pick the build you want to view you will be a on page that looks like this one Towards the bottom of the page you will see the Using the filesEach artifact is an archive that contains one or more builds. Extract the archive and you will have an installer or another archive with the built files. (Depends on the os). All Builds currently are built in debug mode and The ubuntu 22-04 build need libei 1.2.1+. While we do not try to land bad code and have some unit tests to help prevent this. It can still happen so running the most recent master you may find some bugs that are not in the current released stable version (when this happens). Builds from Pull Request Branches Should be considered More likely to be Unstable than builds from the master branch. I've found a bug what todoBefore you report any bugs, Always try to trigger the bug using the most recent build from the master branch. This helps us greatly many times users are running a few commits behind and we have already fixed the issue. If the Issue is still happening then you have a bug, Start by checking the issue tracker to see if its been reported We might already know about or even have Pull Request to fix the bug. If we have a PR that should fix your bug try that and report and Let us know on the Pull Request if it worked for you or not. Bug reports on
|
Beta Was this translation helpful? Give feedback.
-
Where do I download the windows and the linux builds? I looked at the actions tab and I do not know what I am looking at? Are theyre direct download links? I have been using synergy/barrier for years and I am a good tester. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Maybe, add at least SOME note on the current way of getting builds into readme? From a newcomer's perspective, the repo looks as abandoned as barrier's, but it also seems to have no builds at all. There are releases from 2021, but they have only source code, so a regular windows user looks at this and thinks: "yeah, Linux-only app". A more dedicated windows user would go to wiki, see build instructions page and think: "Ohhh... THAT kind of open-source app" (we don't expect a regular user would read wiki thoroughly, without any chapter called "install", just to see a single line that suggests checking out actions tab not even linking to it, do we?). So... maybe, at least link the post in readme? |
Beta Was this translation helpful? Give feedback.
-
Right now on the readme it states:
Which is 100% understandable. What I'd like to know is how can I be notified when input-leap is either ready for beta testing (or production use).
My 2 cents is that it would be helpful to:
By the way I've been a Synergy/Barrier for a long time (and even tried my hand at development for a bit 😶🌫️) and I'm really excited to see development continue! 🎉
Beta Was this translation helpful? Give feedback.
All reactions