Re: Slack Plugin doesn't notify channel

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

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

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, Brant

Re: Slack Plugin doesn't notify channel

i > 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? &

Re: Slack Plugin doesn't notify channel

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 jo

Re: Expanding Parameters when triggering Jobs

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

Re: Expanding Parameters when triggering Jobs

"${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

Re: Release notes from XX previous build change logs in Markdown

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