Maybe it's a permissions issue. What authorization realm (e.g. 'Anyone can do
anything', 'Logged in users can do anything', ...) are you using?
On 16.11.2013, at 19:05, CLOSE Dave wrote:
>
> When others connect, they see omly the default view. I want everyone to see
> all the views automatica
Create your views from the main page not My Views and I think you should
get what you are after.
Richard.
On Sunday, November 17, 2013, CLOSE Dave wrote:
>
> When others connect, they see omly the default view. I want everyone to
> see all the views automatically. Possible?
>
> -Original Me
I too have exactly this issue on Solaris, I've tried 1.535, 1.537-9 and it is
the same with all.
Following suggestions from the actual issue log (18366) I added both JETTY_HOME
and redirected Java.io.tmpdir as a subdirectory and yet I still see the issue
mentioned above.
--
You received thi
When others connect, they see omly the default view. I want everyone to see all
the views automatically. Possible?
-Original Message-
From: Vincent Latombe [mailto:vincent.lato...@gmail.com]
Sent: Friday, November 15, 2013 11:50 PM Pacific Standard Time
To: Jenkins Users
Subject
The next version of email-ext should allow concurrent executions, it will
just put a warning in the build log if you are trying to use content that
doesn't make sense with concurrent builds.
On Fri, Nov 15, 2013 at 11:43 AM, Jeremy Morton wrote:
> Email notifications at the end of Job2 are one o
That is the standard Jenkins behaviour. You'll notice the same without the
build-flow plugin.
On Friday, 15 November 2013 17:12:59 UTC, Zofia Majenka wrote:
>
> Hi,
>
> We are using the Build Flow Plugin in Jenkins. This is scenario:
>
> Start the flow 1: Job1 -> Job2 -> Job3
>
> Start the
Hey,
Sorry for the late reply, i've been suprisingly busy for a while!
I use this plugin:
https://wiki.jenkins-ci.org/display/JENKINS/MSBuild+Plugin
it has dropdown lists to build a project, though you can only add one
project to the list at a time, so you have to create many entries in the
b
Hi there,
I'm fairly new to Jenkins and CI, my company has dipped a very pragmatic
toe into the CI water so far. We're looking at investing in updates to a
very old and creaky build system, a mixture of C#, legacy c++ and other
bits and pieces (some ruby and perl etc). I'm trying to plan out a
