Skip to content

[internal] Reject CI builds if any .rej files exist#6692

Merged
epixa merged 1 commit intoelastic:masterfrom
epixa:reject-rej-files
Mar 29, 2016
Merged

[internal] Reject CI builds if any .rej files exist#6692
epixa merged 1 commit intoelastic:masterfrom
epixa:reject-rej-files

Conversation

@epixa
Copy link
Copy Markdown
Contributor

@epixa epixa commented Mar 29, 2016

.rej are the byproduct of failed patches via git-apply or artifacts of
the backporting process through jasper. Any build that has them should
be rejected early.

.rej are the byproduct of failed patches via git-apply or artifacts of
the backporting process through jasper. Any build that has them should
be rejected early.
@epixa
Copy link
Copy Markdown
Contributor Author

epixa commented Mar 29, 2016

The easiest way to test this is probably to just create some random .rej files and then make sure the task is rejected with them:

touch foo.rej
touch src/bar.rej
touch node_modules/wat.rej
node_modules/.bin/grunt rejectRejFiles

Then confirm that the task does not fail with .rej files in node_modules:

rm foo.rej
rm src/bar.rej
node_modules/.bin/grunt rejectRejFiles

@Bargs
Copy link
Copy Markdown
Contributor

Bargs commented Mar 29, 2016

LGTM

@epixa epixa merged commit cc15b53 into elastic:master Mar 29, 2016
@epixa epixa deleted the reject-rej-files branch March 29, 2016 19:54
elastic-jasper added a commit that referenced this pull request Mar 29, 2016
---------

**Commit 1:**
[internal] Reject CI builds if any .rej files exist

.rej are the byproduct of failed patches via git-apply or artifacts of
the backporting process through jasper. Any build that has them should
be rejected early.

* Original sha: 55e429c
* Authored by Court Ewing <court@epixa.com> on 2016-03-29T17:24:24Z
elastic-jasper added a commit that referenced this pull request Mar 29, 2016
---------

**Commit 1:**
[internal] Reject CI builds if any .rej files exist

.rej are the byproduct of failed patches via git-apply or artifacts of
the backporting process through jasper. Any build that has them should
be rejected early.

* Original sha: 55e429c
* Authored by Court Ewing <court@epixa.com> on 2016-03-29T17:24:24Z
epixa added a commit that referenced this pull request Mar 29, 2016
---------

**Commit 1:**
[internal] Reject CI builds if any .rej files exist

.rej are the byproduct of failed patches via git-apply or artifacts of
the backporting process through jasper. Any build that has them should
be rejected early.

* Original sha: 55e429c
* Authored by Court Ewing <court@epixa.com> on 2016-03-29T17:24:24Z
epixa added a commit that referenced this pull request Mar 29, 2016
epixa added a commit that referenced this pull request Mar 29, 2016
epixa added a commit that referenced this pull request Mar 29, 2016
@epixa epixa added v4.5.2 and removed v4.5.1 labels May 14, 2016
@epixa epixa added v4.5.4 and removed v4.5.2 labels Jul 21, 2016
@epixa epixa removed the v4.4.3 label Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants