-
Notifications
You must be signed in to change notification settings - Fork 277
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
[Proposal] Publish snapshots with partial builds #3180
Comments
+1 |
@saratvemulapalli Are you referring to Maven artifacts or TAR here? We did add an enhancement to publish TAR snapshots for core even if plugins fail but yet to work on the Maven part. We are looking in to moving the snapshot outside of distribution build job to individual repos as well. You can track the progress here. |
I'll close this as we are already taking care of this and move towards publishing artifacts from each repo. |
Is your feature request related to a problem? Please describe
Our distribution manifest consists of bunch of components and is maintained by different maintainers.
Our build/assemble/publish workflow is sequential and assumes all steps of each workflow to succeed.
As the project grows bigger, few components will consistently fail causing blockers for consumers who depend on snapshots. The stale snapshots are ending with manually kicking off builds with updated manifests.
We have seen multiple problems in the recent weeks:
and many more.
Our workflows fail hard when one component fails.
Describe the solution you'd like
Our jenkins workflows should allow fail through and let partial components to be published.
For example:
Our manifest contains OpenSearch, Job Scheduler, security. Its ok to have security to fail the build but we should still continue running though the workflows to publish OpenSearch and JS snapshots.
We can leverage jenkins scripts[1] to smartly identify the successful components and run through all stages of the pipeline for snapshots.
[1] https://www.jenkins.io/doc/pipeline/steps/workflow-basic-steps/
Describe alternatives you've considered
Wait for snapshots being published :/
Additional context
No response
The text was updated successfully, but these errors were encountered: