On Friday, June 10, 2016 at 5:42:14 PM UTC-5, Matt Stave wrote: > > You can add build parameters while the build's in flight, with > [jenkinsURL]/cli/command/set-build-parameter > You should be able to refer to those in subsequent builds > > See also https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin (though > I've never used it) >
This works great! Thanks. > > --- Matt > > On Sunday, May 22, 2016 at 9:22:27 PM UTC-7, Andrew Melo wrote: >> >> Hello, >> >> I had two short questions about what was possible with pipeline jobs: >> >> 1) Suppose I want to track some arbitrary values between builds and >> fail if they have decreased. Is there a way to stash integers/values >> between builds? For example, let's say I want to enforce that the lint >> of the codebase gets better with each commit or github pull request. >> Is there a step/command that could be used within groovy to extract >> the previous value to make the comparison? Or, am I stuck basically >> manually copying results to "magic" places on the master that later >> builds can suck down. >> >> 2) Let's suppose that I want to publish a trend of these values as a >> graph on the main job page. I know there's the HTML publisher that can >> publish arbitrary pages, but that's buried another click down. Is >> there a way to have custom charts/HTML show up on the job/build pages >> themselves? >> >> Thanks! >> Andrew >> >> -- >> -- >> Andrew Melo >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/a16c28fc-3037-4e10-b9de-8643e486d35c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
