The user of these tasks is blissfully unaware of some of the more advanced Ant script approaches used to implement them, which is how things should be when providing good Ant tasks. When put together the two Tasks work very well together, allowing you to login and pass the resulting Session Id to the query task, then parse the results according to your needs with a small peace of inline JavaScript to parse the resulting JSON. You can see both the and tasks in Task further leverages the task to make a call to the Salesforce REST API query end point. The following shows how the Salesforce task was built for last years blog. You can implement these in Java or Ant script itself, using the Ant task. The goal once again was keeping it 100% Ant, this time invoking the Salesforce REST API to perform queries.Īs before the new Ant tasks are defined in single XML file, ant-salesforce.xml, you can download the updated version with the new task and easily into your own Ant scripts.Īnt provides an excellent way to encapsulate complex script in components it calls Tasks. While working with one of ‘s new up and coming DevOps team members Brad Slater (also see Object Model Tool). In addition i wanted share how i was able to recently extend this approach. In this blog i’d like to talk a little bit more about how it was done and highlight the excellent Ant task from Missing Link (so named since surprisingly Ant has yet to provide a core task for HTTP comms). Making the resulting script platform neutral and easier to manage. However there was another goal, that is i wanted to invoke Salesforce API’s using only native Ant script and 100% Java based Apache Ant tasks, so no Java coding or native curl executable invocations. Back in June last year i wrote a blog entitled Look ma, no hands!, its main focus was how to leverage the then new ability to install and uninstall packages via the Metadata API.
0 Comments
Leave a Reply. |