-
Notifications
You must be signed in to change notification settings - Fork 17
Build Automation - RFC #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd be ok with dropping the requirement for Linux/RPM and only having Linux/tar.gz and Linux/Installer (sh). |
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Jarsigning can be disabled by setting the property -DdisableSigning=true Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
I have been thinking of making MC run in embedded mode. This greatly helps in integration testing of server and the plugins. I would like to take a stab at it. |
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
…ertificate Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
I have no idea who might want to install via RPM without a package repo. But it’s a standard package for many setup tools, so likely not difficult to support. Also, I think we should add hashes for the binaries. And we should either get a install4j license or plan to re-implement the install4j scripts. |
Related to issue #2 |
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Overview
Implement automated build, packaging, and publishing capabilities for OIE to streamline development workflows and improve distribution.
Requirements
Priority 1: Core Build Automation
Priority 2: Artifact Publishing
Priority 3: Container Support
Priority 3: Automated Testing & Releases (nice to have)
Success Criteria
Supported Platforms
The text was updated successfully, but these errors were encountered: