tylerbertrand opened a new pull request, #731:
URL: https://github.com/apache/unomi/pull/731

   Hi @sergehuber, it was nice to meet you at Community over Code! Thought I'd 
go ahead and submit a PR connecting unomi to Apache's Develocity instance so 
that you could check it out whenever you get a chance.
   
   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 unomi 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 unomi project and all other Apache 
projects.
   
   On this Develocity instance, Apache unomi 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.
   
   Probably not necessary, but following the checklist, I ran the integration 
tests, and here is the resulting [Build 
Scan](https://ge.solutions-team.gradle.com/s/rzqvtq5vbk22e) with those [test 
results](https://ge.solutions-team.gradle.com/s/rzqvtq5vbk22e/tests/overview). 
   
   ----
   
   **Please** following this checklist to help us incorporate your contribution 
quickly and easily:
   
    - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/UNOMI) filed 
          for the change (usually before you start working on it).  Trivial 
changes like typos do not 
          require a JIRA issue.  Your pull request should address just this 
issue, without pulling in other changes.
    - [ ] Format the pull request title like `[UNOMI-XXX] - Title of the pull 
request`
    - [ ] Provide integration tests for your changes, especially if you are 
changing the behavior of existing code or adding
          significant new parts of code.
    - [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why. 
          Copy the description to the related JIRA issue
    - [x] Run `mvn clean install -P integration-tests` to make sure basic 
checks pass. A more thorough check will be 
           performed on your pull request automatically.
    - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   


-- 
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...@unomi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to