This is an example of BLE GATT Client, which receives broadcast data from BLE_Server_BME280 ( a GATT server) , then transfers values up to mbed Device Connector (cloud).

Please refer details about BLEClient_mbedDevConn below. https://github.com/soramame21/BLEClient_mbedDevConn

The location of required BLE GATT server, BLE_Server_BME280, is at here. https://developer.mbed.org/users/edamame22/code/BLE_Server_BME280/

Revision:
0:29983394c6b6
diff -r 000000000000 -r 29983394c6b6 pal/Jenkinsfile
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pal/Jenkinsfile	Thu Apr 13 04:48:11 2017 +0000
@@ -0,0 +1,45 @@
+
+try {
+  // Reserve an executor from node with label arm-none-eabi-gcc
+  node ("arm-none-eabi-gcc") {
+    // Ensure a clean build by deleting any previous Jenkins workarea
+    deleteDir()
+    // Add timestamps to Jenkins console log
+    timestamps {
+      env.MBEDOS_ROOT = pwd()
+      // Define a Jenkins stage for logging purposes
+      stage ("prepare environment") {
+        // Create a directory and execute steps there
+        dir ("mbed-client-pal") {
+          // clone the sw under test, either branch or PR depending on trigger
+          checkout scm
+        }
+        
+        dir ("mbed-os") {
+          git "git@github.com:ARMmbed/mbed-os"
+          execute ("git checkout tags/mbed-os-5.2")
+        }
+        
+        
+        // Add mbed components
+        execute ("mbed new .")
+
+        // Execute shell command, edit file with sed
+
+
+        writeFile file: 'mbed-os/features/frameworks/.mbedignore', text: '*'
+
+      }
+      
+      stage ("build") {
+        dir ("mbed-client-pal/Test") {
+          execute ("make mbedOS_all")
+        }
+      }
+    }
+  }
+} catch (error) {
+    currentBuild.result = 'FAILURE'
+
+
+}