Bruce Schneier Plugin appears broken

[Nicholas Geovanis]

FWIW, for your amusement, on a Friday afternoon: The Bruce Schneier Plugin 
for jenkins appears to be broken. No Schneier photos replace the butler 
Jenkins.

-- 
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/89ebb79b-7e33-43d8-9a90-360404872f14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 alpha release available

[R. Tyler Croy]

A follow-up on this thread, we released alpha3 today with the new security
setup and some other UI improvements, read more about it here:




On Mon, 29 Feb 2016, R. Tyler Croy wrote:

> As I mention in this blog post: 
> https://jenkins-ci.org/blog/2016/02/29/jenkins2-alphas/
> 
> The first Jenkins 2.0 alpha downloads are available (yay!). You can read more
> about it on the 2.0 landing page (https://jenkins-ci.org/2.0/), which also
> includes the links the download various native packages of the 2.0 alpha.
> 
> 
> I'm going to be linking to this thread from the page and blog post for
> feedback, so by all means, download it and play around with it!
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 
> -- 
> 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/20160229233911.GS13352%40blackberry.coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.



- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
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/20160311210425.GN13352%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: simple build (DSL) for pipeline plugin

[Martin d'Anjou]

Hi Michael,

I played with the plugin quite a bit. I am very enthusiastic about this 
plugin, because it gives me a way to manage the pipeline script development 
as if it were a regular plugin (code, test, version and release), while 
being much easier to write than a regular plugin.

I do not plan to use the mini simpleBuild DSL as is, but I plan to use its 
base class PipelineDSLGlobal and build a different core with it. I do not 
plan on using the Jenkinsfile aspect yet, because I have multiple CD/CI 
pipelines per branch in my projects, and only one Jenkinsfile is supported 
currently.

One thing I was trying to do was to acess the "env" and the build 
parameters from inside the simpleBuild Closure. I changed "env" to "map" in 
the source (so "env" would not be hidden), and I attempted the following:
simpleBuild {
...
map = [url: "http://host/path/${PARAM}/${env.BUILD_NUMBER};]
...
}

I tried various ways of setting the closure delegate (see it on my github 
fork 
)
 
but the alternative I tried results in not being able to resolve the "scm" 
in "checkout scm". If I use ${this.env.BUILD_NUMBER}, then it works, but I 
would feel more comfortable using your code if I understood why 
${env.BUILD_NUMBER} cannot be resolved. The Closure owner is a 
WorkflowScript after all, and it should have "env".

Thanks,
Martin

On Wednesday, February 24, 2016 at 9:42:41 PM UTC-5, Michael Neale wrote:
>
> Hey I thought some may be interested in this Pipeline DSL enhancement (ie 
> a plugin that enhances Jenkins pipeline) which is installable as a plugin: 
> https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For+Pipeline+Plugin 
> - interested in thoughts/feedback (you use it where you would use a 
> Jenkinsfile or pipeline script). 
>
>

-- 
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/a4b0b99e-b89f-4c9b-9bca-ec4552aca7ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Start a job on slave / node that just connected to master server

[Eric Pyle]

Before the reboot, you could queue up the job you want to run right 
after reboot. If other jobs may be competing, you can give your special 
job a higher priority (priority sorter plugin).


Eric

On 3/11/2016 7:05 AM, Jakub Gladykowski wrote:


On Friday, March 11, 2016 at 1:01:01 PM UTC+1, Simon Richter wrote:

This seems like a good time to ask what you *actually* want to do[1].

   Simon

[1] http://xyproblem.info/


 I need to reboot slave few times during test. So whenever slave goes 
back online, I need to execute another job, and another and another,. 
I can always do it by using Python API. However it would be much 
nicer, to start job on that slave, which will handle things.

--
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/ffc35b09-4db5-419f-914d-fdd4ec2e7eb4%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/56E31B4E.1000101%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.

Parameterized TRigger plugin not finding properties files when using Parameter factories

[Elvis Presley]

Jenkins 1.643 on Windows Server 2012R2 x64
Java 1.8.0_20 x86
Parameterized Trigger plugin 2.30

Hi,

Job A uses *"For every property file, invoke one build"* parameter factory 
to call downstream job B.
Here is the file pattern I am using:

d:\scripts\batch\salesconfig*.txt

There are two files in that folder:


*salesconfig124.txt*

*salesconfig126.txt*

Job B fails because job A is not setting the parameters it depends on, or 
something similar. If I look at the parameters for a build of Job B, they 
are empty.

I have the option "*Action to perform when no files found"* set to *"Fail 
the build step*" in Job A, but Job A does not fail, only Job B.

I have also tried:

Escaping backslashes in path (e.g. d:\\scripts\\batch\\salesconfig*.txt)
Using different wildcards (e.g. salesconfig*.txt, salesconfig1??.txt)
Using absolute filename (e.g.d:\\scripts\\batch\\salesconfig126.txt)


The process works when I use *"Parameters from  properties file"* parameter 
type instead of a parameter factory, and specify the full path to one of 
the files, so I know the files are in the right format. I do not want to 
add a parameter for each file I have,
 since I will eventually have 15 or more files.I would prefer to use the 
parameter factory if possible.

Any ideas?

Thanks,
pimy

-- 
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/d6259099-20e4-49da-8505-0d2f0859e8e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Development environment for Pipeline (aka workflow)

[Martin d'Anjou]

On Tuesday, February 2, 2016 at 5:14:54 PM UTC-5, Tom Kierzkowski wrote:
>
>
>- How do you test your scripts within your IDE/development setup?
>
>
>  I do not use and IDE, but I was shown these two plugins which show a way 
of testing pipeline scripts:

   - https://github.com/jenkinsci/simple-build-for-pipeline-plugin
   - https://github.com/jenkinsci/simple-travis-runner-plugin

Both require you to implement your pipeline code as a Jenkins plugin, which 
is the only way I have found to really test pipeline code. In fact they go 
one step further, it's almost like they let you define your own DSL, on top 
of the pipeline DSL.

With the simple-build-for-pipeline-plugin, you can access the env and the 
build parameters from the simpleBuild {} closure by using "this.env" and 
"this.PARAM", e.g. simpleBuild { var = this.PARAM }. Tooks me a while to 
figure this one out.

Martin

-- 
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/40e6aae2-02ae-4d8e-a1b9-ea7406f101e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkinsfile: usable for pull request integration?

[Martin d'Anjou]

If I understand correctly, the Jenkinsfile is stored in the same repository 
as the code it manages. But I have a concern with using the Jenkinsfile to 
manage pull request integration.

My definition of pull request integration: checkout the destination branch, 
merge the pull request, run test, if they pass, push the merge back to 
upstream.

And the question is what if users disable the merge by accident? Subsequent 
runs won't be able to merge anymore, and it's impossible to undo the damage 
when this happens.

Can someone clarify when to use the Jenkinsfile?

Martin

-- 
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/b35c8382-afcf-4b19-b58a-82a40f7a5c84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkinsfile: is more than one possible?

[Martin d'Anjou]

I was re-reading JENKINS-31155 
, and in the context of 
a project in a Git repository, I have more than one CI/CD pipeline per 
branch. So a single Jenkinsfile does not appear to be enough. Anyone has 
thoughts on that?

Martin

-- 
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/2a982e90-1c76-4c4f-8a9d-eef58d002e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limit job start time to period

[Baptiste Mathus]

Don't know any plugin designed precisely for that.
But if I had to do it, I'd try two ways:
* either have a first step to check the current hour to decide to continue
or not
* or have a job dedicated to that, but that would trigger another one
conditionally

Advantage of the second one: you'll only have actual executions on the
downstream job. With the first you'll have visible builds even if they were
stopped at first step.

My 2 cents
Le 11 mars 2016 7:25 AM, "Igor"  a écrit :

> Hello,
> I want to limit a job, to start in the specific time period and just if it
> was triggered.
> How the best is to do it?
>
> 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/6c4d2ce0-7818-4015-93db-d428b015394a%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/CANWgJS6X0u2VGDnXET2_wSChUB9tt8gUpDtaGdxvzts%2BQJ6uJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Start a job on slave / node that just connected to master server

[Jakub Gladykowski]

On Friday, March 11, 2016 at 1:01:01 PM UTC+1, Simon Richter wrote:
>
> This seems like a good time to ask what you *actually* want to do[1]. 
>
>Simon 
>
> [1] http://xyproblem.info/ 
>

 I need to reboot slave few times during test. So whenever slave goes back 
online, I need to execute another job, and another and another,. I can 
always do it by using Python API. However it would be much nicer, to start 
job on that slave, which will handle things. 

-- 
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/ffc35b09-4db5-419f-914d-fdd4ec2e7eb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Start a job on slave / node that just connected to master server

[Simon Richter]

Hi,

On 11.03.2016 12:38, Jakub Gladykowski wrote:

> However all I want
> to do, is to trigger this job, only on the slave / node that just connected.

This seems like a good time to ask what you *actually* want to do[1].

   Simon

[1] http://xyproblem.info/

-- 
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/56E2B36C.20701%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.

Start a job on slave / node that just connected to master server

[Jakub Gladykowski]

http://wiki.jenkins-ci.org/display/JENKINS/Startup+Trigger will trigger 
build, whenever slave / node will connect. You can restrict on which slaves 
this build will be triggered, by using labels. However all I want to do, is 
to trigger this job, only on the slave / node that just connected.
I there a way I can achieve that in Jenkins?

-- 
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/0ce527a0-14a9-4520-96cb-99dccf45ccb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Task - Is it possible to add a windows shell commands as a step ( on Windows salve) inside a Linux master job.

[Jakub Gladykowski]

Hi,

While installing GIT, many UNIX commands can be installed and added to path 
https://git-scm.com/ Then you can execute some shell commands on Windows 
slave. This is fast approach. Full approach would involve installing CYGWIN 
or some other stuff. 

On Friday, March 4, 2016 at 9:10:32 AM UTC+1, Eldad Cohen wrote:
>
> Hi,
>
> Is it possible to add to a master job that runs on Linux , some windows 
> shell commands step on windows slave inside a Linux master job.
> Let's say a , how to run windows commands step on slave when running a job 
> on Linux master.
> Hope I am describing my question correct .
>
> Thanks in Advanced on any help
>

-- 
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/8aaabf24-9901-4c28-9a31-214dcacbdc22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to whitelist the branches to be built upon git hook notification

[Baptiste Mathus]

Le 9 mars 2016 9:36 PM, "Mark Waite"  a écrit :
>
> You might consider the "pipeline plugin".  It includes a multi-branch
facility which will automatically configure a new job for any branch which
has a "Jenkinsrule" file

Nitpicking for future reference: that file is actually named Jenkinsfile.

-- Baptiste

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

Re: Pipeline Workflow && Blocking other jobs

[Baptiste Mathus]

Gonna probably require twiddling with the API, but it should be possible to
use one of the lock plugins (throttle one e.g.).

* On the non pipeline one: use it normally
* On the pipeline one: wrap the required groovy code in a @NonCPS function
to attack the plugin API and acquire the lock.

My 2 cents
Le 10 mars 2016 9:09 AM, "Pierre Lerouge"  a
écrit :

> Hey,
> Nobody had this need with the pipeline plugin ?
>
> Le lundi 7 mars 2016 16:53:56 UTC+1, Pierre Lerouge a écrit :
>>
>> Hi,
>>
>> I'm trying to block some job when a pipeline is running.
>> More precisely I'm trying to find a wrapper around certain stages which
>> could prevent other job to run while this stage is running.
>>
>> My main problem is the following:
>>My workflow plugin launch a maven:release at some point, which create
>> events in the SCM, wich run a standard build job that destroy my
>> integration platform.
>>
>> I don't know if it's clear.
>> I usually use the Exclusion plugin :
>> https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin
>> To prevent a job running when there is already another one using this
>> resource.
>> I've seen that there are some commits that allow this plugin to be run
>> within a pipeline :
>> https://github.com/jenkinsci/exclusion-plugin/pull/5
>> But I really don't know how to implement this.
>>
>> Have anybody already set up this kind of thing ?
>> Thank you for your help.
>>
>> --
> 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/be92093a-baa1-4f2a-86e2-8904b7834516%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/CANWgJS6zOnx6XbwcgXjBHvMCO5TVf%3Do1QQpQfrgJMJofw3Q%3D%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Have job set ball additional ball color

[Baptiste Mathus]

If you're just gonna lookup a string in the logs, BTW, you might find the
Text Finder Plugin a wee bit simpler.
My 2 cents
Le 9 mars 2016 1:49 PM, "Daniel Beck"  a écrit :

> I solved similar problems in the past by making sure a line in the build
> log states e.g. "Nothing downloaded", and then use a plugin like Groovy
> Postbuild to look for that line, and if it was encountered, set the build
> result to Unstable (assuming that right now, you only have Stable and
> Failed builds).
>
> On 09.03.2016, at 07:31, Matt Childress  wrote:
>
> > We use Jenkins CI along with two Python scripts AutoPkg/Aamporter and
> Munki to manage macintoshes (Jenkins controls 5x daily runs of AutoPkg and
> Aamporter which check for 3rd party software updates and import them into
> the munki software repository)
> >
> > Most of the time the jobs are successful and nothing happens (no new
> software found and downloaded).
> >
> > Jenkins ROCKS for this, and we can easily disable a job when the
> software vendor breaks/changes their distribution method (is there an
> option/plug-in for "re-enable in x number of days?)"
> >
> > BUT a successful job (nothing downloaded) and a successful job (new item
> downloaded) both result in a blue ball.  This makes it hard to find the
> downloads in the console output page.
> >
> > What I'd like to be able to do is have a job set a custom icon via
> script if it's downloaded something (I've already got an email script
> taking care of the logic)
> >
> > Any pointers to how-to (including "you're going about it wrong")?
> >
> > Many thanks,
> > M@
> >
> > --
> > 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/fde3e45a-9906-46b7-935f-ec270c494289%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/D362BC1B-FC0A-4404-96A6-2F323507F263%40beckweb.net
> .
> 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/CANWgJS78H92yss1FfWU2MM4tiwxpbvLie5NVbDV%3DqT_3mtBkvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.