Build and run latest released doxygen in Travis CI

[cmonr]

Description

It was discovered yesterday that Travis CI is not running the latest released version of doxygen, since the latest released vesrion in Ubuntu Trusty is 1.8.6, not 1.8.14. Further, Travis CI does not have a PPA/distro that has the latest version.

The latest vesrion discovers issues in the repo that the older version does not.

Fixes #8574

The fix

This fix locally builds and installs the latest released version inside Travis CI. A potential future optimization could be to store this binary elsewhere instead of building it every time, but as of now the build step does not take long.

Future work

Once doxygen issues are fixed, the command that will fail the build on new errors can be enabled.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[0xc0170]

travis-ci/docs — Local docs testing has passed

Is that correct, we are up to date? :-)

[iriark01]

Guys just as a comment, the team is "mbed docs". "mbed-os-docs" has just me, and I have no right to manage that team so it won't be up to date.

[cmonr]

Guys just as a comment, the team is "mbed docs". "mbed-os-docs" has just me, and I have no right to manage that team so it won't be up to date.

...huh. Well, until that gets fixed, @AnotherButler @melwee01 would y'all mind taking a look?

[cmonr]

travis-ci/docs — Local docs testing has passed
Is that correct, we are up to date? :-)

@0xc0170 To be more specific, the job is now up to date. There are still doxygen issues, but they won't block CI until we can get them sorted out.

[melwee01]

Looks fine to me, but I don't really know what I'm looking at!

[0xc0170]

Guys just as a comment, the team is "mbed docs". "mbed-os-docs" has just me, and I have no right to manage that team so it won't be up to date.

Note, @adbridge Auto reviewers should use "mbed docs" team

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3511
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8593/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 3130
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8593/

[adbridge]

Guys just as a comment, the team is "mbed docs". "mbed-os-docs" has just me, and I have no right to manage that team so it won't be up to date.

@iriark01 Shall i delete the mbed-os-docs team from GitHub then to avoid confusion ?

[iriark01]

@adbridge yes please

[mbed-ci]

Test : SUCCESS

Build number : 3297
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8593/3297

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 3134
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8593/