Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 25 09:49
  • Oct 23 2020 18:36
  • Oct 23 2020 09:18

    jglick on master

    [maven-release-plugin] prepare … (compare)

  • Oct 23 2020 09:18

    jglick on promoted-builds-3.7

    (compare)

  • Oct 23 2020 09:18

    jglick on master

    [maven-release-plugin] prepare … (compare)

  • Oct 23 2020 09:07

    jglick on master

    Removing explicit dep on xstream Explicitly call processAnnotati… Merge pull request #150 from jg… (compare)

  • Oct 23 2020 09:07
    jglick closed #150
  • Oct 23 2020 09:07
    jglick labeled #150
  • Oct 08 2020 21:04
    jglick synchronize #150
  • Oct 02 2020 17:49
    jglick opened #150
  • Sep 30 2020 11:25

    oleg-nenashev on master

    [maven-release-plugin] prepare … (compare)

  • Sep 30 2020 11:25

    oleg-nenashev on promoted-builds-3.6

    (compare)

  • Sep 30 2020 11:24

    oleg-nenashev on master

    [maven-release-plugin] prepare … (compare)

  • Sep 30 2020 10:35
    oleg-nenashev labeled #149
  • Sep 30 2020 10:35
    oleg-nenashev unlabeled #149
  • Sep 30 2020 06:15
    ehartmann closed #44
  • Aug 05 2020 08:39
    timja commented #149
  • Aug 05 2020 08:26
    oleg-nenashev commented #149
  • Aug 05 2020 08:26
    oleg-nenashev edited #149
Bogdan I @ FintechOS
@BogdanI-FintechOS
But in order to do that we need to know what has to be done and it's currently unclear. I also feel I could do a brutal demotion like this directly from a system Groovy script and avoid a Jenkins restart but in this case I would really need to know from the start that this can be done without touching plugin's Java code.
Oleg Nenashev
@oleg-nenashev
Any low-level documentation could be indeed useful, but note that there is no commitment to retain compatibility for the current behavior
For me reviewing low-level docs would probably take longer than implementing depromotion API
Bogdan I @ FintechOS
@BogdanI-FintechOS
@oleg-nenashev Can you tell me if you think it's possible to obtain for a given jobA an instance of AbstractBuild for a given completed build (let's say build 39, visible at an URL like: http://machine:port/jobA/jobName/39), starting from a system Groovy script (https://plugins.jenkins.io/groovyv) executed by a different jobB, let's say during build 10. The following objects are bound to the script: build (type: AbstractBuild; represents the currently running build 10 for jobB), listener (type: StreamBuildListener), launcher (type: Launcher)
Oleg Nenashev
@oleg-nenashev

@BogdanI-FintechOS https://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getItemByFullName-java.lang.String- + https://javadoc.jenkins.io/hudson/model/Job.html#getBuildByNumber-int- .

So it would look like jenkins.model.Jenkins.instance.getItemByFullName('jobA').getBuildByNumber(39)

Bogdan I @ FintechOS
@BogdanI-FintechOS
@oleg-nenashev I just tested things out and it seems I can create-instances or get-singletons for any Jenkins "entity" from Groovy scripts, including the jenkins object you suggested I use. I was concerned that in order to be able to reach that jenkins object singleton, something else needs to be bound to my Groovy script and I really wanted to avoid googling how to do that.
Bogdan I @ FintechOS
@BogdanI-FintechOS
It's unlikely, but if I end up using the promoted-builds-plugin this time, I'll come back with Groovy code on how to do a brutal demotion. First, however, I'll try a custom job that does promotion/demotion from beta/RC to GOLD by adding badges / changing descriptions for builds via Groovy build steps. Thanks for the tip.
hakamairi
@hakamairi
Hello, I have a strange question that I don't seem to find the answer for
how do I use the promoted builds with declarative pipeline?
Oleg Nenashev
@oleg-nenashev
@hakamairi See https://issues.jenkins-ci.org/browse/JENKINS-36089 . Jenkins Pipeline is not supported in Promoted Builds ATM
hakamairi
@hakamairi
summer is almost over so I was hoping that maybe this is done already
ok thank you for the information
Oleg Nenashev
@oleg-nenashev
The project was failed in June unfortunately
hakamairi
@hakamairi
oh, sorry to hear that
Oleg Nenashev
@oleg-nenashev
Not all GSoC projects complete
I still want to do that when time allows, but "when" is a pretty big question for me
hakamairi
@hakamairi
alright then, fingers crossed for this one
Nmnaren
@Nmnaren
how do promoted the builds with declarative pipeline?
steven-foster
@steven-foster
I don't think you can
Nmnaren
@Nmnaren
@steven-foster Is there any option to promote the build through pipelin e
Oleg Nenashev
@oleg-nenashev
@/all Promoted Builds 3.5 is out, the regression fixes seem to work fine. https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.5 . Sorry that it took so long
Oleg Nenashev
@oleg-nenashev
@/all If somebody is interested, I have started working on https://issues.jenkins-ci.org/browse/JENKINS-36089 . There are pull requests coming soon, I am trying to reintegrate code from @dernDren161 where possible. FYI @bicschneider @dernDren161
@jonbrohauge ^
JEEBITESH KALANTRI
@jeebitesh
can we incorporate DSL into Scripted Pipeline ?
Oleg Nenashev
@oleg-nenashev
@jeebitesh wrong channel
Claus Schneider
@bicschneider
WOW - cool :-)
JEEBITESH KALANTRI
@jeebitesh
I was talking about promoted Builds plugin, as they can be used in DSL but not in pipeline. But is it possible to call DSL from Jenkins Declarative or Scripted Pipeline or is there a way to call them directly in scripted pipeline
Oleg Nenashev
@oleg-nenashev
@jeebitesh this is what I,am working on, see the links above
elaborateruse
@elaborateruse
Hi @oleg-nenashev : Any news on promoted builds for Jenkins pipeline? We use this plugin on freestyle jobs and would figure it preferable to stick with it on our pipeline builds rather than change to a different publishing system. Of course, life happens so I am just inquiring. Thanks!
Oleg Nenashev
@oleg-nenashev
@elaborateruse i am doing some progress with prototyping, but it does not go as fast as I would like. Maybe I will get to it on w weeks or so
elaborateruse
@elaborateruse
@oleg-nenashev Thanks for the update. Looking forward to it!
Jon E. Eguiluz
@viroide_twitter
Hi all
probably asked before, but... I can't find any clear answer.
Is it possible to configure this plugin with pipeline jobs?
Jon Brohauge
@jonbrohauge
@viroide_twitter Currently it supports freestyle-jobs https://github.com/jenkinsci/promoted-builds-plugin#job-dsl-support
Jon E. Eguiluz
@viroide_twitter
so... no? only freestyle jobs, right?
Jon Brohauge
@jonbrohauge
@viroide_twitter Currently only freestyle. Last year, as a GSoC project, there was an attempt to enhance the plugin to be better integrated in DSL, but the project didn't finish. @oleg-nenashev does work on it, time permitting. You are more than welcome to contribute to the plugin :wink:
Jon E. Eguiluz
@viroide_twitter
I would love to contribute but my knowledge of java ans jenkins plugins is close to none
thanks for the info!
Oleg Nenashev
@oleg-nenashev
Yes. "Time permitting" is a catch :(
Jim
@jep
Hi, I'm trying to determine if there's a way to trigger a downstream job based on a build being promoted via this plugin. Can anyone assist?
Ming Fang
@mingfang
@jep I can help you with that
Jerry Wiltse
@solvingj
is there anywhere i can see a screenshot which shows the "Star" that this plugin adds to builds?
Jerry Wiltse
@solvingj
i guess i was hoping it would appear in the left hand column of the job history on the job summary page
i googled and found some screenshots, but they're all in kind of random places, and not there
varshabhijeet
@varshabhijeet
how to use PROMOTED_URL env parameter in jenkins ?
here I am getting BUILD_URL properly but how to use in build PROMOTED_URL env parameter
Tomas Norre
@tomasnorre_twitter

Hi.

I'm running on jenkins 2.235.1 with promoted-builds 3.5.
When I do the small example like the docu says.

    properties {

        promotions {
            promotion {
                name('build')
                icon('star-silver')
                condition {
                    selfPromotion('false')
                }
            }
        }
     }

I get the error in my jobDslTest

Caused by: javaposse.jobdsl.dsl.DslScriptException: (script, line 86) No signature of method: javaposse.jobdsl.dsl.helpers.properties.PropertiesContext.promotions() is applicable for argument types: (webshop_v8.script$_run_closure1$_closure7$_closure20) values: [webshop_v8.script$_run_closure1$_closure7$_closure20@265f0971]

According to documentation I have added it correctly, but my jobDslTest doesn't allow it. Some one that can give me a hint ? I'm sort of lost atm.

I'm on jobdsl version 1.77
Stacie
@StacieR
how to pass current promote job parameters to Projects to build job? I saw there was current build parameters in list of add parameters but seems not working
precisioninfinity
@precisioninfinity
For the jobs DSL from this line it looks like the actions block only delegates to StepContext only, whereas in the UI interface, it looks like I can configure for both steps and publishers. Thoughts on upgrading this line to delegate to either? https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/integrations/jobdsl/PromotionContext.java