ES devs and testers, this tool is for you!

backstander

@lilbud
I use KiTTY as well! It's a fork of PuTTY that's in active development.

meleu

@lilbud I'm checking the code now.

Can you say the steps you did so I can reproduce it here?

lilbud

Step 1: Update tool to latest version from command line (updating from the tool itself fails immediately)
Step 2: Edit ES Branch list and load ES branches list from Retropie repo
Step 3: Attempt to build any branch from the available list, it will fail immediately and claim connection is bad.

The problem is not on my end, it says the connection failed, but I could download the repo list just fine, so I think the problem lies within the program code.

meleu

@lilbud please, try to get from this URL and try again: https://raw.githubusercontent.com/meleu/rp-testers/master/es-tests.sh

from command line:

wget https://raw.githubusercontent.com/meleu/rp-testers/master/es-tests.sh
chmod a+x es-tests.sh

Hex

@meleu said in ES devs and testers, this tool is for you!:

New version released: epsilon

Update the script using the Update feature at the Main Menu.

Changelog

Added an option to load the repo/branch list from the open Pull Requests in RetroPie's EmulationStation repository (thanks @Hex for the insight!).

The Message ("List of...") should also add that some entries are from currently submitted PRs

meleu

@Hex sorry, I didn't get what you mean. It says "... branches list from open PRs in RetroPie repo", isn't it enough?

Hex

I need to test this out rather than post messages when i am sleepy. Sorry for the confusion.

meleu

@Hex No problem. I'm really happy with this feature, I'm constantly looking for an excuse to use it! :D

Thanks for bringing it up.

meleu

This post is deleted!

Hex

@meleu, I would suggest manual download of jq if apt-get is not found

meleu

@Hex Do you mean that the script shouldn't provide this facility when it detects the absence of jq package?

Hex

"Do you want to install"... triggers apt-get. I use fedora which uses dnf so the command to install fails.

I would like the script to check if apt-get is present else is dnf present and then use that accordantly. If both fail you can get the executable from github (optional)

jq 1.5 is in the official Debian and Ubuntu repositories. Install using sudo apt-get install jq.

jq 1.5 is in the official Fedora repository. Install using sudo dnf install jq.

jq 1.4 is in the official openSUSE repository. Install using sudo zypper install jq.

jq 1.5 is in the official Arch repository. Install using sudo pacman -Sy jq.

meleu

@Hex Well, it's intended to be used on a Debian-based distro (just like RetroPie is). But I'll add a warning if apt-get is not found.

meleu

@Hex Done. If the script can't find apt-get, the user will see this dialog:

Zigurana

Feature request: Build and install based on a current PR number.
Rationale: lower the barrier even more: users do not need to hunt for the correct repo + branch, if they only know the GitHub PR number.

meleu

@zigurana got it. I'll try to implement it this weekend. ;)

darknior

Woaw excellent, i didn't see this ES test project before, i love it, so easy and fast to test branch :)
Thanks a lot to make it...

meleu

@zigurana said in ES devs and testers, this tool is for you!:

Feature request: Build and install based on a current PR number.
Rationale: lower the barrier even more: users do not need to hunt for the correct repo + branch, if they only know the GitHub PR number.

What do you think if we use the PR number rather than a sequential number in the menus? Is it enough?

Like this:

Zigurana

Wow! That was fast! Man, you are ever dependable!
I love it!
I think the PR number is clear enough to understand, no need to re-number them in the script.

~~Will this exist alongside the current method of manually specifying a repository and branch? That would be usefull for things that are not yet PRs.~~
[EDIT:]
Oh wow, I am an ass. I just now see that you already had the function to get the current list of open PRs! Since June! Never mind me, I should have actually updated the tool, I guess. </shameface>

In any case, this new improvement is a bit of cosmetics that will not hurt anyone. At least now it's absolutely clear what PR folks are installing.

So cool of you to jump on this so quickly! Thanks!

darknior

@meleu said

Now look at this menu:

Yes thanks i forgot this, i can come back to the master branch.
Is there a way to compile MASTER branch with your script, it is faster than in Retropie-Setup because you are not removing sources files. I have think to add the GIT of the master branch to compile it like a beta, but maybe you already code something for it ?