clayburn opened a new pull request, #3782:
URL: https://github.com/apache/streampipes/pull/3782
<!--
~ Licensed to the Apache Software Foundation (ASF) under one or more
~ contributor license agreements. See the NOTICE file distributed with
~ this work for additional information regarding copyright ownership.
~ The ASF licenses this file to You under the Apache License, Version 2.0
~ (the "License"); you may not use this file except in compliance with
~ the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
~
-->
<!--
Thanks for contributing! Here are some tips you can follow to help us
incorporate your contribution quickly and easily:
1. If this is your first time, please read our contributor guidelines:
- https://streampipes.apache.org/community/get-involved/
- https://cwiki.apache.org/confluence/display/STREAMPIPES/Getting+Started
2. Make sure the PR title is formatted like: `[#<GitHub issue id>] PR title
...`
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
`[WIP][#<GitHub issue id>] PR title ...`.
4. Please write your PR title to summarize what this PR proposes/fixes.
5. Link the PR to the corresponding GitHub issue (if present) in the
`Development` section in the right menu bar.
6. Be sure to keep the PR description updated to reflect all changes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
8. Make sure tests pass via `mvn clean install`.
9. (Optional) If the contribution is large, please file an Apache ICLA
- http://apache.org/licenses/icla.pdf
-->
### Purpose
<!--
Please clarify what changes you are proposing and describe how those changes
will address the issue.
Furthermore, describe potential consequences the changes might have.
-->
@dominikriemer - this is the PR we discussed at Community over Code this
weekend. This is mergeable already, but please note a few things:
- This PR will not generate build scans until ASF Infra adds the
`STREAMPIPES_DEVELOCITY_ACCESS_KEY` secret to your repo. As far as I know, this
has not yet happened.
- This PR will not generate build scans as it originates from my fork and my
fork cannot access those secrets. You are welcome to push my branch to the
apache/streampipes repo to test it with access to secrets.
This PR publishes a Build Scan for every CI build and for every local build
from an authenticated Apache committer. The build will not fail if publishing
fails.
The Build Scans of the Apache Streampipes project are published to the
Develocity instance at [develocity.apache.org](https://develocity.apache.org/),
hosted by the Apache Software Foundation and run in partnership between the ASF
and Gradle. This Develocity instance has all features and extensions enabled
and is freely available for use by the Apache Streampipes project and all other
Apache projects.
On this Develocity instance, Apache Streampipes will have access not only to
all of the published Build Scans but other aggregate data features such as:
- Dashboards to view all historical Build Scans, along with performance
trends over time
- Build failure analytics for enhanced investigation and diagnosis of build
failures
- Test failure analytics to better understand trends and causes around slow,
failing, and flaky tests
Please let me know if there are any questions about the value of Develocity
or the changes in this pull request and I’d be happy to address them.
### Remarks
<!--
Is there anything left we need to pay attention on?
Are there some references that might be important? E.g. links to Confluence,
or discussions
on the mailing list or GitHub.
-->
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@streampipes.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
