Skip to content

Fixing evolutions command to return a non-cero exit code when evolutions fail. This is helpful to prevent false positives when running on CI servers like jenkins.#534

Merged
pepite merged 1 commit intoplayframework:masterfrom
edovale:master
Dec 29, 2012

Conversation

@edovale
Copy link
Copy Markdown

@edovale edovale commented Aug 17, 2012

... fail. This is helpful to prevent false positives when running on CI servers like jenkins.

…ons fail. This is helpful to prevent false positives when running on CI servers like jenkins.
@edovale
Copy link
Copy Markdown
Author

edovale commented Aug 21, 2012

Any news on this?

@pepite
Copy link
Copy Markdown
Contributor

pepite commented Dec 29, 2012

Is there a lighthouse issue for that one?

@ghost ghost assigned pepite Dec 29, 2012
@pepite pepite closed this Dec 29, 2012
@pepite pepite reopened this Dec 29, 2012
@pepite
Copy link
Copy Markdown
Contributor

pepite commented Dec 29, 2012

Ok missread completely the pull request.

pepite added a commit that referenced this pull request Dec 29, 2012
Fixing evolutions command to return a non-cero exit code when evolutions fail. This is helpful to prevent false positives when running on CI servers like jenkins.
@pepite pepite merged commit 0861a85 into playframework:master Dec 29, 2012
pepite added a commit that referenced this pull request Dec 29, 2012
Fixing evolutions command to return a non-cero exit code when evolutions fail. This is helpful to prevent false positives when running on CI servers like jenkins.
pepite added a commit that referenced this pull request Dec 29, 2012
Fixing evolutions command to return a non-cero exit code when evolutions fail. This is helpful to prevent false positives when running on CI servers like jenkins.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants