[snapshot] First APM package ever

[jalvz]

🎉

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #688 updated

• Start Time: 2020-12-10T13:58:32.145+0000

• Duration: 11 min 26 sec

Test stats 🧪

Test	Results
Failed	0
Passed	56
Skipped	0
Total	56

[jalvz]

@ruflin @mtojek lint is failing because it needs elastic/package-registry#656, which is not yet into the last tagged version of the registry.

I'd like to merge this asap to start "serious testing ™️": is it ok to do it before releasing a new registry version, or something bad will happen?
OTOH, when should we expect a new registry/spec release?

[ruflin]

I suggest we just do a new release of the registry and spec today? @mtojek @ycombinator Do you see any problem with that?

[axw]

LGTM!

[jalvz]

I suggest we just do a new release of the registry and spec today?

@ruflin @mtojek @ycombinator who usually takes care of that, and/or where are the docs for that matter? - ie. any specific release procedure beyond tagging the latest commit?

[mtojek]

Let's first make this PR green.

It looks like there is a problem with validation: no support for traces. I suppose that's because of not bumped up revision in the package storage repository (Dockerfile: https://github.com/elastic/package-storage/blob/snapshot/Dockerfile#L7).

Here are the steps on how to prepare and release the next revision of package-registry: https://github.com/elastic/package-registry#release

[ruflin]

@jalvz Can you prepare a new release for the registry? @mtojek Can you assist him?

[jalvz]

It looks like there is a problem with validation: no support for traces. I suppose that's because of not bumped up revision

Exactly, that's why we need a release first (see #688 (comment))

PR up: elastic/package-registry#661

[jalvz]

This is green now, thanks all. Can some of you have a look at 4322c24 ?

[mtojek]

The CI is green, LGTM!

Keep in mind that you'll have to adjust also other branches (staging, production) with the updated registry version.

[ph]

This is great! !