Although Job DSL scripts work as long as there are no configure blocks,
I haven't been able to get a single configure block to work, including
verbatim examples from the docs. In particular, I've tried the Git
example from the "Real World Examples" at
https://github.com/jenkinsci/job-dsl-plugin/wik
On 13-01-12 09:52 AM, uma shankar wrote:
>
> Summarize the question: I actually want to add group of user who will be
> admin, Other than that, if any user try to login, they should still be
> able to login (if authentication is success via LDAP) but they should only
> have build trigger and r
I'm hoping this won't result in a whole load of flames but instead might
hit a few interested Jenkins users, like myself, who monitor their CI
builds from a Mac.
I've just released an app for the Mac (on the Mac App Store) which does
just that:
https://itunes.apple.com/gb/app/jenkins-notifie
Hi Brian,
I have exactly the same situation and am trying to understand if we yet
have a solution to solve this issue -
My situation is -
Project 1 is dependent on artifacts from Project 2 & Project 3.
Project 2 is dependent on artifacts from Project 3.
Project 3 is independent.
1) When a com
Hi Michael,
I have a similar situation but a little more complex, am curious to know if
you found a solution which I could utilize for my case.
Project 1 is dependent on artifacts from Project 2 & Project 3.
Project 2 is dependent on artifacts from Project 3.
Project 3 is independent.
1) When a
On Sat, Jan 12, 2013 at 1:59 AM, Vincent Latombe
wrote:
> Note that matrix job would work but you would need to maintain a static list
> of nodes. Also, if one node gets stuck (or offline) it would block further
> executions because the 'master' build would never end. My solution is more
> flexib
We have enabled LDAP authentication. At my organization, we have 500+ of
developer and 1000+ applications. We don’t want to take a burden of adding
all the user to Jenkins and provide project wise authorization.
Below are my requirement, if possible by using any of plugin or
configuration
I can't point you at any docs, but I've setup email-ext like I do for
regular jobs and I get one email for each multi-config job and one for the
overall job. I changed the template to put the logs in my email-ext emails
and each email contains the logs. I haven't tried putting test results in
the e
We also ended up generally saving all metadata (system/environment
variables, jenkins parameters, and build properties etc) into properties
file and archieve them. This approach simplifies/works around many problems
we had. Now every build has its metadata archived, for downstream jobs or
later ref
