-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update the pipeline definition and document the library #153
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsanz
changed the title
add pipeline to catalog
Update the pipeline definition and document the library
Mar 28, 2023
@nickpeihl I'm going to merge this to ensure the file is valid |
jsanz
added a commit
to jsanz/ems-client
that referenced
this pull request
Apr 18, 2023
* Include the pipeline definition in the catalog metadata file * Allow only read for users outside EMS * Document a component for Backstage (cherry picked from commit cbe829e)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
jsanz
added a commit
that referenced
this pull request
Apr 18, 2023
…145) | Remove Jenkins CI jobs (#147) | Create catalog-info file (#152) | Update the pipeline definition and document the library (#153) | Add CI docs (#150) | Adds the e (#161) * [Buildkite] Setting up CI to test the library on Pull Requests (#145) * New pipeline with Buildkite * Install yarn and test * Run everything in a single step * Added notification to slack section * Remove the notify section, to avoid duplicates * Adds configuration for the Github webhook * Add the new custom agent image for EMS projects (cherry picked from commit cac7786) * Remove Jenkins CI jobs (#147) (cherry picked from commit af70899) * Create catalog-info file (#152) Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com> (cherry picked from commit d6d4a4c) * Update the pipeline definition and document the library (#153) * Include the pipeline definition in the catalog metadata file * Allow only read for users outside EMS * Document a component for Backstage (cherry picked from commit cbe829e) * Add CI docs (#150) * Add CI docs * Small addition (cherry picked from commit 7a81fd7) # Conflicts: # CHANGELOG.md * Adds the env var to enable comments on PRs (#154) (cherry picked from commit 08da0aa) * Switching to a separate script for better logging (#158) (cherry picked from commit bae3059) --------- Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com>
jsanz
added a commit
to jsanz/ems-client
that referenced
this pull request
May 2, 2023
* Include the pipeline definition in the catalog metadata file * Allow only read for users outside EMS * Document a component for Backstage
jsanz
added a commit
that referenced
this pull request
May 2, 2023
* [Buildkite] Setting up CI to test the library on Pull Requests (#145) * New pipeline with Buildkite * Install yarn and test * Run everything in a single step * Added notification to slack section * Remove the notify section, to avoid duplicates * Adds configuration for the Github webhook * Add the new custom agent image for EMS projects * Remove Jenkins CI jobs (#147) * Create catalog-info file (#152) Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com> * Update the pipeline definition and document the library (#153) * Include the pipeline definition in the catalog metadata file * Allow only read for users outside EMS * Document a component for Backstage * Adds the env var to enable comments on PRs (#154) * Switching to a separate script for better logging (#158) * Update yarn lockfile --------- Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com>
jsanz
added a commit
that referenced
this pull request
May 2, 2023
* fix: upgrade semver from 7.3.5 to 7.4.0 Snyk has created this PR to upgrade semver from 7.3.5 to 7.4.0. See this package in npm: See this project in Snyk: https://app.snyk.io/org/maps/project/69984185-62be-4592-9972-95d0364d0cba?utm_source=github-enterprise&utm_medium=referral&page=upgrade-pr * [Buildkite] Setting up CI to test the library on Pull Requests (#145) * New pipeline with Buildkite * Install yarn and test * Run everything in a single step * Added notification to slack section * Remove the notify section, to avoid duplicates * Adds configuration for the Github webhook * Add the new custom agent image for EMS projects * Remove Jenkins CI jobs (#147) * Create catalog-info file (#152) Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com> * Update the pipeline definition and document the library (#153) * Include the pipeline definition in the catalog metadata file * Allow only read for users outside EMS * Document a component for Backstage * Adds the env var to enable comments on PRs (#154) * Switching to a separate script for better logging (#158) --------- Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: elastic-backstage-prod[bot] <123036547+elastic-backstage-prod[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up from #152
Component
in Backstage (example for reference)