up
--
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
Carlos,
This Plugin clearly doesn't work Please provide a detailed how to at
least rather on how this works.
This is turning out to be a complete waste of time.
Joe
On Monday, December 19, 2016 at 7:44:43 AM UTC, Carlos Sanchez wrote:
>
>
>
> On Tue, Dec 6, 2016, 22:37 Daniel Serodio >
>
Mark,
I cant use freestyle job for the simple reason that, what we are doing
would become a sort of best practice for many projects.
Gui based approach is, in my view, not a good way to share the best
practice.
I will check out multi branch pipeline. Thanks a lot
On Saturday, 28 January 2017
The freestyle job is a single job which would build each branch that
matches as part of that single job.
The multi-branch pipeline will automatically create a job per branch which
matches the wildcard and has a Jenkinsfile. That's where you ultimately
want to go.
Mark Waite
On Sat, Jan 28, 2017
Hi,
I tried to
follow https://gist.github.com/vdupain/832964527b4b8d7d4c648169dae8c656
without maven for a test php project in bitbucket team repository. It gives
me below error after sonarqube analysis stage.
Unable to process url:
http://localhost:9000/api/ce/task?id=AVnksRksMwjM7SNQESTh
A
Hi Mark, Indra,
If I use wildcard as a branch specifier then what would happen if there are
multiple matches?
I would like to know this because my requirement is take each branch and
then build each of them separately.
On Thursday, 26 January 2017 20:21:13 UTC+5:30, Indra Gunawan (ingunawa)
w
Thanks. I do have conceptual questions. I will continue that thread ...
On Saturday, 28 January 2017 10:35:09 UTC+5:30, Mark Waite wrote:
> Did you try the steps I described earlier?
> https://groups.google.com/d/msg/jenkinsci-users/jiwtA088sXc/BjL-X6DjCwAJ
>
> On Friday, January 27, 2017 at 9
> On 27.01.2017, at 19:26, Richard Ginga wrote:
>
> is there some over-riding style sheet at work here?
Check your browser's developer tools to see which rules apply, and why.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe f