Re: GitHub Branch Source Plugin "trusted" pull request property in Jenkinsfile?
On Mon, 2019-03-04 at 15:28 +0100, Baptiste Mathus wrote: > This seems like a useful thing. I would recommend filing an issue in > https://issues.jenkins-ci.org/secure/Dashboard.jspa describing your > goal > and use case (after having checked it's not already filed, that is, > goes > without saying :)). Any idea which component this would be against? Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/95748efd47a5d63458872c934d15a4c673ac4bad.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
GitHub Branch Source Plugin "trusted" pull request property in Jenkinsfile?
Hi. Is the "trusted" property of a GitHub pull request (i.e. the Trust field in "Discover pull requests from forks" in the GitHub Organization configuration screen) available to a Jenkinsfile in any way? I would like to have my Jenkinsfile behave differently based on whether the PR from a fork is considered trusted or not. Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d0522b5128b9da0a08177a8fb043e43b22447a0f.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
original git sha when git[hub] commit is merged with master
Using the multibranch source plugin with github and pipelines, I notice that the commit from the github PR will sometimes be merged with remotes/origin/master and that merge commit is what GIT_COMMIT is set to which is what built and tested. I.e.: > git fetch --no-tags --progress https://github.com/foo/bar.git > +refs/pull/123/head:refs/remotes/origin/PR-123 > +refs/heads/master:refs/remotes/origin/master # timeout=10 Merging remotes/origin/master commit 33a67667a8944137ab8fb36e82cf56c98f84a40a into PR head commit 770d0ad5a3f34254702d34ef880f1502617e5888 Merge succeeded, producing efcd704e69f7ff30388067d2a999ea49d644 Checking out Revision efcd704e69f7ff30388067d2a999ea49d644 (PR-123) GIT_COMMIT is then set to efcd704e69f7ff30388067d2a999ea49d644. But in one of my pipeline steps I need to know the original PR commit sha, which is 770d0ad5a3f34254702d34ef880f1502617e5888 in this case. Is that exposed in any way during a pipeline step? Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/768473199138748efa64c2654a08bf874b9551ed.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: Incorrect visualisation of pipeline with failed stage
On Wed, 2019-01-16 at 01:22 -0800, Vitaly Karasik wrote: > I'm using Jenkins 2.151 with declarative pipeline. This pipeline has > a few > stages. > If one of stages failed, Jenkins classic UI (unlike BlueOcean) shows > all > following steps as failed, even they weren't executed at all - see > attached > screenshot. > > Any ideas how to fix that? https://issues.jenkins-ci.org/browse/JENKINS-39203 with 149 votes and 163 watchers on it. Sadly the Blue Ocean Roadmap[1] shows that over two years since the bug was reported it's not even In Progress yet. It's still only in the Planned stage. But it's been in that stage since the beginning of September at least. I suspect a lot longer than that even. This seems to me to be a really serious bug. It really almost completely invalidates the whole concept of the Pipeline job and makes the Freestyle upstream/downstream job paradigm that it's trying to replace look a lot more inviting again. Anyway, go vote for the ticket. Cheers, b. [1] https://jenkins.io/projects/blueocean/roadmap/ -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c6b29341dbf7b8031e548864b9636601d371e30f.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: fetch the api key for the current user?
On Mon, 2016-02-01 at 13:24 -0800, milki milk wrote: > > The security part comes in when you fetch an arbitrary user's key I never ever said fetch an *arbitrary* user's key. I said a job run as user Bob would fetch the key of the user (again, Bob) who ran it, who has to be already logged into Jenkins (again, as Bob) to even run the job. So it's absolutely no different from you logging into Jenkins, and going to your user/USERNAME/ page and fetching your key. > Fetching the current user's api key doesn't seem to have a REST API > equivalent. Yeah. That was the conclusion I was coming to. > Right now, I just scrape the user's configure page - > /user/USERNAME/configure - and look for the pattern -- > name="\_\.apiToken"[^>]+value="(\w+?)". I guess that's one way. Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1454363076.10065.41.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: fetch the api key for the current user?
On Sun, 2016-01-31 at 23:45 +0100, Daniel Beck wrote: > On 30.01.2016, at 19:10, Brian J. Murrell c...@public.gmane.org> wrote: > > > I am looking for a REST API handle to get the API key of the user > > that > > ran a job. > > I think any answer to this would likely be a security issue and > should be reported as such, rather than posted here. How do you figure? And what exactly are you proposing to report and to whom? This is nothing more than user Bob being able to ask the REST API, (_when_he_is_already_logged_in_to_Jenkins_), "what is my API key?" and more accurately the job that Bob run, (again when Bob has already logged in using Bob's credentials) to initiate further API calls on his behalf, because you know, Bob did ask to run the job. b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1454341086.10065.15.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
fetch the api key for the current user?
I am looking for a REST API handle to get the API key of the user that ran a job. That is, within the build steps of a job, I want to get the API key of the user running the job to use to authenticate to jenkins to carry out other activities within the job. In particular I want to use it to fetch artifacts from another job, but the fetch should be done as, and authenticated as the user running the job. Is there a way, within a job to (a) determine the userid of the user that started the job and/or (b) get that (or just the current) user's API token? Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1454177419.4249.8.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
How to enable JMX with Jenkins?
Hi. I would like to enable JMX with the Jenkins Java process but I seem to get errors such as the following when I add any of the JMX options to the "$JENKINS_ARGS" on a Linux machine startup: Running from: /usr/lib/jenkins/jenkins.war Exception in thread "main" java.lang.reflect.InvocationTargetException 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:622) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.lang.IllegalArgumentException: Multiple command line argument specified: -Dcom.sun.management.jmxremote.port=9010 at winstone.cmdline.CmdLineParser.parse(CmdLineParser.java:68) at winstone.Launcher.getArgsFromCommandLine(Launcher.java:361) at winstone.Launcher.main(Launcher.java:334) ... 6 more Ultimately my Jenkins java command line ends up being: /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Xmx3G -Dhttp.proxyHost=proxy.rr.intel.com -Dhttp.proxyPort=911 -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false --webroot=/var/lib/jenkins/war --httpsPort=8080 --httpPort=-1 --ajp13Port=-1 But that then dies pretty quickly with the above error. The errors will happen with any of the "-Dcom.sun.management.jmxremote arguments", not just the "port" one. Even if you might not know why the above is going wrong, if you have a recipe for enabling JMX, I'd appreciate hearing about it. Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1428766102.17324.11.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: java process consumes up to 200% CPU while using the UI
On Fri, 2015-04-10 at 11:31 -0400, Brent Atkinson wrote: > > You're right, but connecting locally should not require the remote ports > bound, No. You are right about that. But the problem is that the complaint is not isolated to the JMX report options. *Any* JMX option yields a complaint about duplicate options being found. > Anyone know why this doesn't work > out-of-the-box? Yes, indeed. Anyone at all? Please. > At this point, you have options: > > * figure out how to enable remote JMX (why it's failing for you) > * figure out how to enable local JMX (not sure what's involved) Right. These seem like the most fruitful paths but not really knowing anything at all about how Java applications are developed or deployed (i.e. I have no clue what a Jar is or what Winstone is, etc.) I'm kind of grasping in the dark here. > * go another route, such as the monitoring plugin (can't vouch for it) I suspect analysing it from outside (i.e. jconsole) will be more fruitful that analysing from the inside. I did manage to find out that performance is better, (but still not what I would expect) with one of the following plugins disabled: antisamy-markup-formatter.jpi.disabled ant.jpi.disabled cobertura.jpi.disabled configurationslicing.jpi.disabled credentials.jpi.disabled cvs.jpi.disabled external-monitor-job.jpi.disabled git.jpi.disabled javadoc.jpi.disabled locks-and-latches.jpi.disabled mapdb-api.jpi.disabled scm-api.jpi.disabled ssh-slaves.jpi.disabled subversion.jpi.disabled throttle-concurrents.jpi.disabled translation.jpi.disabled windows-slaves.jpi.disabled xunit.jpi.disabled xvnc.jpi.disabled But brute-force is not really the most fruitful way to go about this, particularly when disabling random plugins can actually prevent Jenkins from starting up -- leading to a yak-shaving exercise in debugging plugin dependencies. Plus the fact that even with every single plugin we have installed disabled, performance is still sluggish, just not as sluggish as with one or more of the above plugins enabled. With one or more of the above plugins enabled, job->configure is particularly slow. In any case, maybe time for a new thread on this list about how to enable JMX with Jenkins... Cheers, b. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1428765798.17324.6.camel%40interlinx.bc.ca. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Executor #0 for el6-builder1 is going to execute null
On 13-10-07 12:35 PM, Brian J. Murrell wrote: I'm trying to get an instance of Jenkins 1.530+current versions of plugins up and running but when I try to execute a multi-configuration (a.k.a. matrix) job, the child jobs are failing with: Triggering x86_64,el5 Triggering x86_64,el6.4 x86_64,el5 appears to be cancelled x86_64,el5 completed with result ABORTED x86_64,el6.4 appears to be cancelled x86_64,el6.4 completed with result ABORTED I cranked up the logging to all for this job and this is what I get in the log: hudson.matrix.MatrixProject@2d51e30[foo] added to queue Oct 08, 2013 10:51:02 AM FINE hudson.model.Queue Queue maintenance started hudson.model.Queue@4a0b1960 Oct 08, 2013 10:51:02 AM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: null; Not granted any authorities,Permission[class hudson.model.Computer,Build])=>SYSTEM user has full access Oct 08, 2013 10:51:02 AM FINE hudson.model.Executor Executor #-1 for master grabbed hudson.model.queue.WorkUnit@19d9a49d[work=foo] from queue Oct 08, 2013 10:51:02 AM FINE hudson.model.Executor Executor #-1 for master is going to execute foo #1178 Oct 08, 2013 10:51:02 AM FINE hudson.model.Executor Executor #-1 for master : executing foo #1178 is now executing foo #1178 Oct 08, 2013 10:51:02 AM FINE hudson.model.User hudson.model.User$FullNameIdResolver@7a94f797 mapped brian to brian Oct 08, 2013 10:51:02 AM FINE hudson.Proc Running: /bin/bash -xe /tmp/hudson4186123015711034487.sh Oct 08, 2013 10:51:02 AM FINE hudson.slaves.WorkspaceList Executor #-1 for master : executing foo #1178 acquired /var/lib/jenkins/jobs/foo/workspace Oct 08, 2013 10:51:02 AM FINE hudson.Proc Running: git rev-parse --is-inside-work-tree Oct 08, 2013 10:51:02 AM FINE hudson.Proc Running: git config remote.origin.url ssh://hud...@review.example.com:29418/foo Oct 08, 2013 10:51:02 AM FINE hudson.Proc Running: git fetch -t origin +refs/heads/*:refs/remotes/origin/* Oct 08, 2013 10:51:02 AM FINER hudson.security.HudsonFilter doFilter ENTRY Oct 08, 2013 10:51:02 AM FINER hudson.security.ChainedServletFilter doFilter ENTRY Oct 08, 2013 10:51:02 AM FINER hudson.security.SidACL hasPermission(PrincipalSID:org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983,Permission[class hudson.model.Hudson,Read])=>true Oct 08, 2013 10:51:02 AM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.UsernamePasswordAuthenticationToken@aa62cab2: Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 10.255.15.172; SessionId: d1418782f235664199628db1522a1bca; Granted Authorities: ROLE_IPAUSERS, authenticated, ipausers,Permission[class hudson.model.Hudson,Read])=>true Oct 08, 2013 10:51:02 AM FINER hudson.security.SidACL hasPermission(PrincipalSID:org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983,Permission[interface hudson.model.Item,Read])=>true Oct 08, 2013 10:51:02 AM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.UsernamePasswordAuthenticationToken@aa62cab2: Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 10.255.15.172; SessionId: d1418782f235664199628db1522a1bca; Granted Authorities: ROLE_IPAUSERS, authenticated, ipausers,Permission[interface hudson.model.Item,Read])=>true Oct 08, 2013 10:51:02 AM FINE hudson.model.Queue Queue maintenance started hudson.model.Queue@4a0b1960 Oct 08, 2013 10:51:02 AM FINER hudson.security.SidACL hasPermission(PrincipalSID:org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983,Permission[interface hudson.model.Item,Build])=>true Oct 08, 2013 10:51:02 AM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.UsernamePasswordAuthenticationToken@aa62cab2: Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 10.255.15.172; SessionId: d1418782f235664199628db1522a1bca; Granted Authorities: ROLE_IPAUSERS, authenticated, ipausers,Permission[interface hudson.model.Item,Build])=>true Oct 08, 2013 10:51:02 AM FINER hudson.security.SidACL hasPermission(PrincipalSID:org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983,Permission[interface hudson.model.Item,Workspace])=>true Oct 08, 2013 10:51:02 AM FINE hudson.security.SidACL hasPermission(org.acegisecurity.providers.UsernamePasswordAuthenticationToken@aa62cab2: Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@56e6f983; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.
Re: SEVERE: Executor threw an exception
On 13-10-07 12:35 PM, Brian J. Murrell wrote: I'm trying to get an instance of Jenkins 1.530+current versions of plugins up and running but when I try to execute a multi-configuration (a.k.a. matrix) job, the child jobs are failing with: Triggering x86_64,el5 Triggering x86_64,el6.4 x86_64,el5 appears to be cancelled x86_64,el5 completed with result ABORTED x86_64,el6.4 appears to be cancelled x86_64,el6.4 completed with result ABORTED Just to update on this issue, I've updated Jenkins to 1.534 and the problem persists, unfortunately. Any advise welcome. Cheers, b. -- 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.
SEVERE: Executor threw an exception
I'm trying to get an instance of Jenkins 1.530+current versions of plugins up and running but when I try to execute a multi-configuration (a.k.a. matrix) job, the child jobs are failing with: Triggering x86_64,el5 Triggering x86_64,el6.4 x86_64,el5 appears to be cancelled x86_64,el5 completed with result ABORTED x86_64,el6.4 appears to be cancelled x86_64,el6.4 completed with result ABORTED When I look in the /var/log/jenkins/jenkins.log all it tells me is: Oct 7, 2013 9:24:36 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:243) Oct 7, 2013 9:24:36 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:243) Oct 7, 2013 9:24:44 AM hudson.model.Run execute INFO: foo #1162 main build action completed: ABORTED Oct 7, 2013 9:24:44 AM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onCompleted INFO: Completed. Build: foo #1162 Cause: null I am able to successfully run things on the slaves using the Jenkins->Nodes->...->Script Console so I know the slaves are connected and generally operational. Is there any way I can get more information about what the problem is exactly? Cheers, b. -- 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.
ldap: using uid to bind instead of cn
It would seem that when using the LDAP authentication plugin that the bind attempt to the LDAP server to verify the user credentials is trying to bind using the CN DN. Our LDAP server (AD) is configured to allow binding using the e-mail address of the user rather than their CN (easier to remember I guess since the CN is quite long). Is there any way to configure the LDAP plugin to bind using the user's e-mail address rather than a CN DN for the bind credential? Cheers, b. -- 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: Execute Clean Up on Build Cancel
On 13-05-02 09:36 PM, Eric Blom wrote: > > trap "/home/jenkins/tmp/cleanup.sh" INT TERM There is also the "EXIT" pseudo-signal available in bash. > On the command line I'm testing with Ctrl+C (INT). Based on the webpage below > I believe SIGTERM (TERM) should work for Jenkins' cancel button Yes, an aborted Jenkins job step should get a SIGTERM b. signature.asc Description: OpenPGP digital signature
Re: Role based Authorization for “Logged in user can do anything” in Jenkins
On 13-01-12 09:52 AM, uma shankar wrote: > > Summarize the question: I actually want to add group of user who will be > admin, Other than that, if any user try to login, they should still be > able to login (if authentication is success via LDAP) but they should only > have build trigger and read the console output permission. Matrix-based security or optionally Project-based Matrix Authorization Strategy. Cheers, b. signature.asc Description: OpenPGP digital signature
use tags instead of build numbers in URLs
Anyone know of any way or plugin that allows the use of tag names in Jenkins URLs rather than build numbers. i.e. if I have a job named "foo", I can get build #10's result for it with: http://jenkins/job/foo/10/ But if I've set a tag for that build as "1.2.4" I'd like to be able to use: http://jenkins/job/foo/1.2.4/ To navigate to it. Clearly there's a problem when two builds have the same tag, in which case I'd prefer to always find the most recent, barring any further nomenclature to differentiate between the multiply same-named tags. Multiply-used tags is not a real problem for me though. Cheers, b. signature.asc Description: OpenPGP digital signature
Re: JNLP slave no longer works
On 13-01-11 08:44 AM, Les Mikesell wrote: > > Doesn't the connecting node name already have to be configured in > jenkins Sure. But if anonymous read is allowed, anyone can see the node names. > - and not already connected? Is disconnecting a node really that difficult? You could try attacking a vulnerability or even simply DDoS it. Or even just wait for some network/node flap and jump in while it's not connected. b. signature.asc Description: OpenPGP digital signature
Re: JNLP slave no longer works
On 13-01-11 05:55 AM, matthew.web...@diamond.ac.uk wrote: > > Fixed by going to Manage Jenkins -> Configure Global Security, and under > Project-based Matrix Authorization Strategy I had to enable “connect” in the > “slave” section, for user “Anonymous”. IIUC, that's going to leave your Jenkins server open to allowing any random (i.e. blackhat) slave to connect, accept a build job and submit a build result with a trojan inserted. So not really an acceptable solution, or even work-around. b. signature.asc Description: OpenPGP digital signature
Re: JNLP slave no longer works
On 13-01-11 07:58 AM, SBreitbach wrote: > The slave.jar from LTS 1.480.2 version has parameters "-auth" and > "-jnlpCredentials". I discovered that the -auth in 1.498 also doesn't work. I grabbed the packets that the slave was sending to the jenkins server on connect and there is absolutely no authentication credentials in them, even with -auth account:password being set. > I consider the "manually download the jnlp file" as a very dirty > quickhack... +1 b. signature.asc Description: OpenPGP digital signature
gerrit trigger build on push to refs/heads/*?
Hi, I wonder if there is any way to configure the gerrit trigger to trigger builds on pushes to refs/heads/* as was as the usual refs/for/*. Cheers, b. signature.asc Description: OpenPGP digital signature
Re: Send over ftp only changed scm files
On 12-06-12 02:10 PM, Roy wrote: > There are some way to do that? > > I'm trying to do find some plugin or solution since yesterday. > Can someone help me? I don't know about anyone else but I don't think I really understand what it is you want. b. signature.asc Description: OpenPGP digital signature
Re: user defined axis
On 12-06-07 07:59 AM, Arun Kumar wrote: > But my problem i am not able to execute the above code step. Right. I wasn't saying it was possible. I was saying that I have an RFE open to allow the parent job to define the axis combinations to build. Either by build steps (my use-case) or by passing parameters (your use-case). b. signature.asc Description: OpenPGP digital signature
refer to jobs by something other than their build number -- like an alias or tag
I have a need to be able to refer to build jobs by something other than their build number. To be perfectly clear, I want to be able to access a particular job's artifacts but I might not know the number of the job. I would know a "tag" or "alias" for it though. Given for example a URL on my jenkins server of: http://jenkins/job/foo/arch=x86_64,distro=el6/182/artifact/ I would like to replace the "182" with something more "friendly" and static. Call it say "1.0.1" if it were the build that were released as version 1.0.1 of my project. Then I could predictably access: http://jenkins/job/foo/arch=x86_64,distro=el6/1.0.1/artifact/ and know I'd be getting the artifacts for whatever build was tagged/aliased with that value. Does any such thing exist, as a plugin or otherwise? Cheers, b. signature.asc Description: OpenPGP digital signature
Re: user defined axis
On 12-06-07 07:06 AM, Arun Kumar wrote: > Hi Brian, > > My requirement is like the variable value i give may differ everytime i > execute the job. Like i may give "fruits=apple banana coconut" one time and > next time it will be different value. So i want to take that as a variable > to inject different values. Next time i may give "fruits=mango" Right. Just as I said: "You want a build parameter in the parent job to set the [axis]" (I said hosts but that was just bias from my need). > So execution of the job should be when i give 3 fruit names there will > concurrent execution of jobs for 3 fruits at a time. And when i give 1 > there will be one execution at all. Right. Ultimately your parent job will be a matrix job, and parameterized and the value of the axis comes from the parameter. In my case, build steps would define the axis values. It's really one and the same: the parent job defines the axis values for the child jobs dynamically. Either with a parameter or with build steps. b. signature.asc Description: OpenPGP digital signature
Re: user defined axis
On 12-06-05 05:50 AM, Arun Kumar wrote:
> Hi,
Hi,
> *Parameters:*
> *
> *
> fruits=apple banana coconut
>
> Configuration Matrix : User-defined Axis
> Name : PRODUCTS
> Values : $fruits
> Build
> Execute shell
> Command : build ${PRODUCT}
Do you mean something along the lines of this:
https://issues.jenkins-ci.org/browse/JENKINS-9266. You want a build
parameter in the parent job to set the hosts, I want build steps. They
are just variants of the same thing IMHO.
b.
signature.asc
Description: OpenPGP digital signature
preventing use of certain nodes in matrix jobs
I have my builders labeled with labels like: builder1: x86_64 el6 builder2: x86_64 el5 builder3: i686 el6 builder4: i686 el5 I then make matrix-build jobs that have axes (called "arch" and "distro", respectively) for x86_64/i686 and el5/el6 and then let jenkins figure out which nodes to run the matrix combinations on. I now need to add a new builder: builder5: x86_64 el6 foo which should only be used to build a given job named "foo". The other builders should be able to build foo but other build jobs should not be allowed to use builders with the label "foo". How can I achieve this? I know I could label builder5 with "x86_64 el6-foo" but that doesn't achieve my goal of allowing "foo" to build on any el6 node and also changes up the value of "distro" for the build foo so that it's inconsistent with my other jobs. Any way to do this at all? b. signature.asc Description: OpenPGP digital signature
Re: Promoted Builds Plugin: Does not automatically promote despite qualifications being met
On 12-04-12 02:29 PM, Nicky Ramone wrote: > > Another problem I'm having is that when you manually promote a build that > triggers a downstream build, the triggered downstream build does not > include information from the upstream project, which is a big problem. Yes, I agree. I posted a message only a few days ago about this. The answer seemed to be to use a parameterized trigger, which does work, but this behavior really seems like it ought to be implied. If one executes a downstream build from a promotion, I'd say there is a good chance the downstream job wants to know about why it was triggered so that it can act accordingly. i.e. operate on the artifacts of the upstream job/build -- in this case the promoted build. b. signature.asc Description: OpenPGP digital signature
serializing actions in a promotion process
I have a promotion configuration using the Promoted Builds Plugin. This configuration includes the building of two other jobs in it's Actions list, specifically two "Trigger parameterized build on other projects" items. These seem to happen in parallel though and I would like to force them to happen serially. Additionally, I would like to copy the build artifacts of the first one run in the second one. I think I would be able to do that if the new build number of the first executed project was added to the environment of process running the actions, so then I could pass it to the second job as a parameter. One way of achieving this is of course to combine the two jobs into a single one but the reality is that one of the jobs is called elsewhere so combining it's steps into this first job would be a duplication and future synchronization nightmare. Any ideas? Cheers, b. signature.asc Description: OpenPGP digital signature
Re: how to get access to the data for the job being promoted?
On 12-04-10 04:54 PM, Sami Tikka wrote: > You do not exactly come clean on what kind of "data" it is you are looking > for. Well, specifically, I was looking to know in the executed job which job was being promoted. > If you want access to promoted build artifacts, Copy Artifacts plugin > gives that in the triggered build in Specific build -> Last promoted This sounds racy, but moot in any case since there is no mention of anything to do with promoted builds in the list of artifacts available for copying. But that's ok, see below... > If it is something else you want, you could maybe send it over as a > parameter. Yes, this is what I was looking for! > Use the parameterized trigger in the promotion action to > send what ever "data" you want to pass to the triggered job. Yeah. I hadn't realized that any action plugin that I add would be available as a promotion action. Simply installing the parameterized trigger plugin I was able to send the PROMOTED_* variables to the downstream job. Thanks much! b. signature.asc Description: OpenPGP digital signature
Re: how to get access to the data for the job being promoted?
On 12-04-10 11:44 AM, Brian J. Murrell wrote: > Using the Promoted Builds Plugin, I'm choosing to execute another job as > an action of the promotion. How do I get information on the job and > build that's being promoted in the job steps of the job that the > promotion action starts? Still wondering, but that's not the point of my followup here... > I've seen hints about a $PROMOTED_URL variable (i.e. TODO: Talk about > PROMOTED_URL in > https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin) but > that doesn't seem to be set in my promotion action job. That variable seems available to the job steps one writes directly in a promotion's own "Execute shell" action but doesn't seem to be given to any jobs that a promotion starts with the "Build other projects" actions. So is there really no way for a job to know that it's being executed as an action of a promotion of another job and which job it's being built for? Cheers, b. signature.asc Description: OpenPGP digital signature
access the latest promoted job similar to "lastSuccessful"?
In the same way that I can access a job (with it's log and artifacts, etc.) through the "lastSuccessfulBuild" alias (i.e. http://localhost:8080/job/foo/lastSuccessfulBuild/arch=x86_64,distro=el6/), is there any similar type aliases to get to the last job that was promoted with a given promotion name? I'm imagining for example, given a job foo with a promotion name of bar: http://localhost:8080/job/foo/promotion/bar/lastSuccessfulBuild/... Cheers, b. signature.asc Description: OpenPGP digital signature
how to get access to the data for the job being promoted?
Using the Promoted Builds Plugin, I'm choosing to execute another job as an action of the promotion. How do I get information on the job and build that's being promoted in the job steps of the job that the promotion action starts? I've dumped the environment in the job steps of the job the action starts and there is no sign of any information about the particular build that is being promoted. I've seen hints about a $PROMOTED_URL variable (i.e. TODO: Talk about PROMOTED_URL in https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin) but that doesn't seem to be set in my promotion action job. Cheers, b. signature.asc Description: OpenPGP digital signature
Promoted Builds Plugin: promote downstream jobs also
I am using the Promoted Builds Plugin to manually promote some of my builds of a project called foo. Everytime foo builds though it builds a downstream job called bar. Is there any way I can make the Promoted Builds Plugin also promote the particular downstream bar that the foo that I'm promoting built? So that is if I chose to promote build #32 of foo and build #32 of foo caused build #12 of bar to build, also (automatically) promote build #12 of bar. Thanks, b. signature.asc Description: OpenPGP digital signature
promotion plugin: multiple levels of promotion
The Promoted Builds Plugin description page (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin) says: In more complicated scenarios, one can set up multiple levels of promotions. This fits nicely in an environment where there are multiple stages of testings (for example, QA testing, acceptance testing, staging, and production.) That's exactly the scenario I want to set up. I have the promotion plugin installed and I created a promotion called "blessed". I promoted one of my builds with it just fine. I'm at a loss however how I create a promotion option that will let me promote (only) "blessed" promotions to my next level acceptance. Any hints would be appreciated. Thanks, b. signature.asc Description: OpenPGP digital signature
