Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove seperate resources for handling plugin extension #389

Merged
merged 1 commit into from
Oct 10, 2015

Conversation

jhoblitt
Copy link
Member

There were two orthogonal resource chains for handling plugins with with
the .hpi & .jpi extension. This commit unifies the two code paths. It
should fix the resource ordering problem that causes it to take two runs
to install a plugin and pin it.

resolves #380

There were two orthogonal resource chains for handling plugins with with
the .hpi & .jpi extension.  This commit unifies the two code paths.  It
should fix the resource ordering problem that causes it to take two runs
to install a plugin and pin it.

resolves voxpupuli#380
@jhoblitt
Copy link
Member Author

Alternative to #388 that is a bit more aggressive.

@jhoblitt
Copy link
Member Author

I suspect the pin file should be removed when the plugin is :absent...

@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@rtyler rtyler added this to the 1.6.0 - Kato milestone Oct 10, 2015
rtyler pushed a commit that referenced this pull request Oct 10, 2015
remove seperate resources for handling plugin extension
@rtyler rtyler merged commit 24e669d into voxpupuli:master Oct 10, 2015
@jhoblitt jhoblitt deleted the bugfix/plugin-extension-handling branch October 11, 2015 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Plugins not pinned and updated when using jenkins class
3 participants