I have not found a solution yet but I'd love to know if there is one.
Current best practice seems to be to have a Jenkinsfile which triggers Job
DSL to process DSL files located in a subdirectory, so at least they are
all organized in your repo and Jenkinsfile serves as the single point of
entry. Y
.
>
> https://issues.jenkins-ci.org/browse/JENKINS-36836
>
> Mark Waite
>
> On Thu, Jul 21, 2016 at 2:16 PM Mike Rooney wrote:
>
>> Hello there!
>>
>> We've got some Pipeline jobs that are using "Polling ignores commits in
>> certain paths", plus t
On Thu, Jul 21, 2016 at 11:42 AM, alex kessinger
wrote:
> I've tried the seed job-dsl method previously. Some automation was better
> then no automation, but I think the Jenkinsfile in repo is even better. If
> I make a change to the Jenkinsfile, that change can be isolated in each
> environment/
Hello there!
We've got some Pipeline jobs that are using "Polling ignores commits in
certain paths", plus the required "Force polling using workspace" option.
It looks like we've got this set up correctly based on documentation and
seeing this in the polling log: "Ignored commit
742b406b1d31bc
This need makes a lot of sense to us, where we have a couple related
sub-projects (as sub directories) in a single repository. It makes sense
that they each have their own pipeline jobs and can run on different
schedules. I've also seen cases similar to Alex's (hi Alex!) where there
are differe
Hello there! We're using Jenkins 2.9 with the Bitbucket Branch Source
Plugin 1.5. It picks up on a branch with a Jenkinsfile which is neat, but
the only build output we get is:
Started by user m a
java.lang.NullPointerException
at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:23
A late reply, but as this thread appears on Google for trying to solve this
problem, I figured I'd post my solution. It isn't great as you can't use
the Git plugin, so a new BuildChooser would be superior, but it does result
in one build per git commit across all branches.
First, modify your jo
