Skip to content

Move CloudBees tests to Travis-CI #159

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
merged 2 commits into from
Jun 20, 2018
Merged

Move CloudBees tests to Travis-CI #159

merged 2 commits into from
Jun 20, 2018

Conversation

brarcher
Copy link
Contributor

No description provided.

@brarcher brarcher force-pushed the travis branch 2 times, most recently from 76cf558 to a583600 Compare June 20, 2018 01:01
If a strdup() fails a NULL pointer would be passed to
mkstemp(), and it does not accept NULL pointers.

This was discovered using scan-build.
Earlier this year GitHub deprecated some encryption types from
accessing repos. This broke the FC17 executors on CloudBees.
Trying to update to using the FC25 executors found that not
all tools were installed. CloudBees determined it would take
too much time to install the missing tools on FC25 which were
on FC17 (for a FOSS project), and declined to do so. As a result,
Check's tests no longer run on CloudBees.

In response, the tests which ran on CloudBees are being moved
to Travis-CI. This includes the pre release check, building the
documentation, building with scan-build, and building with some
of the configure arguments.
@brarcher brarcher merged commit 8822b87 into master Jun 20, 2018
@brarcher brarcher deleted the travis branch June 20, 2018 17:16
@brarcher brarcher changed the title Add pre-release check to travis-ci Move CloudBees tests to Travis-CI Jun 20, 2018
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.

1 participant