storj-archived/autobin

Deprecated. Cross platform batch / shell scripts used to automatically build binaries.

autobin's Issues

Can't build binaries if pull request repository has a different name

Duplicate pull request release draft

combine comments of build scripts into one comment (no spam)

There are 2 different ways to implement that:
1)
Remove comments from the build scripts and add a new notification script. The new script should watch for pull requests and wait for binary upload. As soon as all 3 binaries are uploaded the notification script should write one comment. If one script does not work for some reason the notification script should write the comment without the missing binary after a given timeout.
Positiv: One comment on github and slack.
Negativ: First binary is uploaded after a few minutes but my windows build server could need one hour. The comment for the first binary has to wait. New pull request commit would restart the timer.

All 3 scripts still add there comments but delete there old comments. All 3 scripts add all existing binaries to there comment.
Positiv: One comment with all 3 binaries on github. No wait time. On github it would look like editing one comment.
Negativ: Full spam support for slack.

add some more readme information

• script dependencies.
• setup introduction.
• script can be modified for other repositories as well.
• new pull request -> new binary with pull request repository and branch
• new commit on pull request -> new binary with pull request repository and branch
• create a release with the name "autobin draft release" -> new binary with release tag / base branch
• new commit on base branch. ! no change tracker. no new binary. manual delete the binary if you need a new one. create a issue for better changetracker?

autobin script stoped after one failed binary build

A pull request with syntax errors is a problem for the autobin script. py2exe will return an error and it does not return to the main autobin folder. Bugfix needed to return to the main folder even in case of a bad pull request.

autobin script not working for new release tags

Github comment bot not working

Farmer-GUI rename to storjshare-gui stoped the github comment script. No comments added and no cleanup of closed pull requests.

farmer-gui windows binary not working

Appveyor can build a binary but autobin has problems. The folder structure is to long. I have to fix that for every windows binary.

Windws 64bit binary

The windows script must be updated.
https://github.com/Storj/autobin/blob/master/storjshare-gui/build-windows-binary.bat#L74
https://github.com/Storj/autobin/blob/master/storjshare-gui/build-windows-binary.bat#L137-L138

https://github.com/Storj/autobin/blob/master/storjshare-gui/build-windows-binary.bat#L201
https://github.com/Storj/autobin/blob/master/storjshare-gui/build-windows-binary.bat#L251-L252

64bit and 32bit nodejs must be installed. Set path variable to select the nodejs version.
set path=%path%;"C:\Program Files\nodejs"
set path=%path%;"C:\Program Files (x86)\nodejs"

publish binaries on a ftp server

At the moment pull request binaries are published as draft release on github. Only a few developer have access to it. Lets add a ftp server and allow other comunity member to download the test binaries. Lets start with an passwort protected ftp server.

build release binaries for new release tags

At the moment autobin is building binaries only for draft releases. We had no failed binary build for a while now. It is time to move on. I would like to add ARM binaries but they will need more than one hour to complete. If we have to release a hotfix as fast as possible we can't wait more than one hour.

Solution:
Autobin should build even for published releases. Lets start with a tiny time frame of 7 days or the last 2 release tags. We don't want to build binaries for old release tags.
This will allow us to publish the release while the ARM build server is still running.

add storjnode repository

https://github.com/Storj/storjnode

github comment bot doesn't like the new windows 64bit binary

Setup faster windows build server

I am using my nas as windows build server. Running Windows10 64 bit with only 512MB. That setup needs 30 minutes for one binary. Windows10 32 bit should be a littlebit faster.

OSX binary missing on pull request comments

OSX binaries are build and uploaded but the comment looks like this:
autobin binaries (only available for team members)
last commit: 662fbf52934dabf8f7cb530e0792806792d50fcc
storjshare-gui.amd64.deb
storjshare-gui.win32.exe
storjshare-gui.win64.exe

Build docker container

As developer I would like to use autobin to update storshare-cli and storj docker container. That will allow the user to use the container a few minutes after a new release without waiting hours for a sheduled build.

https://docs.docker.com/engine/tutorials/dockerimages/

Build release binaries first

At the moment autobin starts with building binaries for pull requests and later the script will build the release binaries. Sometimes a pull request has commits every few minutes. The release binaries are delayed. As long as the pull request is open there will always be a new binary to build.

Solution: Build release binaries first. Don't delay them. Build pull request binaries later.

Last commit tracking not working on pull request with merge conflicts

Autobin is using merge_commit_sha to track any new commit. In case of a merge conflict that is not working. head.sha would be better in that case.

autobin script doesn't detect existing file. Upload failed.

Normal Situation:
autobin builds a binary and uploads it. A new pull request commit will trigger the script again. autobin deletes the old binary and uploads the new one with the same filename. 2 binaries with the same filename are not possible.

Bug Situation:
autobin builds a binary and while it uploads the binary the connection is lost for some reason. autobin will start again and build the same binary. So far everything works as designed. autobin is not able to detect the old binary. Uploading the new binary failed. Perfect endless loop.

Pull request binary delete release binary

All 3 driveshare-gui build scripts have the same bug. They delete the release binary and not the pull request binary.