[WIP] New pull request triggers


(Mishal Shah) #1

I am currently working on adding new pull request triggers to ci.swift.org, you might have already seen few of them as we test them out.

Following phrases for apple/swift.git will be added:

Benchmark
Phrase: @swift-ci Please benchmark
Description: Benchmark job will compare the results between targeted branch and pull request.
Build config: swift/utils/build-script -R --no-assertions --benchmark

Test and merge
Phrase: @swift-ci Please test and merge
Description: Test and merge job will run tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}”

Smoke test and merge
Phrase: @swift-ci Please smoke test and merge
Description: Smoke Test and merge job will run limited tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}"

ASAN Testing
Phrase: @swift-ci Please ASAN test
Description: ASAN testing job
Build config: swift/utils/build-script" --preset=buildbot_incremental_asan,tools=RDA,stdlib=RDA

Python Lint
Phrase: @swift-ci Please Python lint
Description: Python lint using pep8 rules
Build config: flake8 | cut -f4- -d: | sort | uniq -c

These new triggers are a work in progress, I will send out another email once they are available for use.

Please let me know if you have any feedback.

Thanks,
Mishal Shah


(Andrew Trick) #2

I am currently working on adding new pull request triggers to ci.swift.org <http://ci.swift.org/>, you might have already seen few of them as we test them out.

This is really exciting...

Following phrases for apple/swift.git will be added:

Benchmark
Phrase: @swift-ci Please benchmark
Description: Benchmark job will compare the results between targeted branch and pull request.
Build config: swift/utils/build-script -R --no-assertions --benchmark

Test and merge
Phrase: @swift-ci Please test and merge
Description: Test and merge job will run tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}”

Smoke test and merge
Phrase: @swift-ci Please smoke test and merge
Description: Smoke Test and merge job will run limited tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}”

This is the same build-script invocation as non-smoke testing. How can we reproduce each of the test configurations locally? Can we reveal that information on ci.swift.org <http://ci.swift.org/> just like the build config?

Will the smoke tests cover everything run by the incremental builders?

ASAN Testing
Phrase: @swift-ci Please ASAN test
Description: ASAN testing job
Build config: swift/utils/build-script" --preset=buildbot_incremental_asan,tools=RDA,stdlib=RDA

Python Lint
Phrase: @swift-ci Please Python lint
Description: Python lint using pep8 rules
Build config: flake8 | cut -f4- -d: | sort | uniq -c

These new triggers are a work in progress, I will send out another email once they are available for use.

Great. Please make all of this information visible on ci.swift.org <http://ci.swift.org/>, or link directly to the swift.org <http://swift.org/> pages that have the info.

Andy

···

On Mar 23, 2016, at 4:26 PM, Mishal Shah via swift-dev <swift-dev@swift.org> wrote:

Please let me know if you have any feedback.

Thanks,
Mishal Shah
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev


(Mishal Shah) #3

I am currently working on adding new pull request triggers to ci.swift.org <http://ci.swift.org/>, you might have already seen few of them as we test them out.

This is really exciting…

Thanks!

Following phrases for apple/swift.git will be added:

Benchmark
Phrase: @swift-ci Please benchmark
Description: Benchmark job will compare the results between targeted branch and pull request.
Build config: swift/utils/build-script -R --no-assertions --benchmark

Test and merge
Phrase: @swift-ci Please test and merge
Description: Test and merge job will run tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}”

Smoke test and merge
Phrase: @swift-ci Please smoke test and merge
Description: Smoke Test and merge job will run limited tests on Ubuntu 14.04 and OS X platform and merge the pull request if all of the tests pass.
Build config:
  OS X: swift/utils/build-script --preset=buildbot_all_platforms,tools=RA,stdlib=RA
  Linux: swift/utils/build-script --preset=buildbot_linux_1404 install_destdir="${SWIFT_INSTALL_DIR}" installable_package="${SWIFT_INSTALLABLE_PACKAGE}”

Correction: Smoke test and merge will be using swift/utils/build-script --preset=buildbot_incremental,tools=RA,stdlib=RA

This is the same build-script invocation as non-smoke testing. How can we reproduce each of the test configurations locally? Can we reveal that information on ci.swift.org <http://ci.swift.org/> just like the build config?

The build config information is available in the description of each job.

Will the smoke tests cover everything run by the incremental builders?

It will be covered by preset buildbot_incremental,tools=RA,stdlib=RA

···

On Mar 23, 2016, at 5:01 PM, Andrew Trick <atrick@apple.com> wrote:

On Mar 23, 2016, at 4:26 PM, Mishal Shah via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:

ASAN Testing
Phrase: @swift-ci Please ASAN test
Description: ASAN testing job
Build config: swift/utils/build-script" --preset=buildbot_incremental_asan,tools=RDA,stdlib=RDA

Python Lint
Phrase: @swift-ci Please Python lint
Description: Python lint using pep8 rules
Build config: flake8 | cut -f4- -d: | sort | uniq -c

These new triggers are a work in progress, I will send out another email once they are available for use.

Great. Please make all of this information visible on ci.swift.org <http://ci.swift.org/>, or link directly to the swift.org <http://swift.org/> pages that have the info.

Andy

Please let me know if you have any feedback.

Thanks,
Mishal Shah
_______________________________________________
swift-dev mailing list
swift-dev@swift.org <mailto:swift-dev@swift.org>
https://lists.swift.org/mailman/listinfo/swift-dev


(Andrew Trick) #4

Ok. That makes sense. I see that the build preset also invokes the tests, but that the incremental build (smoke test) skips all device testing, while the normal build runs the simulator.

Thanks for explaining.

Andy

···

On Mar 23, 2016, at 5:21 PM, Mishal Shah <mishal_shah@apple.com> wrote:

Will the smoke tests cover everything run by the incremental builders?

It will be covered by preset buildbot_incremental,tools=RA,stdlib=RA