job level permissions not taking precidence over global permissions
Hi all - I want to allow all users at the global level to do a few things BUT for a particular job, I only want a few people to be able to run it. I seems like once at a global level, if authenticated users have been granted access to run a job then on a per job basis, I can't specify a subset. Is this the desired behaviour or am I missing the boat a bit? -- 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: job level permissions not taking precidence over global permissions
Thank you so much! It also seems additive - so if I add everyone to the job with read-only perms, it's in addition to their global permissions? On Thursday, August 29, 2013 7:16:20 PM UTC-4, Daniel Beck wrote: This is desired behavior in Project-based Matrix security. Try adding a user/group with no permissions on a specific job. This no-op entry will simply disappear when saving. Permissions granted globally cannot be revoked on specific jobs using this security strategy. You could use Role Strategy Plugin, and specify the 'global level' using a regular expression with negative lookahead, thereby matching all projects except a few. Alternatively, commercial Jenkins Enterprise has Role-based Access Control, which allows you to filter (global) roles so they don't apply to a specific project. On 29.08.2013, at 22:01, Maven User maven@gmail.com javascript: wrote: Hi all - I want to allow all users at the global level to do a few things BUT for a particular job, I only want a few people to be able to run it. I seems like once at a global level, if authenticated users have been granted access to run a job then on a per job basis, I can't specify a subset. Is this the desired behaviour or am I missing the boat a bit? -- 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: trigger a build ONLY when there has been a M2_RELEASEBUILD
I ended up using a post-build groovy script (about 12 lines). It detects if it was a maven release and passes along the job name and the release version to the next job. If people care/want this, lemmie know. On Wednesday, August 7, 2013 4:29:17 AM UTC-4, James Nord (jnord) wrote: Currently there is no simple way, hoiwever I think you can achieve what you want with the following: 1) use a URLtrigger (XTrigger plugin) on latestRelease permalink and inspect the content to cause job B to run. 2) use a RunParameter on job B to get the parameters from the release build (I have not tried this). From https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build · To use a Run Parameter, the value should be in the format * jobname#buildNumber* (eg. MyRunParam=foo-job%2399 for foo-job #99) /James *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Maven User *Sent:* 06 August 2013 22:26 *To:* jenkins...@googlegroups.com javascript: *Subject:* trigger a build ONLY when there has been a M2_RELEASEBUILD I think I may be over engineering this one a bit (headed to post-build groovy scripting hell), but I was wondering - is there an easy way to trigger another build (with two parameters from the release plugin) when a maven release has been triggered? For instance, when you run the maven release plugin on job A, I want to call job B only if A was both successful AND if it if IS_M2RELEASEBUILD is true. I looked at all sorts of things but wondering if there's something off the shelf I can use before going back to groovy... 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-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.
persisting changes made via the script console
Hi all -
I'm trying to set the slaveAgentPort (as it is known in the config.xml)
via the script console and I'm struggling a bit.
I'm trying this:
myinstance = Hudson.instance
println( myinstance.tcpSlaveAgentListener.configuredPort)
if (myinstance.tcpSlaveAgentListener.configuredPort == 3)
{
println(equals)
}
else
{
println(not equals)
tcpSlaveAgentListener = new TcpSlaveAgentListener(3)
myinstance.save()
}
What's weird is I can see that a thread is started and listening away at
this new port, but when I go into the global config settings, I don't see
it configured there.
Is there some kinda of other method I need to call to set this property?
--
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?
I tried setting the window but I have no idea what the number relates to. Should it be 4 thousand, 400 thousand, 400 billion? On Tuesday, February 5, 2013 5:39:17 AM UTC-5, teilo wrote: 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: arcvhiving takes forever - just me?
Regardless of the setting NOTHING makes the archiving go faster :-/ -- 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.
arcvhiving takes forever - just me?
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: cron H syntax
H is a drop in for any of the time slots and/or *, so it felt natural (for me) to try H/5. To explain that in a different way, I was attempting to say poll every 5 minutes if nothing is polling, wait for that to finish otherwise. With that out there, if I just leave everything */5 * * * *, and wanted things to poll in isolation, couldn't I turn down the concurrent polling down to 1? IIUC - with the H option, jenkins would decide how to split things up and I could leave the concurrent polling unbounded (which is a better option methinks). I wonder if that would eventually prevent things from getting a chance to poll at all On Wednesday, May 23, 2012 6:09:39 PM UTC-4, Kohsuke Kawaguchi wrote: Thanks for an interesting use case. */5 is just a short hand for 0-60/5, so I guess the general case that needs to be considered here is how to use hash in (s-e)/d construct. What's the good syntax here? H(s-e)/d? H(*)/d vs H/d?
Re: LDAP authentication fails
What version of the AD plugin are you using? If you have 1.27 installed, try rolling back to 1.26 (which may be a manual thing at this point).
controlling upstream/downstream relationships
Hi all - I could have sworn somewhere that a jenkins job stores what it thinks is an upstream or downstream job. I have two jobs that at one point, were misconfigured. Now one always triggers the other. Is there a way to clip this configuration? I could have sworn that in one of the files on the jenkins server it stored that kind of information, but I can't see it anymore.
Re: controlling upstream/downstream relationships
Anyone else? There should be someway to reset this
Re: LDAP authentication fails
I'm sorta wedged at this same place now. While I can log in, the manage' page (among others) is NOT being displayed because there is now an error about First name, Last name having an invalid character in there. How do I even upgrade if I can't reach the plugin pages?
Re: Approach towards Maven profiles and Jenkins
There's a config-file-provider plugin that does what you're looking for: https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin Seems like a horrible idea to put a settings file in a source tree though There's really no way to use properties like env.computername or w/e and leverage the resources plugin to manipulate things? And Stephen is right - don't use MAVEN_OPTS, just the -D options On Thursday, April 26, 2012 4:33:47 AM UTC-4, sebasti...@softwareag.com wrote: Hi, I wonder how to best use Maven profiles on Jenkins. Our profile is stored in a settings.xml file, which is contained in our source tree. We can include this profile in Jenkins using -s path/to/settings.xml option. Usually, a developer would need to alter this file and adapt it to his working machine like including correct local hostname in some properties. How do I do that on Jenkins? I know I can ssh to the machine and make a local change, but that's probably not the best approach. Another approach could be to define specific values using the MAVEN_OPTS edit box on job configuration. Is that the preferred approach to be taken? I would be glad if people could share their experience! Thanks, Sebastian
Re: feed or notification for Jenkins releases
There's a twitter account :-/ On Thursday, April 26, 2012 2:33:41 PM UTC-4, Dan Stine wrote: I know about https://jenkins-ci.org/changelog. But I cannot locate a feed for this information, nor a low-traffic announce-style email list. Is there such a thing? Thanks, Dan
email ext mails - rooturl token wrong
Hi all - This feels like a silly question but where is this setting configured? Here, we have several jenkins master servers - all named ci-group.function.net. When I get an email now, the images are dropped off because when I view source, I can see that the image location is ci.function.net. What am I missing?
Re: email ext mails - rooturl token wrong
At ONE point, we MUST have been using the override settings because I can see the bogus url in there. But the override checkbox was NOT checked, still pulled the value. I've since put in the PROPER value, waiting for an executor to free up so my build can run... On Thursday, April 26, 2012 4:38:21 PM UTC-4, Maven User wrote: Seems like I may have hit: https://issues.jenkins-ci.org/browse/JENKINS-13242 Pulling 2.20 now... And nope, even with override disabled, still pulling bogus value On Thursday, April 26, 2012 4:25:58 PM UTC-4, Maven User wrote: Hi all - This feels like a silly question but where is this setting configured? Here, we have several jenkins master servers - all named ci-group. function.net. When I get an email now, the images are dropped off because when I view source, I can see that the image location is ci.function.net. What am I missing?
Re: Is it possible to parameterize a Subversion Repository URL location in a Jenkins build job configuration?
Have you tried global environment variables?
Jenkins has so much intelligence built into polling, seems like a shame to
ditch that for some quicky hand-rolled script :-/
On Tuesday, April 24, 2012 9:46:27 AM UTC-4, Linley wrote:
Hi,
We have a SVN structure that consists of a main parent directory
which has sub-folders for each deployable project (which happen to be
Maven Java projects). Underneath these sub-folders are the SVN
branches, tags trunk folders where the Maven Java project code
exists. For example:
http://jira/svn/JiraProject [Main parent directory]
|
|---ProjectA
||---branches
||---tags
||---trunk
| |---maven-module
| |---pom.xml
|
|---ProjectB
||---branches
||---tags
||---trunk
| |---maven-module
| |---pom.xml
|
|---etc...
Currently, we have separate Jenkins jobs for each project (i.e.
Project A, Project B, etc) which checks out the code from the
Subversion trunk directory of the specific project (e.g.
http://jira/svn/JiraProject/ProjectA/trunk), builds it using a Maven
profile and triggers another Jenkins job to deploy to an environment.
However, we are going to have a considerable number of these child
projects, so I was wondering if it is possible to have one generic
Jenkins build job rather than separate ones for each project (i.e.
ProjectA, ProjectB, etc)?
If so, how do you parameterize the SVN Repository URL (e.g.
http://jira/svn/JiraProject/${project}/trunk, where ${project} can be
passed as a parameter at runtime)?
Thanks
Re: Mercurial plugin NOT picking up merges back to the default branch
This likely won't be released until it's tested/proven. If anyone has a spare jenkins instance and can run this for a week or so (and provide it some merges to consume).. On Monday, April 23, 2012 6:49:17 PM UTC-4, Rodney Stanton wrote: We have hit the same issue. Also waiting, patiently. On Mon, Apr 23, 2012 at 4:02 AM, hezjing wrote: I'm waiting for the fix too ... our team didn't realized that we actually missed some builds because Jenkins ignored the merge changesets :-( On Tue, Feb 21, 2012 at 4:05 AM, Maven User wrote: Looking at this: https://issues.jenkins-ci.org/browse/JENKINS/component/15502 Seems like it's a mix of released and unreleased bugs/tasks/etc... How does one vote for a release of a plugin explicitly? -- Hez
Re: Maven 3 modules
What's the full use case? Also - if you're doing that - why not break them into individual repositories or modules and just rely on dependencies? Jenkins also has an option to build just what's changed. Maybe that'd be a good compromise? On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: Hi, Any clues when jenkins will support building individual modules for maven 3 ? Currently it displays message Building single Maven modules is not implemented for Maven 3, yet! -Raj
Re: Jenkins master
You may seem some fun tho as the logs for jobs are streamed back to the master (so disk io/memory may pick up). In another life, someone opted for some slow disk for the master. Quickly became a pain point. How many slaves can you have per master specs? No idea :-/ On Thursday, April 19, 2012 10:45:58 AM UTC-4, Guy wrote: AFAIK the master does not check out the project! The link to workspace takes me to the slave workspace as I have just proved by disconnecting the node and looking for the workspace,
Re: Maven does not fail builds whit test failures.
This is actually pretty normal. Generally Hudson/Jenkins OOTB mark builds unstable if the tests fail. Try adding -Dmaven.test.failure.ignore=true to your maven command line - but be forewarned - there will likely be other parts of the job that won't run and I wonder how many artifacts will be archived/brought back to the master if you do this... On Tuesday, April 17, 2012 4:16:17 PM UTC-4, edovale wrote: Folks, I am seeing the maven plugin is acting weirdly when there are test failures. I have some post build steps defined with the option to run only when build succeeds checked and they still run. Has any one experience this problem? I am running jenkins 1.459. Thanks. Erick.
Re: Maven 3 modules
Nope - expand the maven config in your project - look for the Incremental build - only build changed modules option. On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: Scenario is this : Lets say one maven projects has 5 modules. Developer changed only one module and committed it to Version control. Here i was looking for an option where developer and trigger build for only this particular module. As Jenkins surely understand root pom and modules in it and it even gives option to build individual modules but that doesnt work for maven 3 and gives the message Building single Maven modules is not implemented for Maven 3, yet! As per your suggestion i think you are refering to poll scm option in jenkins for building only what's changed ? So lets say if i enable this then jenkins will pull down only the files that got changed but what about the dependencies of these files which are not changed ? Will jenkins figure it self and bring those down too ? -Raj On Wed, Apr 25, 2012 at 7:19 AM, M What's the full use case? Also - if you're doing that - why not break them into individual repositories or modules and just rely on dependencies? Jenkins also has an option to build just what's changed. Maybe that'd be a good compromise? On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: Hi, Any clues when jenkins will support building individual modules for maven 3 ? Currently it displays message Building single Maven modules is not implemented for Maven 3, yet! -Raj On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: Scenario is this : Lets say one maven projects has 5 modules. Developer changed only one module and committed it to Version control. Here i was looking for an option where developer and trigger build for only this particular module. As Jenkins surely understand root pom and modules in it and it even gives option to build individual modules but that doesnt work for maven 3 and gives the message Building single Maven modules is not implemented for Maven 3, yet! As per your suggestion i think you are refering to poll scm option in jenkins for building only what's changed ? So lets say if i enable this then jenkins will pull down only the files that got changed but what about the dependencies of these files which are not changed ? Will jenkins figure it self and bring those down too ? -Raj On Wed, Apr 25, 2012 at 7:19 AM, Maven User: What's the full use case? Also - if you're doing that - why not break them into individual repositories or modules and just rely on dependencies? Jenkins also has an option to build just what's changed. Maybe that'd be a good compromise? On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: Hi, Any clues when jenkins will support building individual modules for maven 3 ? Currently it displays message Building single Maven modules is not implemented for Maven 3, yet! -Raj
Re: Is it possible to parameterize a Subversion Repository URL location in a Jenkins build job configuration?
Problem becomes - what happens if there are 30 jobs that need that same property? Parameters are great if you want to click build, not so hot for polling based things (or use default value I guess).
Re: Jenkins Permission
I'm sorta reading between the lines here - but first order of business might be to make sure the files you're planning on editing (programattically) exist in some resources location in your source tree then the build should process them into their final destination. If this is a non-standard build, you could also check them out, alter them then when the next build triggers, remove the workspace prior to building (also contingent on the AMOUNT of files you have). Are you actually building these things? What does this job actually do? On Wednesday, April 25, 2012 3:48:40 PM UTC-4, b_alves wrote: Hi there. I have instaled Jenkins on red hat. I have one job that is chekingout to jenkins workspace. Then I'm perrforming rsync -aC . desteni_folder so I can build/modify the files. The destination_folder is howned by another user that not jenkins. I receive:rsync: ERROR: cannot stat destination destination_folder: Permission denied (13) Can someone help me pls ? Thanks
parameterized values passed to a groovy build step
Hi all -
I have a job that needs to execute a groovy pre- step that sets a global
environment variable.
Is there anyway to do this?
I have tried the following:
for (nodeproperty in hudson.model.Hudson.instance.globalNodeProperties)
{
println(nodeproperty.getEnvVars());
nodeproperty.getEnvVars().put(FOO, nextdevversion);
hudson.model.Hudson.instance.save();
println(nodeproperty.getEnvVars());
}
and then set:
nextdevversion=NEXT_DEV_VERSION
In the variable bindings - but that just set the global environment
variable to NEXT_DEV_VERSION.
I've tried:
${NEXT_DEV_VERSION}
$NEXT_DEV_VERSION
${env.NEXT_DEV_VERSION}
None of these are the actual parameter.
Is this just not possible?
Re: parameterized values passed to a groovy build step
Not sure if anyone cares, but this is what I got working based on an
example I found on the groovy plugin page:
(there is likely way better ways to manage this)
import hudson.util.*
import hudson.model.*
// get current thread / Executor
def thr = Thread.currentThread()
// get current build
def build = thr?.executable
// ... or if you want the parameter by name ...
def hardcoded_param = NEW_PROP
def resolver = build.buildVariableResolver
def hardcoded_param_value = resolver.resolve(hardcoded_param)
for (nodeproperty in hudson.model.Hudson.instance.globalNodeProperties)
{
println(nodeproperty.getEnvVars());
if(nodeproperty.getEnvVars().get(FOO) != null)
{
nodeproperty.getEnvVars().put(FOO, hardcoded_param_value);
hudson.model.Hudson.instance.save();
println(nodeproperty.getEnvVars());
}
}
On Tuesday, April 24, 2012 4:06:46 PM UTC-4, Maven User wrote:
Hi all -
I have a job that needs to execute a groovy pre- step that sets a global
environment variable.
Is there anyway to do this?
I have tried the following:
for (nodeproperty in hudson.model.Hudson.instance.globalNodeProperties)
{
println(nodeproperty.getEnvVars());
nodeproperty.getEnvVars().put(FOO, nextdevversion);
hudson.model.Hudson.instance.save();
println(nodeproperty.getEnvVars());
}
and then set:
nextdevversion=NEXT_DEV_VERSION
In the variable bindings - but that just set the global environment
variable to NEXT_DEV_VERSION.
I've tried:
${NEXT_DEV_VERSION}
$NEXT_DEV_VERSION
${env.NEXT_DEV_VERSION}
None of these are the actual parameter.
Is this just not possible?
password masking plugin too aggressive
Hi all - I'm using the password masking plugin but when I use the maven release plugin, I can see that it's masking out other parameters (that are NOT checked in the main jenkins config section). My builds end up failing because maven is trying to retrieve a GAV of something like foo:bar: - quite literally. Obviously there's no version . Anyone else seeing these two being combined to ill effect?
Re: password masking plugin too aggressive
Yeah, it's actually not breaking the dl as expected but the fact that it's obfuscating something like foo-8.0-SNAPSHOT is nuts... On Tuesday, March 27, 2012 4:02:45 PM UTC-4, gboissinot wrote: Mask passwords plugin tries to mask passwords values line by line of the log file. If a line contains a string value matching a mask password value, the value is replaced by ''. Therefore, I think you have an another problem. Mask-passwords plugin provides here only a display issue. Hi all - I'm using the password masking plugin but when I use the maven release plugin, I can see that it's masking out other parameters (that are NOT checked in the main jenkins config section). My builds end up failing because maven is trying to retrieve a GAV of something like foo:bar: - quite literally. Obviously there's no version . Anyone else seeing these two being combined to ill effect?
Re: Mercurial plugin NOT picking up merges back to the default branch
I didn't notice the changes (I forked this plugin about a month ago tho). I just ended up creating a checkbox that allowed the user to choose if they'd like the --no-merge option during polling. I'll go take a look to see tho... On Feb 20, 9:28 am, Ringo De Smet ringo.des...@gmail.com wrote: On 17 February 2012 21:38, Maven User maven.2.u...@gmail.com wrote: Hi all - I think we're hitting this issue: https://issues.jenkins-ci.org/browse/JENKINS-12459 I'm not sure why one would ever want the --no-merges option. Shouldn't it be binary? There are changes - build, there aren't changes - don't build? Merged changes don't seem to be triggering builds I have closed that tickets as a duplicate of JENKINS-7594. If you read the comments on this ticket, you will notice that code changes have been committed to resolve this issue, but these changes haven't made it yet into a plugin release. I am also waiting for such a release, so please cast your vote to get a plugin release too! Ringo
