.travis.yml: provide base branch to static tests#10765
.travis.yml: provide base branch to static tests#10765cladmi merged 2 commits intoRIOT-OS:masterfrom
Conversation
0a034a9 to
5f730d4
Compare
jcarrano
left a comment
There was a problem hiding this comment.
Travis is building it, that means it works.
|
Well we should also check against one of the release branches. Let me do a quick rebase. |
5f730d4 to
1f0c409
Compare
1f0c409 to
4a692a4
Compare
|
Mh... Travis doesn't know about |
b5c0e04 to
4a692a4
Compare
|
I think it comes from the cloning method. I will check locally. |
|
It worked with this method. |
|
(I would rather put it in |
|
Yeah, I can change it, I wanted to see if it was working it travis or not. |
122d0a7 to
4e5fe43
Compare
|
Done it myself :-) |
|
And travis likes it. Shall I rebase to master again? |
|
This change probably won't affect PRs against the |
|
I suggest we print the base branch/base commit in the output of the static tests. |
|
If you think that helps, please feel free to open a PR for that. Doesn't really has that much to do with this PR. |
|
Yes please rebase to master and enable "CI: Ready" at the same time. |
4e5fe43 to
2d7be38
Compare
|
Done |
cladmi
left a comment
There was a problem hiding this comment.
ACK, agreed with the changes and it worked against 2018.10-branch (even if this one is getting merged in master).
Putting the fetch in before_script looks like the right place for it.
2d7be38 to
16ff5e0
Compare
|
Without changing anything I force pushed the last commit to re-trigger travis. I think it got confused by the base-branch change. |
Contribution description
In #10759 we noticed that Travis was trying to rebase to
master, though the PR was against2018.10-branch. I suspect the environment was not set properly in #10251. According to the Travis documentation this should be fixed the way I did here.Testing procedure
Run Travis against master and another base branch.
Issues/PRs references
Discovered in #10759, but unrelated.