Implement minimal pipeline to publish a package #731
Conversation
mtojek
changed the title
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
/test |
mtojek
force-pushed
the
implement-minimal-pipeline
branch
from
b25a703 to
947273c
Compare
| steps { | ||
| cleanup(source: 'build-package') | ||
| dir("${BASE_DIR}") { | ||
| packageStoragePublish('build/integrations') |
There was a problem hiding this comment.
I'd vote for moving this to a shared library, so signing and publishing in any repository is basically a one line :)
We would need to see how to pass all the parameters in case environment is not recommended.
There was a problem hiding this comment.
I guess that it would be a big input map with all properties :) I'm ok with moving it there, not sure if I should do this now or later. WDYT?
I guess it's a matter of priorities: indexing & package registry implementation vs. support in apm-pipeline-library
There was a problem hiding this comment.
Yes, do it later, no need to do it now.
| withGoEnv() { | ||
| dir("${BASE_DIR}") { | ||
| sh(label: 'Install elastic-package',script: "make install") | ||
| // sh(label: 'Install elastic-package', script: 'go build github.com/elastic/elastic-package') |
There was a problem hiding this comment.
Yes, as for anyone outside of the elastic-package most likely it would be the other command.
3 participants
Related: #728
This PR implements the minimal pipeline required to publish a package to the Package Storage v2. I extracted the publishing part from the main Jenkinsfile and put it in a separate mini-pipeline. We can discuss if/what we should we push to the apm-pipeline-library.