Hi all,

I would like to share one of the project ideas we have proposed for GSoC
2019: Artifact Promotion plugin for Jenkins Pipeline.
https://jenkins.io/projects/gsoc/2019/project-ideas/artifact-promotion-plugin-for-jenkins-pipeline/
.

This project idea tries to address JENKINS-36089: Pipeline support for
Promoted Builds Plugin <https://issues.jenkins-ci.org/browse/JENKINS-36089>
which is one of the most voted issues in Jenkins JIRA (119 votes). TL;DR:
There is no good out-of-the-box solution for managing artifact promotions
in a manual way for Pipeline jobs (CD Pipelines use input() steps & Co, but
not everybody uses CD in 2019). The issue was around for a long time, and I
believe it is still relevant for a subset of Jenkins users. And all other
users would probably appreciate better REST APIs for promotion management
and traceability in Jenkins. This is what this project is about.

Few years ago we had a discussion about the possible implementation with
Jesse Glick, and we agreed that it rather has to be a new plugin instead of
the Promoted Builds <https://plugins.jenkins.io/promoted-builds>, because
the existing plugin has some serious architecture flaws (e.g. JobProperty
implementing ItemGroup
<https://github.com/jenkinsci/promoted-builds-plugin/blob/e4c9304553f2868f67556644f5831eba60cf2c34/src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java#L54>
which caused a lot of issues in the past). So the outcome of the project
would be a new plugin which would still reuse Promoted Builds extension
points to retain it's fancy UI and existing integrations in Pipeline. If
BlueOcean extensibility JEPs are completed, some integrations with
BlueOcean could be also cool.

I would appreciate any feedback about this project. Would such new plugin
be useful for you? If yes, which particular features would you like to see
in the plugin.

Thanks in advance,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCjpVxQHSu0dG5yr4-8frWsGmeOu7wdWsrNzzMytUVADQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to