forked from tango-controls/cppTango
-
Notifications
You must be signed in to change notification settings - Fork 0
update #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
lorenzopivetta
merged 25 commits into
lorenzopivetta:tango-9-lts
from
tango-controls:tango-9-lts
Apr 23, 2020
Merged
update #3
lorenzopivetta
merged 25 commits into
lorenzopivetta:tango-9-lts
from
tango-controls:tango-9-lts
Apr 23, 2020
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o be the same as ZMQ
The common case is that we are not debugging MSVC failures, therefore we don't need to wait until the timeout hits if an error occurred. This can be easily changed back for debugging.
Automate the deployment from appveyor. We want to publish all artifacts as a new draft prelease on tag push only. For reference see https://www.appveyor.com/docs/deployment/github/ and https://www.appveyor.com/docs/appveyor-yml/. I have created a new github machine user named cppTango-bot for that. And also a personal access token which was encrypted on the appveyor site.
skip_cleanup is now deprecated, and cleanup is false by default. Please refer to https://blog.travis-ci.com/2019-08-27-deployment-tooling-dpl-v2-preview-release for more details
We now support switching the test suite build off using the standard CTest option BUILD_TESTING. This allows environments where the test compilation fails to skip it in a consistent manner. This also removes the unconditional call to enable_testing() which the CTest module now does only if BUILD_TESTING is ON. Co-authored-by: Michal Liszcz <liszcz.michal@gmail.com>
appveyor.yml: Fail jobs faster
Automate the deployment from appveyor. All artifacts are published as assets for a new draft prelease on tag push only. For reference see https://www.appveyor.com/docs/deployment/github/ and https://www.appveyor.com/docs/appveyor-yml/. A new github machine user named cppTango-bot has been created for that and also a personal access token which was encrypted on the appveyor site.
…e-tests CMakeLists.txt: Add option to disable building the test suite
…ecking Fix omniidl error checks
The next version will not be binary compatible with cppTango 9.3 versions.
Tests that event subscription is restored immediately after the device restart.
Cleanup taco
…r-dev-restart-attempt-2 Fix #496 blind event clients after dev restart (attempt 2)
…_for_cppzmq Allow different paths for CPPZMQ and ZMQ
Fixes issue with failing ubuntu:focal jobs due to tzdata package asking user to provide information about location and timezone.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.