[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)

22 views
Skip to first unread message

2017uec1250@mnit.ac.in (JIRA)

unread,
May 23, 2019, 6:01:02 AM5/23/19
to jenkinsc...@googlegroups.com
Prastik Gyawali created an issue
 
Jenkins / Epic JENKINS-57634
GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Issue Type: Epic Epic
Assignee: Prastik Gyawali
Components: promoted-builds-plugin
Created: 2019-05-23 10:00
Labels: gsoc-2019
Priority: Major Major
Reporter: Prastik Gyawali
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

2017uec1250@mnit.ac.in (JIRA)

unread,
May 23, 2019, 6:15:02 AM5/23/19
to jenkinsc...@googlegroups.com
Prastik Gyawali updated an issue
Change By: Prastik Gyawali
Tasks to be completed during the first coding phase.
1) Make all the Extensions,PromotionConditions,Implementations,etc pipeline compatible(by detaching them from the
     promoted-builds)
2) Apply the parameterized-trigger concept to trigger the promotion job.
3) Use the run-selector-plugin and/or copy-artifacts to know the triggering build.
4) Test this job application.
5) [New tasks to be updated or modified]

2017uec1250@mnit.ac.in (JIRA)

unread,
May 23, 2019, 6:17:04 AM5/23/19
to jenkinsc...@googlegroups.com
Prastik Gyawali updated an issue
Change By: Prastik Gyawali
Sprint: GSoC 2019. Coding Phase 1

jnz@topdanmark.dk (JIRA)

unread,
May 28, 2019, 5:08:03 AM5/28/19
to jenkinsc...@googlegroups.com
Jon Brohauge updated an issue
Change By: Jon Brohauge
Labels: gsoc-2019 gsoc-2019-artifact-promotion-pipeline-plugin

jnz@topdanmark.dk (JIRA)

unread,
May 28, 2019, 5:13:34 AM5/28/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
May 29, 2019, 9:33:01 PM5/29/19
to jenkinsc...@googlegroups.com

2017uec1250@mnit.ac.in (JIRA)

unread,
May 31, 2019, 4:13:01 AM5/31/19
to jenkinsc...@googlegroups.com
Prastik Gyawali updated an issue
 
Change By: Prastik Gyawali
Tasks to be completed during the first coding phase.
1) Make all Detaching the Extensions,PromotionConditions,Implementations,etc pipeline compatible(by detaching them extension points from the
     promoted-builds)
2) Apply the parameterized-trigger concept to trigger the promotion job hudson .
3) Use the run-selector-plugin and/or copy-artifacts to know the triggering build plugins .
4) Test this job application promoted_builds for pipeline compatibility .
5) [New tasks to be updated or modified]

2017uec1250@mnit.ac.in (JIRA)

unread,
May 31, 2019, 4:26:02 AM5/31/19
to jenkinsc...@googlegroups.com
Prastik Gyawali updated an issue
*+ Tasks to be completed during the first coding phase. +*
1) Detaching the extension points required modules from hudson.plugins.promoted_builds (and refactoring those) for pipeline compatibility. (Includes 8-10 such modules on which the promoted_builds.condition rely).
2) Detach the extension points from promoted_builds.condition package for pipeline compatibility.
        *_Done in two Stages:_*
#                 Refactor four such conditions(Up/Downstream, Manual and Self Promotion Conditions).
#                 Refactor the remaining extensions points and also make the two points inside integrations.dsl package pipeline compatible(ReleasePromotionCondition and JobDslManualCondition).
3) Create new customs steps for the new plugin. *_(Also Done in Two stages as described in the task.)_*

2017uec1250@mnit.ac.in (JIRA)

unread,
May 31, 2019, 4:29:02 AM5/31/19
to jenkinsc...@googlegroups.com
Prastik Gyawali updated an issue
*+Tasks to be completed during the first coding phase.+*
1) Detaching the required modules from hudson.plugins.promoted_builds(and refactoring those) for pipeline compatibility.(Includes 8-10 such modules on which the promoted_builds.condition rely).

 2) Detach the extension points from promoted_builds.condition package for pipeline compatibility.
         
         *_Done in two Stages:_*
#                 Refactor four such conditions(Up/Downstream, Manual and Self Promotion Conditions).
#                 Refactor the remaining extensions points and also make the two points inside integrations.dsl package pipeline
compatible(ReleasePromotionCondition and JobDslManualCondition).
3) Create new customs steps for the new plugin. *_(Also Done in Two stages as described in the task.)_*

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 16, 2019, 7:27:02 AM12/16/19
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
Change By: Oleg Nenashev
Assignee: Prastik Gyawali
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 16, 2019, 7:28:02 AM12/16/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated Epic JENKINS-57634
 

This GSoC 2019 project was not completed.

I will move the relevant tasks to JENKINS-36089
Change By: Oleg Nenashev
Status: Open Fixed but Unreleased
Resolution: Won't Do

jglick@cloudbees.com (JIRA)

unread,
Dec 16, 2019, 8:34:03 AM12/16/19
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Resolution: Won't Do
Status: Fixed but Unreleased Reopened

jglick@cloudbees.com (JIRA)

unread,
Dec 16, 2019, 8:34:04 AM12/16/19
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Won't Do
 

(just correcting Status)
Change By: Jesse Glick
Status: Reopened Resolved
Resolution: Won't Do
Reply all
Reply to author
Forward
0 new messages