Skip to content

Conversation

@TheNeuralBit
Copy link
Member

@TheNeuralBit TheNeuralBit commented Nov 30, 2020

Instead of running IT classes in the :test task, this PR runs them in a separate :integrationTest task, which is run by the Java PostCommit.

Post-Commit Tests Status (on master branch)

Lang SDK Dataflow Flink Samza Spark Twister2
Go Build Status --- Build Status --- Build Status ---
Java Build Status Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status
Build Status
Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
--- Build Status ---
XLang Build Status Build Status Build Status --- Build Status ---

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website Whitespace Typescript
Non-portable Build Status Build Status
Build Status
Build Status
Build Status
Build Status Build Status Build Status Build Status
Portable --- Build Status --- --- --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests

See CI.md for more information about GitHub Actions CI.

@TheNeuralBit
Copy link
Member Author

Run Java PostCommit

@TheNeuralBit
Copy link
Member Author

Run Spotless PreCommit

@TheNeuralBit TheNeuralBit changed the title Create :sdks:java:extensions:ml:integrationTest target, run in Java PostCommit [BEAM-11363] Create :sdks:java:extensions:ml:integrationTest target, run in Java PostCommit Nov 30, 2020
@TheNeuralBit
Copy link
Member Author

Run Java PostCommit

])

// Disable Gradle cache: these ITs interact with live service that should always be considered "out of date"
outputs.upToDateWhen { false }
Copy link
Member

Choose a reason for hiding this comment

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

Just want to note that "UP-TO-DATE" and "FROM-CACHE" are two different Gradle statuses for a task. I presume if it is never up to date it is also never cached...

Copy link
Member Author

@TheNeuralBit TheNeuralBit Dec 3, 2020

Choose a reason for hiding this comment

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

I copied this from

// Disable Gradle cache: these ITs interact with live service that should always be considered "out of date"
outputs.upToDateWhen { false }

I can update the comments in both places to be more correct - it sounds like just dropping "Disable Gradle cache:" would address it?

@kennknowles kennknowles merged commit 0a4bdb1 into apache:master Dec 3, 2020
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