You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Udi Meiri (JIRA)" <ji...@apache.org> on 2018/08/09 17:32:02 UTC

[jira] [Created] (BEAM-5118) Make Jenkins DSL job development easier, less disruptive

Udi Meiri created BEAM-5118:
-------------------------------

             Summary: 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


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)