[
https://issues.apache.org/jira/browse/SOLR-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865229#comment-16865229
]
Marcus Eagan edited comment on SOLR-13537 at 6/17/19 1:37 AM:
--------------------------------------------------------------
[~elyograg] I was using the Solr artifact/Solr builds so I put it in the Solr
Jira. I've now added the Lucene artifact. So would it be appropriate for
either, or default to Lucene?
More committers in the future could be using GitHub a lot more. That is a
reasonable assumption that I made but it could turn out to be false.
One of my initial motivations was to inspire others to dig into why things were
red. I do not think there's any reputation problem at risk here. Many projects
are often red.
There have been instances, though infrequently, where Lucene did not compile.
Those builds would have been red, but usually Solr is green. It's almost always
green for that task.
Perfect world the tests pass when they should and fail when they should not.
was (Author: marcussorealheis):
[~elyograg] I was using the Solr artifact so I put it in the Solr Jira. I've
now added the Lucene artifact. So would it be appropriate for either, or
default to Lucene?
More committers in the future could be using GitHub a lot more. That is a
reasonable assumption that I made.
One of my initial motivations was to inspire others to dig into why things were
red. I do not think there's any reputation problem at risk here. Many projects
are often red.
There have been instances, though infrequently, where Lucene did not compile.
Those builds would have been red, but usually Solr is green. It's almost always
green for that task.
Perfect world the tests pass when they should and fail when they should not.
> Build Status Badge in git README
> --------------------------------
>
> Key: SOLR-13537
> URL: https://issues.apache.org/jira/browse/SOLR-13537
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build, documentation
> Affects Versions: master (9.0), 8.2
> Reporter: Marcus Eagan
> Priority: Trivial
> Attachments: Markdown Preview Of Build Status README.png, Simple
> Artifact Build Badge.png, Simple Artifact Build Badges.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to aid developers and DevOps engineers who are working in a
> git-driven ecosystem, it would be helpful to see the status builds in the
> README. This is a standard for many open source projects. I think one could
> debate whether we should have a multi-line build badge visual in the README
> because people need to know about the builds for various versions and
> platforms in the case of Lucene/Solr because it is such a large and widely
> used project, in a variety of environments. The badges not only celebrate
> that fact, they support its persistence in the future with new developers who
> look for such information instictively.
> I would recommend the active build pipelines (currently 8.x and 9.x) for each
> platform, Linux, Windows, MacOSX, and Solaris.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
