Re: Cloud slaves not being started by Jenkins
we found the latest jenkins and docker plugin work better together. Older versions would not always fire up a slave when they where supposed to - or fired up the wrong slave type! if you can upgrade to the next soon to be stable LTS and give it a go you may find it works better. On Tuesday, 14 October 2014 21:48:15 UTC+1, Richard Bywater wrote: How long have you waited for it to start a new node? I've found it can take quite a while (minutes) which apparently is caused by https://issues.jenkins-ci.org/browse/JENKINS-24752. Not sure if thats the case in your instance though. If you have a label which only contains docker providers does it work? Richard. On Wed, Oct 15, 2014 at 1:10 AM, Daniel Laird daniel@googlemail.com javascript: wrote: All, I am using the docker-plugin and provisioning containers as I require them. I am using the latest LTS Jenkins release. I have some non cloud based slaves with a label of ubuntu_12.04 and I also use this label for the docker containers. If I take all the non-cloud slaves offline (which is my goal). Then Jenkins fails to launch a slave on the cloud. I get lots of debug suggesting that there is a need for a slave: Current time: Oct 14, 2014 1:07:52 PM BST. Next execution (DIFF) in 24,780 seconds which is Oct 14, 2014 8:00:52 PM BST Oct 14, 2014 1:07:55 PM FINE hudson.slaves.NodeProvisioner Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.3694,idle=0.00,total=0m,=0.5) Oct 14, 2014 1:08:05 PM FINE hudson.slaves.NodeProvisioner Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.4326,idle=0.00,total=0m,=0.5) Oct 14, 2014 1:08:15 PM FINE hudson.slaves.NodeProvisioner Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.489,idle=0.00,total=0m,=0.5) Oct 14, 2014 1:08:25 PM FINE hudson.slaves.NodeProvisioner Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.5404,idle=0.00,total=0m,=0.5) Oct 14, 2014 1:08:35 PM FINE hudson.slaves.NodeProvisioner Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.5863,idle=0.00,total=0m,=0.5) I have enabled the following debug: com.nirima hudson.plugins hudson.slaves And I am getting no more useful debug. What do I have to do to get a Slave created? Is it a problem with the algorithm or the plugin? Hope you can help Dan -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Publish JUnit test result report
Hi, have you checked the time sync between the master and slave? you will get this when Jenkins found test results but they are older then when the build started (that is they did not come from this build but are remenants of a previous build) Regards /James On Monday, 13 October 2014 14:03:51 UTC+1, manasa a wrote: Hi, When am running build in jenkins, am getting following error. error: Test reports were found but none of them are new. Did tests run? Can anyone suggest a solution...THANKS IN ADVANCE -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Cucumber Test Result Plugin - It does not appear at my window the test results
There's a cent jiraComponent issue where jenkins gets confused if you have multiple test result types (both a Junit report and a cucumber report for example). I would argue that cucumber is a different tool to Junit and should be testing stuff built elsewhere so you should not have this mix in a single job (each jenkins job does a few smaller parts). -- 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. For more options, visit https://groups.google.com/d/optout.
Active Directory logins
If the other domain is trusted by the main domain then this should just work. If it is not trusted the you are very likely out of luck. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins API access to Build History
Best practice is to normally have each branch in a different job. Otherwise trends and linear history become a bit meaningless. It also solves your issue as you just use lastStable/api/… /James On Wednesday, 9 July 2014 08:54:31 UTC+1, sebastian.nickel wrote: Hi Darrel, thank you for your answer. I already feared that I have to do it this way :-) This means that I need to do multiple API calls until I found all the builds for my specific branch/tag. I hoped there is a method with doing only one API call and then search for the desired build. Cheers Nick On Tuesday, July 8, 2014 9:26:05 PM UTC+2, DarrelVun wrote: Nick: If you're using Git and Gerrit, then you can find the branch and sha1 under actions and parameters as name/value pairs, with name of GERRIT_BRANCH and GERRIT_PATCHSET_REVISION. I don't know of a way to find the specific build except to walk a project's builds until you find it. So, to be clear: - Start at http://*jenkins_url*/job/*project_name*/api/json?pretty=true - Find the array of builds, each element of which contains a key/value pair of url and the URL you need to visit - E.g. a build URL will look like http://*jenkins_url*/job/*project_name* /*build_number*/api/json?pretty=true - Look for actions - parameters - name == GERRIT_BRANCH I don't know of an easier way. Regards, Darrel V in NC On Tuesday, July 8, 2014 8:02:08 AM UTC-4, sebastian.nickel wrote: Heya, we are using jenkins in combination with capistrano to deploy the artifacts build by jenkins directly to our servers. To get the URL for an artifact we are trying to get the build number for a specific git branch/tag we build in jenkins (doing this with json API calls). We noticed that the API shows only one entry for a specific branch/tag (always the last one). Sometimes it is the case that the latest build failed, so we would like to deploy the last successful build of a specific branch/tag from git. Currently I would like to find the build number via the build history of jenkins, but it seems jenkins doesn't provide API access to the build history. Does anyone have an idea how to get the last successful build for a specific git branch/tag via the API? Cheers Nick -- 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. For more options, visit https://groups.google.com/d/optout.
Re: People using the LDAP plugin to connect to Active Directory
On Thursday, 22 May 2014 16:12:52 UTC+1, Stephen Connolly wrote:
OK, so there is now rumoured to be a faster and better way to look up the
groups that a user belongs to in the LDAP 1.10 plugin.
I say rumoured because due to the complexities of Active Directory server
configurations, one can never be quite sure until one has had a fair amount
of testing.
To that end, please could you set up a simple test Jenkins instance and
upgrade to ldap:1.10 and configure the `Parse user attribute for list of
groups` group membership strategy (again rumour has it that on Active
Directory the attribute `memberOf` is the magic attribute.
See if that ends up giving you the same JENKINS_URL/whoAmI list of groups
as when you have the `Search for groups containing user` set with the
filter being `(member:1.2.840.113556.1.4.1941:={0})`... though the `Parse
user attribute for list of groups` should be very very fast for login while
the `Search for groups containing user` could take *ages*.
it gives the same results as 1.8 - when used without the
LDAP_MATCHING_RULE_IN_CHAIN extension. (ie 'search groups containing user'
= (member={0}) )
using the above OID on large installations is not possible as single
queries take over 90 seconds and are culled by the AD server.
it is faster than 1.8 for the same results - but it sounds like you where
expecting recursive groups to be supported?
Respond back here with your findings so that I can remove the Red text on
the version history about this being a rumour
/James
--
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.
For more options, visit https://groups.google.com/d/optout.
Cucumber Test Result Plugin - It does not appear at my window the test results
If you mean the graph you need at least to runs before it will display. For the individual build you shoul have a Testresult link that will let you drill down into the results. If you don't have that can you share the end of your build log. -- 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. For more options, visit https://groups.google.com/d/optout.
Gerrit trigger troubleshooting
Have you checked that your Jenkins user has stream events on the grit instance that isn't triggering. -- 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. For more options, visit https://groups.google.com/d/optout.
People using the LDAP plugin to connect to Active Directory
I haven't tried that version but I already know that the ad specific LDAP_MATCHING_RULE_IN_CHAIN oid breaks very large installations. One LDAP query will take over 1.5 minutes and will be killed by the ad server. Last I looked using ad browser which was a few weeks my memberOf did not include groups that groups where members of so would give different results than you are expecting -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Where did the maven deploy plugin go?
It shows up for me as part of the standard maven plugin, under a post build action -- 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. For more options, visit https://groups.google.com/d/optout.
ldaps ignore cert errors
Is there a way to use the ldap plugin with ssl (ldaps) without having to setup full trust for the cert? I know what the issues with turning things off like this are - but at least it is marginally better than just sending username/password in cleartext. or to put it another way how to quickly avoid the dreaded javax.naming.CommunicationException: simple bind failed: myldap.myco.com [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] /James -- 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. For more options, visit https://groups.google.com/d/optout.
[ANN] build flow
Hi, Buildflow 0.11 is in the process of releasing and should hit the update center in a few hours. This version contains a significant intentional change that may affect you if you using functionality that was unintentionally exposed. The Flow is now a flyweight task and as such *has no workspace associated*with it and will execute on the master. If you are relying on this functionality then you should not upgrade without migrating the functionality you need to another job. /James -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] build flow
it's now (hopefully) marked as incompatible - (thanks for the pointer - got there before the release was deployed!) As it's not just a simple reconfig the announcement was still needed. On Tuesday, 8 April 2014 20:57:09 UTC+1, Daniel Beck wrote: Shouldn't this info be distributed using update center metadata? E.g.: https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions On 08.04.2014, at 21:52, teilo teilo+...@teilo.net javascript: wrote: Hi, Buildflow 0.11 is in the process of releasing and should hit the update center in a few hours. This version contains a significant intentional change that may affect you if you using functionality that was unintentionally exposed. The Flow is now a flyweight task and as such has no workspace associated with it and will execute on the master. If you are relying on this functionality then you should not upgrade without migrating the functionality you need to another job. /James -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: buildflow hang when cancelling queued builds
Hi Marc,
I ran out of time to get to the root of this - but I'm pretty sure it is an
issue in Jenkins core.
Looks like when a build is scheduled and waitForStart() is called it never
returns if the build is cancelled.
You may want to try with the latest and greatest Jenkins to check its been
fixed - if not raise an issue in JIRA against core and buildflow.
/James
On Friday, 4 April 2014 21:53:08 UTC+1, teilo wrote:
Reproduced the issue locally - but I think the root cause is Jenkins not
the plugin.
On Friday, 4 April 2014 19:04:34 UTC+1, Marc MacIntyre wrote:
The latest snapshot doesn't address this; it does abort running subjobs,
and dequeues those that have not started, but if a sub-job is manually
dequeued, the build flow never notices.
On Fri, Apr 4, 2014 at 1:39 AM, James Nord (jnord) jn...@cisco.comwrote:
I Changed the handling of cancel since the last release – so that it
actually kills the downstream projects as well (including those in the
queue).
Given that there is a good chance that this is fixed – if you feel brave
and want to try a snapshot.
/James
*From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com]
*On Behalf Of *Marc MacIntyre
*Sent:* 03 April 2014 23:21
*To:* jenkins...@googlegroups.com
*Subject:* buildflow hang when cancelling queued builds
I've noticed with the buildflow plugin, when I run parallel jobs and
cancel one of the runs of a job while it is still in the queue, the build
flow never completes.
To illustrate - assume that job1 won't run concurrently:
parallel(
{build(job1)},
{build(job1)},
)
if the 2nd run of job1 is aborted while still in the queue, the build
flow will never complete - it will schedule both jobs, and finish the first
one, but never realize the 2nd one has been cancelled.
Anyone seen this? Am I missing something?
On a related note; anyone have a good way to time out a build flow job?
--
Marc MacIntyre
--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Marc MacIntyre
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: buildflow hang when cancelling queued builds
Looks unrelated to me.
On Monday, 7 April 2014 17:36:11 UTC+1, Schalk Cronjé wrote:
It might be related to JENKINS-19656 (
https://issues.jenkins-ci.org/browse/JENKINS-19656).
On Friday, 4 April 2014 21:53:08 UTC+1, teilo wrote:
Reproduced the issue locally - but I think the root cause is Jenkins not
the plugin.
On Friday, 4 April 2014 19:04:34 UTC+1, Marc MacIntyre wrote:
The latest snapshot doesn't address this; it does abort running subjobs,
and dequeues those that have not started, but if a sub-job is manually
dequeued, the build flow never notices.
On Fri, Apr 4, 2014 at 1:39 AM, James Nord (jnord) jn...@cisco.comwrote:
I Changed the handling of cancel since the last release – so that it
actually kills the downstream projects as well (including those in the
queue).
Given that there is a good chance that this is fixed – if you feel
brave and want to try a snapshot.
/James
*From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com]
*On Behalf Of *Marc MacIntyre
*Sent:* 03 April 2014 23:21
*To:* jenkins...@googlegroups.com
*Subject:* buildflow hang when cancelling queued builds
I've noticed with the buildflow plugin, when I run parallel jobs and
cancel one of the runs of a job while it is still in the queue, the build
flow never completes.
To illustrate - assume that job1 won't run concurrently:
parallel(
{build(job1)},
{build(job1)},
)
if the 2nd run of job1 is aborted while still in the queue, the build
flow will never complete - it will schedule both jobs, and finish the
first
one, but never realize the 2nd one has been cancelled.
Anyone seen this? Am I missing something?
On a related note; anyone have a good way to time out a build flow job?
--
Marc MacIntyre
--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Marc MacIntyre
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
Hi Sascha, Fix is at https://github.com/jenkinsci/build-flow-plugin/pull/42 if you want to get the source and do a local build. Otherwise wait for the code to be accepted and either grab the latest build from Jenkins, or wait for the release. /James On Friday, 4 April 2014 08:36:24 UTC+1, Sascha Herrmann wrote: Thanks for your reply. Yes, using Fiddler, the last request I see before the error is a GET to http://server/job/job_name/descriptorByName/com.cloudbees.plugins.flow.BuildFlow/checkDsl?value=... with value being the encoded text of the DSL. The DSL itself is some 3900 characters. Then add the encoding overhead. The GET request is then some 6522 bytes. When you talk about a fix ... how would we get the fix? Will it go into the next plugin version? Sascha Am Mittwoch, 2. April 2014 22:36:57 UTC+2 schrieb teilo: Sounds like the flow is validating the dsl via a http get request. If the flow is large the http request will be too large for some severs to handle. This intern causes some headers to be lost on the server, to which jenkins will the think you are not authenticated and will clear your cookie... I don't see anything in the code to force it to use http post, but I'm away from my pc for a while so can't check and fix, should be a few lines to change if I am correct at the cause. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: buildflow hang when cancelling queued builds
Reproduced the issue locally - but I think the root cause is Jenkins not
the plugin.
On Friday, 4 April 2014 19:04:34 UTC+1, Marc MacIntyre wrote:
The latest snapshot doesn't address this; it does abort running subjobs,
and dequeues those that have not started, but if a sub-job is manually
dequeued, the build flow never notices.
On Fri, Apr 4, 2014 at 1:39 AM, James Nord (jnord)
jn...@cisco.comjavascript:
wrote:
I Changed the handling of cancel since the last release – so that it
actually kills the downstream projects as well (including those in the
queue).
Given that there is a good chance that this is fixed – if you feel brave
and want to try a snapshot.
/James
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *Marc MacIntyre
*Sent:* 03 April 2014 23:21
*To:* jenkins...@googlegroups.com javascript:
*Subject:* buildflow hang when cancelling queued builds
I've noticed with the buildflow plugin, when I run parallel jobs and
cancel one of the runs of a job while it is still in the queue, the build
flow never completes.
To illustrate - assume that job1 won't run concurrently:
parallel(
{build(job1)},
{build(job1)},
)
if the 2nd run of job1 is aborted while still in the queue, the build
flow will never complete - it will schedule both jobs, and finish the first
one, but never realize the 2nd one has been cancelled.
Anyone seen this? Am I missing something?
On a related note; anyone have a good way to time out a build flow job?
--
Marc MacIntyre
--
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-use...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout.
--
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-use...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout.
--
Marc MacIntyre
--
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.
For more options, visit https://groups.google.com/d/optout.
Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
Sounds like the flow is validating the dsl via a http get request. If the flow is large the http request will be too large for some severs to handle. This intern causes some headers to be lost on the server, to which jenkins will the think you are not authenticated and will clear your cookie... I don't see anything in the code to force it to use http post, but I'm away from my pc for a while so can't check and fix, should be a few lines to change if I am correct at the cause. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Block builds based on parameters
An alternative may be to look at the buildflow plugin (latest source code not latest release) and one of its extensions. If you move your pipeline to be managed by the flow - the flow can control which jobs are allowed to run concurrently (for the same flow) - and the actual jobs can run as many times as you want to allow manual triggering to deploy to random server X. This wouldn't prevent finger trouble where some user hit build now on the deploy job and deployed files to a SUT - but should work in the happy case. https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin /James On Tuesday, 25 March 2014 10:03:56 UTC, David Campos wrote: I figured out how to use the plugin (thanks documentation spread across forums...) but I think that it does not solve my problem. With this plugin I am able to queue the execution of a job but not based on conditionals. I would need to be able to set the category or filter through parameter injection so, when the desired blocking pipeline starts they can lock but not on manual triggers for example. Example: Parent project triggers deploy with category #1 - deploy #1 - Smoke #1 - Compat #1 Parent project triggers deploy with category #2 - deploy (locked by #1 pipeline) Manual trigger of deploy to server Y (OK) On Tuesday, March 25, 2014 10:41:53 AM UTC+1, David Campos wrote: Hi Marc, Being honest I do not know how to use that plugin... I was trying to set all projects into a category but I do not know how to do that... Any hint? On Thursday, March 20, 2014 5:11:48 PM UTC+1, Marc MacIntyre wrote: Will this solve your problem? https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin On Thu, Mar 20, 2014 at 5:17 AM, David Campos noymn.the...@gmail.comwrote: Hi all, I have a scenario that I am not able to solve without some downsides. I don't know if my workflow is currently supported or not so I search for your help. *Scenario:* *Compilation job:* Maven job that executes unit tests and creates deliverables *Deploy job:* Capistrano deployment that deploys deliverables to target machines based on eligible parameters (cd, testing, staging...) *Integration job:* Executes a smoke test using BDD. *BCT job:* Same as Integration but with customer tests and multiple browsers. *Process:* We have a build pipeline based on [compilation - deployment to server - execution of smoke tests (integration) - execution of compatibility tests] that has a step that takes too much time to complete (smoke test). Since deployments should not happen when tests are being executed (would break the compilation chain) we have decided to block deployment build until the downstream finishes... That's OK. *Problem:* Since deployment jobs are blocked by downstream, whenever an IT or BCT job is being executed deployment is forbidden, either to the affected machine or to any testing machine, so we can not perform deployments to testing scenarios for QA to test (an old build for example). *Possible solution:* My possible solution would be to block the execution of deployment *if and only if* the target machine is cd and smoke or BCT tests are being executed. I need a two factor check, one from parameters of the current build (easy) and another from downstream executors. I don't know if that is possible. If that scenario is possible... how can I implement it? Groovy? Can I mark a build as queued and allow other builds to go ahead (parallel builds maybe)? Thanks for the help. -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Marc MacIntyre -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Cannot write file to disk using the build Flow plugin
Depending on what state you want to store you should look at writing either an extension to the build flow, or a new plugin or a combination of both. The states I'd want to store are the polling status of the underlying subversion repository related to the job, No workspace so - this is a bit moot as you have nowhere to checkout and nowhere for jenkins to calculate the changes. However if you are checking out isn't the first thing to do something with that source code? This could either be an upstream job that then kicks the flow subsequently - in which case this information is already persisted and available for you - or its a job in the flow, in which case you can get the changes from that first job (although this would be somewhat harder to then visualize in Jenkins for the buildflow). and the archived job results collected from the sub-jobs. This is again already stored. The flow knows what runs it triggered. the runs know what their artifacts are. If you are wanting to see the artifacts of a flow in a central place to save some clicking - then some custom code is the way to go. Note - that the flow is not expected to be a groovy interpreter. It was written to perform job orchestration and as such being able to do groovy was a side effect that would be removed if it was possible. Indeed there is a severer open ticket to not run all groovy and to only allow a subset of commands to be run for security reasons. Things that you just expect every jenkins job to provide, and that have nothing to do with slave availability other than needing them temporarily before you can archive their artifacts. Sorry - archive artifacts is already handled by jenkins for the sub jobs. You are trying to bend the buildflow plugin to be something it was not intended to be. I don't understand the point of removing these things and then suggesting a plugin extension just to put them back. Firstly you are abusing somewhat the intention of buildflow The buildflow was designed (not by me) as a **coordinator ** of jobs, as such it should not need a workspace - nor should it need to consume an executor as it shouldn't be doing anything more complex than triggering builds based on some other build state in a give order. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Cannot write file to disk using the build Flow plugin
Hi Les, Firstly a workspace will never give you true stateless in Jenkins à workspace availability is best effort (slave may be unavailable, workspace may be deleted to reclaim slave disk space...) Depending on what state you want to store you should look at writing either an extension to the build flow, or a new plugin or a combination of both. /James -- 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. For more options, visit https://groups.google.com/d/optout.
Git plugin 2.0 with Gerrit Trigger plugin
2.0 was horribly broken for me with gerrit. 2.0.1 works fine. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Failed to parse Cucumber JSON with Cucumber json test reporting plugin
Which cucumber implementation (eg cucumber-jvm) and version are you running the tests with? Can you put the offending Jason online somewhere? It sounds like you have a step that is missing a resuilt , they should all have even if the step not run. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: compiling under java 1.6.0_71
If you don't need jdk auto install then try using maven toolchains. Then run the job with whatever jdk works for maven and Jenkins -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Can't configure jobs, display stuck at LOADING
Take a look in the server logs for any exceptions. I saw something similar when the jelly rendering of a plugin failed, the exception pointed me at the plugin which was ultimately caused by an upgrade failing leaving a mix of New and old plugin classes lying around. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins Enterprise from Cloudbees
On Tuesday, 21 January 2014 17:02:55 UTC, MoBarger wrote: Hi - just curious if anyone here has implemented JE. Yes - many have (including me) Can same functionality be achieved with free plugins instead of going with the paid versions that Cloudbees offers? No. Some of it can - but not all of it. The free plugins don't give you support backed by an SLA (which you can also pay for elsewhere). -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Semaphore system for matrix jobs
I know of a comercial (not free) plugin that does this - http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-label-throttled-build-execution-plugin.cb As a plugin exists, the answer to your second question about extension points is answered with a yes - but I'm not sure what they are. As always there are possibly other solutions to the same issue. /James On Monday, 20 January 2014 20:31:46 UTC, thorste...@knime.com wrote: Hi all, We have a product that we are currently testing on six different operating systems. Our test jobs is a matrix job that runs on six different slaves (one for each OS). However, the slaves are virtual machines on a single host computer. It has enough RAM and disk space for even more VMs, but only six cores. I.e. if all matrix subjobs run at the same time, the system will be overloaded. On the other hand, sequential execution just takes too long. We need a mechanism to control the maximum number of concurrent matrix subjobs that are allowed to run at the same time. I haven't found any plug-in that can achieve this. Ideally each slave can be assigned a semaphore (the physical host for the VM) that has a maximum value (the number of jobs that can run at the same time). Does anybody know a way to achieve this with available plug-ins? How difficult would it be to create such an extension? Cheers, Thorsten -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Securely obtain the Jenkins package and public key
On Sunday, 12 January 2014 22:20:17 UTC, Abhijith Chandrashekar wrote: Of course, you'd need a secure way to make sure it's actually his signature, but that should be easier than changing the entire distribution chain. That's exactly the problem. Any ideas on how I can do that? Thanks, Abhijith http://kohsuke.org/about/pgp/ But if you are that security paranoid then you should download the sources, inspect them (and the history) and then compile them yourself every release (like you do for all the plugins right!?). /James -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Securely obtain the Jenkins package and public key
an interesting target for attacks Jenkins security is a joke. You can find security issues without trying, even in core. And the process to resolve them seems to be really broken. Have you helped to improve this situation by actually reporting them via the proper channels? https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories /James -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Central Git Checkout
Sounds like you want a shallow clone rather than a full one. you have thus option on the git plugin for about a year. That way you won't have all of the history for the clone and hence less disk space and network traffic is required. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Gerrit Trigger generating large queue of jobs
For our commit build we use a change hook on Gerrit that notifies Jenkins, Then just use normal git setup with polling @yearly. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Experiences with LTS vs Bleeding edge
Issues won't get fixed as quickly as they need to be in a release for two weeks first. That said you are less likely to discover new issues - with the exception of a new major lts version, however that has an amount of testing which latest never has. If you are really concerned with bugs there are a few commercial vendors who will provide a support context, and I've been using one of them for a long time. I moved to lts a long time ago when I no longer need all the features that went into every release and things have been generally much more stable since -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to display archived maven artifacts on top level of job page rather than via modules subpage.
I believe thus is broken for jobs that use maven3 rather than maven 2. There is probably a jira issue already for it, off not you should probably raise one. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: build flow, early exit from parallel construct?
Take a look at src/test/groovy/com/cloudbees/plugins/flow/AbortTest.groovy
- this should say that it is possible to do what you want :-)
On Tuesday, 29 October 2013 02:43:19 UTC-4, asmundo wrote:
On Tue, Oct 29, 2013 at 4:16 AM, James Nord (jnord)
jn...@cisco.comjavascript:
wrote:
The changes I have put in to support this are not in a release version
of the buildflow – so you will need to download source and compile, or grab
it from the Jenkins ci instance.
I forgot to state that I am did this. Sorry about that. I am running:
* 305af7f Merge pull request #37 from mattiasbpersson/master
* build-flow-plugin:0.11-SNAPSHOT
I did very much like the groovy shell evaluation!
Asmund
** **
/James
** **
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *Åsmund Østvold
*Sent:* 28 October 2013 17:34
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Re: build flow, early exit from parallel construct?
** **
Thank you James,
** **
I finally freed up some time and was able do a new stab at this. I have
inlined some questions and feedback.
** **
On Fri, Oct 25, 2013 at 6:33 AM, James Nord (jnord)
jn...@cisco.comjavascript:
wrote:
KillRunningjobs is called internally if the flow is aborted (or one of
the jobs is aborted).
Internallyt this is handled by catching either (IIRC) a
JobAborteException (or also an IOException).
** **
I did search for 10 minutes for JobAborteException or something close
to this. But my Jenkins/Java knowledge is limite...
The IOException will show a stack trace in your console output – wheres
the jobAbortEx will just show “Aborted” (and the cause if you set one),**
**
** **
I did try the blow but was not able to abort flow job. Job 'pass' takes
20s and job 'fail' taks only 5s:
** **
parallel(
{ b = build(pass);
if (b.getResult() == Result.FAILURE) {
throw new java.io.IOException(foo)
} },
{ b = build( fail );
if (b.getResult() == Result.FAILURE) {
throw new java.io.IOException(foo)
}}
)
** **
Console output:
** **
** **
parallel {
Schedule job fail http://ao:8080/job/fail/
Schedule job pass http://ao:8080/job/pass/
Build fail #40 http://ao:8080/job/fail/40/ started
Build pass #33 http://ao:8080/job/pass/33/ started
fail #40 http://ao:8080/job/fail/40/ completed : FAILURE
pass #33 http://ao:8080/job/pass/33/ completed
}
** **
I am probably doing something wrong but I am not able to see it. Any
help would be appreciated.
So just throw one of those. I guess I should add this to the
extensions so you can just call ext.abortFlow(“Reason”) J
** **
With my limited understanding I believe this would be very good to have.
If you add this could you consider adding something like:
** **
ext.failFlow(“Reason”)
** **
It should do the same was for abortFlow(foo) but fail the build. For my
use case this would keep the overall status as if all the jobs in the
parallel section had finished. To also cover 'UNSTABLE' and 'SUCCESS' could
the generalisation be exposing something like:
** **
terminateFlow(Result r, String s)
** **
?
Also no need to check the string – check getResult() == Result.FAILURE
or getResult().isWorseOrEqual(Result.FAILURE)
** **
Thanks for this.
Asmund
** **
--
dyslectic
--
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-use...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/groups/opt_out.
--
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-use...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Branch-specific e-mail recipients?
Hi Chris, The best practice approach is to have a single job per branch. This not only solves your problem but your trend reports will then have some form of linear code progression contained within them rather than jumping all over the shop. So you are probably trying to fix something that isn't broken. As always though its code and there is probably a way this could work with the email-ext plugin and a pre-send that modifies the headers. /James On Friday, 25 October 2013 11:23:34 UTC-7, Chris Warren wrote: I've got a build job that will build any branch in a repository where new changes are seen. I'd like to let the users specify lists of e-mail recipients on a per-branch basis, so that the right people get news about their branch's build. My first thought was that this could be done with a config file in the source tree where users could edit their branch of the file to have the addresses they want, but I would prefer it if I could keep this configuration in Jenkins instead of in outside files. Is this a problem that other people run into, or am I trying to fix something that isn't broken? Thanks. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Using Build Flow to run a test using two machines
There is a commercial plugin from cloudbees that will allow you to do this with VMware. A single job can have multiple VMs assigned on which you can run commands like starting your server and then starting your client. There are possibly other ways but I have not used them. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: LDAP Configuration
The LDAP plugin is (at least it was before we unceremoniously ditched it)
MUCH MUCH quicker to authenticate users than the AD one when you have a
lovely large tree of domains…
Now I will prefix this with I am not an AD expert but…
http://technet.microsoft.com/en-us/library/cc728188(v=ws.10).aspx
The global catalog is a distributed data repository that contains a
searchable, partial representation of every object in every domain in a
multidomain Active Directory Domain Services (AD DS) forest. The global
catalog is stored on domain controllers that have been designated as global
catalog servers and is distributed through multimaster replication.
Searches that are directed to the global catalog are faster because they do
not involve referrals to different domain controllers.
I don’t notice any delay using the global catalogue and LDAP – using AD we
often saw multi second (into the tens) delays in authentication – the above
may or may not be the reason for it.
/James
On Tuesday, 15 October 2013 14:01:38 UTC+1, Stephen Connolly wrote:
Can we just ask one question:
WHY ARE YOU USING THE LDAP PLUGIN AND NOT THE ACTIVE DIRECTORY PLUGIN?
People seem to keep on wanting to inflict pain on themselves and go with
the more complex LDAP plugin rather than the much much easier to use Active
Directory plugin.
If there is some feature missing that causes you to decide to plump for
the LDAP plugin it would be good to know so that the feature could be added
to the Active Directory plugin.
On 15 October 2013 13:17, Ricardo García Fernández
ricard...@gmail.comjavascript:
wrote:
Hi Zac !
I was dealing with the same issue: authentication against LDAP/AD and
your answer was the right one.
Also, I fixed the group filter and configured group properties using this
filter:
Group search filter: ( (cn={0}) (objectclass=group) )
Group Search Base: your OU groups separated with comas (,).
Thus I can configure groups and users from general configuration to Job
one.
Thanks for your solution it was very helpful
El miércoles, 14 de diciembre de 2011 20:01:34 UTC+1, Zac Harvey escribió:
I am trying to set up Jenkins to authenticate using our AD domain over
LDAP. I have been working with the Systems Group trying to configure
all of the settings under Manage Jenkins Configure System Access
Control. We finally have all the settings configured correctly (at
least, in the eyes of the Systems people), and we are not getting any
red validation errors in the GUI. However I still cannot login via
LDAP/AD. Below is the console output. Any nudges in the right
direction are enormously appreciated!
Console Output:
Dec 14, 2011 1:47:21 PM
hudson.security.**AuthenticationProcessingFilter**2
onUnsuccessfulAuthentication
INFO: Login attempt failed
org.acegisecurity.**AuthenticationServiceException**:
LdapCallback;[LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; nested exception is javax.naming.**NameNotFoundException: [LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; remaining name 'dc=myproject,dc=com'; nested exception is
org.acegisecurity.ldap.**LdapDataAccessException: LdapCallback;[LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; nested exception is javax.naming.**NameNotFoundException: [LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; remaining name 'dc=myproject,dc=com'
at
org.acegisecurity.providers.**ldap.**LdapAuthenticationProvider.**
retrieveUser(**LdapAuthenticationProvider.**java:
238)
at
org.acegisecurity.providers.**dao.**AbstractUserDetailsAuthenticat**
ionProvider.authenticate(**AbstractUserDetailsAuthenticat**
ionProvider.java:
119)
at
org.acegisecurity.providers.**ProviderManager.**doAuthentication(**
ProviderManager.java:
195)
at
org.acegisecurity.**AbstractAuthenticationManager.**authenticate(**
AbstractAuthenticationManager.**java:
45)
at
org.acegisecurity.ui.webapp.**AuthenticationProcessingFilter**
.attemptAuthentication(**AuthenticationProcessingFilter**.java:
71)
at
org.acegisecurity.ui.**AbstractProcessingFilter.**doFilter(**
AbstractProcessingFilter.java:
252)
at hudson.security.**ChainedServletFilter
$1.doFilter(**ChainedServletFilter.java:87)
at
org.acegisecurity.ui.**basicauth.**BasicProcessingFilter.**doFilter(**
BasicProcessingFilter.java:
173)
at hudson.security.**ChainedServletFilter
$1.doFilter(**ChainedServletFilter.java:87)
at jenkins.security.**ApiTokenFilter.doFilter(**
ApiTokenFilter.java:61)
at hudson.security.**ChainedServletFilter
Re: LDAP Configuration
Hi Stephen,
I will see what I can do, but can't promise a quick turnaround (I need to
get a fair amount done before the JUC next week)
This may have something to do with the location of the main servers for the
domain.
e.g.
nslookup -q=SRV _ldap._tcp.mydomain.com
returns servers that are not located in the same site as Jenkins (indeed
some are on the other side of the globe and all have the same weight!).
The AD plugin does multiple queries as it recursively checks for group
membership (a change that I did - so you can slap me with a wet fish for
that). This was to support if you are a member of group Y and group Y is a
member of Jenkins_Admins then you will correctly be identified as a user
with ROLE_jenkins_admin.
pings to the server in the other side of the world are 72ms...
pings to my local global catalogue server - well that's 1 ms :-)
now you can imagine if each query took just a round trip time that 100
queries (lot of groups in large companies.) that that would be 100 * 72ms
which is about 7 seconds, compared to a not noticeable 0.1s.
(NB: slight correction below).
/James
On Tuesday, 15 October 2013 15:32:14 UTC+1, Stephen Connolly wrote:
James, would you be amenable to firing up a test jenkins and giving some
comparative timings?
At least in Unix mode they should be pretty much identical in performance,
though theAD plugin should be much easier to configure
On 15 October 2013 14:47, teilo teilo+...@teilo.net javascript: wrote:
The LDAP plugin is (at least it was when we unceremoniously ditched the
AD plugin) MUCH MUCH quicker to authenticate users than the AD one when you
have a lovely large tree of domains…
** **Now I will prefix this with I am not an AD expert but…
** **http://technet.microsoft.com/en-us/library/cc728188(v=ws.10).aspx
** **The global catalog is a distributed data repository that contains
a searchable, partial representation of every object in every domain in a
multidomain Active Directory Domain Services (AD DS) forest. The global
catalog is stored on domain controllers that have been designated as global
catalog servers and is distributed through multimaster replication.
Searches that are directed to the global catalog are faster because they do
not involve referrals to different domain controllers.
** **I don’t notice any delay using the global catalogue and LDAP –
using AD we often saw multi second (into the tens) delays in authentication
– the above may or may not be the reason for it.
** **/James
On Tuesday, 15 October 2013 14:01:38 UTC+1, Stephen Connolly wrote:
Can we just ask one question:
WHY ARE YOU USING THE LDAP PLUGIN AND NOT THE ACTIVE DIRECTORY PLUGIN?
People seem to keep on wanting to inflict pain on themselves and go with
the more complex LDAP plugin rather than the much much easier to use Active
Directory plugin.
If there is some feature missing that causes you to decide to plump for
the LDAP plugin it would be good to know so that the feature could be added
to the Active Directory plugin.
On 15 October 2013 13:17, Ricardo García Fernández
ricard...@gmail.comwrote:
Hi Zac !
I was dealing with the same issue: authentication against LDAP/AD and
your answer was the right one.
Also, I fixed the group filter and configured group properties using
this filter:
Group search filter: ( (cn={0}) (objectclass=group) )
Group Search Base: your OU groups separated with comas (,).
Thus I can configure groups and users from general configuration to Job
one.
Thanks for your solution it was very helpful
El miércoles, 14 de diciembre de 2011 20:01:34 UTC+1, Zac Harvey
escribió:
I am trying to set up Jenkins to authenticate using our AD domain over
LDAP. I have been working with the Systems Group trying to configure
all of the settings under Manage Jenkins Configure System Access
Control. We finally have all the settings configured correctly (at
least, in the eyes of the Systems people), and we are not getting any
red validation errors in the GUI. However I still cannot login via
LDAP/AD. Below is the console output. Any nudges in the right
direction are enormously appreciated!
Console Output:
Dec 14, 2011 1:47:21 PM
hudson.security.**Authentication**ProcessingFilter**2
onUnsuccessfulAuthentication
INFO: Login attempt failed
org.acegisecurity.**Authenticati**onServiceException**:
LdapCallback;[LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; nested exception is javax.naming.**NameNotFoundExcep**tion: [LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
(NO_OBJECT), data 0, best match of:
'DC=MYPROJECT,DC=COM'
]; remaining name 'dc=myproject,dc=com'; nested exception is
org.acegisecurity.ldap.**LdapDat**aAccessException:
LdapCallback;[LDAP:
error code 32 - 208D: NameErr: DSID-031001E4, problem 2001
Re: Jenkins kick of all the builds after restarting the service
This sounds like you have slaves as well as polling the SCM. Which is pretty much a bit of a side effect, as the polling will kick off potentially before the slaves are available - so the last known revision is not available (its in the workspace) and so a new build is kicked off to get the revision. You should be able to confirm this in the actual SCM polling log (not sure I remember where they are as we moved to push notification from SVN Gerrit) and this problem went away! Alternativley depending on your SCM there may be some options that will make polling happen on the master (Git certainly has an option to do this IIRC its called - fast repote polling) /James On Thursday, 26 September 2013 18:39:04 UTC+1, Maneesh M P wrote: In our project we have observed that whenever we restart the jenkins service, it kicks of all the builds even though builds are configured using SCM polling. is this an expected behavior ? Can someone tell me a solution if it is not an expected behavior ? Thanks, Maneesh -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins Build node CentOS 6.4
On Wednesday, 25 September 2013 14:49:05 UTC+1, flex...@googlemail.com wrote: Hi teilo, I created the file custom.sh in /etc/profile.d/ folder: export LANG=en_US.UTF-8 export LC_ALL=en_US.UTF-8 which should (as far I know) set the settings system wide. no it doesn't - see my earlier email Calling echo $LANG as jenkins user in the bash shows echo $LANG en_US.UTF-8 that doesn''t matter as you are running that in an INTERACTIVE LOGIN shell - what happens when you run the command directly via ssh (not in a shell in ssh but directly in ssh - again see previous post). if you want to change this system wide then you probably need to change /etc/sysconfig/i18n - but there may be other places... try searching in your favourite search engine on this subject and it will enlighten you, e.g. https://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin#SSHSlavesplugin-Loginprofilefiles http://stackoverflow.com/questions/216202/why-does-an-ssh-remote-command-get-fewer-environment-variables-then-when-run-man -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Build Flow Plugin and artifacts management in the DSL
To be honest I wouldn't pass buildnumber, I would use a run parameter so
that manual triggering should you ever need it (e.g. a failed deploy) would
be easier.
Format the build as
def job1runparam = build1.project.fullName + # build1.number
and then add that to the paramerers
def myparams = new HashMap();
myparams['job1', 'job1runparam']
then in the copy artifact a bit of fudging to use version '${job1_NUMBER'}
/James
On Monday, 16 September 2013 14:47:24 UTC+1, Emmanuel Boudrant wrote:
Thanks, I will try !
-emmanuel
On Monday, September 16, 2013 6:04:02 AM UTC-7, Emmanuel Boudrant wrote:
Hello,
We've checked the Build Flow Plugin for parallel execution, is is
possible to manage the artifact in the plugin.
Example :
parallel (
// Each job is going to produce one artifact{ build(job1) },
{ build(job2) },
...
{ build(jobN) }
)
// deploy need access to all the artifact generated by job1, job2, ..., jobN.
build(deploy)
Our use case is we have plenty of slaves for building the artifacts but only
one slave can deploy them.
Thanks,
-emmanuel
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Build flow plugin: How to copy results from downstream jobs
The BuildFlow doesn't use a workspace anymore[1] - so your workaround most
likely won't work as you expect.
I'm not convinced that this is a good thing as like you I would like to
show test results in the main flow job - not have another job that is just
aggregate report.
On Monday, 12 August 2013 20:17:54 UTC+1, John Russell wrote:
Do you guys have any idea how to pull files, specifically test results,
from the jobs started in a build flow up to the build flow job itself so it
can be the one that presents all of the test results?
I presume that if I can copy them from the slaves up to the workspace of
the build flow build that the post build step of processing the test
results will get them all. Any thoughts on how to get those files back
to the master?
On Thursday, January 3, 2013 2:30:31 AM UTC-5, Nicolas De loof wrote:
sure, rescue handle whatever happens in gard block, that has no
restriction on nested content
2013/1/3 Patrick van der Velde petrikva...@gmail.com
Thanks for that suggestion. One question about the guard statement. Can
it handle multiple statements? i.e. is the following allowed?
guard {
build(job1)
build(job2)
} rescue {
build(finaljob)
}
or even this
guard {
parallel(
{ build(job1a) },
{ build(job2a) },
)
parallel(
{ build(job1b) },
{ build(job2b) },
)
} rescue {
build(finaljob)
}
My script looks a bit like that last one but when I tried putting a
guard clause around it I got the following error:
ERROR: Failed to run DSL Scriptgroovy.lang.MissingMethodException
http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: com.cloudbees.plugins.flow.FlowDelegate.rescue()
is applicable for argument types: (Script1$_run_closure1_closure3) values:
Removing the guard clause made it work. So I'm guessing guard can only
handle 1 item?
Thanks
Petrik
On Wed, Jan 2, 2013 at 10:16 PM, nicolas de loof
nicolas...@gmail.comwrote:
use gard+rescue so you can execute a post-job even when some jobs are
unstable
2013/1/2 Patrick petrikva...@gmail.com
Ok I'm going to have to amend this answer. My idea of having a
separate job at the end to gather the results would work if it wasn't for
the fact that the build flow plugin kills the build as soon as one of the
jobs fails. That means I only can get the results if the build works
which
is not what I want. I want the results gathering to always take place,
even
if the all the build jobs fail. Any way to achieve this?
Thanks
Petrik
On Wednesday, 2 January 2013 11:46:54 UTC+13, Patrick wrote:
Hi
Mmm ok, I guess I could create a separate job to gather all the test
results. Thanks for the advice :)
Regards
Petrik
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Right procedure to send for Security Advisories
Hi Christian, You should create an issue in the Jenkins bug tracker under the Security Issues project. This project has restricted access so only the select few will be able to see your report. See https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories for more info. /James On Thursday, 29 August 2013 11:36:04 UTC+1, Christian Catalano wrote: Hi everyone, I am executing a PT for my company... in my targets there is a server with a Jenkins application. I think I have found a severe security vulnerability so I would like to know the right procedure to: - advise the jenkins team - send the documentation to explait the vulnerability and to prove it - how I can obtain a CVE Identifier Best regards Christian -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Right procedure to send for Security Advisories
My experience (of just one) was that it got picked up and looked at pretty quickly. Perhaps it got missed if it was towards the end of holidays, or because one of the select few[1] was busy flying around the world for Jenkins user events - so a prod on the dev list may help to spur things along. /James [1] There are only a few people who have the privileges to look see issues reported on the security project, not all commiters have this right. On Thursday, 29 August 2013 17:13:44 UTC+1, matthew...@diamond.ac.uk wrote: I opened a “Security Issues” ticket (SECURITY-53) back in Jan/2013, with no response. So I’m not sure what triggers someone to actually look at your report … *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *teilo *Sent:* 29 August 2013 11:48 *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: Right procedure to send for Security Advisories Hi Christian, You should create an issue in the Jenkins bug tracker under the Security Issues project. This project has restricted access so only the select few will be able to see your report. See https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories for more info. /James On Thursday, 29 August 2013 11:36:04 UTC+1, Christian Catalano wrote: Hi everyone, I am executing a PT for my company... in my targets there is a server with a Jenkins application. I think I have found a severe security vulnerability so I would like to know the right procedure to: - advise the jenkins team - send the documentation to explait the vulnerability and to prove it - how I can obtain a CVE Identifier Best regards Christian -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- 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. For more options, visit https://groups.google.com/groups/opt_out.
SECURITY-47 with xpath
Hi all, After a lot of head scratching[1] I found that you can no longer (by default) use text() in an xpath in api/xml/xpath=blah. The associated commit references SECURITY-47 - which I can't see but from the other commit would seem to be related only to jsonp[2]? What I'm finding hard to work out is what the attack vector is for xpath primatives? the content is returned as text/plain so should not be interpreted by any browser. Anyone any pointers? enabling hudson.model.Api.INSECURE=true to get xpath primatives would expose jsonp which is not something that I would want to do as the attack vector there is well understood. Regards, /James [1] https://issues.jenkins-ci.org/browse/JENKINS-19221 [2] http://www.cloudbees.com/jenkins-advisory/jenkins-security-advisory-2013-02-16.cb -- 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. For more options, visit https://groups.google.com/groups/opt_out.
CI usability - isn't there a problem that tests are executed only after a developer pushed his changed to the repsitory?
Hi Avyhal, It's a problem with your tools and workflow. I suggest you look at some tools that enforce some code review as part of your SCM use, so that the build midst have passed test before it can be in the mainline. E.g Gerrit, cloudbees commit validator etc. Regards James -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins Job list empty after JENKINS_HOME was moved
Another potential reason is the Java security manager that your today is using is preventing reading and it writing files that are outside the tomcat webapp dir. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Policy of fixes in LTS?
Generally if the fix has been in the mainline for a few weeks without any regressions and is easy to back port, if it has been tagged then it will be back ported. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Having trouble with Maven Release plugin -- Cannot prepare the release because you have local modifications
You need too add target/ to svn:ignore -- 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. For more options, visit https://groups.google.com/groups/opt_out.
pre-build maven step not working with default maven?
https://issues.jenkins-ci.org/browse/JENKINS-755 -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Mass Jenkins job updates
That somehow may depend on what you are evaluating – but it is dynamic on
job save, so if you update the parameters the job is updated.
e.g. my template has
“checkstyle” in the template is a checkbox.
--snip --
reporters
hudson.plugins.checkstyle.CheckStyleReporter
% if (checkstyle) { %
thresholds
unstableTotalAll0/unstableTotalAll
/thresholds
% } // end if (checkstyle) %
/hudson.plugins.checkstyle.CheckStyleReporter
-- snip –
Or – where I have an option for maven parallel building (-Txxx)
goals-e ${parallelBuilds} -Dmaven.test.failure.ignore=false test
checkstyle:checkstyle pmd:pmd findbugs:findbugs/goals
And as it was added at the start of the template I have a default value
%
/*
* New parameters may be null so set a suitable default.
*/
if (parallelBuilds == null) {
parallelBuilds = ;
}
%
Other places – where I need it just cope with the fact the value hasn’t
been set (but this is partly due to the fact that I create template jobs
inside a template folder J - and then force the user update the config by
disabling the jobs until they have entered the required info)
mavenName${maven_version == null ? :
maven_version.getName()}/mavenName
I suggest you raise a support call with cloudbees or provide the template
and full transform and error, this is no longer a Jenkins issue and doesn’t
really belong on this list.
/James
On Wednesday, 22 May 2013 13:53:10 UTC+1, Bob Bick wrote:
I tried someAttribute and it did not work either.
The Groovy code is executed prior to the user entering the template
attributes. This makes using Groovy code not very useful since it can’t be
dynamic.
Bob
*From:* teilo [mailto:teilo+...@teilo.net javascript:]
*Sent:* Tuesday, May 21, 2013 5:39 PM
*To:* jenkins...@googlegroups.com javascript:
*Cc:* 'teilo'; Bob Bick
*Subject:* Re: Mass Jenkins job updates
its just someAttribute not $someAttribute (although my groovy isn't the
best and $someAttribute could also be correct syntax :/ )
You need to make sure that the template creates valid XML that represents
a job that is known to Jenkins.
Might be best to start by loading a an existing job and then adding a
single parameter and then changing the groovy transform.
If not the error you get back although cryptic and in martian does give
you somewhat of a clue as where to look.
I wanted to open source our templates, but I have more urgent things
blocked in the approval queue so I have not pursued it.
Maybe someone with karma could allow read access to the Jenkins templates
at https://jenkins.ci.cloudbees.com/template/ unless they contain secret
info?
/James
On Tuesday, 21 May 2013 16:32:35 UTC+1, Bob Bick wrote:
Thanks James.
I am trying out the CloudBees template approach using Groovy template
transformations.
Overall, it seems nice; however, it is not clear how to access attributes
in Groovy code. The CloudBees doc shows this trivial example of adding
Groovy code:
foo
%
for (int i=0; i100; i++) {
if ((i%2)==0) {
%
data${i}/data
%
}
}
%
/foo
I’d like to use an attribute whose value is provided by the user when the
job is instantiated. Here is a simplified example of what I am trying to do:
foo
%
def x = “a” + $someAttribute
%
data${x}/data
/foo
Unfortunately, the above example does not work. Does anyone know if it is
possible to access attribute values in the Groovy template code?
Thanks in advance.
Bob
*From:* teilo [mailto:teilo+...@teilo.net]
*Sent:* Tuesday, May 21, 2013 9:11 AM
*To:* jenkins...@googlegroups.com
*Cc:* 'teilo'; Bob Bick
*Subject:* Re: Mass Jenkins job updates
You can add new parameters, so long as you handle the fact that the
parameter may be null in the transformer used by the template.
There's a bit about this in my presentation from the Jenkins User event in
London, and the online docs from cloudbees should give you more details of
this.
Others have pointed out there may be other ways to solve the same issue
with various advantages/disadvantages.
On Tuesday, 21 May 2013 14:04:55 UTC+1, Bob Bick wrote:
Thanks James, that clears it up!
I guess a template could not add a new parameter. Is that correct? Or,
maybe there is a way to define a default value that all jobs would get?
Bob
*From:* teilo [mailto:teilo+...@teilo.net]
*Sent:* Tuesday, May 21, 2013 8:59 AM
*To:* jenkins...@googlegroups.com
*Cc:* Bob Bick
*Subject:* Re: Mass Jenkins job updates
Hi Bob,
Just so I understand what you are saying... If you create a job based
on a template, and then you make a change to the template, all jobs are
automatically updated based on the template?
Yes - if your jobs
Mass Jenkins job updates
I use option 4 - Jenkins enterprise This won't be a drop in solution for you as your jobs need to be templatized before you can update them by just tweaking the template. You could do this with some groovy but that has drawbacks if you mess up your groovy. But Jenkins enterprise has other benefits (at least to me) that the initial pain of moving jobs too templates was worth it. Configuration slicing didn't do it to me, groovy can be an issue if you only have a subset of your jobs share the same config - as you have to maintain a whitelist/blacklist. The other option is wget and some sed/perl/... scripting -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Mass Jenkins job updates
Hi Bob, Just so I understand what you are saying... If you create a job based on a template, and then you make a change to the template, all jobs are automatically updated based on the template? Yes - if your jobs are based on that template then they are all automatically updated. I have not tried this; however, I would assume that you'd need to modify the template and then re-run the transformation with the exact same parameters to re-create each job. That's not how the plugin works - when you create a job you no longer create a FreeStyle job or a Maven2 job, you create a Mytemplate job. The only thing the job will ask you for is the parameters defeined by the template, and these are stored in the job. The template then converts these parameters using the definition stored in the template. If so, that seems like a hassle because you'd need to re-run the transformation for many jobs which would be inefficient. That would be ineficient - which is why it doesn;t work like that. Basically, if your job has been created from a template then once you update the template then the job is automatically updated. However your jobs are not created from a tempalte, so you would first have to create a template and then convert (recreate?) your jobs to be based on the template. /James On Tuesday, 21 May 2013 13:52:19 UTC+1, Bob Bick wrote: Thank you for the response. Just so I understand what you are saying... If you create a job based on a template, and then you make a change to the template, all jobs are automatically updated based on the template? I have not tried this; however, I would assume that you'd need to modify the template and then re-run the transformation with the exact same parameters to re-create each job. If so, that seems like a hassle because you'd need to re-run the transformation for many jobs which would be inefficient. Do I understand that correctly? Thanks, Bob -Original Message- From: jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] On Behalf Of teilo Sent: Tuesday, May 21, 2013 4:03 AM To: jenkins...@googlegroups.com javascript: Subject: Mass Jenkins job updates I use option 4 - Jenkins enterprise This won't be a drop in solution for you as your jobs need to be templatized before you can update them by just tweaking the template. You could do this with some groovy but that has drawbacks if you mess up your groovy. But Jenkins enterprise has other benefits (at least to me) that the initial pain of moving jobs too templates was worth it. Configuration slicing didn't do it to me, groovy can be an issue if you only have a subset of your jobs share the same config - as you have to maintain a whitelist/blacklist. The other option is wget and some sed/perl/... scripting -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Mass Jenkins job updates
You can add new parameters, so long as you handle the fact that the parameter may be null in the transformer used by the template. There's a bit about this in my presentation from the Jenkins User event in London, and the online docs from cloudbees should give you more details of this. Others have pointed out there may be other ways to solve the same issue with various advantages/disadvantages. On Tuesday, 21 May 2013 14:04:55 UTC+1, Bob Bick wrote: Thanks James, that clears it up! I guess a template could not add a new parameter. Is that correct? Or, maybe there is a way to define a default value that all jobs would get? Bob *From:* teilo [mailto:teilo+...@teilo.net javascript:] *Sent:* Tuesday, May 21, 2013 8:59 AM *To:* jenkins...@googlegroups.com javascript: *Cc:* Bob Bick *Subject:* Re: Mass Jenkins job updates Hi Bob, Just so I understand what you are saying... If you create a job based on a template, and then you make a change to the template, all jobs are automatically updated based on the template? Yes - if your jobs are based on that template then they are all automatically updated. I have not tried this; however, I would assume that you'd need to modify the template and then re-run the transformation with the exact same parameters to re-create each job. That's not how the plugin works - when you create a job you no longer create a FreeStyle job or a Maven2 job, you create a Mytemplate job. The only thing the job will ask you for is the parameters defeined by the template, and these are stored in the job. The template then converts these parameters using the definition stored in the template. If so, that seems like a hassle because you'd need to re-run the transformation for many jobs which would be inefficient. That would be ineficient - which is why it doesn;t work like that. Basically, if your job has been created from a template then once you update the template then the job is automatically updated. However your jobs are not created from a tempalte, so you would first have to create a template and then convert (recreate?) your jobs to be based on the template. /James On Tuesday, 21 May 2013 13:52:19 UTC+1, Bob Bick wrote: Thank you for the response. Just so I understand what you are saying... If you create a job based on a template, and then you make a change to the template, all jobs are automatically updated based on the template? I have not tried this; however, I would assume that you'd need to modify the template and then re-run the transformation with the exact same parameters to re-create each job. If so, that seems like a hassle because you'd need to re-run the transformation for many jobs which would be inefficient. Do I understand that correctly? Thanks, Bob -Original Message- From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of teilo Sent: Tuesday, May 21, 2013 4:03 AM To: jenkins...@googlegroups.com Subject: Mass Jenkins job updates I use option 4 - Jenkins enterprise This won't be a drop in solution for you as your jobs need to be templatized before you can update them by just tweaking the template. You could do this with some groovy but that has drawbacks if you mess up your groovy. But Jenkins enterprise has other benefits (at least to me) that the initial pain of moving jobs too templates was worth it. Configuration slicing didn't do it to me, groovy can be an issue if you only have a subset of your jobs share the same config - as you have to maintain a whitelist/blacklist. The other option is wget and some sed/perl/... scripting -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from
Re: Mass Jenkins job updates
its just someAttribute not $someAttribute (although my groovy isn't the
best and $someAttribute could also be correct syntax :/ )
You need to make sure that the template creates valid XML that represents a
job that is known to Jenkins.
Might be best to start by loading a an existing job and then adding a
single parameter and then changing the groovy transform.
If not the error you get back although cryptic and in martian does give you
somewhat of a clue as where to look.
I wanted to open source our templates, but I have more urgent things
blocked in the approval queue so I have not pursued it.
Maybe someone with karma could allow read access to the Jenkins templates
at https://jenkins.ci.cloudbees.com/template/ unless they contain secret
info?
/James
On Tuesday, 21 May 2013 16:32:35 UTC+1, Bob Bick wrote:
Thanks James.
I am trying out the CloudBees template approach using Groovy template
transformations.
Overall, it seems nice; however, it is not clear how to access attributes
in Groovy code. The CloudBees doc shows this trivial example of adding
Groovy code:
foo
%
for (int i=0; i100; i++) {
if ((i%2)==0) {
%
data${i}/data
%
}
}
%
/foo
I’d like to use an attribute whose value is provided by the user when the
job is instantiated. Here is a simplified example of what I am trying to do:
foo
%
def x = “a” + $someAttribute
%
data${x}/data
/foo
Unfortunately, the above example does not work. Does anyone know if it is
possible to access attribute values in the Groovy template code?
Thanks in advance.
Bob
*From:* teilo [mailto:teilo+...@teilo.net javascript:]
*Sent:* Tuesday, May 21, 2013 9:11 AM
*To:* jenkins...@googlegroups.com javascript:
*Cc:* 'teilo'; Bob Bick
*Subject:* Re: Mass Jenkins job updates
You can add new parameters, so long as you handle the fact that the
parameter may be null in the transformer used by the template.
There's a bit about this in my presentation from the Jenkins User event in
London, and the online docs from cloudbees should give you more details of
this.
Others have pointed out there may be other ways to solve the same issue
with various advantages/disadvantages.
On Tuesday, 21 May 2013 14:04:55 UTC+1, Bob Bick wrote:
Thanks James, that clears it up!
I guess a template could not add a new parameter. Is that correct? Or,
maybe there is a way to define a default value that all jobs would get?
Bob
*From:* teilo [mailto:teilo+...@teilo.net]
*Sent:* Tuesday, May 21, 2013 8:59 AM
*To:* jenkins...@googlegroups.com
*Cc:* Bob Bick
*Subject:* Re: Mass Jenkins job updates
Hi Bob,
Just so I understand what you are saying... If you create a job based
on a template, and then you make a change to the template, all jobs are
automatically updated based on the template?
Yes - if your jobs are based on that template then they are all
automatically updated.
I have not tried this; however, I would assume that you'd need to
modify the template and then re-run the transformation with the exact same
parameters to re-create each job.
That's not how the plugin works - when you create a job you no longer
create a FreeStyle job or a Maven2 job, you create a Mytemplate job.
The only thing the job will ask you for is the parameters defeined by the
template, and these are stored in the job. The template then converts
these parameters using the definition stored in the template.
If so, that seems like a hassle because you'd need to re-run the
transformation for many jobs which would be inefficient.
That would be ineficient - which is why it doesn;t work like that.
Basically, if your job has been created from a template then once you
update the template then the job is automatically updated.
However your jobs are not created from a tempalte, so you would first have
to create a template and then convert (recreate?) your jobs to be based on
the template.
/James
On Tuesday, 21 May 2013 13:52:19 UTC+1, Bob Bick wrote:
Thank you for the response.
Just so I understand what you are saying... If you create a job based on a
template, and then you make a change to the template, all jobs are
automatically updated based on the template? I have not tried this;
however, I would assume that you'd need to modify the template and then
re-run the transformation with the exact same parameters to re-create each
job. If so, that seems like a hassle because you'd need to re-run the
transformation for many jobs which would be inefficient.
Do I understand that correctly?
Thanks,
Bob
-Original Message-
From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On
Behalf Of teilo
Sent: Tuesday, May 21, 2013 4:03 AM
Re: Job Config History Plugin and Jenkins Enterprise from CloudBees
Hi Bob, I am heavily using CB Enterprise plugins. (Note Folders is not an enterprise plugin but one of the cloudbees free as-in-beer ones) I have found most plugins now work. Over the couple of years I have found some incompatabilities with plugins. When I have previously found issues cloudbees have been pretty responsive in fixing the issue in the plugin (if its on their list[1]). /James [1] http://wiki.cloudbees.com/bin/download/Jenkins+Enterprise/WebHome/CertifiedPlugins.pdf On Monday, 20 May 2013 16:30:12 UTC+1, Bob Bick wrote: Hi, We are using Jenkins Enterprise from CloudBees and have jobs contained within CloudBees Folders. The JobConfigHistory plugin ( https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin ) works fine for jobs that are at the root level; however, if the job is under a CloudBees folder, the JobConfigHistory plugin does not work. Has anyone else ran into this issue? Any workaround? As a Jenkins newbie administrator, I am starting to re-think whether to use Jenkins Enterprise CloudBees features since generic Jenkins plugins may have issues. Is that a valid concern? Are other Jenkins administrators avoiding Jenkins Enterprise CloudBees features because some plugins may not play well with CloudBees? Any guidance on avoiding CloudBees features would be much appreciated. Thanks, Bob *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Discard Old builds/Artifacts
Artifacts/builds will be discarded when any of the conditions are met and the job is run. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins and Maven releases...
You could use the xTrigger plugin to monitor the job/lastReleaseBuild url - which would get changed on release. On Tuesday, 7 May 2013 17:39:00 UTC+1, Jeff Vincent wrote: In my dev group we use Jenkins to do the CI portion of our Maven builds for our team but the company uses Thoughtworks GO for continuous delivery. We are trying to improve our process such that we can tell GO to use the Maven artifact published during the jenkins build instead of redoing the build again. To do this we created a generic Maven wrapper project that has a dependency on the WAR artifact. The artifact details in the wrapper POM are parameterized and set on the command-line. We then use the versions-maven-plugin to update the project properties in the POM with the latest snapshot version and then run it through the GO pipeline. This works pretty well for normal snapshot builds, but we'd like to trigger the GO pipeline specifically after the Maven release build (triggered w/ Jenkins Maven Release Plugin) is published and before Jenkins picks up the next SNAPSHOT build. In other words there seems to be 2 builds that happen as a direct result of the Maven release process and one that happens as a side effect of the SCM change: 1. Current SNAPSHOT build 2. New Release build 1. How to insert GO trigger for release build before #3 happens? 3. Next SNAPSHOT build Anyone have ideas on how to inject a command at step 2.1 to trigger GO to deploy the release? I am drawing a blank...ack! Thanks! -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[M2Release] MAVEN RELEASE - SVN 403 Forbidden
The release process will use the authentication available to the subversion command line client when run as the user that Jenkins runs as on the slave. If you have not told the release plugin otherwise it won't pass a user to the svn client either, so if Jenkins is running as root it will try and create the tag as the root user. It sounds like you need to use a user other than root and if you don't want to have to specify a username/password eachtime then you can add -Dusername=myuser to the real ease goals and put the password for this used in the subversion credential cache (this is not the Jenkins svn credential store) -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins / Flexmojos 4.0-RC2 issue (Error: null)
spaces in the path (caused by spaces in the job name)? This is known to cause issues with some flaky maven mojos (although not used flexmojos...) and would be worthwhile ruling out. Writing configuration dump to C:\Jenkins\workspace\Common presentation - DEV\target\common-presentation-4.3-SNAPSHOT-configs.xml Error: null mojoFailed org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-RC2(default-compile-swc) projectFailed be.vanhoecke.common:common-presentation:4.3-SNAPSHOT sessionEnded [INFO] [INFO] BUILD FAILURE [INFO] On Tuesday, 9 April 2013 14:03:47 UTC+1, Bert Vandamme wrote: Hi, This is probably not a Jenkins issue, but someone else might have run into a similar issue, hence this post... A couple of days ago one of the jobs on our buildserver started failing, which as odd because the same build on our local dev machines worked just fine. (both are build with the same maven script) As you can see in the attached log file, the build fails with a not very helpful exception (Error: null, line 4120 in the attached log file) after writing the configuration dump. The exact same project builds just fine when ran outside of the Jenkins workspace folder on that same server. Disabling the jenkins service (to prevent any folder locking) does not make a difference. So far I've updated the maven version (3.0.5), the java jdk (1.7) and jenkins (latest version) to rule out any problems on those domains, but had no success so far. The problem folder has all necessary rights as well... *System info (logfile extract):* Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: C:\Programs\Apache\Maven\3.0.5 Java version: 1.7.0_17, vendor: Oracle Corporation Java home: C:\Program Files\Java\jre7 Default locale: en_US, platform encoding: Cp1252 OS name: windows server 2008, version: 6.0, arch: x86, family: windows Does this kind of issue ring a bell for anyone? Any pointers? Thx! Bert -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject
On Monday, 18 March 2013 18:44:18 UTC, Tomek Kaczanowski wrote: Hi James, thanks for the quick response! the simplest quick fix is to downgrade Jenkins... yeah, sure it is What version did you upgrade from - and what options/parameters are you using? 1.496 what options/parameters you are asking about? When you release there are options for the username/password, comment prefix, tag, nexus pro support.. There was a similar defect raised when the plugin was run in Hudson 2.2 - and I think Jenkins recently updated it's json library... So the problem may be how to get this to work in a backwards compatible way. In the interim there is a pull request that will fix this (not tested on older releases yet) so you may be able to grab that, build locally and use it to unblock you whilst I look at if anything else is needed. https://github.com/jenkinsci/m2release-plugin/pull/9 -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject
the simplest quick fix is to downgrade Jenkins... What version did you upgrade from - and what options/parameters are you using? /James On Monday, 18 March 2013 16:30:28 UTC, Tomek Kaczanowski wrote: after upgrading to 1.506 when trying to do a maven release via https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin ver 0.9.1 I get this: Status Code: 500Exception: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Stacktrace: javax.servlet.ServletException: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject at org.jvnet.hudson.plugins.m2release.M2ReleaseAction.doSubmit(M2ReleaseAction.java:239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) ... 42 more any hints on how to solve this issue? -- Regards, Tomek Kaczanowski -- You received this message
Re: Jenkins job stuck waiting for self
Presumably you have Block build when upstream project is building enabled. If so the reason is that the project has itself marked as an upstream project. This could happen if you trigger the job to run itself again (e.g. you want a continous loop). Assuming you haven't done that then you need to work out why the job has itself as an upstream job - this can be caused by the job downloading from the maven repo a previous version of its artifacts (e.g. you use dependency-copy for a jar in a module in the reactor, but you are not running package in jenkins) /James On Thursday, 14 March 2013 13:02:21 UTC, Jason Voegele wrote: Hi, recently many of our Jenkins jobs are stuck waiting for themselves to finish executing before they can start executing. What I mean is that a Maven job is in the queue to execute, but never actually does execute because it says that it is waiting for itself to finish, even though it has never started. See for example the attached screenshot. Can anyone explain this recent behavior? Is it a Jenkins bug? -- Jason Voegele A child of five could understand this! Fetch me a child of five. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Frequent crashes
Presumably the service account under which Jenkins is running does not have write permissions in the system32 folder. You may want to add “-XX:ErrorFile=c:\some\path\where\jenkins\can\write\hs_err_.log” to your Jenkins JVM startup options so that in the event of a crash the log can be found. It may be caused by a fault in the JDK - and you may want to submit a bug report to Oracle with this log file. /James On Monday, 18 February 2013 19:47:50 UTC, MDKF wrote: Hi Stuart, Thanks for the link. It has happened while viewing the console output, but we don't have any slave machines, just two executors on the master. But as in the bug report we don't have .log files either. On Mon, Feb 18, 2013 at 2:40 PM, Stuart Whelan stu...@somepointinthefuture.co.nz javascript: wrote: Could it be related to this: Jenkins master node crashes often when viewing console logs of builds on slaves https://issues.jenkins-ci.org/browse/JENKINS-16528 It happens to me maybe half a dozen times a day. It is causing us huge problems, I am about to rebuild our jenkins master with a clean os to see if that fixes it. On Mon, Feb 18, 2013 at 11:44 AM, MDKF michael...@gmail.comjavascript: wrote: Hi all, Jenkins keeps crashing randomly. There seems to be no particular trigger. Any idea whats happening? Heres my log: Running from: C:\Program Files (x86)\Jenkins\jenkins.war webroot: EnvVars.masterEnvVars.get(JENKINS_HOME) Jenkins home directory: C:\Program Files (x86)\Jenkins found at: EnvVars.masterEnvVars.get(JENKINS_HOME) Running from: C:\Program Files (x86)\Jenkins\jenkins.war webroot: EnvVars.masterEnvVars.get(JENKINS_HOME) Jenkins home directory: D:\Jenkins_Home found at: EnvVars.masterEnvVars.get(JENKINS_HOME) return code: 0 stderr: stdout: The command completed successfully. Running from: C:\Program Files (x86)\Jenkins\jenkins.war webroot: EnvVars.masterEnvVars.get(JENKINS_HOME) Jenkins home directory: D:\Jenkins_Home found at: EnvVars.masterEnvVars.get(JENKINS_HOME) return code: 0 stderr: stdout: The command completed successfully. # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x018d1a23, pid=1516, tid=3204 # # JRE version: 6.0_39-b04 # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode, sharing windows-x86 ) # Problematic frame: # J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z # # An error report file with more information is saved as: # C:\Windows\system32\hs_err_pid1516.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Running from: C:\Program Files (x86)\Jenkins\jenkins.war webroot: EnvVars.masterEnvVars.get(JENKINS_HOME) Jenkins home directory: D:\Jenkins_Home found at: EnvVars.masterEnvVars.get(JENKINS_HOME) return code: 2 stderr: System error 85 has occurred. The local device name is already in use. stdout: # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x0154dd23, pid=4728, tid=4012 # # JRE version: 6.0_39-b04 # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode, sharing windows-x86 ) # Problematic frame: # J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z # # An error report file with more information is saved as: # C:\Windows\system32\hs_err_pid4728.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: arcvhiving takes forever - just me?
Fingerprints? https://issues.jenkins-ci.org/browse/JENKINS-13154 That made a significant difference to me. Other than that google for bandwidth delay product and ssh plugin (check the last comment in https://issues.jenkins-ci.org/browse/JENKINS-3922) /James On Monday, 4 February 2013 21:17:26 UTC, Maven User wrote: Hi all - Super quick question - maybe this is a known issue When archiving a large artifact, jenkins seems to take forever (in some cases, taking a 1 min build up to 30 min). What's weird is when I ssh up to that same slave and scp over that same artifact to the same final location, it takes less than 10 seconds. Suggestions? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: m2release plugin release:rollback
Hi, It’s not supported (which is why the RFE is still open) and comments in the wiki are not monitored by the plugin maintainer. Wipe out workspace is probably the best form or release:rollback J maven won’t delete the tag if it created it anyway - so depending on what failed you may well need to do something by hand anyway. Regards, /James On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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. For more options, visit https://groups.google.com/groups/opt_out.
workspace archiver plugin?
Hi all, Before I embark on some coding, does anyone know if there is such a plugin that will archive the entire workspace ? I don't want all the files as attached artifacts - but the workspace as one big zip/tgz, and ideally be able to only keep it with a different schedule from the build artifacts? The Clone Workspace SCM plugin[1] is almost what I'm looking for but not quite (and I don't think it makes sense to extend this). The use case I am trying to solve is that we will be moving to RAM disks for the build machines - and as we don;t have 100's of GB of RAM for each slave we need to wipe the workspace at the end of the build (builds can float between slaves). This is fine until there is a failed build - which if the reason is not obvious in the JUnit test then there will be nothing around to poke at (as the workspace will be wiped). Not wiping the workspace is not a viable solution as there may be several failed builds (of both the same job and other jobs) and as the build may not run on the same slave next time failed builds will accumulate leading us to run out of disk space. Regards, /James --
Re: Help w/ maven release and git
Yup - works like a charm :-) ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. That implies to me that it can't find the server calls svcSCM which comes from your developerConnection in the POM. have you verified whats in the workspace after a failed build and that the pom its trying to checkin is what you expect. On Saturday, 26 January 2013 00:00:34 UTC, Jeff Vincent wrote: Bumpanyone using GIT w/ maven-release-plugin in Jenkins? On Wed, Jan 23, 2013 at 9:41 PM, Jeff preda...@gmail.com javascript:wrote: Two questions (from a Git n00b) dealing with Git + Maven in Jenkins: 1) When I do a release, I either want a new branch based on the maven release version or a release branch sync'd w/ the latest master code and tagged with the latest release version so we can pull it if we ever need to do a hot fix based on release code. I haven't found the thing that helps me do this using the Maven Release Plugin and Git. Can anyone point me in the right direction? 2) I've configured Jenkins w/ the SSH keys for our Git service account to our internal gitolite repository. I can successfully pull and it seems that during the maven release process, the commit works when updating the POM, but it seems pushing the new branch fails with: MyGitProject: Unable to commit files Provider message: The git-push command failed. Command output: ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The user has the same rights as my personal user and I can do branching and pushing operations manually with either account on the Jenkins box. I've tried leaving the SCM username/password blank when scheduling a maven release and I've also tried just setting the user name to match the Git service account user with similar failed results. I'm sure I'm missing something fundamentally simple, but I'm not seeing it. Any and all help is much appreciated. -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group, send email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: best linux production env for jenkins?
Hi Russ, To be pretty honest - I would suggest you skip the packaged versions and use your own init scripts and the war with the inbuilt winstone container. As for which distro - if you take the above advice it depends on you. Pretty much anything recent will have a good enough kernel and the reset is just java. I use CentOS, but I prefer to admin debian - but work is RH/CentOS. If you are thinking of support then make sure that whatever you choose is covered by your support vendor. Whichever you choose you can always choose not to install the defaults but install just what you want (but having things installed should not be an issue - just don;t start the services and install root on cheaper HDD and then have your JENKINS_HOME on the SSD Don'f forget to replace those SSDs early before they wear out :-) /James On Friday, 25 January 2013 20:18:12 UTC, Russ Tremain wrote: Hi, Does anyone have suggestions for the best linux production environment for jenkins? I want to run a trimmed down server optimized for web performance. In the past, I've always run jenkins under tomcat, but am open to other suggestions. Looking for specific version info for distros tomcat. Will run on vmware infrastructure with outrageous (SSD-based) i/o performance. tia, -Russ
Re: best linux production env for jenkins?
On Friday, 25 January 2013 21:56:41 UTC, LesMikesell wrote: On Fri, Jan 25, 2013 at 3:43 PM, teilo teilo+...@teilo.net javascript: wrote: To be pretty honest - I would suggest you skip the packaged versions and use your own init scripts and the war with the inbuilt winstone container. As for which distro - if you take the above advice it depends on you. Pretty much anything recent will have a good enough kernel and the reset is just java. I use CentOS, but I prefer to admin debian - but work is RH/CentOS. If you are thinking of support then make sure that whatever you choose is covered by your support vendor. Whichever you choose you can always choose not to install the defaults but install just what you want (but having things installed should not be an issue - just don;t start the services and install root on cheaper HDD and then have your JENKINS_HOME on the SSD For RH or CentOS, I think the yum install is even easier if you want to use the embedded winstone. http://pkg.jenkins-ci.org/redhat/ You can configure your options in the /etc/sysconfig/jenkins file so subsequent updates won't overwrite them. JENKINS_HOME will be /var/lib/jenkins (following packaging guidelines) so mount whatever you want there before then install. Its easier for the first install, but after that it is not as good. Packages are guaranteed to be broken more than the war alone (as there is an extra layer it is one more thiing that can change/break - as shown by the recent deb change) The war arguments are not likely to change but will be added to (if needed) but the config exposed by these scripts is not the same. For example what happens if you say want to run SSL - you then add custom ARGs to the line. Later the init scripts add a user friendly option for SSL (defaults to -1). so now the init script can fail as the HTTPS_PORT var is not -1 (as it doesn't exist in your config) - or worse it is 8443 by default so it uses the default as well as your different port. That is a contrived example - but that has happend recently on the deb when a parameter was removed. upgrades/downgrades are a simple change of a symlink with the jenkins war. by all means grab the init scripts from the src repo - but in the long run the ease is lost. my 2p from experience.
Re: java process on jenkins master pegged at 650% since upgrading some plugins
Hi Chris,
Depending on how you upgraded you can go to
{jenkinsurl}/pluginManager/installed and look at the previously installed
version.
Then if you look on disk in jenkinshome/data/plugins and take a look at the
imestamps on the hpi/jpi files that will tell you when the plugins where
installed.
You can then correlate this info to see what you upgraded, and what its
previous version was.
The 100% cpu is that each core counts as 100% so if all cores are
spinning on a core system the maximum will be 800%
/James
On Friday, 18 January 2013 13:26:50 UTC, Chris Withers wrote:
Hi,
Our Jenkins server runs Jenkins 1.470.
This morning, I updated a bunch of plugins (the one I needed was Jenkins
build timeout plugin from 1.10 to 1.11, but I thought I'd do the others
on offer to be the safe side) and since the restart, the java process on
the Jenkins master has been pegged at 650% plus! (it's a box with lots
of cores, but still, how can one process use more than 100% cpu?)
Anyway, a few questions:
- has anyone else seen this?
- how can I find the full list of plugins I updated? I wasn't that
concerned so I didn't make an exact list of the boxes I was checking,
now I wish I had :-(
- how can I debug exactly what's hogging all the CPU? I tried restarting
the process and the problem persisted, so if I need config changes to
get more info, that's easily done?
I'm not a Java programmer so I have no idea how to debug what's going
on. Any help would be very much appreciated!
cheers,
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
- http://www.simplistix.co.uk
Re: java process on jenkins master pegged at 650% since upgrading some plugins
On Friday, 18 January 2013 14:09:07 UTC, Chris Withers wrote:
Depending on how you upgraded you can go to
{jenkinsurl}/pluginManager/installed and look at the previously
installed version.
Where can I find more info on exactly how those downgrade to previous
version buttons work?
I think the answer to that is source code... There may be a WIKI. but
basically it will replace the current version (foo.hpi) with the previous
version (foo.bak) and then you will need to restart jenkins. Hopefully the
configuration hasn't been updated by the plugin to a newer version, but if
you have saved any jobs or the system config since updating this may not be
the case
What's considered the previous version? If I hit
the button, restart, what's then shown as the previous version?
At this point I'm not sure - it could be nothing or it could be the version
that you currently have.
Then if you look on disk in jenkinshome/data/plugins and take a look at
the imestamps on the hpi/jpi files that will tell you when the plugins
where installed.
Ah, good call :-)
The 100% cpu is that each core counts as 100% so if all cores are
spinning on an 8 core system the maximum will be 800%
I'm confused as to how one process can span multiple cores?
I thought, by definition a process was tied to one core?
I guess we're into the blurred world of threads/processes and their
exactly implementation?
In its simplistic view a thread can only run on a single core at any given
time. A process may be made up of a number of threads.
A thread may execute of core1 now and core5 at some point in the future.
Generally processes and threads are not tied to a processor although there
are OS tools to enable you to do this.
Re: Master + slave + job JVM memory tuning...
I would never advise more than one executor per slave :-o At some point there will be unit test failures in a project as it has badly written unit tests that blindly assume they can use port 12345 (and it will be in use for a different job - and then fight each other). And it will be the CI systems fault and come at a time that the most awkward for you (the project is trying to release, and you are about to leave for the weekend!) The exception to this would be where the jenkins job is acting more as a controller and the work is being performed on some other system. /James On Monday, 7 January 2013 18:36:58 UTC, Jeff Vincent wrote: Thanks...I unfortunately can't be in the UK for the event. So if the amount of RAM is fixed (4GB), what is a good rule of thumb for determining what to allocate to the slave process, how many executors it can reasonably support, etc? I realize there are a lot of other variables but any starting point and things to consider or factor in that may not be obvious could help. Or is it just a matter or monitoring and tuning? On Jan 7, 2013 2:31 AM, Nord, James jn...@nds.com javascript: wrote: Have enough RAM on the slave that you can run your jobs plus Jenkins + some for overhead. (e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests in forked VM) + OS overhead) Although this amount is mostly an overkill setting it too close to the threshold will slow your jobs down due to paging at best, or mean you get intermittent failures due to OOM at worst – (memory is generally cheaper that human time taken to investigate issues!) (our maven jobs can be very memory hungry so your figures will vary) (Note I recommend a single executor per slave) The master depends more on how many jobs / reports per jobs / job history you have etc – we use 10GB (but not tomcat). If you’re in the UK and there is any spaces left I will cover some things like this next week at the Jenkins User Event. /James *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Jeff *Sent:* 04 January 2013 21:56 *To:* jenkins...@googlegroups.com javascript: *Subject:* Master + slave + job JVM memory tuning... I'm trying to optimize how much memory I allocate to the master application (aka - tomcat), slave processes, maven tasks, etc. and going crazy. I've been unsuccessful in finding a guideline to determine how much memory I ought to allocate or if I should just let the defaults work. All machines are single processor, dual core with 4 GB ram. I've typically set tomcat to use 2048MB + 512MB permgen space and set my maven process to use 384MB max. Is this reasonable? My slaves are set to run 4 executors. Jobs use either svn or git to check out code and Maven to build with a SONAR post-build analysis. We also do Maven releases at times. How much does the core slave process need? Is there a rule-of-thumb based on the number of executors? Any perspective/considerations/resources/links/pointers are much appreciated. -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com javascript: and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
Re: LTS upgrade notifications
you may waat to remove the contents of jenkins_dir/data/updates /James On Monday, 7 January 2013 13:53:18 UTC, Jon Schewe wrote: I just switched one of my Jenkins servers to the LTS release. I downloaded the war file and replaced my current war file. I then updated the update site for the plugins and restarted. Everything is running fine, except when I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding edge release. Did I miss something here or do the LTS releases not check a separate update site? In the bottom right I see 1.480.1. -- http://mtu.net/~jpschewe
Re: Setting the context root on Jenkins 1.498 on debian 6 (latest) has broken
/etc/default/jenkins should be your friend on debian. /James On Monday, 7 January 2013 21:52:35 UTC, Colin Yates wrote: Hi all, I have been running jenkins on Debian for quite a while now, and the documented way to set the context root to /jenkins was to add a --prefix=/jenkins to the JENKINS_OPTS variable in the /etc/init.d/jenkins script. When I did an apt-get update; apt-get dist-upgrade it told me the latest version has removed that. I went ahead and installed the latest script assuming there was another way of doing it but I cannot figure out where I should add it now. /etc/init.d/jenkins no longer has the environment variable, and ~/config.xml doesn't include any likely looking suspects. Any ideas? The wiki didn't turn up much either (it suggested adding the --prefix). Thanks. Col
Re: Is it possible to fail build if test time increases by X%
There is no way that I currently know of, and the company I work for have have a need for performance regression tests jobs (so I have looked). I have not yet had time to open an IDE to look at this. (we want to look at a rolling average rather than the last successful job, and also match this to individual tests - so when a new test is introduced it doesn't immediately mark the build as unstable!) On Monday, 7 January 2013 21:57:29 UTC, Keith B. Perry wrote: Hi all, Does anyone know how to do this? Can I fail a build if a test time increases by a certain percentage? For example, if a test takes 100 ms today, but tomorrow it takes 5 seconds...can I have Jenkins fail the build?
Re: Jenkins svn ssh / host key verification problems
Hi Bjørn As the jenkins user on the slave ssh to the svn server and accept its key. Depending on your ssh clinet it may override the entry stored in ~/.ssh/known_hosts or may not. (if not then remove the entry manually from this file and retry with the ssh command) That should get it working /James On Friday, 4 January 2013 14:19:31 UTC, Bjørn Water wrote: So i am trying to use the M2-release plugin to release my project and push it to my nexus. I can do svn checkout and i can even tag my build and see it in my repo but when i try to do mvn release:prepare after a succesfull build i get an error [ERROR] BUILD FAILURE[INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:287) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 28 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
Re: Jenkins svn ssh / host key verification problems
I have completely to opposite experience, native svn+ssh is so much simpler than all other options! The provider also says it only works with http/https so may not even be much use (but then again documentation could just be out of date) On Friday, 4 January 2013 14:32:35 UTC, domi wrote: We had lots of issues when using the cli subversion client for release builds, therefore we moved to the svnjava provider and have no issues anymore: http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/ /Domi On 04.01.2013, at 15:19, Bjørn Water bjorn...@gmail.com javascript: wrote: So i am trying to use the M2-release plugin to release my project and push it to my nexus. I can do svn checkout and i can even tag my build and see it in my repo but when i try to do mvn release:prepare after a succesfull build i get an error [ERROR] BUILD FAILURE[INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:287) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at
Re: Jenkins svn ssh / host key verification problems
Jenkins tags using its inbuilt library (svnkit) as far as I am aware so the native ssh client doesn't get a look in. to see if its overridden the entry just check ~/.ssh/known_hosts for an entry for your server (after you removed it) What happens if as the jenkins user on the slave you run svn info svn+ssh://yourserver/path/to/repo ? On Friday, 4 January 2013 14:46:40 UTC, Bjørn Water wrote: Hi James, I have manually removed the entry from the file and then did a SSH command again and accepted the certificate. Still getting the same problems as before. Is there a way to see if it overrides the entry? Because it works when I tag it and that is also a commit right? Thanks, Bjørn On Friday, January 4, 2013 3:28:46 PM UTC+1, teilo wrote: Hi Bjørn As the jenkins user on the slave ssh to the svn server and accept its key. Depending on your ssh clinet it may override the entry stored in ~/.ssh/known_hosts or may not. (if not then remove the entry manually from this file and retry with the ssh command) That should get it working /James On Friday, 4 January 2013 14:19:31 UTC, Bjørn Water wrote: So i am trying to use the M2-release plugin to release my project and push it to my nexus. I can do svn checkout and i can even tag my build and see it in my repo but when i try to do mvn release:prepare after a succesfull build i get an error [ERROR] BUILD FAILURE[INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels
Re: Jenkins svn ssh / host key verification problems
are you sure you are looking in the correct file? it should be in the home file of the user that the jenkins service runs as. for the rpm the default (IIRC is ~jenkins/.ssh/known_hosts) - it may be somewhere else depending on your container / launch /install method. the svn commands also needs to be run as this jenkins user. On Friday, 4 January 2013 15:32:55 UTC, Bjørn Water wrote: I have removed the host from the file and then ran it again. There is no entry being made in that file so it does not override or writes something to the known_hosts file On Friday, January 4, 2013 3:54:09 PM UTC+1, teilo wrote: Jenkins tags using its inbuilt library (svnkit) as far as I am aware so the native ssh client doesn't get a look in. to see if its overridden the entry just check ~/.ssh/known_hosts for an entry for your server (after you removed it) What happens if as the jenkins user on the slave you run svn info svn+ssh://yourserver/path/to/repo ? On Friday, 4 January 2013 14:46:40 UTC, Bjørn Water wrote: Hi James, I have manually removed the entry from the file and then did a SSH command again and accepted the certificate. Still getting the same problems as before. Is there a way to see if it overrides the entry? Because it works when I tag it and that is also a commit right? Thanks, Bjørn On Friday, January 4, 2013 3:28:46 PM UTC+1, teilo wrote: Hi Bjørn As the jenkins user on the slave ssh to the svn server and accept its key. Depending on your ssh clinet it may override the entry stored in ~/.ssh/known_hosts or may not. (if not then remove the entry manually from this file and retry with the ssh command) That should get it working /James On Friday, 4 January 2013 14:19:31 UTC, Bjørn Water wrote: So i am trying to use the M2-release plugin to release my project and push it to my nexus. I can do svn checkout and i can even tag my build and see it in my repo but when i try to do mvn release:prepare after a succesfull build i get an error [ERROR] BUILD FAILURE[INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The svn command failed. Command output: Host key verification failed. svn: Commit failed (details follow): svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: Network connection closed unexpectedly at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:153) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303
jenkins plugin for sona type repository manager
The m2 release plugin supports closing nexus stages for releases. A future version will support auto dropping or promoting then as well.
Re: Null pointer in M2ReleaseBuildWrapper
*Hello,* getProject*().*getBuilds*() is returning a list which contains a null entry which is just not good.* *This appears on first inspection to be a Jenkins core issue – can you try with earlier cores to track down when this was introduced?* * **/James* On Thursday, 11 October 2012 15:47:16 UTC+1, Thierry wrote: Hello, I get this exception at end of perform maven release build. This is a feature from M2 Release Plugin En attente que Jenkins finisse de récupérer les données channel stopped ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com javascript: java.lang.NullPointerException at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.isSuccessfulReleaseBuild(M2ReleaseBuildWrapper.java:270) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@9046f8[cmiiappjavasimpledemoTmp] project.getModules()=[hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/com. alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/co m.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:] FATAL: null configuration : Plugin version is 0.10.0. Jenkins is 1.485. java jre 1.6.0_35 windows xp additionnal infos : - mvn release:perform (in dos command line) succeeds. - I have first installed plugin 0.9.1. I got quite the same NPE. I though issue could be similar to http://issues.jenkins-ci.org/browse/JENKINS-10042 and decided to try 0.10.0 - I can provide more information on demand. In help in order to fix this issue is welcome ! Thanks in advance. Thierry
Switching from bleeding edge to LTS?
Downgrading to an earlier lts may not work if the mainline version has changed any configuration (although it might work as well). Since I stopped taking the mainline and moved to lts I've found far far fewer suprises. Downside is you don't see the new experimental stuff so can't provide feedback in any use full timeframe. (aka the new popup menus are just plain annoying and get in the way)
Re: Triggering builds from slave nodes
You can poll for the existence of a file with the xtrigger plugin but if one minute isn't satisfactory then you could move the polling into a job that is always running and doesn't return until the file exists. Then your script in ftpd creates this trigger file when it wants the job to be done. That's one way to do it, there may be others. On May 11, 11:59 am, Chris Platts chris.pla...@ocs.co.uk wrote: Hi all, We've been really successful with using Jenkins to manage our software development. Now, I'm working on pulling all of our 'batch jobs' - FTP transfers, etc - into Jenkins so that we've got a consistent interface via which jobs can be monitored. We have a Linux system sat in a DMZ which handles all of our external transfers (pulling files via (S)FTP as well as running its own (S)FTP servers). This is configured as a slave in Jenkins. The Jenkins server itself sits inside our corporate network - the DMZ firewall allows SSH through so that the slave can operate. One of the things I'd like to achieve is to have Jenkins jobs triggered by our FTP server. We're using proftpd which features a module (mod_exec) which can execute scripts at various points - e.g. when an FTP user disconnects. Ideally, I'd like the disconnection of a user to trigger a Jenkins job so that Jenkins can then a) pull the FTP log to record what happened during the transfer and b) kick off other tasks to handle the received files (if any). However, the firewall doesn't allow any comms back from the DMZ, so proftpd scripts on the linux box cannot contact the Jenkins host. Is there any way that a script can instruct the slave process to talk to the Jenkins host via the already-established SSH link so that a job could be triggered? (Incidentally, I know the obvious question - why do the jobs need to be triggered from the slave side rather than just have Jenkins run on a schedule? The problem is that we need these tasks to be triggered immediately on receipt of files, rather than on an scheduled interval. Unfortunate, I know!) Thanks for any help, Chris OCS CATERING I CLEANING I ENGINEERING I HORTICULTURE I HYGIENE I INTEGRATED_SERVICES I PEST_CONTROL I RETAIL_SUPPORT I SECURITY I WASTE_MANAGEMENT MEMBER OF EUROLIANCE OCS Group UK Limited. Registered in England No. 3056469 Registered Office: Tilgate Forest Business Park, Brighton Road, Crawley, RH11 9BPwww.ocs.co.uk This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee, please note that any distribution, dissemination, copying or use of this communication or the information in it is prohibited. If you have received this message in error, please notify the sender immediately at the above e-mail address or telephone number and delete the information from your computer system. Attachments are virus checked, but the company does not accept any liability in respect of any virus which is not detected. v.04ii10 image_jpeg_part 92KViewDownload
