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
>>>   <http://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
>>>>>   <http://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
>>>>>>   <http://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
>>>>

Re: [workflow-plugin] ClassCastException on brand new project

[Brenton]

Well I'll be a monkey's uncle ...
https://issues.jenkins-ci.org/browse/JENKINS-29295 was created a few days
prior to my email, and updated just the day before,  welp, there we go.
Thanks Jesse.

On 12 August 2015 at 14:06, Jesse Glick  wrote:

> On Thursday, July 23, 2015 at 2:07:24 AM UTC-4, Brantone wrote:
>>
>> what am I doing wrong?
>>
>
> Using the Build Blocker plugin, which apparently makes a “blind cast”
> that now fails. Report a bug for that plugin, add the `workflow` label.
>
> --
> 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/HT1XEzfFs_E/unsubscribe.
> To unsubscribe from this group and all its topics, 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/0e011390-451c-4f8f-8cc5-8fb027441d6e%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/CAD4EsfFsRTPLOixS6-WiuvyH73iYB8pgZe7xcXtf5xu%3DziuWUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slack Plugin doesn't notify channel

[Brenton Bartel]

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
> <http://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
>>> <http://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
>>>> <http://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 u

Re: Slack Plugin doesn't notify channel

[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-users+unsubscr...@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
> https://groups.google.com/d/topic/jenkinsci-users/9rl3I3DAiOg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CACDvQTqos_gDVBKwNfx0NLt1pZwxmZ3vjpGLthm%2B-3_h_imL8Q%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/CAD4EsfG1AnzC1at5z51eJ%2BG5wAftB453A9JQAKgtQYtdswS2NA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Expanding Parameters when triggering Jobs

[Brenton Bartel]

Yeah, that's what I was hoping to avoid.
Simply choosing "Use Current Parameters", and have it auto-magically
include the evaluated value ... which is not feasible, so I'm trying to do
something it's not meant to do. Hence, thread closed ;)

On 19 September 2014 02:13, Jan Seidel  wrote:

>
> 
> Ah, I got your point :)
> use the "Predefined parameters" opton. Then the variables will expand.
> See picture attached
>
> Am Dienstag, 16. September 2014 03:21:03 UTC+2 schrieb Brantone:
>>
>> Perhaps just not using the right terms to look for an answer as I'm
>> thinking this isn't crazy unique.
>>
>> So "Job A" triggers "Job B".
>>
>> Job A has a parameter called PROJECT_PATH, whose value =
>> "${WORKSPACE}/project/trunk/".
>>
>> When triggering Job B choosing "Current Build Parameters", It passes it
>> straight as is, but I want it to expand on "${WORKSPACE}" so it actually
>> uses the value from Job A.
>>
>> Something simple I'm missing??
>>
>  --
> 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/xgx3snzEgsI/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Expanding Parameters when triggering Jobs

[Brenton Bartel]

"${WORKSPACE}" was a poor example ... how about "${SOME_RANDOM_FOLDER}" ..
the point was, when param goes to get passed, it doesn't evaluate any
nested parameters, just passes it straight text.

On 19 September 2014 00:46, Jan Seidel  wrote:

> ${WORKSPACE} is dynamic.
> Job A and job B have their own defined workspace and will use different
> values.
> If you want job B to use the same you could pass the value as parameter
> like:
>
> ALT_WORKSPACE=${WORKSPACE}
>
>
> Am Dienstag, 16. September 2014 03:21:03 UTC+2 schrieb Brantone:
>>
>> Perhaps just not using the right terms to look for an answer as I'm
>> thinking this isn't crazy unique.
>>
>> So "Job A" triggers "Job B".
>>
>> Job A has a parameter called PROJECT_PATH, whose value =
>> "${WORKSPACE}/project/trunk/".
>>
>> When triggering Job B choosing "Current Build Parameters", It passes it
>> straight as is, but I want it to expand on "${WORKSPACE}" so it actually
>> uses the value from Job A.
>>
>> Something simple I'm missing??
>>
>  --
> 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/xgx3snzEgsI/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Release notes from XX previous build change logs in Markdown

[Brenton Bartel]

I thought HockeyApp already had the radio button to do that (or is it
broken?) ... This would still only put it in the current build, not
necessarily for span over build numbers, correct?
I'm thinking more simply xml -> MD converter/executor.



On 22 August 2014 18:01, Daniel Beck  wrote:

> Looks like JENKINS-12032, which I haven't yet begun work on. Feel free to
> take over.
>
> On 23.08.2014, at 02:46, Brantone  wrote:
>
> > Looking to publish release notes based on change logs from SCM commit
> messages .. and preferably in Markdown, but plain text will do ... alas,
> surprised no plugin exists (that I can find), so curious how others handle
> such a scenario, or else I guess I'm writing a plugin :)
> > I do have
> https://wiki.jenkins-ci.org/display/JENKINS/Changes+Since+Last+Success+Plugin
> ; however, formatting for that is machine (html, xml, json), but nothing
> just plain text.
> > Quick scan of mailing list didn't reveal anything "ah ha!", so wondering
> if this is such a unique situation, or already solved and it's obvious I'm
> just not seeing it.
> >
> > 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.
> > 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
> https://groups.google.com/d/topic/jenkinsci-users/U4SReCE2tok/unsubscribe.
> To unsubscribe from this group and all its topics, 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.