Your use case sounds familiar, isn’t it already supported by the https://plugins.jenkins.io/promoted-builds/?
Ulli > Am 16.03.2023 um 15:05 schrieb Tamás Mucs <tamas.muc...@gmail.com>: > > Dear Community, > > I have been struggling hard with implementing a new plugin. While some of the > core concepts are more or less clear to me (ExtensionPoint, @Extension > annotation, Descriptor, Describable and jenkins.model package), I could not > get my project get started. I spent so much time already. > I know of the Jenkins developer <https://www.jenkins.io/doc/developer/>, > o'reilly book of extending jenkins > <https://learning.oreilly.com/library/view/extending-jenkins/9781785284243/index.html> > and some youtube videos from the masters Plugin development > <https://www.youtube.com/watch?v=azyv183Ua6U> and its second part > <https://www.youtube.com/watch?v=iAJBKFe8mMo>. > > So what's the goal? > This plugin adds a button to each build (Run class?) to mark it "as release > build" > When the user presses this button, some basic data is written to the > build.xml of the corresponding build (for example, isReleaseBuild -> true). > Even better. this could not just be a plain button on the build but rahter an > Action on the sidebar which brings to a page (jelly view?) that has a form > and the user can enter specific data about the deployment. Say, a general > description (String), url etc. > When a build is marked as release build, it keeps the build forever (as if > the user pressed "keep this build forever" button. > If a build is marked as release build there's a small badge next to the build > (like in badge plugin <https://plugins.jenkins.io/badge/>) > On Job level there's a section (Action) that lists all builds that are marked > as release, with hyperlinks to the build itself. > Optionally (nice to have) there's a button on the Dashboard level that lists > all deployments grouped by Jobs. > Nice to have: Pipeline (workflow) method that marks the build as release > build right at build time. > Reference plugins, learn materials are also appreciated. I am also up for a > pair programming session. I also published my plguin to github here > <https://github.com/mucst/release-build-marker> though it is quite empty now. > Pull requests are appreciated if it is easier done than explained though > don't get me wrong, it is not like I want someone to the work. > I'd really like to gain knowledge so that I can later on contribute to the > ecosystem of JenkinsCI plugins. > > Tamas > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/d9ae5142-be88-435c-a006-719e1fa30a37n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/d9ae5142-be88-435c-a006-719e1fa30a37n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/262894B3-F681-4C42-B9AD-C35D60D914ED%40gmail.com.
