Closed markjhoy closed 10 months ago
- the jenkins pipeline appears to do some artifact archiving here; we don't need that any longer?
The artifact_paths
in the pipeline file will upload the artifacts that are the same from the Jenkins version (there's the coverage report in tests
and the gemfile itself in packaging
).
- also looks like maybe we had slack notifications setup (although not 100% sure they were enabled); confirming we no longer need this?
This will be enabled automagically once this gets into main
as we have the notifications set for for all pipelines that are under the enterprise-search
team to flow into the alerting Slack channel.
The
artifact_paths
in the pipeline file will upload the artifacts that are the same from the Jenkins version (there's the coverage report intests
and the gemfile itself inpackaging
).
oh nice, totally missed that, thank you!
This will be enabled automagically once this gets into
main
as we have the notifications set for for all pipelines that are under theenterprise-search
team to flow into the alerting Slack channel.
awesome!
Status | Branch | Result |
---|---|---|
❌ | 8.11 | The branch "8.11" is invalid or doesn't exist |
To backport manually run:
backport --pr 571 --autoMerge --autoMergeMethod squash
Status | Branch | Result |
---|---|---|
❌ | 8.3 | Commit could not be cherrypicked due to conflicts |
❌ | 8.11 | Cherrypick failed because the selected commit (a393128c) is empty. Did you already backport this commit? |
To backport manually run:
backport --pr 571 --autoMerge --autoMergeMethod squash
Status | Branch | Result |
---|---|---|
✅ | 8.3 |
Note: Successful backport PRs will be merged automatically after passing CI.
Please refer to the Backport tool documentation
Migrates the primary pipeline from Jenkins to Buildkite
Checklists
Pre-Review Checklist
v7.13.2
,v7.14.0
,v8.0.0
)