Aashish Radhakrishnan

In the interest of backlog refinement, is this PR still a work in progress?

@travier As part of the backlog refinement, we came across this issue. We wanted to know if this is a relevant issue.

We can create a PR with the jenkins plugin updates with this code - https://github.com/coreosbot-releng/fedora-coreos-pipeline/pull/2 https://jenkins-fedora-coreos-pipeline.apps.ocp.stg.fedoraproject.org/job/bump-jenkins-plugins/49/console

@jlebon I have addressed all the comments and have made the changes.

Posting the links for the PR and jenkins build below for reference: PR for the plugins update - https://github.com/coreosbot-releng/fedora-coreos-pipeline/pull/10 Jenkins build - https://jenkins-fedora-coreos-pipeline.apps.ocp.stg.fedoraproject.org/job/bump-jenkins-plugins/152/console

> Haven't reviewed the code again (will leave that to @dustymabe), but just looking at the example PR in [coreosbot-releng#10](https://github.com/coreosbot-releng/fedora-coreos-pipeline/pull/10), we should include in the commit message the job information....

> This LGTM. > > I think the remaining piece in my mind is what happens to the PRs when they are created? > > Do we just merge them...

Arent we missing out on the basic-branch-build-strategies plugin dependencies here ? `basic-branch-build-strategies depends on branch-api:2.1092.vda_3c2a_a_f0c11,scm-api:672.v64378a_b_20c60,structs:324.va_f5d6774f3a_d` > 7 plugins. They were already installed by `base-plugins.txt` and were updated as a result...

Checked with the Openshift team on the reason why `resolveDependency` function was disabled. Apparently they had several issues with the `resolveDependency` plugin resolution which gave non-compatible plugins that had to...

I haven't looked into the process of using the built-in plugin manager. If we are implementing the testing hack of using `resolveDependency`, we can add that hack to the` test-jenkins`...