Folks;
we use Jenkins all along with a local Apache Archiva maven repository to
build maven projects. There's a dedicated user for Jenkins to access the
repository and download (and deploy) artifacts. The user has all the
required permissions, but I fail to set up maven in Jenkins to work with
I auto-generate a bunch of build jobs and build pipeline views with the Job
Generator plugin and the Job DSL plugin. My jobs use the Conditional Build
Step plugin and can launch sub-jobs depending on runtime conditions. For
instance, if we find a smoke test defined in the source at runtime,
Checkout this blog entry
http://www.adam-bien.com/roller/abien/entry/how_to_fix_the_libs
On Dec 11, 2014 4:55 PM, Scott Genevish sc...@genevish.org wrote:
I’m trying to build a NetBeans project in Jenkins. I have added these
lines to the Properties of the “Invoke Ant” build step:
Hi.
You can use EBS on the EC2 slaves and choose the stop instead of terminate
for non spot instances.
It depends on what in the workspace you can to keep as there are a number
of publishers which save things back to the master.
--
You received this message because you are subscribed to the
As far as I can tell, if I am using the built in project based security, I
*HAVE
*to give users overall read permissions, then in the security for a
particular project, I can modify the settings? This seems really dumb. What
I want to do is have a Demo user, who can see nothing but the
Overall/Read does not give them access to any project (just Jenkins itself). So
give the demo user 'Overall/Read' globally, as well as 'Job/Read' (or just
'Read') for the specific projects. Do not give them 'Job/Read' globally.
The only thing missing is that they don't automatically have access
I feel I am missing something obvious here. I have a test bed Jenkins
server v 1.592 with workflow 1.0 plugins installed, this includes the
Workflow: Global Shared Library for CPS workflow plugin. All the workflow
plugins are installed and enabled.
Given that, attempting to do *git clone
The only thing missing is that they don't automatically have access to
newly created projects, which seems a very unusual requirement (and
surprising to your users?).
Sorry, this was unclear. This is what I'm currently seeing (Demo user is
seeing new projects), but *not *what I want. I'll look
Hi, I have a Jenkins freestyle job that is creating a new workspace each
time I run it. Each workspace is named workspace@number. I am not sure
how to eliminate this procedure as I have trying to attach a file from the
original workspace and it is not possible when it build in a new workspace
each
That form of workspace naming is typically used by Jenkins when more than
one build of the same job is running at the same time. If you've enabled
concurrent builds for that job, then you may see workspace names with
numbers appended.
Mark Waite
On Fri, Dec 12, 2014 at 4:35 PM, Leah
This should only happen if you configured the job to run multiple builds in
parallel.
If that's not the case:
0. Make sure Jenkins is up to date. This one should be really obvious. If
you're on 1.560 or lower, this may be JENKINS-21622.
1. Check the system log at the URL /log/all to see
Check and see if you have allowed concurrent builds on this job. That's
what Jenkins will do to avoid workspace collisions with concurrent builds.
Eric
On Dec 12, 2014 6:35 PM, Leah l...@wolfssl.com wrote:
Hi, I have a Jenkins freestyle job that is creating a new workspace each
time I run it.
Hello,
I have git repository which contains just property files, around 30, I
would like to kick start same parametrized jobs for 30 times passing each
of these different property files.
Is there an easy way other than adding the triggers manually ?
Thanks,
Manesh
--
You received this
Hello,
I have used schedule plugin to schedule around 35 jobs at 7 PM this
evening. Job gets started fine, but though I have around 16 executors
between two build servers for execution job got assigned to only only build
server and executing jobs in sequential order.
Is there anything I
14 matches
Mail list logo
