HOW? Declarative Pipeline - Build Cause change default Parameter

[jieryn]

Does anyone have a fragment or can lend a hand in me figuring out how
to get a Jenkinsfile based declarative pipeline where we have a
parameters { } section which will get a different defaultValue
depending on the build cause?

The goal is that I want to do a maven deployment if and only if this
job is being triggered by Jenkins during a nightly build trigger. The
default ought to change from false to true if we're in that @nightly
build trigger (or if the user has clicked build now, and has overriden
the default).

Any help is appreciated, thanks!

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ibH2qt9BkP8PDbmcfVAMhL0Zn2Xxo28_4W%3D8T3D2WgVzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to disable a Jenkins Multibranch Pipeline job?

[jieryn]

That solution is kind of disappointing, it doesn't really disable the
job. Someone can still run invoke it..

Also, there doesn't seem to be a way for me to remove the branches
that were autovivified into the job.

I'm trying to clean up, but am not ready yet to just delete the jobs.
I guess that's my problem.

On Tue, May 1, 2018 at 10:08 AM, Victor Martinez
 wrote:
> https://stackoverflow.com/questions/47840096/how-to-disable-a-jenkins-multibranch-pipeline-project
> might help you
>
> Cheers
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/c6ef0e30-e9a2-412a-8955-ecb0786ead3e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iak84F8COh7FJnWVVchxwy4VHNC4b7qcgTN-PmmcVREtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to disable a Jenkins Multibranch Pipeline job?

[jieryn]

I want to temporarily disable a Jenkins Multibranch Pipeline job. With
a traditional job, I can just click the Disable Project button. I am
looking all over, I am not able to figure out how to disable a
Multibranch Pipeline job... please, a hint?

Thanks!

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ib_KSN%3DhdggCMecgVF_T%2BF1MErVrnhQ%3DJuRfyDBVmcdVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline Recipe for Timer Cause vs User Build Button Cause?

[jieryn]

I use the latest Jenkins release with all the common plugins fully up
to date on RHEL 7 via Java 8.

Does anyone happen to have a recipe I can follow to set different
`defaultValue` for ```parameters { booleanParam (defaultValue: xxx,
...) }``` depending on whether the this run was triggered by a timer
action or by a user action?

I use build parameters to enable/disable various stages in the
pipeline, many of which are long running, depending on whether or not
I want to pay the cost/time for those stages at that moment. Sometimes
I just want to quickly get through to a particular phase of testing,
or perhaps to production deployment. And I know I can skip the costly
phases and just get right to where I want the build to go, but still
using the automated pipeline which has become the standard vehicle for
delivering to production.

I'm finding that when the build is triggered via timer, Jenkins should
not skip any stages; but it is common when developers trigger builds
manually that build execution is always customized in common ways. Any
help is appreciated to reduce the amount of time I'm spending clicking
checkboxes in manually triggered builds,

Thanks!

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iY4tit3EJXcgFuaG4Uv9zpAHa8xQ6%3DE9AjOs%3DN1yaVAiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Installing / maintaining Jenkins on a Linux host machine

[jieryn]

RedHat user here.. Or you can just install Jenkins' repository flavor
of your choice without waiting for upstream:

https://pkg.jenkins.io/redhat/
https://pkg.jenkins.io/redhat-stable/

Jenkins really has lead the way and set the bar quite high for open
source projects and making itself available for users of all types and
risk level willingness.


On Tue, Jul 11, 2017 at 12:54 PM, John Mellor  wrote:
> There are competing update philosophies to consider:
> Ubuntu ships the latest (unstable) release of Jenkins all the time, while
> RedHat/CentOS/etc ships the stable version. I host on a Ubuntu VM, but
> definitely wish it was better tested. If stability is key, then Ubuntu may
> not be your best choice.
>
>
> On Tue, 2017-07-11 at 16:44 +, Jason LeMauk wrote:
>
> We are currently provisioning a physical server as our automation server. We
> are making considerations as far as what our native operating system should
> be on this physical machine.
>
> We are going to use a Linux OS as our operating system. From the Jenkins
> download page, I can see that Jenkins’ package distribution is available to
> Red Hat / Fedora / CentOS (which we will not be using), as well as Ubuntu /
> Debian. I also notice that a Generic Java package (WAR) distribution is
> available.
>
> ·Am I correct in assuming that if we use a non-Ubuntu / non-Debian
> operating system, we can still install Jenkins via the WAR distribution
> without issue?
>
> ·If we are not able to install via WAR without issue, are we
> relegated to using Debian / Ubuntu if we’re going to install Jenkins on a
> Linux machine (with the possibility of Red Hat / Fedora / CentOS ruled out)?
>
> It should probably be noted that we will likely install / upgrade on the
> Jenkins LTS release schedule.
>
> Thanks for any guidance from anybody who may have experience installing /
> maintaining a Jenkins instance on a Linux machine!
>
> Jason
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1499792036.3165.5.camel%40esentire.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iaceViyKf1bXt85WKi4M0aAyw5TQqOax5e5PB_vcebTaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: Parallel block force to 1 node?

[jieryn]

Is it possible for debug purposes to force a parallel block to be run
via a single node for test purposes?

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZC6CspZZxSyzAc4R2Sn4S58-9WH9BgcagUuekFz7VtAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline startup errors

[jieryn]

Yes, I am using the experimental update centre here
http://updates.jenkins-ci.org/experimental/update-center.json

Perhaps the intra-dependency references are not properly being
defined? I manually installed the two plugins and was able to get past
the error message. I do now find:

Sep 08, 2016 8:01:40 AM hudson.PluginManager dynamicLoad
INFO: Plugin pipeline-graph-analysis:1.1 dynamically installed

for example, which suggests to me, a dummy, that perhaps this is an
optional maven dependency not being pulled in when I install the top
level blueocean/pipeline plugins? Not sure at all, but I'm past it
now.


On Thu, Sep 8, 2016 at 5:23 AM, Baptiste Mathus <m...@batmat.net> wrote:
> Weird. Are you using the experimental update center? I see the missing
> dependency is a beta one.
>
>
> Le 6 sept. 2016 3:34 PM, "jieryn" <jie...@gmail.com> a écrit :
>>
>> Sep 06, 2016 9:31:57 AM hudson.PluginManager$2$1$1 run
>> SEVERE: Failed to install pipeline-rest-api: One or more dependencies
>> could not be resolved for pipeline-rest-api : pipeline-graph-analysis
>> (0.1-beta-1)
>> Sep 06, 2016 9:31:57 AM hudson.PluginManager$2$1$1 run
>> SEVERE: Failed to install pipeline-stage-view: One or more
>> dependencies could not be resolved for pipeline-stage-view :
>> pipeline-rest-api (1.8-beta-1)
>>
>> Any ideas how to resolve this? All plugins are up to date, and I
>> forced the plugin check to be current.
>>
>> Page generated: Sep 6, 2016 9:31:35 AM EDT  REST API  Jenkins ver. 2.7.3
>> RHEL 7, Java 8
>>
>> --
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ib8OcaQyU0C33wed5RBgXFncoic2OBFaf75ik1E%2BFYz4g%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4_yRGSjcz6fAQtKip5ienrY8wuAOQUh4HV4CrU09LYrw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iYh43t-ZQOVmdxHgsujMMhomD%2B77NX9cBj0GrYMUsxayA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline: feedback

[jieryn]

https://issues.jenkins-ci.org/browse/JENKINS-37985

Yep. All of our independent jobs really just do one mvn invoke each.
They are smart in that they can be passed a git tag to build, or they
will work against master; this is really nice because sometimes we
just want to trigger, independently, a certain subphase / substage of
the pipeline without going through all the steps. I think this will
maintain durability of the pipeline as a whole, but also be flexible
enough to meet our needs for maintaining the same basic behavior as we
had before Jenkins had this advanced pipeline.

Being able to see the launched job's console output will be valuable
and make 'build'  consistent with all the other types of launchers,
well, the only one I know of, the 'sh' target.

On Fri, Sep 2, 2016 at 7:30 AM, Baptiste Mathus <m...@batmat.net> wrote:
> You should probably file an issue in Jira with this.
>
> IMO the potential big issue of this use case is that if the jobs you call
> are big ones with many steps, you then make the durability durability
> feature of pipeline far less useful.
>
>
> Le 2 sept. 2016 7:08 AM, "jieryn" <jie...@gmail.com> a écrit :
>>
>> It would be nice if when a Pipeline invokes a Jenkins Job, that the
>> log of that job would be visible inside the Blue Ocean pipeline output
>> similar to the way any other pipeline stage works. We use individual
>> jobs for each stage because it lets us get a lot of reusability for
>> common functions which can be run independent of the pipeline. Right
>> now, when each stage invokes a dedicated job, the pipeline has almost
>> no information in it other than the stage/job status. It would be
>> really useful to consume the launched job's console output
>>
>> --
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ianBAXQAhbDxBMyqAzyUHG2EsebePkczZDPinrWwHuneA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6BD550kS4pmb2KaTfuDxa6oqOSM-1hMfCzG8yja06o%2BA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZ9BQLcV6Om%2BZRSRkeEjWpjqp4K0CdknxeRjPYnapG96g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

pipeline startup errors

[jieryn]

Sep 06, 2016 9:31:57 AM hudson.PluginManager$2$1$1 run
SEVERE: Failed to install pipeline-rest-api: One or more dependencies
could not be resolved for pipeline-rest-api : pipeline-graph-analysis
(0.1-beta-1)
Sep 06, 2016 9:31:57 AM hudson.PluginManager$2$1$1 run
SEVERE: Failed to install pipeline-stage-view: One or more
dependencies could not be resolved for pipeline-stage-view :
pipeline-rest-api (1.8-beta-1)

Any ideas how to resolve this? All plugins are up to date, and I
forced the plugin check to be current.

Page generated: Sep 6, 2016 9:31:35 AM EDT  REST API  Jenkins ver. 2.7.3
RHEL 7, Java 8

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ib8OcaQyU0C33wed5RBgXFncoic2OBFaf75ik1E%2BFYz4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

pipeline: feedback

[jieryn]

It would be nice if when a Pipeline invokes a Jenkins Job, that the
log of that job would be visible inside the Blue Ocean pipeline output
similar to the way any other pipeline stage works. We use individual
jobs for each stage because it lets us get a lot of reusability for
common functions which can be run independent of the pipeline. Right
now, when each stage invokes a dedicated job, the pipeline has almost
no information in it other than the stage/job status. It would be
really useful to consume the launched job's console output

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ianBAXQAhbDxBMyqAzyUHG2EsebePkczZDPinrWwHuneA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't receive build email notification from Jenkins

[jieryn]

You are sending email to this list from lingv...@gmail.com yet your
Jenkins is configured to send to ling...@gmail.com ... looks like user
error.

On Thu, Aug 4, 2016 at 2:25 AM, Martin  wrote:
> Hello, my console output shows that my project is built successful and email
> was sent out too, but the recipients can't receive the emails. The final
> output is:
>
> channel stopped
> Email was triggered for: Always
> Sending email for trigger: Always
> Sending email to: ling...@gmail.com
> Finished: SUCCESS
>
>
> However, I can't see the email in ling...@gmail.com. Also, the Test Email
> also works fine in Jenkins configuration.
>
>
> What might be the problem? Thank you.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/be8c5bcc-f57d-42c2-afe7-cc3f92ec8522%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iYhHZ04d%3DQ4A8nx4gN%3DeOE_QxLUahxWgsYEiFL%2BX%3DAzxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating a maven-based job to pipeline style

[jieryn]

Hi,

On Sun, Jul 31, 2016 at 3:09 AM, khmarbaise  wrote:
>
>> enforcement, other stuff). So for example, running a clean install and
>> skipping all tests on a typical project versus clean install yields
>> about 10-20% reduction in wall clock execution time.
>
> Skipping Test will of course reduce the time (Do you know how long the tests
> alone take?)
> but I wanted to know the exact "wasted" time you have mentioned by
> compile/resources?
> So running a linear (single thread) mvn clean install vs. mvn install (in
> both cases with skipping tests at all)...
>
> If you always do a clean than Maven (plugins) can't identify things which
> have already been done cause they are not there...so yes in this case you
> are wasting time...

Maybe I am wrong, but I think the unit tests account for 10-20% of the
time of the build in my example. When I run the exact same build with
tests and then without tests, without tests is faster by 10-20% of the
total time. Therefore I blame 10-20% of the time on tests and 80-90%
of the time for the remainder of the build that will be in common for
just about every run of the same project.

Running clean every time only accounts for a small amount of the
waste. I quickly did a test just now, on the same project I ran clean
install and then install by itself, there was only a savings of 3%
total time for omitting the clean phase. By 80-90% waste, I also meant
that before discrete separate jobs/pipeline stages I could just stack
all my goals into a single Maven invocation. The build would be very
long, but I wouldn't pay the Maven POM initialization and other costs
for general running multiple times.

Finally, since our pipeline / CD strategy uses a per-build version
with updated pom.xml for each release candidate branch, won't the
updated pom.xml timestamp force a rebuild of all objects anyway? I
think it ought to, even if Abc.java and Abc.class appear to be up to
date and in sync, there's a more new pom.xml timestamp which should
invalidate all previously built classes; assuming we are even lucky
enough to run on the same node as previous stage, which seems
increasingly unlikely given how many more steps we'll be running now,
occupying more and more executors.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iY1zcJHjZ4fFgHiTZ902Od2z%2B84kLUFa9N0JhjWLf1Ccg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating a maven-based job to pipeline style

[jieryn]

Hi,

On Sat, Jul 30, 2016 at 2:39 PM, khmarbaise  wrote:
> so have you really measured the time you are "wasting" ? Furthermore which
> Maven version and plugin versions do you use? Are you using freestyle or
> Maven job type...


Yes, we have measured. Both with the Tesla Maven Profiler, but also
even just crudely. The profiler led us to remove a lot of stuff that
we had attached to the build lifecycle and have now pushed into
dedicated jobs (e.g. pathological but necessary m-enforcer-p
enforcement, other stuff). So for example, running a clean install and
skipping all tests on a typical project versus clean install yields
about 10-20% reduction in wall clock execution time. That, to me,
means we are repeating about 80-90% of "stuff" when we execute it
again but just to run the integration tests and again for acceptance
tests. Those timings were found on my development machine.

We do not run the Maven job type anymore, I used to be a big fan of
it, but in order to get supremely fast flow, we abandoned it. A lot of
the nice stuff where Maven integrates with Jenkins just isn't all
useful enough for the cost. I realize that is a sensitive topic, and I
don't want to get into it more, and all the research that I performed
is at least a year old, I'm not looking to start a discussion on this,
and I'm certainly not willing to go through another round of research.
We use Freestyle, and that is unlikely to change unless someone else
can demonstrate very sizable performance wins.

We always run the latest Maven version, 3.3.9 currently, all
dependencies and plugins are up to date (thank you
versions:display-{dependency,plugin}-updates mojo which we run weekly
and then perform updates). Finally, most developers in our area use
--threads 2.0C but on Jenkins we do not because we strictly control
the number of slaves per real machine, and do not like to get
surprised about how much usage a slave is actually going to cost.
Though, since we did move to RHEL 7 with systemd and cgroups, this
probably isn't an actual issue anymore and we should revisit it. But
for simplicity, -T1 is used for all slaves.


> On Saturday, July 30, 2016 at 8:13:14 PM UTC+2, Jesse Farinacci wrote:
>>
>> My team faces similar challenges, and I agree with almost everything
>> said so far. I definitely echo the sentiment that it feels like there
>> is a lot of wasted repetition when invoking discrete phases
>> separately. We currently do this via separate jobs now, which often
>> run at different frequencies. However, we have been able to configure
>> Maven such that we really only have two repetitious phases, across
>> these multiple jobs, which luckily are not costly for us. Maven
>> generate-resources and compile phases, as we can skip over tests and
>> deployments which are not part of the logical unit being executed. In
>> the end, even though we know we are wasting some execution time, it
>> turns out not to be all that much at all.. and isn't yet worthy of any
>> kind of optimization or special attention.
>>
>> So right now our (~2min) compile+unit test runs every commit and only
>> runs Junit tests.
>
> 2 Minutes..Ok how many time is "wasted"  (timestamper plugin and the mojo
> execution in Jenkins if you you are using maven job type can help here)
> BTW: How many modules does you project contains of?


Please see above for timing calculation process and results. A typical
project for us has 25 Maven modules.


>> Our (~8min) compile+integration test runs almost
>
> You might run jobs in parallel ?


It would be kind of crummy if we burned 8 minutes on integration test
if a 2 minute unit test would have aborted the build pipeline
previously. Our integration tests do not run the unit tests. Our user
acceptance tests do not run either the integration or unit tests. We
basically check out the project, update the version to be
1.0.$BUILD_NUMBER, run the unit tests, and if they pass we push the
branch to GitLab. That kicks off a ton of compliance jobs, all in
parallel (yaay!) And then after those all pass, we go to integration
test stage. This stage is just running our Arquillian tests, and given
how costly this phase and the phases after it is in time and
resources, we go back down to blocking pipeline on this job.


>> Our (~15min) compile+user acceptance test runs
>> every day and only runs Selenium tests. Then we have lots of on the
>> side jobs which ensure legal compliance, code coverage, file encoding
>> fixes, code style fixes, static analysis, etc etc, which run hourly,
>> daily, or weekly, and are mostly fast (<5min).
>>
>> We are exploring Jenkins Pipeline in order to chain, both sequential
>> where necessary and then parallel where it makes sense, these discrete
>> jobs in such a way that we will have a continuous delivery available
>> at the end which has run the full gauntlet of all our testing and best
>> practices verification for every commit without doing unnecessary and
>> expensive steps, failing the 

Re: Migrating a maven-based job to pipeline style

[jieryn]

My team faces similar challenges, and I agree with almost everything
said so far. I definitely echo the sentiment that it feels like there
is a lot of wasted repetition when invoking discrete phases
separately. We currently do this via separate jobs now, which often
run at different frequencies. However, we have been able to configure
Maven such that we really only have two repetitious phases, across
these multiple jobs, which luckily are not costly for us. Maven
generate-resources and compile phases, as we can skip over tests and
deployments which are not part of the logical unit being executed. In
the end, even though we know we are wasting some execution time, it
turns out not to be all that much at all.. and isn't yet worthy of any
kind of optimization or special attention.

So right now our (~2min) compile+unit test runs every commit and only
runs Junit tests. Our (~8min) compile+integration test runs almost
every commit+jenkins build window to group multiple commits and only
runs Arquillian tests. Our (~15min) compile+user acceptance test runs
every day and only runs Selenium tests. Then we have lots of on the
side jobs which ensure legal compliance, code coverage, file encoding
fixes, code style fixes, static analysis, etc etc, which run hourly,
daily, or weekly, and are mostly fast (<5min).

We are exploring Jenkins Pipeline in order to chain, both sequential
where necessary and then parallel where it makes sense, these discrete
jobs in such a way that we will have a continuous delivery available
at the end which has run the full gauntlet of all our testing and best
practices verification for every commit without doing unnecessary and
expensive steps, failing the pipeline as soon as possible. Each commit
triggers a build which triggers a new git branch which is passed to
subsequent phases, if any stage fails, the branch is deleted and makes
no further progress. Additionally, we are trying to leverage separate
Jenkins jobs for each discrete job so that we can trigger it on demand
in order to do some quick checking, we also find that we can get
easier cross-project reuse using that technique. We're using Git,
Apache Maven, Jenkins CI, Jacoco, Arquillian, SonarQube, Checkstyle,
PMD, FindBugs, and many others.

There are only two critiques we can find with this style: 1) the
aforementioned modest amount of wasted generate-resources and compile
phases across multiple jobs in the same pipeline, and 2) each phase is
producing artifacts to be tested and not reusing the ones built and
verified at previous stages, thus there may be a hypothetical
difference between what different stages are actually testing, though
we think the risk of this is not consequential. This technique
otherwise seems like a holy grail to me and the team. I welcome ideas
about it.

On Mon, Jul 25, 2016 at 10:36 AM, Victor Noël  wrote:
> Thanks for your feedbacks!
>
> So in the end, what is the solution you adopted? more coarse grained stages?
>
> Le dimanche 24 juillet 2016 14:18:18 UTC+2, wo...@anomalizer.net a écrit :
>>
>> Hello Victor,
>>
>> I am faced with a similar problem and gave up on the idea rather early on.
>> Here are some of the characteristics of multiple stages of a pipeline
>>
>> Ability of each stage to be explictly invoked by some command
>> Ability of each stage to be re-run in such a way that it can start off
>> from where the previous stage finished
>>
>> The maven lifecycle reactor does not play well with these concepts. For
>> example, there is no elegant way to tell maven to compile the code assuming
>> that the generation phase has happened. Likewise, one cannot ask maven to
>> simply execute the tests assuming that compilation has already taken place.
>> The short answer that the benefits of breaking something into various
>> pipeline stages is lost when maven.
>>
>> The situation with gradle is not better as far as the relationship with
>> the build tool and jenkins is concerned. However, the fact that gradle is
>> much better at quickly checking if earlier steps have been completed makes
>> it only marginally better.
>>
>>
>> On Saturday, July 23, 2016 at 1:10:08 PM UTC+5:30, Victor Noël wrote:
>>>
>>> Hi,
>>>
>>> I'm trying to wrap wy head around moving to pipeline jobs.
>>>
>>> Currently I use maven jobs (but my question applies to freestyle jobs
>>> that execute maven) by executing one single build command that will validate
>>> constraints (checkstyle and/or other stuffs like that), generate code,
>>> compile, run test, run it test and deploy artefacts.
>>>
>>> What is the best way to convert to pipeline with multiple stages?
>>>
>>> My main concern is that if I simply run each of the step with maven in
>>> each stage, then I feel like some of steps from maven may be executed
>>> multiple times (such as test being executed again for it tests or for
>>> deploy).
>>>
>>> Is there some success stories around here on how to handle such a
>>> migration?
>>>
>>> Thanks!
>
> --
> You 

Re: What is the best way to download all the Jenkins plugins along with their dependencies?

[jieryn]

bash$ jar xf the.jpi
bash$ find the/WEB-INF/lib

On Fri, Apr 1, 2016 at 6:28 PM, Hemant Gupta  wrote:
> Thanks for response !!
> I can write bash to download the plugin(.hpi) from the
> http://updates.jenkins-ci.org/download/plugins/
>
> But, if I download a .hpi plugin file, it doesn't download the dependent
> .hpi files.
> In other words, downloading a plugin doesn't download its dependencies.
>
> Can you throw some light on writing the logic that would also download the
> dependencies?
>
>
> On Friday, April 1, 2016 at 4:59:13 PM UTC-5, Jesse Farinacci wrote:
>>
>> The built plugin (.jpi / .hpi) already has its dependencies bundled
>> within it. Every plugin has a symlink to the latest version. This
>> seems like a pretty straightforward web crawler walk, downloading only
>> the /latest/ linkage from
>> http://updates.jenkins-ci.org/download/plugins/
>>
>> On Fri, Apr 1, 2016 at 5:51 PM, Hemant Gupta  wrote:
>> > I am thinking of writing a bash script(plugin.sh) that would download
>> > the
>> > plugins along with their dependencies.
>> >
>> > I am also thinking of creating a text file(plugin.txt) where I would
>> > list
>> > the plugin and version that I need to download.
>> >
>> > The bash script(plugin.sh) will take text file(plugin.txt) as an input
>> > and
>> > would download all the plugins along with their dependencies in the
>> > /var/lib/plugins
>> >
>> >
>> > I am sure someone must have done this earlier. I will highly appreciate
>> > if
>> > you can provide a few references to it.
>> >
>> > --
>> > 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 jenkinsci-use...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/jenkinsci-users/4cc79c22-9c9c-4f11-91b2-f190c7d0f4e0%40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/ff7dc842-ebac-4f20-8ef3-b2bd1b1aedea%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iYioQod5bMU_dACjCgJY9nu5485zA%3DhaRNz2pi2%3DXQJ9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is the best way to download all the Jenkins plugins along with their dependencies?

[jieryn]

The built plugin (.jpi / .hpi) already has its dependencies bundled
within it. Every plugin has a symlink to the latest version. This
seems like a pretty straightforward web crawler walk, downloading only
the /latest/ linkage from
http://updates.jenkins-ci.org/download/plugins/

On Fri, Apr 1, 2016 at 5:51 PM, Hemant Gupta  wrote:
> I am thinking of writing a bash script(plugin.sh) that would download the
> plugins along with their dependencies.
>
> I am also thinking of creating a text file(plugin.txt) where I would list
> the plugin and version that I need to download.
>
> The bash script(plugin.sh) will take text file(plugin.txt) as an input and
> would download all the plugins along with their dependencies in the
> /var/lib/plugins
>
>
> I am sure someone must have done this earlier. I will highly appreciate if
> you can provide a few references to it.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/4cc79c22-9c9c-4f11-91b2-f190c7d0f4e0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZaJj03MXGR8Rfy1WTQAANbP1YedNNT1cSDx9MU_2xucg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Save all configurations after Jenkins update

[jieryn]

Looks interesting! I haven't tried it.

It doesn't appear to work with external changes coming into the
configuration from outside the Jenkins server. (git pull)

So we'd have to make up our own minds about when to do that anyway,
this plugin porcelain doesn't seem to buy much.

On Wed, Feb 17, 2016 at 4:56 PM, Victor Martinez
<victormartinezru...@gmail.com> wrote:
> What about
> https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin ?
>
> On Wednesday, 17 February 2016 21:39:18 UTC, Jesse Farinacci wrote:
>>
>> I've used JobConfigHistoryPlugin in the past. I find just using git is
>> easier and fits better with our existing tools, etc.
>>
>> On Wed, Feb 17, 2016 at 4:35 PM, Victor Martinez
>> <victormar...@gmail.com> wrote:
>> > Maybe the below plugin might help you:
>> >
>> >  - https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
>> >
>> > cheers
>> > On Wednesday, 17 February 2016 17:55:49 UTC, maciej wrote:
>> >>
>> >> jieryn (2016-02-17 17:01):
>> >> > for (item in hudson.model.Hudson.instance.items) {
>> >> >println("Saving " + item);
>> >> >item.save();
>> >> > }
>> >>
>> >> Thanks, works great :-). I've just run it through Script Console.
>> >>
>> >> Regards,
>> >> Nux.
>> >
>> > --
>> > 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 jenkinsci-use...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/jenkinsci-users/94def6f1-4ede-43ed-ab11-1e3baae30252%40googlegroups.com.
>> >
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/84d95c91-a0ce-43b8-b53b-917784be7fb0%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ibKezDvf3q57%3D3JonUFHSvHP-zQs%3D-3byqvVE5ycD6xVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Save all configurations after Jenkins update

[jieryn]

I've used JobConfigHistoryPlugin in the past. I find just using git is
easier and fits better with our existing tools, etc.

On Wed, Feb 17, 2016 at 4:35 PM, Victor Martinez
<victormartinezru...@gmail.com> wrote:
> Maybe the below plugin might help you:
>
>  - https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
>
> cheers
> On Wednesday, 17 February 2016 17:55:49 UTC, maciej wrote:
>>
>> jieryn (2016-02-17 17:01):
>> > for (item in hudson.model.Hudson.instance.items) {
>> >println("Saving " + item);
>> >item.save();
>> > }
>>
>> Thanks, works great :-). I've just run it through Script Console.
>>
>> Regards,
>> Nux.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/94def6f1-4ede-43ed-ab11-1e3baae30252%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZ0r9Lo6uq2MRjBZvPjs6ZokcZqiEVAnzMBO6V%2BUFWZ0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Save all configurations after Jenkins update

[jieryn]

Create a new freestyle job, run it @daily, or whatever. Add Groovy
script execution build step, the full script is:

for (item in hudson.model.Hudson.instance.items) {
  println("Saving " + item);
  item.save();
}

On Wed, Feb 17, 2016 at 10:33 AM, Maciej Jaros  wrote:
> Hi.
>
> When you save configuration of a Job after Jenkins update there are some
> changes made in the config.xml (e.g. plugin version change). Since I keep a
> history of all config.xml files in a repository that mess up history of
> changes...
>
> So. Is there some script or plugin that can re-save configuration of all
> Jobs in a batch?
>
> Maybe something like (?):
> for job in jobs
>   job.save()
>
> Regards,
> Nux.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/56C492E6.9040009%40mol.com.pl.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZOD5fXgsqa1zcMkhpk8n%2B4eyc8%3D2Jr%3DNVRtAvo9BYYog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there any way for an Administrator to view a job as Non-Admin

[jieryn]

https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin

Then just look at the job without being logged in..

On Tue, Feb 16, 2016 at 7:33 PM, Mark Bidewell  wrote:
> Is there any way for an Administrator to view a job as Non-Admin?  This
> would be helpful when testing roles and permissions.
>
> Thanks
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/5c17a63f-49ca-4d38-a07f-07613a9b2021%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ibjHh5Z5MPrGemshhVrRo_Uks2qWu8-FZq8ZHBke8SM2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [theme] New Jenkins Material Design Theme

[jieryn]

+1

Default no-plugin install looks beautiful. Soon as you add any plugin that
adds an Action, it doesn't look so good anymore (mixed icons).

On Fri, Jan 29, 2016 at 10:30 PM, James Dumay  wrote:

> Hi Afonso,
>
> Super impressed with your work here! Google have done an excellent job
> with their Material Design Language – works well in a lot of situations.
>
> Did you have to do any changes that could break plugin compatibility along
> the way? I know when various people have looked at this sort of work here
> at CloudBees we've found it difficult to do this in a way that doesn't mess
> up plugins. If there is anything you could share on this topic that would
> be fantastic.
>
> Thanks,
> James Dumay
> CloudBees
>
> On Friday, January 22, 2016 at 4:16:50 AM UTC+11, Afonso F wrote:
>>
>> Hi guys,
>>
>> I created a Jenkins theme based on Google Material Design. It changes the
>> layout and icons using SVG ones. Take a look!
>>
>> http://afonsof.com/jenkins-material-theme/
>>
>>
>> 
>> 
>> 
>>
>>
>>
>>
>>
>> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/31c07159-c02b-4742-a079-9717c6fb7dcf%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZm1uEpoQ%2BdOUTQAOHFp3hq74SKCRHym82qh%2Bsh%2BcnYfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Threads dying...

[jieryn]

I was seeing this quite frequently too. I updated to the latest
1.609.3 LTS, they haven't reappeared.

On Thu, Sep 3, 2015 at 11:47 AM, Peter Berghold  wrote:
> Why does this happen?
>
> java.lang.IllegalStateException:
> /usr/share/tomcat6/webapps/jenkins/jobs/DEV-dnsstat/builds/2 already
> existed; will not overwite with DEV-dnsstat #2
>
>
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAArvnv2pVHyiur6Ew7SKanXhcfD2X%3DQSH28973VJK0%3DuGeJFOg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9ib2_cQEOQwgOE7uNTRSvCSn4jFL17FK_gLH2xGNNzX_Fw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JUC East and EU - slides/videos available

[jieryn]

Thanks! Will the keynotes be made available, too?

On Tue, Jul 21, 2015 at 7:58 PM, Alyssa Tong alyton...@gmail.com wrote:
 Hi Everyone,

 If you missed JUC East and or JUC Europe - videos and slides from these
 conferences are now available HERE (JUC East) and HERE (JUC EU).

 The agenda for JUC West (Sept 2-3, 2015) is also available HERE. Seats are
 filling up fast so sign up before the conference is sold out.  I am looking
 for community experts to staff the Ask The Experts booth. Pls shoot me an
 email if you're interested.

 thanks,
 alyssa




 --
 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/CAC9wNaw1ZeUE0fh1nP2k6O7o2qWiW%2BAQi4bLp8kNOzr8Dkrr5Q%40mail.gmail.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iY9pKkm2dHWzTAyim9meDy%2BAADRz_feOH_rqgirVZ%2BOnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to *properly* switch from Maven-style jobs to Freestyle jobs?

[jieryn]

There is no automated mechanism.

On Mon, Jun 15, 2015 at 5:50 AM, Victor Noël victor.n...@gmail.com wrote:
 Anybody? It seems an important issue to me…

 Thanks,

 Victor


 Le lundi 8 juin 2015 10:21:46 UTC+2, Victor Noël a écrit :

 Hi,

 Following the switch to Java 7+, many users have problem with the
 Maven-style jobs: they are forbidden to execute them with a version of Java
 inferior to 7.
 See for example https://issues.jenkins-ci.org/browse/JENKINS-28294.

 The common solution proposed by people is to switch to Freestyle project:
 there is more configuration to do, but the behaviour of the build will be
 more deterministic (see
 http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html
 for example for more explanation of why anyway maven-style jobs apparently
 sucks).

 So, my question now is: how do I properly switch to a freestyle project?

 In particular, my main concern is with dependencies and build triggering:
  - I want to be able to see the tree of builds like this:
 http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/265/
  - I want to see upstream and downstream projects like this:
 http://jenkins.petalslink.com/job/Petals%20Components%20-%20BC%20SOAP/
  - I want my jobs to be triggered when one of its dependencies was built
 (and not by checking every hours if a dependency has changed as one of the
 jenkins plugins do).

 Anybody has good suggestion to either do that, or to convince me I don't
 need it?

 Thank you :)

 Victor

 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/d5e12297-218e-4564-bad1-03cac3cf6250%40googlegroups.com.

 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAArU9iZ%2B_7mn1_UNrdjp9i8CGwvMgwDRcODP%3DYxdOUnXsbAceg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: force mass job save

[jieryn]

I don't have the same findings as you. I @daily have an
infra_save_items job with an Execute system Groovy script of:

for (item in hudson.model.Hudson.instance.items) {
  println(Saving  + item);
  item.save();
}

Not only does this work, but it does it quite quick; it also preserves
any sort of ACL permission system is in place. I find it helpful to
run this after a plugin update, I see the new versions of the plugins
in the jobs/*/config.xml. I'm using Jenkins LTS 1.565.3.



On Wed, Oct 15, 2014 at 5:56 PM, Darragh Bailey daragh.bai...@gmail.com wrote:

 Just went through an upgrade from an old version of jenkins/plugins and
 discovered that some jobs have not had their XML properly updated.

 This is resulting in odd behaviour where triggered jobs do not appear in the
 UI and are not readable, but the associated files appear on-disk.

 By going to the configure page for some jobs have been able to confirm that
 simply saving the job appears to sort the problem out. I suspect that this
 forces the correct configuration options to be set.


 I've tried using the script console to iteratively call 'job.save()' and
 that doesn't appear to have the same effect, I'm guessing it requires
 putting the current configuration through the latest forms and saving the
 result to get a working config. Where as just calling save writes the
 current stored config to disk without it going through any of the form
 validation code in the plugins.


 Is it possible to mass trigger a save for each job defined? Have close to
 2000, so doing this manually to catch the few broken ones is a bit of a
 chore. I've tried mechanize with the following in python:

 ###
 import mechanize
 import base64

 br = mechanize.Browser()
 username = insert
 apitoken = insert
 auth = 'Basic ' + base64.encodestring('%s:%s' % (username, apitoken))[:-1]
 auth_header = ('Authorization', auth)
 br.addheaders = [auth_header]
 br.set_handle_robots(False)
 br.set_proxies({})

 br.open(http://myjenkins/job/myjobname/configure;)

 br.select_form(name=config)
 br.submit(name=Submit)

 ###

 And all I see in response is mechanize._response.httperror_seek_wrapper:
 HTTP Error 400: This page expects a form submission. So it's not a simple
 straight forward submission.

 Any other way to essentially force the job configs to be updated based on
 the latest plugin options via the UI?

 --
 Darragh


 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SSH Agent Plugin - UnsatisfiedLinkError

[jieryn]

I'm not using any slave nodes of any kind. I just want to have a
Jenkins job with access to an SSH agent such that it can work with SCM
URIs of the type scm:svn:svn+ssh:// without me having to launch the
master Jenkins instance via ssh-agent directly in the startup script.

This is a RHEL 6.5 system that is fully up to date. It doesn't have
any unusual hackery for multi-lib.

On Mon, Jul 14, 2014 at 3:46 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
 This is an issue with which I have severe issues trying to reproduce.

 If you can document how you set up a slave node vm step by step from a known
 starting point perhaps I may be able to fix the issue, but right now *every*
 time I try to recreate the issue the damn SSH Agent works for me.

 One working theory is that you have 32-bit and 64-bit shared libraries being
 mis-identified...

 Another working theory is that it is something to do with JNR and
 classloader conflicts over remoting...

 All this is speculation though without a test case to verify against


 On 12 July 2014 03:05, jieryn jie...@gmail.com wrote:

 I'm using Jenkins LTS 1.554.3, and SSH Agent Plugin 1.4.1. I am seeing
 UnsatisfiedLinkError during jobs which try to use an SSH agent. How do
 I resolve this issue? There are only instructions for MacOS on the
 plugin wiki page.

 https://gist.github.com/jieryn/5248b713599321f2d548
 https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin

 Thank you.

 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SSH Agent Plugin - UnsatisfiedLinkError

[jieryn]

-bash-4.1$ uname -a
Linux ci.acme.com 2.6.32-431.21.1.el6.x86_64 #1 SMP Tue Jun 3 19:11:40
EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

-bash-4.1$ ls -la /lib/libc.so.6
lrwxrwxrwx. 1 root root 12 Jun  3 09:57 /lib/libc.so.6 - libc-2.12.so

-bash-4.1$ ldd /lib/libc.so.6
/lib/ld-linux.so.2 (0x00813000)
linux-gate.so.1 =  (0x00391000)

-bash-4.1$ file /lib/libc-2.12.so
/lib/libc-2.12.so: ELF 32-bit LSB shared object, Intel 80386, version
1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux
2.6.18, not stripped

-bash-4.1$ rpm -qf /lib/libc.so.6
glibc-2.12-1.132.el6_5.2.i686


On Wed, Jul 16, 2014 at 5:49 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:


 On Wednesday, 16 July 2014, Richard Bywater rich...@byh2o.com wrote:

 Is your RHEL6.5 system running as 32-bit or 64-bit? Also what does 'file
 /lib/libc.so.6' show (I imagine it will show symbolic link so if you then do
 a file on the resulting link what does that show?)


 I am suspecting it could be an ld-script... Perhaps even one that starts
 with a comment...

 (Says he who may have found the RCA if not the origin Of the RCA)

 Richard.


 On Thu, Jul 17, 2014 at 4:45 AM, jieryn jie...@gmail.com wrote:

 I'm not using any slave nodes of any kind. I just want to have a
 Jenkins job with access to an SSH agent such that it can work with SCM
 URIs of the type scm:svn:svn+ssh:// without me having to launch the
 master Jenkins instance via ssh-agent directly in the startup script.

 This is a RHEL 6.5 system that is fully up to date. It doesn't have
 any unusual hackery for multi-lib.

 On Mon, Jul 14, 2014 at 3:46 AM, Stephen Connolly
 stephen.alan.conno...@gmail.com wrote:
  This is an issue with which I have severe issues trying to reproduce.
 
  If you can document how you set up a slave node vm step by step from a
  known
  starting point perhaps I may be able to fix the issue, but right now
  *every*
  time I try to recreate the issue the damn SSH Agent works for me.
 
  One working theory is that you have 32-bit and 64-bit shared libraries
  being
  mis-identified...
 
  Another working theory is that it is something to do with JNR and
  classloader conflicts over remoting...
 
  All this is speculation though without a test case to verify against
 
 
  On 12 July 2014 03:05, jieryn jie...@gmail.com wrote:
 
  I'm using Jenkins LTS 1.554.3, and SSH Agent Plugin 1.4.1. I am seeing
  UnsatisfiedLinkError during jobs which try to use an SSH agent. How do
  I resolve this issue? There are only instructions for MacOS on the
  plugin wiki page.
 
  https://gist.github.com/jieryn/5248b713599321f2d548
  https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin
 
  Thank you.
 
  --
  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 jenkinsci-users+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
 
 
  --
  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 jenkinsci-users+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



 --
 Sent from my phone

 --
 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 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SSH Agent Plugin - UnsatisfiedLinkError

[jieryn]

Well... yes, that's true, but I also have the 64-bit version:

[root@ci ~]# yum info glibc
Installed Packages
Name: glibc
Arch: i686
Version : 2.12
Release : 1.132.el6_5.2
Size: 13 M
Repo: installed
From repo   : RHEL-65-x86_64-updates
Summary : The GNU libc libraries
URL : http://sources.redhat.com/glibc/
License : LGPLv2+ and LGPLv2+ with exceptions and GPLv2+
Description : The glibc package contains standard libraries which are used by
: multiple programs on the system. In order to save disk space and
: memory, as well as to make upgrading easier, common system code is
: kept in one place and shared between programs. This
particular package
: contains the most important sets of shared libraries:
the standard C
: library and the standard math library. Without these two
libraries, a
: Linux system will not function.

Name: glibc
Arch: x86_64
Version : 2.12
Release : 1.132.el6_5.2
Size: 12 M
Repo: installed
From repo   : RHEL-65-x86_64-updates
Summary : The GNU libc libraries
URL : http://sources.redhat.com/glibc/
License : LGPLv2+ and LGPLv2+ with exceptions and GPLv2+
Description : The glibc package contains standard libraries which are used by
: multiple programs on the system. In order to save disk space and
: memory, as well as to make upgrading easier, common system code is
: kept in one place and shared between programs. This
particular package
: contains the most important sets of shared libraries:
the standard C
: library and the standard math library. Without these two
libraries, a
: Linux system will not function.

On Wed, Jul 16, 2014 at 6:33 PM, Richard Bywater rich...@byh2o.com wrote:
 Ok so looks like you've got the the x86 version of glibc installed on a
 64-bit system (which I don't think is a default position). So I guess the
 question for Stephen was whether he had installed the x86 glibc as well
 during his testing of CentOS?

 Richard.


 On Thu, Jul 17, 2014 at 10:18 AM, jieryn jie...@gmail.com wrote:

 -bash-4.1$ uname -a
 Linux ci.acme.com 2.6.32-431.21.1.el6.x86_64 #1 SMP Tue Jun 3 19:11:40
 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

 -bash-4.1$ ls -la /lib/libc.so.6
 lrwxrwxrwx. 1 root root 12 Jun  3 09:57 /lib/libc.so.6 - libc-2.12.so

 -bash-4.1$ ldd /lib/libc.so.6
 /lib/ld-linux.so.2 (0x00813000)
 linux-gate.so.1 =  (0x00391000)

 -bash-4.1$ file /lib/libc-2.12.so
 /lib/libc-2.12.so: ELF 32-bit LSB shared object, Intel 80386, version
 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux
 2.6.18, not stripped

 -bash-4.1$ rpm -qf /lib/libc.so.6
 glibc-2.12-1.132.el6_5.2.i686


 On Wed, Jul 16, 2014 at 5:49 PM, Stephen Connolly
 stephen.alan.conno...@gmail.com wrote:
 
 
  On Wednesday, 16 July 2014, Richard Bywater rich...@byh2o.com wrote:
 
  Is your RHEL6.5 system running as 32-bit or 64-bit? Also what does
  'file
  /lib/libc.so.6' show (I imagine it will show symbolic link so if you
  then do
  a file on the resulting link what does that show?)
 
 
  I am suspecting it could be an ld-script... Perhaps even one that starts
  with a comment...
 
  (Says he who may have found the RCA if not the origin Of the RCA)
 
  Richard.
 
 
  On Thu, Jul 17, 2014 at 4:45 AM, jieryn jie...@gmail.com wrote:
 
  I'm not using any slave nodes of any kind. I just want to have a
  Jenkins job with access to an SSH agent such that it can work with SCM
  URIs of the type scm:svn:svn+ssh:// without me having to launch the
  master Jenkins instance via ssh-agent directly in the startup script.
 
  This is a RHEL 6.5 system that is fully up to date. It doesn't have
  any unusual hackery for multi-lib.
 
  On Mon, Jul 14, 2014 at 3:46 AM, Stephen Connolly
  stephen.alan.conno...@gmail.com wrote:
   This is an issue with which I have severe issues trying to
   reproduce.
  
   If you can document how you set up a slave node vm step by step from
   a
   known
   starting point perhaps I may be able to fix the issue, but right now
   *every*
   time I try to recreate the issue the damn SSH Agent works for me.
  
   One working theory is that you have 32-bit and 64-bit shared
   libraries
   being
   mis-identified...
  
   Another working theory is that it is something to do with JNR and
   classloader conflicts over remoting...
  
   All this is speculation though without a test case to verify against
  
  
   On 12 July 2014 03:05, jieryn jie...@gmail.com wrote:
  
   I'm using Jenkins LTS 1.554.3, and SSH Agent Plugin 1.4.1. I am
   seeing
   UnsatisfiedLinkError during jobs which try to use an SSH agent. How
   do
   I resolve this issue? There are only instructions for MacOS on the
   plugin wiki page.
  
   https://gist.github.com/jieryn/5248b713599321f2d548
   https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent

SSH Agent Plugin - UnsatisfiedLinkError

[jieryn]

I'm using Jenkins LTS 1.554.3, and SSH Agent Plugin 1.4.1. I am seeing
UnsatisfiedLinkError during jobs which try to use an SSH agent. How do
I resolve this issue? There are only instructions for MacOS on the
plugin wiki page.

https://gist.github.com/jieryn/5248b713599321f2d548
https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin

Thank you.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins deploy to maven site

[jieryn]

Make your job parameterized, add a parameter which lists the SCM tags,
refer to that variable in the SCM checkout section.

On Mon, Jan 13, 2014 at 7:12 AM, Trista Monaghan
tristamonag...@gmail.com wrote:
 I need a separate site job to deploy to maven site after release build. How
 can I deploy the correct version without SNAPSHOT dependency?

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [ANN] Credentials plugin 1.9.3 - now with in-place add support

[jieryn]

Why not just hide the button entirely?

On Fri, Nov 8, 2013 at 10:55 AM, Stephen Connolly 
stephen.alan.conno...@gmail.com wrote:

 One more thing... if you don't have permission to create credentials, the
 button will be disabled...



-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: LTS 1.509.3 -- Bad Fingerprint Invasion

[jieryn]

Greetings,

On Wed, Oct 9, 2013 at 1:23 AM, Daniel Beck m...@beckweb.net wrote:
 It looks like you're referring to 
 https://issues.jenkins-ci.org/browse/JENKINS-19515 which will be fixed in 
 1.509.4. There's already an RC, so you could try upgrading.

https://issues.jenkins-ci.org/browse/JENKINS-19515 is a fix for
something introduced by
https://issues.jenkins-ci.org/browse/JENKINS-16301 which itself is
just a poor performance issue. I'm a bit conflicted on this, but I
think a case could be easily made that performance fixes shouldn't be
injected into an existing LTS line. Perhaps a new LTS, sure, but given
that 16301 only seemed to affect artifacts in the 100s of megabytes
range, I have doubts that this hits very many installations, and so
its inclusion into LTS seems suspect.

 Did you test the 1.509.3 RC when it was available for almost four weeks 
 before the final version was released?

If I wanted to be in the RC testing game I would just use the RCs
themselves. As I do for every Jenkins LTS, I deploy it locally on my
laptop first and run about a dozen jobs for my most critical use
cases. They all worked and I did not see this issue. This is way
beyond what most users do! There seems to be very little value in
having an LTS line at all if we're just going to off load extensive
testing to the users again -- given your attitude, please tell me how
this differs from the weekly releases?

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

LTS 1.509.3 -- Bad Fingerprint Invasion

[jieryn]

bash$ find /var/lib/jenkins/fingerprints/ -type f | while read fp ; do
xmllint --format $fp /dev/null ; if [[ $? == 1 ]] ; then echo
stupid $fp ; rm $fp ; fi ; done

Why do I have to do this? This seems like a huge failure. Not sure how
this got to LTS..

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Javadoc plugin 1.0 displaying error in plugin manager

[jieryn]

Greetings,

On Fri, May 31, 2013 at 8:09 AM, Kamal Ahmed kamalah...@yahoo.com wrote:
 any idea how to resolve this ?

Uninstall the TestSwarm plugin.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Javadoc plugin 1.0 displaying error in plugin manager

[jieryn]

Greetings,

On Fri, May 31, 2013 at 9:11 AM, Kamal Ahmed kamalah...@yahoo.com wrote:
 question is how come javadoc, which is a core plugin, depending on testswarm?

There is absolutely no evidence that you have ever reported that even
remotely links javadoc, or the Jenkins Javadoc Plugin, to the issue.
So unless you are not reporting all the problems, you are under a
grave misunderstanding.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.