Create build artifacts
See original GitHub issueAs of now There are no tested build artifacts, this issue ensures we have all the artifacts and cleaned build pipeline.
- Use official NodeJS website for downloading the artifacts
- Remove
-no-oss
flag from the build tool - Remove
-oss
flag from the build tool - Ensure we produce only oss distribution
- Tar
- windows
- OSX
- Linux
- Docker
- OS Distribution
- Deb
- RPM
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Publish and download build artifacts - Azure Pipelines
Artifacts can be published at any stage of your pipeline. You can use YAML or the classic Azure DevOps editor to publish your...
Read more >Build Artifact | TeamCity On-Premises Documentation - JetBrains
Build artifacts are files produced by a build. Typically, these include distribution packages, WAR files, reports, log files, and so on.
Read more >Configuring build artifacts - IBM
Build artifacts can be configured within the build template or on a build process based on the created artifact sets.
Read more >Storing Build Artifacts - CircleCI
The store_artifacts step uploads two build artifacts: a file ( /tmp/artifact-1 ) and a directory ( /tmp/artifacts ). After the artifacts successfully upload, ......
Read more >About build artifacts - Acquia Docs
After the build is complete, Pipelines creates a “build artifact” consisting of the contents of the SOURCE_DIR and commits the artifact to your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, Any update on the Docker part?
The original issue here is resolved. Follow-ups for automation are in the build repo: https://github.com/opensearch-project/opensearch-build/issues