You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cayenne.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/01/06 10:56:57 UTC

Jenkins build became unstable: Cayenne pull requests #98

See <https://builds.apache.org/job/Cayenne%20pull%20requests/98/changes>

Re: Jenkins build became unstable: Cayenne pull requests #98

Posted by Robert Zeigler <ro...@puregumption.com>.

Jenkins builds can become unstable for any number of reasons. For instance:

* code coverage falls below a preset threshold for stability
* Linting tools found more than a preset threshold number ( or percentage) of problems

To name a few.  If you go into the jenkins management console, you should be able to hover over the “health” icon of the build and see a tooltip with some details regarding why the indicated build has the indicated health status.

Robert

> On Jan 6, 2016, at 1/69:14 AM , Andrus Adamchik <an...@objectstyle.org> wrote:
> 
> 
>> On Jan 6, 2016, at 4:56 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
>> 
>> See <https://builds.apache.org/job/Cayenne%20pull%20requests/98/changes>
>> 
> 
> "Unstable"? Jenkins emails are as cryptic as ever.

Re: Jenkins build became unstable: Cayenne pull requests #98

Posted by Andrus Adamchik <an...@objectstyle.org>.

> On Jan 6, 2016, at 4:56 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
> 
> See <https://builds.apache.org/job/Cayenne%20pull%20requests/98/changes>
> 

"Unstable"? Jenkins emails are as cryptic as ever.