[jira] [Commented] (SOLR-14883) Add a Muse (CI) configuration file
[ https://issues.apache.org/jira/browse/SOLR-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201187#comment-17201187 ] ASF subversion and git services commented on SOLR-14883: Commit 6599cc835a7c47162f0bef5cb37e71cee7590d19 in lucene-solr's branch refs/heads/master from Thomas M. DuBuisson [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=6599cc8 ] SOLR-14883 Add a Muse (Continuous assurance platform) configuration (#1901) * Add a Muse (Continuous assurance platform) configuration The full documentation is docs.muse.dev. Most interesting is the repository configuration reference https://docs.muse.dev/docs/repository-configuration/ which details how to change which tools runs, add custom tools (other than those built into the platform by default), filter for or against certain bug types, etc. For example, an explicit `.muse/config.toml` file might be: ``` jdk11 = true build = "./gradlew assemble" tools = [ "infer", "errorprone", "findsecbugs" ] customTools = [ ] ``` * Add a comment to the toml file > Add a Muse (CI) configuration file > -- > > Key: SOLR-14883 > URL: https://issues.apache.org/jira/browse/SOLR-14883 > Project: Solr > Issue Type: Test > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Thomas DuBuisson >Priority: Trivial > Time Spent: 1h 50m > Remaining Estimate: 0h > > This ticket is a continuation of conversation that started > https://issues.apache.org/jira/browse/SOLR-14819?filter=-2 and was also on > the mailing list. > > The Apache infrastructure team has installed the Muse GitHub application. In > order for Lucene-Solr to benefit the application must understand how to build > the project. While it has build heuristics, it does not guess between JDK8 > or JDK11 (two JDKs most supported by several static analysis tools). Thus, > this configuration explicitly instructs use of JDK11. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14883) Add a Muse (CI) configuration file
[
https://issues.apache.org/jira/browse/SOLR-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17199812#comment-17199812
]
Thomas DuBuisson commented on SOLR-14883:
-
[~dsmiley] Gladly, though I have no links that address this topic.
I work for Muse Dev, a company focused on bringing static analysis closer to
the developer ("shift left" as they say these days). We have been talking with
Apache both in developer to developer engagements and through the foundation at
more of an organizational level. This organization level discussion has
resulted is us getting in touch with the infrastructure team and getting the
GitHub app (also called Muse, often "MuseBot") installed. Though we are small,
we are looking to support Apache and join the community.
The current aim is to run a bug bash at the Apache conference, thus motivating
people to put some elbow grease in as well as a create an atmosphere for
mentoring or pulling in new contributors to the participating Apache projects.
This issue (and the matching PR on github) is part of getting ready for the
bash - regardless of having the app installed we can and certainly will provide
links to the analysis results to the bash participants. However, that's a
misuse of the analysis, which is best used during PRs to surface new issues
when the relevant code is already paged in mentally. Less critically, for the
duration of the bash we will run a leaderboard tallying fixed bugs - earning
precious internet points is easier when the leaderboard updates automatically
via hooks we have in the app.
As for our relation with GitHub, we are separate companies. Our app is
available on GitHub cloud and enterprise as well as on the enterprise version
of GitHub competitors. Certainly we have a symbiotic relationship and contacts
within these companies but it's all pretty cut and dry.
> Add a Muse (CI) configuration file
> --
>
> Key: SOLR-14883
> URL: https://issues.apache.org/jira/browse/SOLR-14883
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Thomas DuBuisson
>Priority: Trivial
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This ticket is a continuation of conversation that started
> https://issues.apache.org/jira/browse/SOLR-14819?filter=-2 and was also on
> the mailing list.
>
> The Apache infrastructure team has installed the Muse GitHub application. In
> order for Lucene-Solr to benefit the application must understand how to build
> the project. While it has build heuristics, it does not guess between JDK8
> or JDK11 (two JDKs most supported by several static analysis tools). Thus,
> this configuration explicitly instructs use of JDK11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14883) Add a Muse (CI) configuration file
[ https://issues.apache.org/jira/browse/SOLR-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17199686#comment-17199686 ] David Smiley commented on SOLR-14883: - Can you please add some links here on ASF infra's / GitHub's relationship to Muse? I'm not familiar. > Add a Muse (CI) configuration file > -- > > Key: SOLR-14883 > URL: https://issues.apache.org/jira/browse/SOLR-14883 > Project: Solr > Issue Type: Test > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Thomas DuBuisson >Priority: Trivial > Time Spent: 0.5h > Remaining Estimate: 0h > > This ticket is a continuation of conversation that started > https://issues.apache.org/jira/browse/SOLR-14819?filter=-2 and was also on > the mailing list. > > The Apache infrastructure team has installed the Muse GitHub application. In > order for Lucene-Solr to benefit the application must understand how to build > the project. While it has build heuristics, it does not guess between JDK8 > or JDK11 (two JDKs most supported by several static analysis tools). Thus, > this configuration explicitly instructs use of JDK11. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
