logo ┌─[✗]─[[email protected]]─[~] └──╼ $./Pwn3d.sh Dear Admin/s, Greetings from ./Payload.sh [ Homepage: https://Payload.sh/ ] Your database has been dumped we have all '_users' in a .sql* Proof:'1','Victor','fd60ce6b028082526ca18e9a05f5af32','XYNd3d3h','Wow8TYxNI7D7tEnR3GQZrnTdb5snhus1LSKtsTglBbDV71VAu7','[email protected]' Anyways not going to lie, things ain't preety for you. Next time keep your shit up to date & maybe take some time to patch your server. exit
Thread Rating:
Auto-Build and Release System
2020-12-05, 03:33 PM, (This post was last modified: 2020-12-05, 03:33 PM by Victor.)
#1
Auto-Build and Release System
At inception, ACR required manual work to package releases.

Eventually, we added Travis CI builds to auto-build the master branch and pull requests to ensure new commits don't break the build (cause the compile to fail). However, releasing was still a manual process.

I also added a script to package ACR into .zip files for releases, but the process was still manual.

GitHub eventually added their own CI system (GitHub Actions).
I moved the build system from Travis CI to GitHub Actions and added a workflow that will build and generate the .zip releases as artifacts.
I also auto-drafts a release when a tag is created, reducing the work of releasing to just adding a description and changelog.

The only current limitation is that linux builds will be only for x64 (amd64), and there are no x86 builds (i386).

Best regards,
Victor
//victorz.ca
Code:
Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|)
My antithesis compares favorably with _that of_ any high magnitude of pwnage. (|-me| > |-p|, |me| > |p|)
Post Reply Quote this message in a reply
« Next Oldest | Next Newest »


Forum Jump:


Contact Us | Victor | Return to Top | | Lite (Archive) Mode | RSS Syndication | Valid XHTML 1.0 | Valid CSS 2.1