[
https://issues.apache.org/jira/browse/BEAM-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627522#comment-16627522
]
Scott Wegner commented on BEAM-5118:
------------------------------------
Unassigning this; anybody should feel welcome to make contributions here. I
recommend possibly breaking this up into tangible sub-tasks.
Some specific thoughts:
{quote}Is there an IDE that could inspect these objects and do
completion?{quote}
IntelliJ understands Groovy for syntax completion, which is what I use. We
could go further and set up a proper build project for jenkins groovy scripts
which would probably enable symbol completion across files.
{quote}Is there a test Jenkins instance (could INFRA set one up)?{quote}
I'm also annoyed by this, and I don't know what the best solution is. I know it
takes non-trivial effort to maintain a separate test environment which mirrors
prod, but we could ask INFRA about setting it up. [~Ardagan] has added some
documentation on how to set up your own dockerized jenkins instance:
https://github.com/apache/beam/tree/master/.test-infra/dockerized-jenkins
> Make Jenkins DSL job development easier, less disruptive
> --------------------------------------------------------
>
> Key: BEAM-5118
> URL: https://issues.apache.org/jira/browse/BEAM-5118
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Udi Meiri
> Assignee: Scott Wegner
> Priority: Major
>
> Here is my aborted attempt to add command line arguments to the gradlew
> invocation:
> https://github.com/apache/beam/pull/6188/files#diff-22460ba8f153644bf2a508681023ab54
> (error:
> ERROR: (PrecommitJobBuilder.groovy, line 79) No such property: steps for
> class: javaposse.jobdsl.dsl.jobs.FreeStyleJob
> https://builds.apache.org/job/beam_SeedJob/2403/console
> )
> Some possible improvements to the development process could be:
> 1. I used vim to edit .groovy files. Is there an IDE that could inspect these
> objects and do completion?
> 2. In order to test my I needed to:
> a. Commit and push my PR changes.
> b. Add a "run seed job" comment.
> c. Wait about 3m for it to succeed/fail.
> Another issue is that the only way to test my code is in production.
> Is there a test Jenkins instance (could INFRA set one up)? I know that I can
> run something like 'docker run -p 127.0.0.1:8080:8080 jenkins/jenkins:lts',
> but that requires a lot of setup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
