Development environment

[Jeremy Marshall]

Hi

I liked job-dsl so much I decided to download the code to have a look at it. I also had a look at the jenkins demo plugin. So I have gradle too (Maven comes with my mac)

My question is, what is the best IDE to develop in? I tried Eclipse and then IntelliJ and think intelliJ integrates better but haven't found how to build it into the 

test Jenkins server I now seem to have. I suppose its the difference between maven and gradle. Do I need to drop into a shell to build?

Thanks 

Jeremy

[Jeremy Marshall]

okay so I looked in the directory like I should have (IDE's keep that from you) and its 

./gradlew server

or from intellij  JetGradle plugin 'server' item

In my defence I am more a vi type of developer

[Andrew Harmel-Law]

Hey Jeremy,

Thanks for your post.  I'm not sure about the other guys, but I'm on a corporate laptop (windows 7 enterprise) and swap between IntelliJ IDEA 12.1.4 and Netbeans 7.3.  I use their built-in git support / git bash (I'm trying to learn more about how git works) / SourceTree.  For builds, I, like you, build from the command line.  I know Netbeans used to have nice Jenkins development support, but that was a few years ago.

HTH

Anyone else want to share their dev platform?

Cheers, Andrew

Andrew Harmel-Law

twitter: @al94781

blog: the-music-of-time.blogspot.com

flickr: flickr.com/photos/andrewbrucelaw

--
You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/4532e593-87fa-4d6c-a1a2-31d4e7d4997f%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Chris Doré]

On both my Macbook and Win7 desktop I'm using a mix of commandline/gradle as well as IntelliJ (thanks to Justin's IntelliJ mini-tutorial at the Gradle Summit).  From what I heard at the Gradle Summit a few weeks ago, IntelliJ 13 should have even better/deeper gradle integration, but we'll see.

In addition to the server task, you might find the run task quite useful.  Using the run task allows you to generate config xml without having to fire up Jenkins.  If you're running the latest from master (or sometime after June 1st, when support for the args property was added):

Add some job dsl content to a file, say job.dsl

# ./gradlew run -Pargs=job.dsl

Note: the run task loads the file relative to the job-dsl-core directory, so I always just put my test files in there.

Note2: if your dsl code contains a task named "myJob", the run task will generate myJob.xml.

Chris

[Andrew Harmel-Law]

Cheers Chris,

I put the "run" tip up on the "User Power Moves" page on the wiki: https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#generate-a-job-configxml-without-having-to-fire-up-jenkins

Regs, Andrew

Andrew Harmel-Law

twitter: @al94781

blog: the-music-of-time.blogspot.com

flickr: flickr.com/photos/andrewbrucelaw

--

You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/6d6950cd-c30d-4eeb-8dd3-ed10bceb6e00%40googlegroups.com.

[Chris Doré]

EDIT:

Note2: if your dsl code contains a job named "myJob",  the run task will generate myJob.xml.

I updated the wiki as well.

Chris

[Andrew Harmel-Law]

Great.  Thanks.

Andrew

Andrew Harmel-Law

twitter: @al94781

blog: the-music-of-time.blogspot.com

flickr: flickr.com/photos/andrewbrucelaw

--

You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/11e64095-90a3-402b-9589-9c7189464da8%40googlegroups.com.

[Patrick Bruneton]

Hi,

This is nice.

I have to process a few DSL files (more than 150), and it takes quite some time if I run gradle each time.

Is there an easy way to process all files at once ?

[Justin Ryan]

It's a good idea. I just committed and pushed a fix to HEAD that will take multiple args. It'll be in 1.16.

I'd be curious to know what your "use case" is, to need to run more than 150 files on the command line.

--

You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/7da0824c-750a-4d31-b5c5-0551cb6bec9f%40googlegroups.com.

[Patrick Bruneton]

In my company, we have many projects, and we want generate some jobs for each of them.

These jobs are configured using your plugin ! 

[Chris Doré]

Hi Patrick,

You're generating these jobs by running the plugin from Jenkins though, right?  Justin is wondering about the use case for running so many job dsl files/projects through the commandline interface, which is mostly intended for testing and development of the plugin.

Chris

[Patrick Bruneton]

Yes, I am generating these jobs using the plugin.

BTW, I noticed something which probably could be improved : sometimes, I generate a XML file which is not valid for Jenkins. The plugins says it has generated a job X, but when I click on the link the job X does not exist.

Could the plugin verifiy that the job has been actually created, and give the exception if it is not the case ?

[Andrew Harmel-Law]

Hi Patrick,

Sounds like a nice feature request.  Do you want to have a try at adding it and submit a pull request?  If you need any help, post back here.

Cheers, Andrew

Andrew Harmel-Law

twitter: @al94781

blog: the-music-of-time.blogspot.com

flickr: flickr.com/photos/andrewbrucelaw

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/282803bc-4435-44e9-809c-a1b91de46f53%40googlegroups.com.

[b...@shand.org.uk]

Hi Everyone,

Great work on the DSL plugin.  I'm using some parameters in our seed job.  Running through Jenkins is great - but is there a way I can specify the parameters when running on the the command line so that I can speed up my iteration time on my dev machine?

eg parameters = P4_DEPOT_PATH - that I want to use in my seed DSL.

Cheers

Bob

[Alan Beale]

Bob,

  If you have 1.16 tag or later, you can create environment variables named after you parameters and then run the plugin from the command line.

  For example, assuming you have a parameter named P4_DEPOT_PATH on linux in bash you run the following

   export P4_DEPOT_PATH=/tmp/path_to_p4_depot

  ./gradlew :job-dsl-core:run -Pargs=/path/to/your/job-dsl-file

Alan

[Pushkar Raste]

Hi,
I want to create jobs without firing Jenkins but from a template job. How does script knows where do my template job lives?

[Baptiste Mathus]

Hi,

Sorry to excavate and old thread, but I tried using that and I guess what you refer to is the job-dsl repository? As I'm actually not hacking on the job-dsl repo itself, I haven't cloned it locally.

I used https://github.com/sheehan/job-dsl-gradle-example/ as a basis for our job dsl internal repository, and the run task is indeed unavailable with the included build.gradle.

I'm not gradle-savvy, but I seem to understand I could copy some parts of https://github.com/jenkinsci/job-dsl-plugin/blob/master/build.gradle#L73 inside my own build.gradle. 

I'm gonna test that. But I'd appreciate if someone could chime in and help about this, that'd be great (mainly meaning: how to make that tip usable outside the job-dsl's own build.gradle file, IIUC).

Thanks

Le lundi 24 juin 2013 01:06:50 UTC+2, Chris Doré a écrit :

[Daniel Spilker]

You can't adopt the code from the job-dsl-plugin build files directly. Try to create a JavaExec Gradle task (https://gradle.org/docs/current/dsl/org.gradle.api.tasks.JavaExec.html) and set the main class to 'javaposse.jobdsl.Run'.

task run(dependsOn: 'classes', type: JavaExec) {
  main = 'javaposse.jobdsl.Run'
  classpath sourceSets.main.runtimeClasspath
  args 'jobs/test.groovy'
}

Daniel

--

You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugi...@googlegroups.com.
To post to this group, send email to job-dsl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/18491970-2228-4057-93a2-88b6c535bf9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Baptiste Mathus]

Thanks a lot, that helped me get in the right direction. I renamed it debugxml locally and added to our dsl repo.

To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/CAKqW32DvOGWTFntPHUs55D0hj32Dr3ifBQzFAQeBXzAGFqDi3A%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !