Refactor task names

[ghale]

Since we support both jobs and views now, it makes sense to refactor the task names from "updateJenkinsJobs" to "updateJenkinsItems", "dumpJenkinsJobs" to "dumpJenkinsItems", etc.

[zeeke]

+1

[sgoings]

It also might be neat if you could leverage task rules to mess with items:

jenkins {
  servers {
    production { ... }
    test { ... }
    development { ...}
  }
}

Would enable one to run:

• updateJenkinsItemsProduction
• updateJenkinsItemsTest
• updateJenkinsItemsDevelopment

This is a bit nicer to use sometimes than passing in properties to the job (and also shows up in --tasks output). Additionally, I could type the short form even more efficiently: ./gradlew uJIP vs ./gradlew uJIT vs ./gradlew uJID

Thoughts?

[ghale]

That's a pretty good idea. I've done something similar with some plugins we use internally and it works really well. Then we'd just make updateJenkinsItems an aggregator task for all of the updateJenkinsItems* tasks. I like it.

[ghale]

This turned into a non-trivial refactor of the task plumbing, but the end result is much cleaner. Needs some further testing/scrutiny, but core use cases should be covered.

[ghale]

This is in v1.1.0.