Skip to content

Conversation

@staticfloat
Copy link
Member

No description provided.

- master
- staging
- trying
- /^v[0-9]+\.[0-9]+\.[0-9]+$/ # version tags
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

keep these?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we keep these, that means there will be no CI run on pull requests.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these are only for branch pushes, not PRs.

only:
- staging
- trying
- /^v[0-9]+\.[0-9]+\.[0-9]+$/ # version tags
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

keep?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we keep this, that means there will be no CI run on pull requests.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those are only for branch pushes,not PRs.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So according to #1401 it looks like it's half-true; we don't get the build of the tip of the PR branch (Which I think is valuable, it helps to debug bad interactions and general flakiness) so perhaps what we should do is to add /^refs/pull/.*/ or something, so that we get both, but we don't get pushes of branches that don't have a PR open, to keep the number of unnecessary CI runs down?

@staticfloat staticfloat force-pushed the sf/enable_travis_appveyor branch from 95517ef to a647b73 Compare September 18, 2019 22:38
@codecov
Copy link

codecov bot commented Sep 18, 2019

Codecov Report

Merging #1400 into master will increase coverage by 0.09%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1400      +/-   ##
==========================================
+ Coverage   87.51%   87.61%   +0.09%     
==========================================
  Files          25       25              
  Lines        5335     5335              
==========================================
+ Hits         4669     4674       +5     
+ Misses        666      661       -5
Impacted Files Coverage Δ
src/Operations.jl 92.8% <0%> (+0.41%) ⬆️
src/PlatformEngines.jl 77.5% <0%> (+0.69%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f5a1b2...42d7d83. Read the comment docs.

@staticfloat staticfloat force-pushed the sf/enable_travis_appveyor branch from a647b73 to 42d7d83 Compare September 18, 2019 22:42
@staticfloat staticfloat force-pushed the sf/enable_travis_appveyor branch from 42d7d83 to 25e2265 Compare September 19, 2019 15:53
@staticfloat
Copy link
Member Author

Merging this as well, to get CI working again.

@staticfloat staticfloat merged commit 266c327 into master Sep 19, 2019
@staticfloat staticfloat deleted the sf/enable_travis_appveyor branch September 19, 2019 15:54
fredrikekre pushed a commit that referenced this pull request Sep 20, 2019
(cherry picked from commit 266c327, PR #1400)
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.

3 participants