Deploy Oozie Jobs using Jenkins

[Abhishek Srivastava]

I am working on a project which requires me to write oozie jobs.

Is there a way in which jenkins can deploy my oozie jobs? is there a plugin 
for oozie in jenkins?

I searched for jenkins plugins for oozie but did not find anything. 

-- 
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/93ed3b46-d82d-406f-9689-682f6d695e66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Issue while installing Jenkins plugin nodelabelparameter

[Tatzagata]

Hi,

I am getting the following issue while installing 
plugin nodelabelparameter. 

java.io.IOException: Failed to dynamically deploy this plugin
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1383)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1161)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at 
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Failed to install nodelabelparameter plugin
at hudson.PluginManager.dynamicLoad(PluginManager.java:487)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1379)
... 5 more
Caused by: java.io.IOException: Dependency token-macro (1.11), jquery (1.7.2-1) 
doesn't exist
at 
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:533)
at hudson.PluginManager.dynamicLoad(PluginManager.java:477)
... 6 more


Any help will be appreciated.


Regards,


Tathagata

-- 
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/66059441-3000-462d-938d-41e151d1078f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Configuring Specflow scenarios tags running in CI (Jenkins)

[Ana Sousa]

Hi all, 

I have a lot of specflow feature files in my .Net code with loads of 
scenarios for each feature file. 
I'm putting some tags in the scenarios in order to categorize my tests and 
only run sub-sets of the tests. My tags are as simple as @smoke 
@integration @regression @critical.

I was wondering if someone knows a way to configure CI (jenkins) in order 
to run only the "smoke" or "critical" or "integration" tags.

Thank you for your help.

Best regards,
Ana

-- 
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/e14ed0e5-521d-42af-8e02-7260ff782613%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: MultiJob retry functionality...I cant get it working

[Zheng LiSheng]

My problem is that nothing happens after selecting "Enable retry".

On Thursday, October 15, 2015 at 9:44:09 PM UTC+8, Kris Massey wrote:
>
> Hey All,
>
> I'm new to the Jenkins MultiJOb plugin and I'm having some troubles using 
> the retry functionality. 
>
> I have a job configured
>
> MultiJob
>  - Phase 1
>   - Job 1
>   - Job 2
>  - Phase 2
>- Job 3
>
>
> Job 2 can have random failures (due to external client system), I've 
> noticed that the MultiJob -> Phase -> Job configuration offers  a 'Enable 
> retry' option, so I was hoping this would then attempt a retry and kick off 
> phase 2 if the job passed the second time. 
>
> My issue is the retry never seems to happen, below is some output on the 
> console of the MultiJob
>
> [EnvInject] - Loading node environment variables.
> Building in workspace /var/lib/jenkins/jobs/build-process/workspace
> >> Job status: [Job2] the 'build only if scm changes' feature is disabled.
> Starting build job p2 .
> >> Job status: [Job1] the 'build only if scm changes' feature is disabled.
> Starting build job p1 .
> Finished Build : #21  
> of Job : Job2 with status : FAILURE 
> *Scanning 
> failed job console output using parsing rule file .
> Parser rules file not found.*
> Failed the build, the failure doesn't match the rules.
> Finished Build : #23  
> of Job : J ob1 with status 
> : SUCCESS 
> Build step 'MultiJob Phase' marked build as failure
> Notifying upstream projects of job completion
> Warning: you have no plugins providing access control for builds, so falling 
> back to legacy behavior of permitting any downstream builds to be triggered
> Finished: FAILURE
>
>
> I've highlighted the lines I believe may be causing the issue, however I've 
> got no idea how to solve it (hopefully its missing config as apposed to a bug 
> in the MultiJob plugin)
>
>
> Any help greatly appreciated! 
>
>

-- 
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/eac911af-34c8-4077-a38b-074e5702f169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parameterized Remote Trigger Plugin fails job on server downtime

[Lampe, Ingo]

Hello,

is there an way to avoid failing the which uses if the
Parameterized Remote Trigger Plugin failed on server downtime

mee_my_wrong_Remote_Jenkins
Connection to remote server failed, waiting for to retry - 5 seconds until next 
attempt.
Retry attempt #1 out of 5
mee_my_wrong_Remote_Jenkins
Connection to remote server failed, waiting for to retry - 5 seconds until next 
attempt.
Retry attempt #2 out of 5
mee_my_wrong_Remote_Jenkins
Connection to remote server failed, waiting for to retry - 5 seconds until next 
attempt.
Retry attempt #3 out of 5
mee_my_wrong_Remote_Jenkins
Connection to remote server failed, waiting for to retry - 5 seconds until next 
attempt.
Retry attempt #4 out of 5
mee_my_wrong_Remote_Jenkins
Connection to remote server failed, waiting for to retry - 5 seconds until next 
attempt.
Retry attempt #5 out of 5
mee_my_wrong_Remote_Jenkins
ERROR: Remote build failed for the following reason, but the build will 
continue:
ERROR: Max number of 
connection retries have been exeeded.
ERROR: Build step failed 
with exception
java.lang.NullPointerException
at 
org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:1167)
at 
org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:488)
at 
hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at 
hudson.model.Build$BuildExecution.build(Build.java:205)
at 
hudson.model.Build$BuildExecution.doRun(Build.java:162)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
at 
hudson.model.Run.execute(Run.java:1741)
at 
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at 
hudson.model.ResourceController.execute(ResourceController.java:98)
at 
hudson.model.Executor.run(Executor.java:408)
Build step 'Trigger a remote parameterized job' marked build as failure


Best Regards

Ingo Lampe

-- 
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/1BE265180764CA40B7D4EE075EC6C8F4E6165A70%40framsexm11.magna.global.
For more options, visit https://groups.google.com/d/optout.

Re: How to get the list of user views by the api

[Yohann Perraud]

Thanks.

I don't understand why this *user* informations are not actually exposed on 
the /*user* api.

So, I create a new UserProperty called UserViewsProperty (source code in 
attachment) and integrate it in a plugin.
This solution required me to create an empty config.jelly for the 
/user/configure page. My skills on Jenkins core being insufficient, I 
haven't really understood why.
When I call the user api, I 've got now a new property called "userViews"

In any case, it works but I'm interested in any comments or another type of 
solution.

Le mercredi 13 janvier 2016 16:09:35 UTC+1, Daniel Beck a écrit :
>
> These are not exposed via the API. The MyViewsProperty is one of the empty 
> {} in 'property'. 
>
> On 13.01.2016, at 15:52, Yohann Perraud  > wrote: 
>
> > Hi, 
> > 
> > Is there a way to retrieve the list of view for a user via the Rest API 
> ? 
> > 
> > I tried /user//my-views/api/json, /user/picadmin/api/json with 
> differents depth but it never return his views. 
> > I googled it and I 've found nothing. 
> > 
> > Thanks in advance. 
> > 
> > Yohann. 
> > 
> >   
> > 
> > -- 
> > 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/85cb952a-8012-4ce3-aeb5-e9dd2873dc9b%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/994ffddb-c262-46bf-bcfc-0743dabf377a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
package fr.laposte.disfe.pic.adb.jenkins.plugin.property;

import hudson.Extension;
import hudson.model.UserProperty;
import hudson.model.UserPropertyDescriptor;
import hudson.model.MyViewsProperty;
import hudson.model.User;
import hudson.model.View;

import java.util.ArrayList;
import java.util.List;

import net.sf.json.JSONObject;

import org.kohsuke.stapler.StaplerRequest;
import org.kohsuke.stapler.export.Exported;

public class UserViewsProperty extends hudson.model.UserProperty {

	public UserViewsProperty() {

	}

	@Exported(name = "userViews"/* , inline = true */)
	public List getUserViews() {
		final User user = User.current();

		if (user != null && user.getProperty(MyViewsProperty.class) != null) {
			return new ArrayList(user.getProperty(MyViewsProperty.class).getViews());
		}
		return new ArrayList();

	}

	@Extension
	public static final class DescriptorImpl extends UserPropertyDescriptor {

		@Override
		public String getDisplayName() {
			return null;
		}

		@Override
		public UserProperty newInstance(final User user) {
			return new UserViewsProperty();
		}

		@Override
		public UserProperty newInstance(final StaplerRequest req, final JSONObject formData)
throws FormException {
			return null;
		}

	}

}

run job chain parameter-depended on different slaves at the same time

[Lampe, Ingo]

Hello,

I have the following  problem


1 jenkins master (1.625.3)

2 windows 7 slaves ( connected and started over JLNP):

-slave1

-slave2

3 job: (TestStarter -> FlashEcu -> TestEcu)




DownstreamTrigger
of
Job Test_Starter

DownstreamTrigger
of
Job FlashEcu


master| Test Starter


Slave1 | FlashEcu

Slave1 | TestEcu

Slave2 | FlashEcu

Slave2 | TestEcu

…

..



the job will be triggered on the special slave depending on the parameter 
CurrentVariant(Variant1-3 runs on slave 1,Variant4 runs on slave2)

This work generally fine but the test takes much time, so it would be nice if 
the test job(FlashEcu & TestEcu) can run parallel on the 2 or more slaves.

I have tried it with the Throttle Concurrent Build plugin, but it worked not 
really parallel the FlashJob will be blocked till it has ended.

Can anyone help me or give me a hint?

Best Regards

Ingo




-- 
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/1BE265180764CA40B7D4EE075EC6C8F4E6165AAE%40framsexm11.magna.global.
For more options, visit https://groups.google.com/d/optout.

Re: Git Plugin: updated password now cannot connect to repo

[Mark Waite]

I doubt it is a bug in the git plugin or the git client plugin, just based
on the things that have changed and the things that have not changed.
You've changed credentials, and not changed the git plugin or the git
client plugin.

http://askubuntu.com/questions/336907/really-verbose-way-to-test-git-connection-over-ssh
suggests
that you might be able to use ~/.ssh/config to enable much more verbose
logging.  That might provide better hints to the root of the problem.

Mark Waite

On Thu, Jan 14, 2016 at 6:12 PM Jim Klo  wrote:

> Hi,
>
> Over the last few days my password used for Jenkins' Git Plugin expired,
> of which I promptly updated in Jenkins.
>
> Unfortunately, even with the correct password (which uses the same special
> characters as the previous password) it won't authenticate, and there
> doesn't seem to be any other error that what I captured in the attached
> screen grab.
> The same credentials work with Jenkins SVN Plugin, noting that our SCM
> uses LDAP.  I can switch to another user's credentials and it work fine,
> but I cannot seem to get the original login to work.
>
> Not sure what I'm doing wrong.  Is this a bug?  Is there a workaround?  It
> seems like to me like Git might caching credentials globally, but not sure.
>
> --
> 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/90f66c85-97f7-4c24-81ad-acd8210efe62%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/CAO49JtHZ4RqGRnRz5_Abw%2BveDzzyZcrjSrzkJ5s80noJkT_awg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git Plugin: updated password now cannot connect to repo

[Jim Klo]

Thanks, unfortunately that doesn't yield much more help...

Building in workspace /Users//.jenkins/jobs/junk/workspace
Cloning the remote Git repository
Cloning repository https://xx.com/scm/git/ROR/-packaging
 > git init /Users/sunflower/.jenkins/jobs/junk/workspace # timeout=10
Fetching upstream changes from https://xx.com/scm/git/ROR/xxx-packaging
 > git --version # timeout=10
using .gitcredentials to set credentials
 > git config --local credential.username xx # timeout=10
 > git config --local credential.helper store 
 > --file=/var/folders/vx/bg9y23jd4dnd_8c0vdkk097rgn/T/git7310946539402031311.credentials
 >  # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://xx.com/scm/git/ROR/xxx-packaging 
 > +refs/heads/*:refs/remotes/origin/*
 > git config --local --remove-section credential # timeout=10
ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
:
 Command "git -c core.askpass=true fetch --tags --progress 
https://xx.com/scm/git/ROR/xxx-packaging 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: remote error: Invalid username or password.



Now I've also tried upgrading Jenkins and all the plugins... same error.

Jim 

-- 
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/086eb3e7-3884-4569-b99a-d39392dffd70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slack Plugin doesn't notify channel

[Michael Meluso]

I actually found it on the slack documentation first instead of jenkins:
https://slack.com/apps/A0F7VRFKN-jenkins-ci. Unfortunately I don't think
slack apps are set up like a wiki.

On Thu, Jan 14, 2016 at 3:06 PM Christopher Orr  wrote:

> Feel free to just add documentation to the wiki page (as it suggests you
> do), since that's the place most people will look for information:
> https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin says
>
> Regards,
> Chris
>
>
> On 14/01/16 19:28, Brenton wrote:
> > So who wants to write up a PR? :)
> >
> > On 13 January 2016 at 21:47, Mike Meluso  > > wrote:
> >
> > Yes I agree, it should be added to the instructions. I'm glad I
> > found this thread or I would've given up.
> >
> > On Monday, March 30, 2015 at 4:31:34 PM UTC-4, Brantone wrote:
> >
> > Agreed would be handy ... even anything at this point since it's
> > pretty scarce.
> > It does seem slightly counter-intuitive that a Post-build action
> > would be required for something that could send a notification
> > before it even builds ... but, there ya have it.
> >
> > On 30 March 2015 at 13:23, Hugo M  wrote:
> >
> > Wow! I didn't know that I should add it as a post-build
> > action. It worked like a charm. Thanks!!
> >
> > Maybe this should be added to "Jenkins Instructions" section
> > of the repo README?
> >
> >
> > Hugo Massaroli on about.me
> >
> > Hugo Massaroli
> > about.me/hugo.massaroli
> >
> >
> > 
> >
> > 2015-03-30 14:27 GMT-03:00 Brenton Bartel <
> bre...@letrabb.com>:
> >
> > No other dependency as far as I'm aware. Have you added
> > Slack as a post-build action and checked off necessary
> > options in the job itself?
> >
> >
> > On 30 March 2015 at 10:13, Hugo M 
> wrote:
> >
> > Another discovery, when I press "Test connection" I
> > see things happening in the jenkins.log. But If I
> > start a job, or if that job fails (job configured
> > with Slack plugin), nothing appears on the log
> > (nothing related with Slack plugin).
> >
> > Does Slack plugin has a dependency on another
> > plugin? It seems that is simply not triggering the
> > post when a job start / fail / etc.
> >
> >
> > Hugo Massaroli on about.me
> >
> > Hugo Massaroli
> > about.me/hugo.massaroli
> >
> >
> > 
> >
> > 2015-03-30 10:10 GMT-03:00 Hugo M  >:
> >
> >  Hi Brantone, thanks for your answer.
> >
> > Both "Test connection" in job configuration and
> > in Global Settings work in the sense that a
> > message is posted on Jenkins: "Slack/Jenkins
> > plugin: you're all set."
> >
> > If I put wrong data there I get "Success" too
> > but no message is posted, and I can see errors
> > in the Jenkins log.
> >
> > My problem is that I'm not getting the
> > notifications from the jobs anyway.
> >
> > Maybe this is related with the fact that I'm
> > using a private channel? But I can see the
> > Jenkins message even if it's a private channel,
> > so it souldn't be an issue.
> >
> >
> >
> >
> > Hugo Massaroli on about.me
> >
> > Hugo Massaroli
> > about.me/hugo.massaroli
> >
> >
> > 
> >
> > 2015-03-30 4:46 GMT-03:00 Brantone
> > :
> >
> > I'm guessing part of what you're seeing is
> > mentioned
> > here:
> https://github.com/jenkinsci/slack-plugin/issues/51
> >
> > Have you verified your configs in the Manage
> > Jenkins > Configure System > Global Slack
> > Notifier Settings  ?
> >
> > I've found that that's a better test of
> > configuration and values stick better when
> > individual jobs use them.
> >
> >
> > On Thursday, 26 March 2015 11:59:09 UTC-7,
> >

Git Plugin: updated password now cannot connect to repo

[Jim Klo]

Hi, 

Over the last few days my password used for Jenkins' Git Plugin expired, of 
which I promptly updated in Jenkins.

Unfortunately, even with the correct password (which uses the same special 
characters as the previous password) it won't authenticate, and there 
doesn't seem to be any other error that what I captured in the attached 
screen grab.
The same credentials work with Jenkins SVN Plugin, noting that our SCM uses 
LDAP.  I can switch to another user's credentials and it work fine, but I 
cannot seem to get the original login to work.

Not sure what I'm doing wrong.  Is this a bug?  Is there a workaround?  It 
seems like to me like Git might caching credentials globally, but not sure.

-- 
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/90f66c85-97f7-4c24-81ad-acd8210efe62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slack Plugin doesn't notify channel

[Brenton]

So who wants to write up a PR? :)

On 13 January 2016 at 21:47, Mike Meluso  wrote:

> Yes I agree, it should be added to the instructions. I'm glad I found this
> thread or I would've given up.
>
> On Monday, March 30, 2015 at 4:31:34 PM UTC-4, Brantone wrote:
>>
>> Agreed would be handy ... even anything at this point since it's pretty
>> scarce.
>> It does seem slightly counter-intuitive that a Post-build action would be
>> required for something that could send a notification before it even builds
>> ... but, there ya have it.
>>
>> On 30 March 2015 at 13:23, Hugo M  wrote:
>>
>>> Wow! I didn't know that I should add it as a post-build action. It
>>> worked like a charm. Thanks!!
>>>
>>> Maybe this should be added to "Jenkins Instructions" section of the repo
>>> README?
>>>
>>>
>>> [image: Hugo Massaroli on about.me]
>>>
>>> Hugo Massaroli
>>> about.me/hugo.massaroli
>>>   
>>>
>>> 2015-03-30 14:27 GMT-03:00 Brenton Bartel :
>>>
 No other dependency as far as I'm aware. Have you added Slack as a
 post-build action and checked off necessary options in the job itself?


 On 30 March 2015 at 10:13, Hugo M  wrote:

> Another discovery, when I press "Test connection" I see things
> happening in the jenkins.log. But If I start a job, or if that job fails
> (job configured with Slack plugin), nothing appears on the log (nothing
> related with Slack plugin).
>
> Does Slack plugin has a dependency on another plugin? It seems that is
> simply not triggering the post when a job start / fail / etc.
>
>
> [image: Hugo Massaroli on about.me]
>
> Hugo Massaroli
> about.me/hugo.massaroli
>   
>
> 2015-03-30 10:10 GMT-03:00 Hugo M :
>
>  Hi Brantone, thanks for your answer.
>>
>> Both "Test connection" in job configuration and in Global Settings
>> work in the sense that a message is posted on Jenkins: "Slack/Jenkins
>> plugin: you're all set."
>>
>> If I put wrong data there I get "Success" too but no message is
>> posted, and I can see errors in the Jenkins log.
>>
>> My problem is that I'm not getting the notifications from the jobs
>> anyway.
>>
>> Maybe this is related with the fact that I'm using a private channel?
>> But I can see the Jenkins message even if it's a private channel, so it
>> souldn't be an issue.
>>
>>
>>
>>
>> [image: Hugo Massaroli on about.me]
>>
>> Hugo Massaroli
>> about.me/hugo.massaroli
>>   
>>
>> 2015-03-30 4:46 GMT-03:00 Brantone :
>>
>> I'm guessing part of what you're seeing is mentioned here:
>>> https://github.com/jenkinsci/slack-plugin/issues/51
>>>
>>> Have you verified your configs in the Manage Jenkins > Configure
>>> System > Global Slack Notifier Settings  ?
>>>
>>> I've found that that's a better test of configuration and values
>>> stick better when individual jobs use them.
>>>
>>>
>>> On Thursday, 26 March 2015 11:59:09 UTC-7, Hugo M wrote:

 Hello, I'm using: https://wiki.jenkins-ci.org/
 display/JENKINS/Slack+Plugin

 Version: 1.7
 Jenkins: 1.6

 I'm not getting the notifications even if I set all the
 notifications options in "Advanced options", BUT I'm getting the 
 "Slack/Jenkins
 plugin: you're all set." message in my Slack channel the first time I
 configure it. So it's able to connect to Slack, but it doesn't notify 
 when
 the job starts, ends, etc.

 Another issue: when I press on "Test Connection" I get success no
 mather what I put on the configuration (url, channel, etc.).

>>> --
>>> You received this message because you are subscribed to a topic in
>>> the Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-users/9rl3I3DAiOg/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/d31028bb-66e7-4b73-83bc-99c78e06cc9a%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> 

Re: Slack Plugin doesn't notify channel

[Christopher Orr]

Feel free to just add documentation to the wiki page (as it suggests you
do), since that's the place most people will look for information:
https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin says

Regards,
Chris


On 14/01/16 19:28, Brenton wrote:
> So who wants to write up a PR? :)
> 
> On 13 January 2016 at 21:47, Mike Meluso  > wrote:
> 
> Yes I agree, it should be added to the instructions. I'm glad I
> found this thread or I would've given up.
> 
> On Monday, March 30, 2015 at 4:31:34 PM UTC-4, Brantone wrote:
> 
> Agreed would be handy ... even anything at this point since it's
> pretty scarce.
> It does seem slightly counter-intuitive that a Post-build action
> would be required for something that could send a notification
> before it even builds ... but, there ya have it.
> 
> On 30 March 2015 at 13:23, Hugo M  wrote:
> 
> Wow! I didn't know that I should add it as a post-build
> action. It worked like a charm. Thanks!!
> 
> Maybe this should be added to "Jenkins Instructions" section
> of the repo README?
> 
>  
> Hugo Massaroli on about.me
>   
> Hugo Massaroli
> about.me/hugo.massaroli
>  
> 
> 
> 
> 2015-03-30 14:27 GMT-03:00 Brenton Bartel :
> 
> No other dependency as far as I'm aware. Have you added
> Slack as a post-build action and checked off necessary
> options in the job itself?
> 
> 
> On 30 March 2015 at 10:13, Hugo M  wrote:
> 
> Another discovery, when I press "Test connection" I
> see things happening in the jenkins.log. But If I
> start a job, or if that job fails (job configured
> with Slack plugin), nothing appears on the log
> (nothing related with Slack plugin).
> 
> Does Slack plugin has a dependency on another
> plugin? It seems that is simply not triggering the
> post when a job start / fail / etc.
> 
>  
> Hugo Massaroli on about.me
>   
> Hugo Massaroli
> about.me/hugo.massaroli
>  
> 
> 
> 
> 2015-03-30 10:10 GMT-03:00 Hugo M :
> 
>  Hi Brantone, thanks for your answer.
> 
> Both "Test connection" in job configuration and
> in Global Settings work in the sense that a
> message is posted on Jenkins: "Slack/Jenkins
> plugin: you're all set."
> 
> If I put wrong data there I get "Success" too
> but no message is posted, and I can see errors
> in the Jenkins log.
> 
> My problem is that I'm not getting the
> notifications from the jobs anyway.
> 
> Maybe this is related with the fact that I'm
> using a private channel? But I can see the
> Jenkins message even if it's a private channel,
> so it souldn't be an issue.
> 
> 
> 
>  
> Hugo Massaroli on about.me
>   
> Hugo Massaroli
> about.me/hugo.massaroli
>  
> 
> 
> 
> 2015-03-30 4:46 GMT-03:00 Brantone
> :
> 
> I'm guessing part of what you're seeing is
> mentioned
> here: 
> https://github.com/jenkinsci/slack-plugin/issues/51
> 
> Have you verified your configs in the Manage
> Jenkins > Configure System > Global Slack
> Notifier Settings  ?
> 
> I've found that that's a better test of
> configuration and values stick better when
> individual jobs use them.
> 
> 
> On Thursday, 26 March 2015 11:59:09 UTC-7,
> Hugo M wrote:
> 
> Hello, I'm using:
> 
> https://wiki.jenkins-ci.org/__display/JENKINS/Slack+Plugin
> 
> 

Re: PeriodicWork not running periodically

[Christopher Orr]

On 14/01/16 21:30, Kevin wrote:
> Hi all, I've got some custom cloud providers that don't seem to get
> triggered, I've traced it back to NodeProvisionerInvoker not being
> called (even after 30 minutes of waiting), I can call the
> nodeProvisioners by hand (using the update function) in the same way
> that the NodeProvisionerInvoker does in the groovy script console and
> things seem to work.  Actually it seems like a number of bits related to
> PeriodicWork classes aren't working since I assume git polling and the
> periodic build setting are a PeriodicWork things, but they're also not
> triggering.
> 
> I did also look at PeriodicWork.all().collect {it.class.name}
> and println jenkins.util.Timer.get() and got:
> 
> hudson.diagnosis.HudsonHomeDiskUsageChecker,
> hudson.diagnosis.MemoryUsageMonitor,
> hudson.model.FingerprintCleanupThread,
> hudson.model.LoadStatistics$LoadStatisticsUpdater,
> hudson.model.WorkspaceCleanupThread,
> hudson.slaves.ComputerRetentionWork,
> hudson.slaves.ConnectionActivityMonitor,
> hudson.slaves.NodeProvisioner$NodeProvisionerInvoker,
> hudson.triggers.Trigger$Cron,
> jenkins.model.DownloadSettings$DailyCheck,
> org.jenkinsci.plugins.periodicreincarnation.PeriodicReincarnation]
> 
> 
> and 
> 
> jenkins.util.ErrorLoggingScheduledThreadPoolExecutor@6d72bb0e[Running,
> pool size = 10, active threads = 10, queued tasks = 2521, completed
> tasks = 1134830]

If the number of active threads remains equal to the pool size, then I
would guess that some tasks are getting stuck.

Can you see a bunch of timer-related or otherwise suspicious-looking
tasks running if you go to /threadDump on your Jenkins instance?

Regards,
Chris

-- 
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/56980F9F.2030009%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

PeriodicWork not running periodically

[Kevin]

Hi all, I've got some custom cloud providers that don't seem to get 
triggered, I've traced it back to NodeProvisionerInvoker not being called 
(even after 30 minutes of waiting), I can call the nodeProvisioners by hand 
(using the update function) in the same way that the NodeProvisionerInvoker 
does in the groovy script console and things seem to work.  Actually it 
seems like a number of bits related to PeriodicWork classes aren't working 
since I assume git polling and the periodic build setting are a 
PeriodicWork things, but they're also not triggering.

I did also look at PeriodicWork.all().collect {it.class.name} and println 
jenkins.util.Timer.get() and got:

hudson.diagnosis.HudsonHomeDiskUsageChecker, 
hudson.diagnosis.MemoryUsageMonitor, hudson.model.FingerprintCleanupThread, 
hudson.model.LoadStatistics$LoadStatisticsUpdater, 
hudson.model.WorkspaceCleanupThread, hudson.slaves.ComputerRetentionWork, 
hudson.slaves.ConnectionActivityMonitor, 
hudson.slaves.NodeProvisioner$NodeProvisionerInvoker, 
hudson.triggers.Trigger$Cron, jenkins.model.DownloadSettings$DailyCheck, 
org.jenkinsci.plugins.periodicreincarnation.PeriodicReincarnation]


and 

jenkins.util.ErrorLoggingScheduledThreadPoolExecutor@6d72bb0e[Running, pool 
size = 10, active threads = 10, queued tasks = 2521, completed tasks = 
1134830]


respectively.  Anyways does anyone have any idea what might make periodic 
work items decide to no longer run?  Is there any way to restart this thing 
without rebooting Jenkins?

I'm using the latest Jenkins now, but was using a Jenkins from ~November 
and also had this issue crop up recently (after having run on that version 
without encountering this issue for a couple months)

Thanks in advance.
-Kevin

-- 
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/c9270830-8c0a-4623-95d7-eac10b9d426c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue while installing Jenkins plugin nodelabelparameter

[Eric Pyle]

It looks like you don't have installed the token-macro and jquery 
plugins, or perhaps not the right versions.


On 1/14/2016 3:36 AM, Tatzagata wrote:

Caused by: java.io.IOException: Dependency token-macro (1.11), jquery (1.7.2-1) 
doesn't exist
at 
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:533)
at hudson.PluginManager.dynamicLoad(PluginManager.java:477)
... 6 more


--
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/5697B803.1020006%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.