Re: POST key build data to a REST API after the build is complete
Read /job/jobname/build_number/api On 29.08.2014, at 11:26, ckyconsultinguk wrote: > Dear Friends, > > I would like to POST key build information (ex: Job name, status of build > ok/failed, revision number of the repository and if possible the results) via > POST to a REST API from jenkins once after each build is complete. Is it > possible ? > > I tried the 'Post Completed Build Results' plugin but it is only posting the > build url ex: http://jenkins.mydomain.com/job/jobname/buid_number. How can I > now pull information using this url from external servers ? If I can do this > then that is ok too. > > Thanks, > -geek876 > > -- > 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. -- 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: build timeout plugin - JVMs from aborted builds not killed
You forgot to mention your Jenkins version. Killing processes was broken on Linux from 1.553-1.574. On 28.08.2014, at 11:48, ptol...@tibco.com wrote: > We have a regressions server, running regressions of different applications, > using Jenkins. > > Some of these applications, tend to misbehave during the regression run, and > the build needs to be aborted. The runtimes of these applications are a mix > of JVM and native code, interfaced via JNI, and also httpd instances. > > Now, in our setup, we have the build timeout plugin configured. Typically > this is set as follows (with time out action being Abort the build on some > jobs and Fail the build on some jobs). > > > > Now, what we see is that when a build fails, the JVMs and servers and httpd > instances corresponding to the build are still up. This keeps happening for a > series of jobs, the OS runs out of memory and this crashes the machine. > > We have confirmed these process have JENKINS_SERVER_COOKIE environment > variable set, so jenkins should in principle be able to clean them up. > > Looking at the documentation for build timeout plugin > (https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) I see > > Because Java only allows threads to be interrupted at a set of fixed > locations, depending on how a build hangs, the abort operation might not take > effect. For example, > * if Jenkins is waiting for child processes to complete, it can abort > right away. > * if Jenkins is stuck in an infinite loop, it can never be aborted. > * if Jenkins is doing a network or file I/O within the Java VM (such as > lengthy file copy or SVN update), it cannot be aborted. > So if you think the build time out isn't taking effect, our default > assumption is that the build is hanging at the place that cannot be > interrupted. If you suspect otherwise, please obtain the thread dump and > report it. > > > So am planning to collect the thread dump for the next set of runs and > understand the issue better. > > Also I was thinking of enabling more logs for the build timeout plugin. > Looking at the configure logging help page, > https://wiki.jenkins-ci.org/display/JENKINS/Logging, looks like I need the > name of the logger to configure for detailed logging. > > > > Can someone help me with the name of the logger to configure, please? > > Also any other pointers to debug the issue at hand would be more than welcome > ... > > thanks and regards, > pankaj > > -- > 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. -- 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: Masking build environment variables on env variables screen
If you're using Env-Inject, try using its built-in password support instead of Mask Passwords. On 26.08.2014, at 01:50, Marc Esher wrote: > Greetings, > > I'm using env inject and mask passwords, which works great in the console > output for jobs. However, Any global password variables I set show up in > plaintext on a build's Environment Variables screen. > > Is there a way to mask or remove variables from that Build env variables > screen? > > Thanks, > > Marc > > -- > 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. -- 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: Unable to startup slave post master upgrade to 1.576
When searching the web for the original error message (the last line in the console that starts with 'Caused by'), what did the first page of search results suggest is the cause? What happened when you followed the advice you found? On 24.08.2014, at 20:32, Sudhakar.Shanmugam wrote: > I have master/3 slave configuration, post upgrade from 1.500 to 1.576, master > and slave#1 came up without issues, however slaves 2&3 are not starting up. > > All running on OS RHEL 5.10 > > I'm seeing below error in the console log. > > JNLP agent connected from /10.64.10.33 > <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection with > the slave node3 > java.io.IOException: Remote call on node3 failed > at hudson.remoting.Channel.call(Channel.java:748) > at > hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:453) > at > jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) > at > jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) > at > jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) > at > jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) > at > hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156) > Caused by: java.lang.ClassFormatError: Failed to load > hudson.slaves.SlaveComputer$SlaveVersion > at > hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:193) > at > hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:144) > at java.lang.ClassLoader.loadClass(ClassLoader.java:631) > at java.lang.ClassLoader.loadClass(ClassLoader.java:597) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:163) > at > hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:113) > at > java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1568) > at > java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1490) > at > java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1723) > at > java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) > at > java.io.ObjectInputStream.readObject(ObjectInputStream.java:363) > at > hudson.remoting.UserRequest.deserialize(UserRequest.java:182) > at hudson.remoting.UserRequest.perform(UserRequest.java:98) > 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:284) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at hudson.remoting.Engine$1$1.run(Engine.java:58) > at java.lang.Thread.run(Thread.java:810) > Caused by: java.lang.UnsupportedClassVersionError: > (hudson/slaves/SlaveComputer$SlaveVersion) bad major version at offset=6 > at java.lang.ClassLoader.defineClassImpl(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:258) > at java.lang.ClassLoader.defineClass(ClassLoader.java:195) > at > hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:191) > ... 22 more > ERROR: Connection terminated > java.nio.channels.AsynchronousCloseException > at > java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) > at > sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) > at > hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:35) > at > sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) > at > sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) > at > sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.InputStream.read(InputStream.java:101) > at > sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) > at > hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) > at > java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293)
Re: Release notes from XX previous build change logs in Markdown
Looks like JENKINS-12032, which I haven't yet begun work on. Feel free to take over. On 23.08.2014, at 02:46, Brantone wrote: > Looking to publish release notes based on change logs from SCM commit > messages .. and preferably in Markdown, but plain text will do ... alas, > surprised no plugin exists (that I can find), so curious how others handle > such a scenario, or else I guess I'm writing a plugin :) > I do have > https://wiki.jenkins-ci.org/display/JENKINS/Changes+Since+Last+Success+Plugin > ; however, formatting for that is machine (html, xml, json), but nothing just > plain text. > Quick scan of mailing list didn't reveal anything "ah ha!", so wondering if > this is such a unique situation, or already solved and it's obvious I'm just > not seeing it. > > Cheers. > > -- > 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. -- 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: Possible culprit? Re: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
There's a known issue with CLI authentication via --username not working for some commands in Jenkins 1.538-1.576. Try using SSH key based authentication. On 22.08.2014, at 17:58, G Dameron wrote: > I think I may be on to something, and I think it's related to the issue > https://issues.jenkins-ci.org/browse/JENKINS-21086 I mentioned in my OP. The > system log responds this way when I try to to a get-job on project_B: > > Aug 22, 2014 9:23:07 AM WARNING > hudson.cli.handlers.GenericItemOptionHandler$1 run > running as anonymous could not find > hudson.model.FreeStyleProject@2130a9c[project_B] of class > hudson.model.AbstractItem > > I still have the "login" just before it, as recommended in the issue. I even > tried (a) appending the --username and --password args to the get-job, and > even (b) opening up Overall/Read to the anonymous user, then using the > "restart" URL to restart the server. Still no joy. > > (Thanks, Daniel, for hanging in there through my struggle.) > > > On Thursday, August 21, 2014 6:56:21 PM UTC-6, Daniel Beck wrote: > What kind of project is it (e.g. freestyle, maven, multijob, build flow, > ...)? What plugin provides it? > > On 22.08.2014, at 02:31, G Dameron wrote: > > > Just alphanumerics and underscores in the name. We're not using any > > CloudBees plugins. > > > > On Thursday, August 21, 2014 6:14:16 PM UTC-6, Daniel Beck wrote: > > Are there leading/trailing spaces in the project name? Characters that are > > not basic printable ASCII, preferably alphanumeric, e.g. characters with > > special meaning on the command line, like the dollar sign? > > > > Are you using the Cloudbees Folders plugin, and the job is actually in a > > folder? Other than changing project names, are the java calls in your first > > question unmodified (e.g. no parameters removed)? > > > > On 22.08.2014, at 02:01, G Dameron wrote: > > > > > The job name I'm using meets the URL criterion. (It also meets the > > > "snowman" criterion, which implies the job's "real name" and "display > > > name" are identical, if I'm understanding you correctly). Is there any > > > other string I could/should use for the get-job argument? > > > > > > On Thursday, August 21, 2014 5:43:33 PM UTC-6, Daniel Beck wrote: > > > If it says '/job/foo' in the URL when you view the job, 'foo' is its > > > name. Even if it says something like "Project ☃" on the page you're on, > > > in that case '☃' is its display name. (That character used for the > > > display name is supposed to be the Unicode snowman U+2603 if your email > > > client doesn't display it.) > > > > > > To the best of my knowledge, there is no way to determine a project's > > > name from the CLI if the project has a differing display name and the > > > name is not already known, short of writing a plugin or patching Jenkins. > > > > > > On 22.08.2014, at 01:33, G Dameron wrote: > > > > > > > What does a job's "real name" look like? > > > > Is there a string I can build up from known parts that would convince > > > > "get-job" that it's a legitimate argument? > > > > > > > > On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: > > > > It's likely the following: > > > > > > > > list-jobs shows the project's _display name_, but as parameter to > > > > commands you need to specify the project's real _name_. > > > > > > > > It's mind-bogglingly stupid, and there is currently no solution other > > > > than not using display names for projects, or patching Jenkins. > > > > > > > > A possible solution is tracked as JENKINS-22301. > > > > > > > > -- > > > > 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. > > > -- > 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. -- 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: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
What kind of project is it (e.g. freestyle, maven, multijob, build flow, ...)? What plugin provides it? On 22.08.2014, at 02:31, G Dameron wrote: > Just alphanumerics and underscores in the name. We're not using any CloudBees > plugins. > > On Thursday, August 21, 2014 6:14:16 PM UTC-6, Daniel Beck wrote: > Are there leading/trailing spaces in the project name? Characters that are > not basic printable ASCII, preferably alphanumeric, e.g. characters with > special meaning on the command line, like the dollar sign? > > Are you using the Cloudbees Folders plugin, and the job is actually in a > folder? Other than changing project names, are the java calls in your first > question unmodified (e.g. no parameters removed)? > > On 22.08.2014, at 02:01, G Dameron wrote: > > > The job name I'm using meets the URL criterion. (It also meets the > > "snowman" criterion, which implies the job's "real name" and "display name" > > are identical, if I'm understanding you correctly). Is there any other > > string I could/should use for the get-job argument? > > > > On Thursday, August 21, 2014 5:43:33 PM UTC-6, Daniel Beck wrote: > > If it says '/job/foo' in the URL when you view the job, 'foo' is its name. > > Even if it says something like "Project ☃" on the page you're on, in that > > case '☃' is its display name. (That character used for the display name is > > supposed to be the Unicode snowman U+2603 if your email client doesn't > > display it.) > > > > To the best of my knowledge, there is no way to determine a project's name > > from the CLI if the project has a differing display name and the name is > > not already known, short of writing a plugin or patching Jenkins. > > > > On 22.08.2014, at 01:33, G Dameron wrote: > > > > > What does a job's "real name" look like? > > > Is there a string I can build up from known parts that would convince > > > "get-job" that it's a legitimate argument? > > > > > > On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: > > > It's likely the following: > > > > > > list-jobs shows the project's _display name_, but as parameter to > > > commands you need to specify the project's real _name_. > > > > > > It's mind-bogglingly stupid, and there is currently no solution other > > > than not using display names for projects, or patching Jenkins. > > > > > > A possible solution is tracked as JENKINS-22301. > > > > > > -- > > > 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-users+unsubscr...@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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
Are there leading/trailing spaces in the project name? Characters that are not basic printable ASCII, preferably alphanumeric, e.g. characters with special meaning on the command line, like the dollar sign? Are you using the Cloudbees Folders plugin, and the job is actually in a folder? Other than changing project names, are the java calls in your first question unmodified (e.g. no parameters removed)? On 22.08.2014, at 02:01, G Dameron wrote: > The job name I'm using meets the URL criterion. (It also meets the "snowman" > criterion, which implies the job's "real name" and "display name" are > identical, if I'm understanding you correctly). Is there any other string I > could/should use for the get-job argument? > > On Thursday, August 21, 2014 5:43:33 PM UTC-6, Daniel Beck wrote: > If it says '/job/foo' in the URL when you view the job, 'foo' is its name. > Even if it says something like "Project ☃" on the page you're on, in that > case '☃' is its display name. (That character used for the display name is > supposed to be the Unicode snowman U+2603 if your email client doesn't > display it.) > > To the best of my knowledge, there is no way to determine a project's name > from the CLI if the project has a differing display name and the name is not > already known, short of writing a plugin or patching Jenkins. > > On 22.08.2014, at 01:33, G Dameron wrote: > > > What does a job's "real name" look like? > > Is there a string I can build up from known parts that would convince > > "get-job" that it's a legitimate argument? > > > > On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: > > It's likely the following: > > > > list-jobs shows the project's _display name_, but as parameter to commands > > you need to specify the project's real _name_. > > > > It's mind-bogglingly stupid, and there is currently no solution other than > > not using display names for projects, or patching Jenkins. > > > > A possible solution is tracked as JENKINS-22301. > > > > -- > > 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
If it says '/job/foo' in the URL when you view the job, 'foo' is its name. Even if it says something like "Project ☃" on the page you're on, in that case '☃' is its display name. (That character used for the display name is supposed to be the Unicode snowman U+2603 if your email client doesn't display it.) To the best of my knowledge, there is no way to determine a project's name from the CLI if the project has a differing display name and the name is not already known, short of writing a plugin or patching Jenkins. On 22.08.2014, at 01:33, G Dameron wrote: > What does a job's "real name" look like? > Is there a string I can build up from known parts that would convince > "get-job" that it's a legitimate argument? > > On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: > It's likely the following: > > list-jobs shows the project's _display name_, but as parameter to commands > you need to specify the project's real _name_. > > It's mind-bogglingly stupid, and there is currently no solution other than > not using display names for projects, or patching Jenkins. > > A possible solution is tracked as JENKINS-22301. > > -- > 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. -- 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: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
It's likely the following: list-jobs shows the project's _display name_, but as parameter to commands you need to specify the project's real _name_. It's mind-bogglingly stupid, and there is currently no solution other than not using display names for projects, or patching Jenkins. A possible solution is tracked as JENKINS-22301. On 22.08.2014, at 01:03, G Dameron wrote: > I can successfully run the list-jobs CLI: > java -jar /path/to/jenkins-cli.jar -s http://my_server.com:8080/ list-jobs > and get a full listing of all the project names on my server: > project_A > project_B > project_C > ... > > But if I try to get one of them: > java -jar /path/to/jenkins-cli.jar -s http://my_server.com:8080/ get-job > project_B > ... I get this: > No such job 'project_B' > <... get-job's usage information ...> > > I'm on 1.563. I get the same behavior inside a Jenkins job as I do with a > standalone bash script. > > [FYI: We're using LDAP authentication, and both my Jenkins job and my > standalone bash script have the two CLI commands above preceded by a "login", > per the workaround shown in > https://issues.jenkins-ci.org/browse/JENKINS-21086. I've also done a reload > config from disk, but it didn't help.] > > Bound to be something simple. What am I missing here? > > > -- > 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. -- 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 upgrade 1.576 issue
Known issue: https://issues.jenkins-ci.org/browse/JENKINS-24316 On 20.08.2014, at 06:15, Rajesh Patwardhan wrote: > Hello, > > We just upgraded to 1.576 on Centos (CentOS release 5.8 (Final)) > > Some of the plugin images are gone missing from the site. The images > themselves are on the disk > > 110934464 -rw-r--r-- 1 jenkins jenkins 1572 Aug 11 21:31 > plugins/credentials/images/24x24/credentials.png > > -rw-r--r-- 1 jenkins jenkins 3981 Nov 18 2013 > plugins/claim/icons/claim-48x48.png > > I kind of see the issue but don't know how to fix it (or even if I am looking > in the right direction) > > > here is the url \ images show correct i.e. that works : > style="width: 24px; height: 24px; margin: 2px;" alt="" > src="/static/e3ea21a2/plugin/credentials/images/48x48/credentials.png" /> > > Here is the url \ image shows broken i.e. that does not work: > > src="//plugin/claim/icons/claim-24x24.png" /> href="/claims">Claim Report > > > Any help in the right direction will be greatly appreciated. > > Regards, > Rajesh > > > -- > 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. -- 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 multijob plugin not loading
Make sure EnvInject plugin is installed and enabled. On 19.08.2014, at 11:45, John McGowan wrote: > Anyone seen this error before. Tried added multijob to a well established LTS > server (I have it on another server ok, same version but different plugin > set). > Jenkins ver. 1.565.1 > > 18-Aug-2014 10:56:38 hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 > error > WARNING: Failed to instantiate > Key[type=com.tikal.jenkins.plugins.multijob.MultiJobBuilder$DescriptorImpl, > annotation=[none]]; skipping this component > com.google.inject.ProvisionException: Guice provision errors: > > 1) Error injecting constructor, java.lang.NoClassDefFoundError: > org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter > at > com.tikal.jenkins.plugins.multijob.MultiJobBuilder$DescriptorImpl.(Unknown > Source) > > 1 error > at > com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) > at com.google.inject.Scopes$1$1.get(Scopes.java:65) > at > hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) > at > com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) > at > com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) > at > com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) > at > com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) > at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) > at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) > at hudson.ExtensionFinder._find(ExtensionFinder.java:151) > at > hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:341) > at hudson.ExtensionList.load(ExtensionList.java:295) > at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) > at hudson.ExtensionList.iterator(ExtensionList.java:138) > at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1192) > at > hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:99) > at > hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) > at hudson.PluginManager$2$1$2.run(PluginManager.java:376) > at > org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) > at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) > 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:679) > Caused by: java.lang.NoClassDefFoundError: > org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2444) > at java.lang.Class.getMethod0(Class.java:2687) > at java.lang.Class.getMethod(Class.java:1620) > at hudson.model.Descriptor.(Descriptor.java:283) > at > hudson.tasks.BuildStepDescriptor.(BuildStepDescriptor.java:56) > at > com.tikal.jenkins.plugins.multijob.MultiJobBuilder$DescriptorImpl.(MultiJobBuilder.java:443) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at > com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) > at > com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) > at > com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) > at > com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) > at > com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) > at > com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) > at > com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) > ... 25 more > Caused by: java.lang.ClassNotFoundException: > org.jenkinsci.plugins.envinject.service.EnvInjectVariableGetter > at > jenkins.util.AntClassLoader.findClassIn
Re: How can i pass build properties to downstream build ?
Try Parameterized Trigger Plugin. On 17.08.2014, at 15:48, Alex Brodov wrote: > Hi, > I have a few jobs, for example job A which is the upstream and job B which is > the downstream, i've defined some properties in job A: > Build Environment -> marked the "Inject environment variables to the build > process" checkbox -> and added a few properties to the "Properties Cintent" > text box such as: > HOME_DIR = home path, and so on. > I'm trying to figure out how can i access those properties from my downstream. > Should i install some plugins? > > Thanks, > Alex > > -- > 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. -- 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: Lookings for Jenkins version used by JENKINS_HOME
That's (mostly) the correct version. This field is updated whenever the Jenkins system configuration is saved. If you don't do that, the file isn't getting updated. "1.0" written to the file can happen when you save only e.g. the security configuration and never the system configuration, at most very early in an instance's lifetime. On 17.08.2014, at 08:00, Dan Tran wrote: > For disaster recovery, we dont have the jenkins installation but only the > JENKINS_HOME from the backup. Now need to find the Jenkins version was used. > By looking at JENKINS_HOME/config.xml, looks like tag the right > place, however its value is undermine. I am seeing the value varies from 1.0 > to the actually jenkins version ( 1.5xxx) > > Am I looking at the right place? > > Thanks > > -D > > -- > 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. -- 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: Adding an administrative build (job)
This looks like Build Flow DSL, and you need to specify parameters in there --
parameterized trigger plugin is a completely different way to trigger builds,
but you didn't mention Build Flow earlier.
How to pass parameters using Build Flow (and how to get the environment
available to the build flow, including parameters) is documented here:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin#BuildFlowPlugin-Basics
On 14.08.2014, at 22:39, Alex Brodov wrote:
> Hi Daniel,
> Thanks for your response, I've installed this plugin.
> I'm going to tell you what I've done and where is my problem now:
> 1) I've created an upstream build which is managing 2 builds for now
> 2) I've added a DLS to this build (a flow) - for example
> Build ("B")
> Build("C")
> 3) I've added a parameterized String field in the upstream and I gave it a
> name "VERSION_NUMBER" .
> 4) In the post-build Actions of the upstream job I've added 'Triger
> parameterized build on other projects' and chose current build parameters ->
> then tried to access this parameter from one of my scripts that are running
> on downstream and it printed {env.VERSION_NUMBER} and not the value that i've
> entered. Maybe i need to configure anything else in the downstream?
> Thanks,
> Alex
>
> On Aug 14, 2014 2:29 PM, "Daniel Beck" wrote:
> Parameterized Trigger Plugin
>
> On 14.08.2014, at 10:54, Alex Brodov wrote:
>
> > Hi,
> > i'm trying to figure out how can i add an administrative build to Jenkins
> > that will manage a few builds, and how can i path the parameters from the
> > administrative build to the child builds.
> >
> >
> >
> > --
> > 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.
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/6f9kIkGdEhM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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-users+unsubscr...@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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Adding an administrative build (job)
Parameterized Trigger Plugin On 14.08.2014, at 10:54, Alex Brodov wrote: > Hi, > i'm trying to figure out how can i add an administrative build to Jenkins > that will manage a few builds, and how can i path the parameters from the > administrative build to the child builds. > > > > -- > 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. -- 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: Remove Slave node via Groovy: kill() not removing from list?
Simpler:
jenkins.model.Jenkins.instance.setNodes([])
On 12.08.2014, at 14:10, Efekt wrote:
> Here's a script I've written based on yours deleting all the slaves
>
> import hudson.model.*
>
> // For each slave
> for (aSlave in hudson.model.Hudson.instance.nodes) {
> println("SLAVE DELETED: "+aSlave.name)
> hudson.model.Hudson.instance.removeNode(aSlave)
> }
>
>
>
> --
> View this message in context:
> http://jenkins-ci.361315.n4.nabble.com/Remove-Slave-node-via-Groovy-kill-not-removing-from-list-tp3948782p4714544.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
> --
> 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.
>
--
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: What are the difference between Jenkins and HP ALM?
On 13.08.2014, at 14:50, Manju wrote: > I just wanted to know what is the advantages of Jenkins over the HP ALM? It's not ActiveX based. > If my understanding is correct, Jenkins is also a one type of test management > tool like HP QC/HP ALM. Jenkins is a very fancy Task Scheduler. -- 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: loosing history
File an issue against core (for now) in Jira. Provide the information requested here: https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Whattoputinthedescriptionofanissuereport%3F ... and respond to any comments asking for more information. On 12.08.2014, at 12:20, Sven Schultschik wrote: > Hi, > > we have a Jenkins 1.568 on a Win7 64 running as Windows Server > > We have the problem that we are loosing the build history after one day. The > jobs where build on a daily base und where configured to keep all builds or > for 70days 100builds. Both show in the interface only the builds of the > current date. But on the harddisc they are still available. > > I searched the group here for "loosing history" "miss history" and so on and > didn't found a valueable answer. > > Is that a known issue? Or a issue caused by behaviour of some config / plugin > combination? > > If you need some specific info to declare the issue, just tell me. > > Thank you for 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-users+unsubscr...@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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Stupid configuration issue: utf8 ?
Are you building on master or a slave node? If the latter, it has its own /systemInfo and also needs to have a UTF-8 locale. On 12.08.2014, at 10:43, Erwan de Ferrières wrote: > Nope, I don't think it's coming from there. > On the build summary page, the characters are well displayed > on the console output, KO > on the console plain text output, KO for the accented chars, but OK for the > ASCII created by grunt. > > Couldn't this be coming from the jdk I'm using (openjdk) ? > > Le mardi 12 août 2014 10:23:57 UTC+2, Richard Bywater a écrit : > I'm not an expert in the area, but could it be related to your Browser's > language setting? (What language is in the request header?) > > Richard. > > On 12/08/2014 7:55 PM, "Erwan de Ferrières" wrote: > No, there is no tomcat on the machine. > Only a nginx in front, that's all. > > Le mardi 12 août 2014 09:47:59 UTC+2, Stephen Connolly a écrit : > Are you running in Tomcat? IIRC Tomcat does not do UTF-8 by default... or > something like that > > > On 12 August 2014 08:03, Erwan de Ferrières wrote: > Hi, > > here are the outputs : > root@jenkins:~# locale > LANG=fr_FR.UTF-8 > LANGUAGE=fr_FR: > LC_CTYPE="fr_FR.UTF-8" > LC_NUMERIC="fr_FR.UTF-8" > LC_TIME="fr_FR.UTF-8" > LC_COLLATE="fr_FR.UTF-8" > LC_MONETARY="fr_FR.UTF-8" > LC_MESSAGES="fr_FR.UTF-8" > LC_PAPER="fr_FR.UTF-8" > LC_NAME="fr_FR.UTF-8" > LC_ADDRESS="fr_FR.UTF-8" > LC_TELEPHONE="fr_FR.UTF-8" > LC_MEASUREMENT="fr_FR.UTF-8" > LC_IDENTIFICATION="fr_FR.UTF-8" > LC_ALL=fr_FR.UTF-8 > > executable-war/var/lib/jenkins/jenkins.war > file.encoding ANSI_X3.4-1968 > file.encoding.pkg sun.io > file.separator / > hudson.diyChunking true > java.awt.graphicsenv sun.awt.X11GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.print.PSPrinterJob > java.class.pathjenkins.war > java.class.version 50.0 > java.endorsed.dirs/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/endorsed > java.ext.dirs > /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext > java.home /usr/lib/jvm/java-6-openjdk-amd64/jre > java.io.tmpdir/tmp > java.library.path > /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib > java.protocol.handler.pkgs org.apache.axis.transport| > java.runtime.name OpenJDK Runtime Environment > java.runtime.version 1.6.0_31-b31 > java.specification.nameJava Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version1.6 > java.vendorSun Microsystems Inc. > java.vendor.urlhttp://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_31 > java.vm.info mixed mode > java.vm.name OpenJDK 64-Bit Server VM > java.vm.specification.nameJava Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendorSun Microsystems Inc. > java.vm.version23.25-b01 > jna.platform.library.path > /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib > line.separator > mail.smtp.sendpartial true > mail.smtps.sendpartial true > os.archamd64 > os.name Linux > os.version3.2.0-67-generic > path.separator : > sun.arch.data.model64 > sun.boot.class.path > /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/classes > sun.boot.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64 > sun.cpu.endianlittle > sun.cpu.isalist > sun.io.unicode.encoding UnicodeLittle > sun.java.command jenkins.war -Xloggc:/var/log/jenkins/gclog.log > --httpPort=8080 > sun.java.launcher SUN_STANDARD > sun.jnu.encoding ANSI_X3.4-1968 > sun.management.compiler HotSpot 64-Bit Tiered Compilers > sun.os.patch.level unknow
Re: Stupid configuration issue: utf8 ?
Make sure LANG has a UTF-8 value (e.g. en_US.UTF-8) on all nodes. If that doesn't help, post /systemInfo contents. On 11.08.2014, at 16:50, Erwan de Ferrières wrote: > Hi all, > > I have a configuration issue I can't resolve. I'm using the latest release, > Ubuntu 12.04.4 LTS (GNU/Linux 3.2.0-67-generic x86_64), on a cloud machine > hosted by rackspace. > We have commit message in French, and jenkins is displaying the accentued > characters wrongly, as well as in the build log. > > Here are some examples : > > restreintes pour la visibilit�� des messages > > grunt-shell@0.7.0 node_modules/grunt-shell > � chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1) > > > Which information should I give you so we can find what is going wrong ? > > Regards, > > -- > 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. -- 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: warning about "reverse proxy set up is broken"
This happens when the configured location (URL) of Jenkins in Manage Jenkins » Configure System is different from how you're actually accessing Jenkins. On 11.08.2014, at 10:10, Mike Bayliss wrote: > I've just started upgrading (from version 1.550) to 1.574 and I'm seeing the > warning about the reverse proxy setup for the first time. > > I'm running the debian package as a service on Ubuntu 12.04 and do not have > any webserver on the system, nor do I have the reverse proxy plugin installed. > > Can I ignore this message or is there something I need to fix? (The link only > talks about configuring tomcat or nginx.) > > Thanks, > > Mike > > -- > 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. -- 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: How do I protect a job but publish the results?
Use (Project-based) Matrix Authorization Strategy and optionally enable the artifact permission by setting the Java system property -Dhudson.security.ArtifactsPermission=true This way, you can allow users read access to a job, builds, and build logs, but prevent access to job config, workspace, and archived artifacts. On 07.08.2014, at 18:57, Raine Nguyen wrote: > I need to have a way to protect all the jobs since I do not want to expose > the protected data including the source code after build, but still allow > users to view the build results to check the issues etc. Please let me know > if there is any path I should take. > > All suggestions, advice are very appreciated. > > Best > > Raine > > -- > 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. -- 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: Trigger jobs via API plus with upstream
On 07.08.2014, at 17:12, Hiran Chaudhuri wrote: > Now if I do that the triggered job always is displayed as "triggered by > anonymous user". Is there any chance to trigger it via REST such that the > upstream project information is kept? I could not find anything in the docs > or the online REST API help... Enable the 'trigger builds remotely' build trigger in the job configuration, then trigger builds by POSTing to /job/jobname/build?token=foo&cause=bar 'cause' is a magic parameter that lets you record the build cause when triggering this way. Not as nice as real upstream causes, but may work for you. -- 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: How to use Measurements Plot Plugin?
Given the stagnating install counts and the 4 year old initial release being the only available version, it's unlikely this plugin has many active users. On 06.08.2014, at 20:32, Andrew Pritykin wrote: > Bump. Would has anyone used this plugin? > > On Tuesday, August 5, 2014 11:38:19 AM UTC-4, Andrew Pritykin wrote: > Hi everyone, > > I have a JS file that looks to see how long it takes to load a webpage. Once > the page loads it saves the result (time in ms) to a file. After looking at > the Measurements Plugin I see its a extension to the Junit Test result post > build. > > currently my script writes to a file "time_load.xml" and writes the following > for example: > > Time (ms)11352 > > When my build finishes it fails and this is the console output: > > Loading time 11352 msec > Recording test results > None of the test reports contained any result > Build step 'Publish JUnit test result report' changed build result to FAILURE > Finished: FAILURE > > > Anyone have experience with this plugin or understand how to get this to work? > > https://wiki.jenkins-ci.org/display/JENKINS/Measurement+Plots+Plugin > > Thanks, > Andrew > > -- > 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. -- 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- Best Practices for Security
On 01.08.2014, at 18:12, Rahul Harikrishna wrote: > One thing that I've observed that the Jenkins users with > Administer/Run_Scripts permissions get to have way more rights than they > should. For example- Why do you want to prevent administrators from doing what you describe? Don't make these users administrators in the first place if you are concerned about this. -- 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: Error message being displayed on Jenkins website
Filed as https://issues.jenkins-ci.org/browse/INFRA-63 On 31.07.2014, at 12:17, matthew.web...@diamond.ac.uk wrote: > When browsing on http://jenkins-ci.org/changelog, I see the following text > displayed within the page: > warning: unlink(/tmp/cache_lock): No such file or directory in > /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 128. > Maybe someone wants to take a look at that. > Matthew > > > > > -- > 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/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: Combine multiple login-names to a single user account
Nicolas wrote the 'Additional Identities Plugin' that seems to do that: https://github.com/ndeloof/additional-identities-plugin It's unreleased though, and I don't know why. Still, worth a try if you know how to build a Maven project. On 30.07.2014, at 08:44, Simon Schlachter wrote: > Hi Jenkins Users! > > Is there any way to map multiple logins to the same user account? > > The scenario: > We use multiple version control systems - in all of them, the same user may > have a different "name". (e.g. in CVS its the short login name while in git > it is "My Name "). We would like to "map" both virtual > users to the same real user and this user's login. > > Is there something available to achieve this? > > Thanks for any pointers. > Simon > > -- > 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. -- 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: Moved Jenkins to different location/user now slave-agent.jnlp has invalid duplicate port number in the url
Run the following in Script Console and report the output:
println Jenkins.instance.rootUrlFromRequest
println JenkinsLocationConfiguration.get().url
println
org.kohsuke.stapler.Stapler.currentRequest.getHeader('X-Forwarded-Host')
println
org.kohsuke.stapler.Stapler.currentRequest.getHeader('X-Forwarded-Port')
Are you accessing Jenkins through a reverse proxy?
On 28.07.2014, at 18:12, Hansen Loke wrote:
> The config is the same as before the move, so it's:
> http://my.machine.com:8080/jenkins/
>
>
>
> On Monday, 28 July 2014 17:08:23 UTC+1, Daniel Beck wrote:
> What's configured in Manage Jenkins » Configure System » Jenkins Location »
> Jenkins URL?
>
> On 28.07.2014, at 12:08, Hansen Loke wrote:
>
> > Hi,
> >
> > Recently I've moved the Jenkins installation to a different HDD location on
> > the same host, and to be started by a different user, reasons for the move
> > was that it was previously freeloading from another user. After this move
> > all *nix slave nodes connects fine but the windows jnlp slave node doesn't
> > come up anymore with the following errors in the slave node logs:
> >
> > jenkins-slave.err.log:
> >
> > JNLP file
> > http://my.machine.com:8080/jenkins/computer/node01/slave-agent.jnlp?encrypt=true
> > has invalid arguments: [, node01, -url,
> > http://my.machine.com:8080/jenkins/, -url,
> > http://my.machine.com:8080:8080/jenkins/, -headless, -jar-cache,
> > C:\.jenkins\cache\jars]
> > Most likely a configuration error in the master
> > "http://my.machine.com:8080:8080/jenkins/"; is not a valid value for "-url"
> >
> >
> > I had a look in the downloaded slave-agent.jnlp file from the website and
> > it has:
> >
> > > codebase="http://my.machine.com:8080/jenkins/computer/node01/";>Slave
> > Agent for node01Jenkins project > href="https://jenkins-ci.org/"/> > version="1.5+"/> > href="http://my.machine.com:8080/jenkins/jnlpJars/remoting.jar"/> > name="hudson.showWindowsServiceInstallLink"
> > value="true"/> > main-class="hudson.remoting.jnlp.Main">some_hexnode01-urlhttp://my.machine.com:8080/jenkins/-urlhttp://my.machine.com:8080:8080/jenkins/
> >
> >
> > The part where it is marked in bold font is the part where it is
> > complaining about, whereas before the move it didn't have this extra url.
> >
> > I then had a look at the Jenkins source code to see where did this url come
> > from:
> >
> > The file in
> > jenkins-master/core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly
> > has this:
> >
> >
> >
> > -url
> > ${app.rootUrlFromRequest}
> >
> > Thus, this means that somehow after the move the rootUrlFromRequest is now
> > different. Except now I'm lost where to find and correct the "root URL from
> > request" or where that is being set.
> >
> > After the move I've already grep and replaced paths in the Jenkins setting
> > that pointed to the old location.
> >
> > Any pointers to where I should look next?
> >
> > Cheers,
> > Hansen
> >
> >
> >
> > --
> > 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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Jenkins logout when pushing the browser Back button
On 28.07.2014, at 17:57, Daniel Beck wrote: > Are you sure the page isn't just cached? Try reloading. Note that the login form shows even when you're logged in as it has its own URL. Look to the top right to see whether you're logged in. -- 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: Moved Jenkins to different location/user now slave-agent.jnlp has invalid duplicate port number in the url
What's configured in Manage Jenkins » Configure System » Jenkins Location »
Jenkins URL?
On 28.07.2014, at 12:08, Hansen Loke wrote:
> Hi,
>
> Recently I've moved the Jenkins installation to a different HDD location on
> the same host, and to be started by a different user, reasons for the move
> was that it was previously freeloading from another user. After this move all
> *nix slave nodes connects fine but the windows jnlp slave node doesn't come
> up anymore with the following errors in the slave node logs:
>
> jenkins-slave.err.log:
>
> JNLP file
> http://my.machine.com:8080/jenkins/computer/node01/slave-agent.jnlp?encrypt=true
> has invalid arguments: [, node01, -url,
> http://my.machine.com:8080/jenkins/, -url,
> http://my.machine.com:8080:8080/jenkins/, -headless, -jar-cache,
> C:\.jenkins\cache\jars]
> Most likely a configuration error in the master
> "http://my.machine.com:8080:8080/jenkins/"; is not a valid value for "-url"
>
>
> I had a look in the downloaded slave-agent.jnlp file from the website and it
> has:
>
> codebase="http://my.machine.com:8080/jenkins/computer/node01/";>Slave
> Agent for node01Jenkins project href="https://jenkins-ci.org/"/> version="1.5+"/> href="http://my.machine.com:8080/jenkins/jnlpJars/remoting.jar"/> name="hudson.showWindowsServiceInstallLink"
> value="true"/> main-class="hudson.remoting.jnlp.Main">some_hexnode01-urlhttp://my.machine.com:8080/jenkins/-urlhttp://my.machine.com:8080:8080/jenkins/
>
> The part where it is marked in bold font is the part where it is complaining
> about, whereas before the move it didn't have this extra url.
>
> I then had a look at the Jenkins source code to see where did this url come
> from:
>
> The file in
> jenkins-master/core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly
> has this:
>
>
>
> -url
> ${app.rootUrlFromRequest}
>
> Thus, this means that somehow after the move the rootUrlFromRequest is now
> different. Except now I'm lost where to find and correct the "root URL from
> request" or where that is being set.
>
> After the move I've already grep and replaced paths in the Jenkins setting
> that pointed to the old location.
>
> Any pointers to where I should look next?
>
> Cheers,
> Hansen
>
>
>
> --
> 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.
--
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: How to make the Job name not updatable
On 28.07.2014, at 13:13, Maciej Jaros wrote: > Anyone with access to job configuration has access to the machine Jenkins is > on - i.e. one could create a job that changes a directory of Jenkins job and > Jenkins job name is connected to the directory name. There are extension points that allow preventing execution of arbitrary jobs on Jenkins master. One implementation is Folders Plus in Jenkins Enterprise. And destroying data on a slave node usually isn't nearly as serious. -- 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 logout when pushing the browser Back button
Are you sure the page isn't just cached? Try reloading. On 28.07.2014, at 16:09, Ali Yakout wrote: > Hi > > I have a problem with my Jenkins. After logging in, if I click the browser > back button, it logs me out from jenkins. > I tried several browsers but still the same issue. > > Any clue what could be the problem here. > > 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/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: How to: Start application on destination after the build
https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller On 28.07.2014, at 17:00, Steven Scott wrote: > I am new to Jenkins and love the tool, but I am having one problem > that I can not imagine is unique to me, and I have not found a plugin > to deal with the issue. > > The problem I have is that I have an application running on server > that provides emulation data for our tests. In order to update this > application, it must be stopped, files updated, then I want to restart > it afterwards. > > I have a Jenkins job that will copy the appropriate files over, and I > use the PSKILL utility via a batch file to stop the application when > the build launches. The problem I have, is restarting the > application. Using a batch file does not work, even if I run 'start > application.exe' since the termination of the build process, seems to > kill these processes as well. > > Any suggestions would be appreciated. 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. -- 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: Downgrade the weather upon test failure
On 25.07.2014, at 23:16, Mark Sinclair wrote: > Is there a way to configure it so the weather gets cloudy if any tests fail? No. While the weather report is customizable in principle, it's not used that way. -- 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: Downgrade the weather upon test failure
Not true: Have more than 20% of tests fail. Only then you'll get the 'partially cloudy' icon due to tests alone. On 25.07.2014, at 21:58, Mark Sinclair wrote: > Currently if some tests fail, I get unstable status (yellow), but weather is > good. The weather is linked to the build status only. I'd like to make test > failures contribute to bad weather. What's the easiest way to accomplish > this? > > 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/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: Maven lastupdated file problem
Not a Jenkins issue. Try passing `-U` argument to Maven to force repository check. On 23.07.2014, at 17:40, Juan Ignacio Garzón wrote: > Hi, > > I'm having this problem. I use an Artifactory server to store my maven > libraries. I configured the maven installation inside the jenkins server to > use that artifactory server as central repository. > > Sometimes an app being built uses a library that does not exist in the > Artifactory server and also does not exists on the central maven repository > (the artifactory server connects to the maven central repo). So, the build > inside Jenkins fails, and I have to manually deploy that library on > artifactory and execute the build inside Jenkins again. The problem, is that > the Maven installation used by Jenkins creates a file called xxx.lastupdated > inside the local repository. So, jenkins does not try to download the library > from the artifactory server again. To solve this, I have to manually connect > to the jenkins server, delete the .lastupdated file and build again. Is there > a way to avoid connecting via console to my server, asi it requires some > special permissions on my company? (I mean: Plugins, maven configuration for > this case, or something). > > > Thanks a lot!!! > > -- > 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. -- 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: Can't get a response body any more when launching a job via curl
This was changed in 1.561. Here's the issue:
https://issues.jenkins-ci.org/browse/JENKINS-13546
(You should probably change your password.)
On 23.07.2014, at 08:57, Barthélémy wrote:
> Hello,
>
> I used to be able to start a job with "buildWithParameters" using curl and to
> get a json response containing information such as the future build number
> (nextBuildNumber) and the queueItem. Without changing anything I am not
> receiving the response body any more. I didn't use this code for quite some
> time, thus jenkins was updated meanwhile. I see that the response header
> contains a location that actually contains the queueId.
>
> Was there a change in the API ?
>
> Am I doing something wrong ?
>
> Here is the curl code equivalent to what I do in PHP :
> curl -v --user user:password -k -X POST -H "Content-Type: application/json"
> -d '{"module":"amoreTST"}'
> https://localhost/jenkins/job/AMORE-single-module/buildWithParameters
>
> And the response :
> * About to connect() to localhost port 443 (#0)
> * Trying HIDDEN... connected
> * Connected to localhost (HIDDEN) port 443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * warning: ignoring value of ssl.verifyhost
> * skipping SSL peer certificate verification
> * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * Server certificate:
> * subject: HIDDEN
> * start date: May 06 12:10:48 2014 GMT
> * expire date: Nov 02 12:10:48 2014 GMT
> * common name: HIDDEN
> * issuer: HIDDEN
> * Server auth using Basic with user 'HIDDEN'
> > POST /jenkins/job/AMORE-single-module/buildWithParameters HTTP/1.1
> > Authorization: Basic HIDDEN
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3
> > zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: localhost
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 21
> >
> < HTTP/1.1 201 Created
> < Date: Wed, 23 Jul 2014 06:46:16 GMT
> < Location: https://localhost/jenkins/queue/item/53/
> < Content-Length: 0
> < Connection: close
> < Content-Type: text/plain; charset=UTF-8
> <
> * Closing connection #0
>
>
>
>
> Here is my code in PHP that used to work :
> // ... this is in a class, thus the member
> $this->ch = curl_init();
> curl_setopt($this->ch, CURLOPT_RETURNTRANSFER, 1);
> curl_setopt($this->ch, CURLOPT_SSL_VERIFYPEER, 0);
> curl_setopt($this->ch, CURLOPT_HEADER, 0);
> curl_setopt($this->ch, CURLOPT_USERPWD, $user . ":" . $password);
> curl_setopt($this->ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
> curl_setopt($this->ch, CURLOPT_URL,
> $this->baseUrl . "job/" . $jobName . "/buildWithParameters?module="
> . $moduleName);
> curl_setopt($this->ch, CURLOPT_HTTPHEADER, array('Accept:
> application/json'));
> curl_setopt($this->ch, CURLOPT_POST, true);
>
> $result = curl_exec($this->ch);
> // here $result has a header but no body
>
> Thank you in advance for your help,
> Barth
>
> --
> 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.
--
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: What to do about NullPointerException (possibly associated with Naginator plugin)?
This issue seems to be fixed but the fix not yet released, so building a snapshot of naginator plugin and installing that should work. https://github.com/jenkinsci/naginator-plugin/commit/6789567dd81904efa775019c7b114144238612ec On 22.07.2014, at 12:52, David Aldrich wrote: > Hi > > I periodically see the following exception in the Jenkins log. I am running > Jenkins 1.570. What can I do to find the reason for this please? > > Best regards > > David > > == > > Jul 22, 2014 10:06:55 AM WARNING hudson.ExpressionFactory2$JexlExpression > evaluate > Caught exception evaluating: it.transientActions in > /jenkins/view//console. Reason: > java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor641.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) > at > org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) > at > org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) > at > org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) > at > org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) > at > org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) > at > org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) > at > org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) > at > hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) > at > org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) > at > org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at > org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) > at > org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) > at > org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) > at > org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) > at > org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) > at > org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) > at > org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) > at > org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) > at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) > at > org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) > at >
Re: Can't get "negative readahead" to work
On 22.07.2014, at 09:00, Mark Syms wrote: > The help indicates that (?!_Nightly) should be the magic regex that is needed > but I either end up with nothing selected or every build selected. > > Does this negative readahed regex actually work for filtering jobs or am I > just doing it wrong? There's a difference between lookahead (something not preceded by something else) and lookbehind (something not followed by something else). The example is a negative lookahead, in your situation you need negative lookbehind. The following should work: .*(?https://groups.google.com/d/optout.
Re: Any comments on the UI changes in 1.572
The redesign just makes the mess more obvious because the buttons are higher contrast now. Screenshot of 1.569: http://i.imgur.com/zV5bRvx.png On 18.07.2014, at 20:05, Andrew Kujtan wrote: > EmailExt configuration is also borked with the new redesign, the > triggers selection has the delete buttons all over the place. > > http://i.imgur.com/XAW8ycn.png -- 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: Any comments on the UI changes in 1.572
On 18.07.2014, at 15:15, David Aldrich wrote: > I'm not sure if this is relevant to this discussion, but I find the behaviour > of the 'Save' and 'Apply' buttons in the Project Configuration screen odd. > Clicking 'Apply' gives a green banner saying 'Saved'. Clicking 'Save' gives > no message. 'Apply' behaves correctly (although the banner looks a bit weird now, with the dark header). Clicking 'Save' should forward you to the index page of the project. If that's not the case, and you're staying on the config form please file a new Jira issue. If possible, try to reproduce the problem on other browsers and Jenkins versions. -- 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: Any comments on the UI changes in 1.572
Actually, it's not the first stage. Some changes already went into 1.570 (form element styling, especially buttons, and dropdown shadows for popup menus). It's just the most noticeable recent change, as the Jenkins header color was changed, among other things. Issues I know of: - if you use security, the 'username | log out' links are misaligned (JENKINS-23837 and others, fix scheduled for 1.574) - a badly configured IE9 places elements weirdly (JENKINS-23779, fix scheduled for 1.574) - logged in users who cannot see any jobs and cannot create jobs see an empty colored block on the 'All' view (fix scheduled for 1.574) - if you set long build names and/or have long build badges, a job's list of builds can overlap the main area (JENKINS-23829) - the sidepanel is wider, especially on screens with high resolution (i.e. less horizontal space for the main area) - Jenkins redesigns using e.g. Simple Theme Plugin break due to restructured UI So far there's nothing really badly broken that I could find. Community feedback to 1.572 via the changelog is rather negative (17/4/5 compared to 21/1/1 for 1.571), but no Jira issues were linked, so it's difficult to say what caused this. Specific feedback on things that don't work well would be helpful. On 18.07.2014, at 14:32, matthew.web...@diamond.ac.uk wrote: > I noticed that according to the changelog (http://jenkins-ci.org/changelog), > Jenkins 1.572 is the first stage of a UI redesign. > Has anyone installed that, and if so, what did you think? > We haven't upgraded yet, but would be prepared to in order that we can > provide feedback - provided the first attempt 1.572 is still usable . > Matthew > > > -- > 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/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: How do I stay logged into multiple Jenkins servers
Add an alias for that host in DNS (and use hostname:8080 / madscientistalias:9090 in the future), or put a reverse proxy in front of both (e.g. madscientist.hostname / hostname). Or, the sane solution: put them on different machines. On 18.07.2014, at 14:08, Rob Mandeville wrote: > I've been using http://hostname:8080 for one and http://hostname:9090 for the > other. I took another's suggestion and am using an alternate browser for my > second instance. It works, though if there is a simple solution that allows > me to use the same browser, I'd be all ears. If it's going to take some real > effort, I'll just go by the two-browser method. > > --Rob > > From: jenkinsci-users@googlegroups.com > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Bywater > Sent: Thursday, July 17, 2014 2:55 PM > To: jenkinsci-users@googlegroups.com > Subject: Re: How do I stay logged into multiple Jenkins servers > > I'm guessing you are using the same host name for both instances and > switching based on context? If so, changing it to switch by (virtual) host > names would solve what sounds like a cookie issue although not sure if > Winstone supports virtual host concept? > > Richard. > > On Friday, July 18, 2014, Rob Mandeville wrote: > I have two Jenkins servers: one for prime time use (my production > environment; my customers' development environment) and another for my own > mad science development. Both are currently on the same Linux machine and > running out of Winstone, but both aspects of that are negotiable. The fact > that it's using Active Directory for authentication is less negotiable. > > The problem is that I have to work on both of them. I do some work on one, > then I go to the other one and I have to log in again. Once I flip back to > the first one, I have to log in _again_. Is there any way for me to remain > logged into both instances simultaneously? > > Thanks in advance, > > --Rob > > > This e-mail and the information, including any attachments it contains, are > intended to be a confidential communication only to the person or entity to > whom it is addressed and may contain information that is privileged. If the > reader of this message is not the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, please > immediately notify the sender and destroy the original message. > > Thank you. > > Please consider the environment before printing this email. > -- > 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. > -- > 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. > > > Click here to report this email as spam. > > > This e-mail and the information, including any attachments it contains, are > intended to be a confidential communication only to the person or entity to > whom it is addressed and may contain information that is privileged. If the > reader of this message is not the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, please > immediately notify the sender and destroy the original message. > > Thank you. > > Please consider the environment before printing this email. > > -- > 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. -- 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: xml api output broken?
What version of Subversion plugin is this? On 18.07.2014, at 08:16, Simon Haegler wrote: > hi jenkins user > > i noticed that this call > http://my-jenkins-host:8080/job/myjob/api/xml?tree=builds[changeSet[items[affectedPaths]]] > > produces output where the first character is missing of each > content: > > > > > > > > > > runk/com.proc... ### redacted ### > > > > > note: the "runk" should read "trunk". > > bug? > > thanks, > simon > > -- > 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. -- 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: Shell build steps stopped working
> - Is this a bug in the EnvInject plugin or just some misconfiguration > on my side? Could be either, but if you didn't mess with PATH globally, on the node, or in the job, it's likely Env-Inject's fault. You wouldn't be the first one to be affected. > - How did you find out that I've installed the EnvInject plugin > between those builds? Unfortunately the table of installed plugins [1] > lacks an "Installed on" column ... Env-Inject adds an 'Environment Variables' action to builds that were run while it was installed. So I noticed the extra sidepanel item on build #92. Chances are you now have some cleanup to do if you haven't already: Go to Manage Jenkins » Manage Old Data. -- 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: Shell build steps stopped working
It's very suspicious that between those two builds, you installed the Env-Inject plugin. Disable that and try again. On 16.07.2014, at 09:35, Sebastian Schuberth wrote: > Hi, > > I'm running Jenkins 1.554.3 LTS on Windows Server 2008 R2 64-bit with MSYS > configured to run shell build steps. Everything used to be working fine, but > something between June 26 [1] and July 9 [2] made my shell build steps not > work anymore. The error is that command line programs (like wget etc.) are > not found anymore. This has been working before although I'm not aware of any > configuration change I made in between. I've only updated some plugins and > Jenkins core, but downgrading Jenkins to 1.554.2 did not help. > > When looking at the shell configuration I actually wonder how it could have > ever worked: In my case the shell is at "C:\mingwGitDevEnv\bin\sh.exe" and > I've configured this in Jenkins, but Jenkins does not seem to invoke this as > a login shell, so etc\profile and other scripts are never executed, and the > PATH environment is not set correctly. > > Any idea why this ever worked and what made it break? > > Thanks! > > [1] https://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-build-installer/91/ > [2] https://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-build-installer/92/ > > Regards, > Sebastian > > > -- > 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. -- 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: Using Jenkins to Commit to SVN 1.8
On 15.07.2014, at 16:27, Eric wrote: > Is there currently a way to work around this? * Don't use the SVN 1.8 client when modifying the Jenkins SVN checkout (is there _really_ a reason to upgrade the client, other than the new version existing?). * Have the Workspace Cleanup plugin remove the workspace before or after the build so you're always working with a fresh checkout. The Subversion plugin's strategy 'Always checkout a new copy' might also work. -- 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: How to restrict ssh credentials use in slave node configuration
On 14.07.2014, at 16:25, martin flehmig wrote: > 8) Login as userA and create slave node called nodeA: > * Configure nodeA: > * Launch method: Launch slave agents on Unix machines via SSH > * Host: dummyh...@dummydomain.de > * Add Credentials: >- Username with password >- Scope: System >- Username: userA >- description: userA@dummNode What you need to do is create the credentials ahead of time from the 'Manage Credentials' link on the side bar. There, create a credentials domain, specify a host name restriction of 'dummyHost.dummyDomain.de', and add the credential for the host there. Repeat for the second host in a second credential domain. Then, only the credential in the matching domain will be offered to users configuring each slave. -- 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: How to restrict ssh credentials use in slave node configuration
On 14.07.2014, at 18:34, Stephen Connolly wrote: > Unless you put the nodeA credentials in a credentials domain bound to > dummyHost then that is functioning as designed it is not possible to > restrict credentials further. If you have access to configure one slave you > have access to all credentials that are available for connecting slaves. The UI of the 'Add Credentials' button -- and I'm sure 99% of users create their credentials there -- does not allow putting the credentials into a domain. Only /credential-store has that UI. -- 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: Frustration with build-step/post-build-action access...
> I wouldn't call it "misusing". I'm simply working with what is there (that I > knew about). ... for a problem 'what is there' was not designed to solve. Law of the instrument ;-) > Since I can't do SSH in post-build I am limited to what I can do, hence my > frustration. With the emergence of Continuous Delivery/Deployment, I wish a > job could be defined more broadly and tasks or steps within a job more > fluidly to include any step in any order without having to resort to > writing/installing all sorts of plugins or having to fence an operation to an > explicit "type" of job or build phase. > [...] > Thanks for the feedback and I'm looking forward to trying the Workflow > plugin. Is there any information or designs I can look at? https://github.com/jenkinsci/workflow-plugin Slides of "Workflow in Jenkins" at https://www.cloudbees.com/jenkins/juc-2014/boston/sessions Also, the jenkinsci-dev list archives should have various bits about it. > As for the current job definition I've been working with, I would likely do > more things in a post-build action if I were allowed to, thus the point of my > frustration. I missed the "Any Build Step Plugin" but I will definitely give > it a try. > > As for using environment variables to handle user/passwords, does that allow > restricted access, including obfuscation in build logs? I'm unaware of the > mechanism for managing/obfuscating users/passwords in a secure way outside of > using the plugins. I'll look into that as well. Mask Passwords Plugin does that, Env-Inject Plugin probably as well (this requires that you specifically configure it as a password, not a regular env var). Definitions are either globally or per job, which is a bit weak but mostly worked so far for me. Note that IIRC some of the build log obfuscation of one of these didn't work when running the job on Windows, I don't rememeber the specifics though. -- 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: How to restrict ssh credentials use in slave node configuration
On 10.07.2014, at 12:03, Stephen Connolly wrote: > Credentials for use against slave nodes only should be set to scope SYSTEM... > that's what SYSTEM scope is for... Each credential should only be available for configuring one specific slave, and not the other slave. Maybe domain restrictions might work here? -- 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: Frustration with build-step/post-build-action access...
Your problem is that you're misusing the 'software build' concept and job type for something that isn't strictly a software build, and its limitations become obvious. Post-build steps usually fall into one of the categories 'recorder' (e.g. archive artifacts) and 'notifier' (email notifications), things that usually don't make sense before the actual work is done. I expect that very few actual build scripts need to SCP right in the middle, at least compared to those that upload things somewhere when they're finished. So that's what the plugin author decided should be the supported use case, and the reason you have difficulty achieving what you want. When I try do something like this, I usually try to get all the basic functionality going from a shell/batch script so it's usable outside Jenkins if there's a need to, reducing Jenkins to a fancy scheduler, log archiver and notifier. Passwords are provided by Jenkins as environment variables, SSH keys are stored on the slaves. Versioning of configuration is easier that way, and the job configurations don't become too complex. That said, have you tried Any Build Step Plugin? It might allow you to do what you want to achieve. The upcoming Workflow plugin probably also has the required flexibility of combining steps more flexibly in its job type. On 10.07.2014, at 00:53, Jeff wrote: > This is a bit of a rant, but I'm unclear why it matters which steps are > available as a build step vs. a post-build step. > > I'm trying to create a simple job to grab debian packages archived from > various upstream "build" jobs and installing/configuring the debian packages > on a set of test servers as part of an "install" job. > > The "Install job" sequence would be: > * Copy artifacts from previous jobs > * SCP them to the specified server(s) > * Run the installers via SSH > * Update configuration > However, I am unable to use the Jenkins plugins to do step 2 and 3 in the > proper order because the "Publish artifacts to SCP Repository" plugin option > is not available as a "build step" and "Execute shell script on remote host > using ssh" plugin as it's not available as a "post-build action". (chicken > or egg paradox). > > The motivation to use these plugins is to help manage the hosts/passwords > required to use SCP/SSH. > > Thus, the question is ... why does Jenkins need to differentiate between a > build step and a post-build action? Why not allow a mix of any type of > operation/step, regardless if it's type? > > It seems job creation flexibility would be enhanced if all tasks could be > used, particularly for jobs that don't really do builds (in the traditional > sense) such as creating a "pipeline" of phases/steps (continuous delivery, > etc.) deploy-dev --> functional test --> deploy-staging --> integration test > --> deliver release candidate. > > Has there been consideration around allowing any step to be added in any > order? > > -- > Jeff Vincent > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > > -- > 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. -- 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: audit-trail - don;t log build cause?
There is no way to disable this. I'd just rip out the AuditTrailRunListener.java class, then nobody should call AuditTrailPlugin.onStarted(Run). On 03.07.2014, at 17:44, James Nord (jnord) wrote: > Hi all, > > I'm experimenting with the audit trail plugin but for the life of me I can't > work out how to not get it to spam the logs with build started events. > > The config (XML) is as follows > > > .*/(?:configSubmit|doDelete|cancelQueue|stop|toggleLogKeep|doWipeOutWorkspace|createItem|createView|toggleOffline) > true > > > /path/to/jenkins/data/logs/audit > 50 > 2 > > > > > Is there any way not to log build started events - or does this require a > code change? > > e.g. my output of /path/to/jenkins/data/logs/audit is > Jul 3, 2014 4:14:38 PM job/foo/job/bar/job/commit/com.myco$my-app/ #57 Started > Jul 3, 2014 4:14:43 PM /view/All/createItem by builduser > Jul 3, 2014 4:14:47 PM job/foo/job/baz/job/baz-aat/job/commit/ #8 Started by > an SCM change > Jul 3, 2014 4:14:49 PM /job/abc/configSubmit by builduser > Jul 3, 2014 4:15:07 PM > job/foo/job/baz/job/baz-aat/job/commit/com.myco$baz-aat/ #8 Started > Jul 3, 2014 4:15:12 PM > job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-validation/ > #201 Started > Jul 3, 2014 4:15:12 PM > job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-transformer/ > #201 Started > Jul 3, 2014 4:15:12 PM > job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-model/ > #201 Started > Jul 3, 2014 4:15:12 PM > job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-jms/ > #201 Started > > But I just want > Jul 3, 2014 4:14:43 PM /view/All/createItem by builduser > Jul 3, 2014 4:14:49 PM /job/abc/configSubmit by builduser > > /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. -- 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: Want to build Jenkins job every after 15 seconds
You can't. Are you sure you're using the right tool for the job? https://en.wiktionary.org/wiki/if_all_you_have_is_a_hammer,_everything_looks_like_a_nail On 02.07.2014, at 10:42, Swapnil Pawar wrote: > Can you please tell me How I can schedule Jenkins Job which will execute > every after 15 seconds. -- 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:
On 30.06.2014, at 08:52, Panikera Raj wrote: > Update default Subversion credentials cache after successful authentication. > This option has been removed as of version 2.0 of the plugin, as authentication now uses predefined credentials. -- 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 1.568 does not use latest svn repo format
Downgrade TortoiseSVN, or install another SVN (1.7) client to modify the working copies used in Jenkins. Jenkins Subversion Plugin does not support SVN 1.8. On 27.06.2014, at 19:49, Notes Jonny wrote: > It is somewhat tricky to integrate out-of-date Jenkins with svn and > TortoiseSVN > > e.g: > > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy at '/cygdrive/c/jenkins/sdk_build' > is too old (format 29) to work with client version '1.8.9 (r1591380)' > (expects format 31). You need to upgrade the working copy first. > > > $ svn --version > svn, version 1.8.9 (r1591380) > compiled May 14 2014, 22:20:14 on i686-pc-cygwin > > TortoiseSVN: > TortoiseSVN 1.8.5, Build 25224 - 32 Bit , 2014/02/18 20:05:11 > Subversion 1.8.8, -release > > But Jenkins is using out of date: Subversion Workspace version 1.7 > > Any ideas? > > > > On Fri, Jun 27, 2014 at 10:46 AM, Notes Jonny wrote: >> Hello >> >> I installed Jenkins 1.568 on a Windows7 machine that has latest >> TortoiseSVN. Unfortunately I see Jenkins is using a much older repo >> format. >> >> Could Jenkins be updated to use latest SVN repo format? It is very >> inconvenient that I can't commit files that I modify in the Jenkins >> checkout.. >> Jon > > -- > 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. > -- 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: HTML formatting not working in Jenkins 1.568
Install the anything-goes-formatter plugin, and change the formatter used in global security preferences. On 27.06.2014, at 15:26, Notes Jonny wrote: > Hello > > I am migrating from Hudson and also a Jenkins 1.459 to Jenkins 1.568 > > I found that my HTML formated messages that I added to each build > configuration and also the System Message (Under Manage Jenkins) does > not display. > > In fact I see the HTML codes directly on the page. > > Any ideas? > Jon > > -- > 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. > -- 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 upgrade from 1.529 to 1.569
It should be. Give Jenkins time on first launch to finish loading, and check the logs for any (new) problems. Check out Manage Jenkins » Manage Old Data to see if some data became unloadable. Note that sometimes, plugins start misbehaving due to subtle changes in Jenkins core. If that happens, check to see if there's a plugin update. If you're not needing the absolutely latest and greatest and are likely to stay on the new version for a while, consider switching to the LTS release line of more thoroughly tested releases. On 26.06.2014, at 12:49, Bhavana Shrivastava wrote: > Hi, > > Currently we are using Jenkins 1.529. I want to upgrade it to Jenkins 1.569. > Is it possible to directly upgrade 1.529 to 1.569? > > 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/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: "Execute Windows batch command" not executing
On 26.06.2014, at 00:35, Gavin Goodrich wrote: > default That's the default matrix/multi-project configuration name for the single existing sub-project if there are no axes defined. Compare the following two URLs to see the difference: Meta-job just triggering configuration builds: /job/(jobname)/(buildnumber)/console 'default' configuration build with actual output: /job/(jobname)/default/(buildnumber)/console -- 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: Build pipeline plugin ERR_CONTENT_DECODING_FAILED error
Please file a bug in Jira and provide a full explanation on how to reproduce the issue starting with a blank Jenkins instance. (Please make sure it's not just happening on your production instance i.e. has other dependencies on your configuration than what you mentioned) In the past similar issues were caused e.g. by HTTP headers being sent twice, or the gzip header being sent and then uncompressed output. If you know how to, it'd help if you could check for these or similar issues in your browser's dev console. On 24.06.2014, at 18:59, Jeff Storey wrote: > I have just installed the build pipeline plugin, and I'm trying to run the > pipeline with the "Run" button from the pipeline view, but I'm getting a very > generic ERR_CONTENT_DECODING_FAILED error. I'm using Jenkins 1.569 and Build > Pipeline version 1.4.3. Has anyone seen this issue before? I've seen posts > related to other plugins with this issue and something to do with gzipped > content, but there doesn't seem to be a clear solution. > > -- > 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. -- 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 connect slave "Caused by: java.io.IOException: Invalid PEM structure, '-----BEGIN...' missing"
On 18.06.2014, at 16:19, Seth Floyd wrote: > where we point to the .pub file using the "SSH username with private key" > option That cannot possibly work. ".pub" indicates a public key. -- 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 connect slave "Caused by: java.io.IOException: Invalid PEM structure, '-----BEGIN...' missing"
On 17.06.2014, at 20:18, Seth Floyd wrote: > Did you ever figure this out? Im getting the same thing and im stumped. I can > connect just fine if I ssh from master to the slave using the key...but not > when I try to launch the slave from inside Jenkins. The credentials are somehow wrong. Make sure you didn't specify the path to the key file, or your public key, in the "Enter directly" key field of the SSH credential used for the slave. -- 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 launch slave agent on Win XP slave
On 16.06.2014, at 15:16, David Aldrich wrote: > 1) Sometimes, when I click the "Launch slave agent" button, I see: > > POST is required for hudson.slaves.SlaveComputer.doLaunchSlaveAgent > Will be fixed in 1.570. -- 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: how to specify the default ANT
'(Default)' means to use whatever's on your system's PATH rather than one of the versions configured in Jenkins. There is no way to get Jenkins to preselect a specific version for newly added Ant build steps. On 13.06.2014, at 14:13, Eric Wood wrote: > I have three installations of ANT 1.8.4, 1.9.3 1.9.4. There is no way to > specify on the configuration page which is the default. On the job page I > can specify the default. How do I select one of these installations to be > the default? Is it the first installation? It seems like the 1.8.4 is the > default version. > > Thansk, Eric > > -- > 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. -- 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: syntax highlighting of "Build" -> "execute shell"
And of course https://issues.jenkins-ci.org/browse/JENKINS-23151 which probably more users are concerned about. On 12.06.2014, at 21:53, Daniel Beck wrote: > https://issues.jenkins-ci.org/browse/JENKINS-23148 > > On 12.06.2014, at 18:25, min yuan wrote: > >> Hello, >> >> I have installed Jenkins last week and I can see the field "Build execute >> shell" has syntax highlighting support when I type my shell script. >> But today I reinstalled Jenkins and then the syntax highlighting is no more >> supported. >> >> Can somebody tell me why? Or should I send a bug report to Jenkins? >> >> 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. > > -- > 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. > -- 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 change language intermitentily
Please be more specific what you mean by 'Jenkins is configured to use English'. By default, Jenkins tries to return responses in the language preferred by the user (Accept-Language header). Use Locale Plugin to have Jenkins ignore your users' preferences. On 12.06.2014, at 16:52, Eduardo Dias wrote: > Hi All, > > we are experiencing a weird Jenkins behavior, without any change in Jenkins > configuration, the language changes from English to Portuguese.The Jenkins is > configured to use English. > To set the language back to English we just open the Jenkins configuration > and save without change nothing. The users that has admin access use English > browser, but has some viewers that can be using Portuguese browsers, we have > a team split in US and Brazil. > > Has anyone that has experienced this behavior before? > > Thanks in advance. > > Regards, > > Eduardo > > -- > 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. -- 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: syntax highlighting of "Build" -> "execute shell"
https://issues.jenkins-ci.org/browse/JENKINS-23148 On 12.06.2014, at 18:25, min yuan wrote: > Hello, > > I have installed Jenkins last week and I can see the field "Build execute > shell" has syntax highlighting support when I type my shell script. > But today I reinstalled Jenkins and then the syntax highlighting is no more > supported. > > Can somebody tell me why? Or should I send a bug report to Jenkins? > > 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. -- 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: EXTERNAL: Re: How to debug inability to create a new job
I don't know about IE, but on Chrome or Firefox I usually go to the browser's Developer Tools and check both the Console and the Network tabs for Javascript or HTTP errors. Regards, Daniel Serodio On Wednesday, June 4, 2014 1:15:45 PM UTC-3, Anne wrote: > > Google chrome works great. Internet explorer did not. > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Horton, Anne B > *Sent:* Wednesday, June 04, 2014 10:28 AM > *To:* jenkins...@googlegroups.com > *Subject:* RE: EXTERNAL: Re: How to debug inability to create a new job > > > > Same browser, different Jenkins instance works. It is not a permissions > problem as I can go to the jobs directory and create a new job directory no > problem. > > Any more ideas on how to debug this? > > > > *From:* jenkins...@googlegroups.com [ > mailto:jenk...@googlegroups.com ] *On Behalf Of * > k.thi...@comcast.net > *Sent:* Wednesday, June 04, 2014 10:25 AM > *To:* jenkins...@googlegroups.com > *Subject:* EXTERNAL: Re: How to debug inability to create a new job > > > > Out of curiosity, have you tried this in a different browser? > -- > > *From: *"Anne B Horton" > > *To: *jenkins...@googlegroups.com > *Sent: *Wednesday, June 4, 2014 9:19:23 AM > *Subject: *How to debug inability to create a new job > > Jenkins experts, > > When trying to create a new Job (any type), after clicking the OK button, > the Jenkins instance does not appear to do anything, it says on the New Job > webpage. When I go to the /jobs/directory, there are no new jobs created. > There are no errors in the Jenkins.log file – it reports that “Jenkins is > fully up and running”. > > > > Is there a way to turn on more detailed logging in Jenkins? > > > > Thank you very much in advance, > > Anne > > -- > 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. > > -- > 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Anyone else having trouble with Jenkins Update?
On 06.06.2014, at 22:26, scott crook wrote:
> Is there a configuration setting in Jenkins that I could just point it at the
> U Oregon mirror directly? I have looked but I don't see a setting that is
> obvious. Maybe there's something in a config XML file on the hard drive?
The download URLs are provided in the configured update center URL (e.g.
http://updates.jenkins-ci.org/update-center.json ). They get stored on disk in
the 'updates' folder. Since the UC metadata points you to
update.jenkins-ci.org, which redirects to one of the mirrors, you'll need to
replace those URLs.
You have quite a few options I can think of:
Option 1:
If you're behind a proxy, you might be able to configure it to automatically
redirect your requests to a specific mirror whenever you're trying to access a
URL of the form http://updates.jenkins-ci.org/updates/...
Option 2:
Provide your own update center (e.g. using a rewriting proxy, or a periodic
download job that edits the file afterwards and makes it available via HTTP)
and change the metadata to point to a specific mirror. Setting the undocumented
system property hudson.model.DownloadService.noSignatureCheck to 'true' will
help as the update center metadata is digitally signed, and failed checks
prevent use of the data. Changing the update center URL is probably easiest
with the UpdateSites Manager Plugin.
Option 3:
Rewrite the contents of the cached metadata files in JENKINS_HOME/updates (e.g.
default.json). Jenkins should immediately pick up these changes, as it always
checks the modification time of the file on disk.
Option 4:
Run your own UC metadata update process within Jenkins, e.g. by running the
following in Script Console (or as System Groovy build step, or in Scriptler,
...):
==
def originalurl = 'http://updates.jenkins-ci.org/download/'
def mirroredurl = 'http://jenkins.mirror.isppower.de/' // change to whatever
works for you
def ucUrl = new URL('http://updates.jenkins-ci.org/update-center.json')
// loadJSON is not considered public API
def json = hudson.model.DownloadService.loadJSON(ucUrl).replace(originalurl,
mirroredurl)
def site = Jenkins.instance.updateCenter.getById('default')
// updateData is not public API either; false means don't verify the signature
def result = site.updateData(json, false)
==
As you can see, this uses a lot of private API, so it might break in any
Jenkins update. Also, the regular update process is unchanged, so whenever it
runs (which should only happen when manually triggered from Manage Plugin »
Advanced if you schedule this script for periodic execution), the URLs are set
back to the original values.
--
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: Anyone else having trouble with Jenkins Update?
http://mirrors.jenkins-ci.org/status.html It looks like the xmission mirror was unavailable today for a while, and the Chinese mirror has been broken for a while. >From 1.565 Jenkins tells you in the error message which mirror it tries to >download from, so you can check whether it got redirected to a mirror that was >offline. On 06.06.2014, at 21:40, scott crook wrote: > I run a couple of Jenkins servers for a small development team. I was looking > to upgrade some of my plugins today through the control panel within the web > interface in jenkins. As a sanity check I tried downloading the latest > version of Jenkins from the web using the link that is front and center on > Jenkins-CI.org (http://mirrors.jenkins-ci.org/war/latest/jenkins.war) and I > get a 'connection reset' error. > > I have found that I can download from the mirror at Oregon State University > however. > > Is anyone else having this problem? > > -- > 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. -- 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: iframes no longer displayed after Jnekins upgrade (1.557)
On 06.06.2014, at 16:04, Christophe Lebel wrote: > i have recently upgraded to 1.566 and the issue remains, even with global > security> HTML RAW, iframes in view description are no more displayed. Use the Anything Goes Formatter plugin. "Raw HTML" isn't "raw", but rather "safe" (and the next release will change the name and description accordingly). -- 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: 4-5min delay at end of job on slave
First check the /threadDump page during this time to try to determine what Jenkins does during that time. Reload a few times to get a representative sample. The relevant section will likely be called something like 'Executor #42 for nodename: executing jobname #23' A Jira issue would be pretty useless, as this thread currently contains almost no information that could be used to investigate further. On 05.06.2014, at 16:10, Baptiste Mathus wrote: > FWIW, we're also having the same issue. > Jenkins 1.559. > > If someone knows an already filed JIRA, I'll be happy to report there. Or if > not create the new one. > > Thanks for any hint. > > > 2014-05-21 14:25 GMT+02:00 Corneil du Plessis : > We are experiencing a 4-5minute delay on a linux slave at the end of a job. > > We though it was sending mail but with or without the email step doesn't make > a difference. > It is not the 'Archiving artifacts' step because it usually takes 15-20s > There is not step after the sending mail. > > The log entries below from different jobs will illustrate. > > 00:45:20.995 > Archiving artifacts > > 00:45:37.263 > Sending e-mails to: xox...@xoxoxoxoxo.xo > > 00:49:19.280 > Finished: SUCCESS > > 00:18:05.538 > Archiving artifacts > > 00:21:41.815 > Finished: SUCCESS > > > 00:44:13.036 > Archiving artifacts > > 00:44:17.691 > Checking for post-build > > 00:44:17.691 > Performing post-build step > > 00:44:17.691 > Checking if email needs to be generated > > 00:44:17.691 > Email was triggered for: Success > > 00:44:17.691 > Sending email for trigger: Success > > 00:44:17.691 > Overriding default server settings, creating our own session > > 00:44:17.700 > messageContentType = text/html; charset=UTF-8 > > 00:44:17.702 > Adding recipients from recipient list > > 00:44:17.704 > Adding developers > > 00:44:17.704 > Sending to requester > > 00:44:17.708 > Successfully created MimeMessage > > 00:44:17.708 > Sending email to: xox...@xoxoxoxoxo.xo > > 00:49:18.196 Finished: SUCCESS > > > Does anyone have any ideas of what this can be? > 5minutes dead time is causing headaches. > > Corneil > > -- > 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. > > -- > Baptiste MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! > > -- > 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. -- 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: LTS 1.554.2 updates
On 04.06.2014, at 15:40, Shawn Baker wrote: > So, is this the directory I should be removing the contents? Yes. I fixed the wiki. -- 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: Most downloaded plugins?
On 03.06.2014, at 17:16, James Green wrote: > Need top one plugins in tabular format with paging: Name, Category, Brief > Description. There's also some raw popularity data as JSON (usually updated every month on the day after the first Saturday): http://stats.jenkins-ci.org/plugin-installation-trend/latestNumbers.json I wrote a Greasemonkey userscript that adds the install count as a column to the plugin manager. It only requires you to place that json file into JENKINS_HOME/userContent. https://github.com/daniel-beck/jenkins-userscripts/blob/master/Jenkins_Plugin_Popularity.user.js -- 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: Save job configuration returns an Oops page
On 02.06.2014, at 23:43, Slide wrote: > Released 2.38.1 today, should fix this issue. I confirm this is resolved. BTW, is there a reason you replaced the checkboxes with the drop-down? It takes more clicks to configure, it's more difficult to tell at a glance what's not configured, and takes more vertical space. And it's sortable with no obvious effect. -- 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: Save job configuration returns an Oops page
On 02.06.2014, at 14:05, Slide wrote: > I don't think its valid to not have at least one type of recipients selected. I use that a lot. The problem is that the per-trigger list of recipients is not part of this mechanism. Example: In case of success, send email to a...@example.org (Success trigger, Advanced, Recipient List). In case of failure, send email to b...@example.org (Failure trigger, Advanced, Recipient List). - No Project Recipient List (although it'd be a workaround for this problem to leave that field empty and select 'Recipient List' anyway) - No Culprits - No Developers - No Requestor Configure your notification like this, and Jenkins goes *boom* -- 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: Most downloaded plugins?
This site provides some of that: Plugins by popularity, optionally only those with 500+ or 1000+ installations, in graph format: http://stats.jenkins-ci.org/jenkins-stats/svg/svgs.html On 02.06.2014, at 11:21, James Green wrote: > I'm looking at https://wiki.jenkins-ci.org/display/JENKINS/Plugins > > I can lots of plugins across various categories. > > I don't necessarily know what I want or under which category it might exist. > Would it be possible to create a page listing plugins by their downloads > count? Most commonly used ones would then be instantly found by those new to > the ecosystem. > > Thanks, > > 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. -- 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: Save job configuration returns an Oops page
On 01.06.2014, at 01:43, Slide wrote: > I'll have to make that an error condition then, saving a trigger with no > recipient providers selected wouldn't make much sense. The documentation says 'Recipient List' refers to the 'Project Recipients List', so the Trigger-specific Recipients List would still receive the email, even with none of Culprits/Developers/Recipients List/Requestor selected. -- 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: Save job configuration returns an Oops page
On 31.05.2014, at 17:47, Slide wrote: > I am unable to reproduce this issue,so more information will be needed to > debug it. Did you restart Jenkins after upgrading the plugin? Reproducible in 2.38: Deselect all recipient providers (culprits, etc.) in a trigger. Save the project. This is a regression from 2.37.2.2. -- 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: python script argument misinterpreted in Jenkins Execute Shell step - how to overcome?
Are you sure it changes, or is it only the warped output of bash -x?
What version of Jenkins does this occur with?
Could you provide a test case anyone can run that demonstrates the problem?
Would 'echo' rather than 'sudo myscript.py' do?
On 30.05.2014, at 04:55, mpc8250 wrote:
> Hi All
>
> When we run my python script in the shell terminal, it works
>
> sudo myscript.py --version=22 --base=252 --hosts="{'hostA':[1],'hostB':[22]}"
>
> But when we run in Hudson and Jenkins, using Execute Shell step, somehow, the
> string --hosts="{'hostA':[1],'hostB':[22]}" is interpreted as
>
> sudo myscript.py --version=22 --base=252
> '--hosts="{'hostA':[1],'hostB':[22]}"'
>
> How do we overcome this so that our script would run in Jenkins and Hudson ?
>
> Thank you.
>
> Sincerely
>
>
> --
> 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.
--
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: Multi-configuration Build - Multiple Parameters on Single Axis?
Call them 'A', 'B', and 'C', and derive the Name and URL from that in your build script. Clearly they're not independent axes. On 29.05.2014, at 22:23, Trey Duskin wrote: > We are trying to set up a multi-configuration job in Jenkins with a > user-defined axis that will set multiple parameters in the job. For example, > we need to have a value called $name and a value called $url set in each > build, like the following: > > $name, $url > "URL A", "www.some-url.com/thing-a" > "URL B", "www.some-url.com/thing-b" > "URL C", "www.some-url.com/thing-c" > > If I try to set up two user defined axes, each with their respective lists of > values for $name and $url, the matrix build job will run all combinations of > these two, which will not be correct. > > I could use a Combination Filter to explicitly restrict which combinations > can be run, but when this list of values grows to, say, 10 values, the filter > will get pretty hairy. Is there a better way to either (a) specify multiple > values on a single axis, or (b) configure the multi-configuration job to only > run combinations where the axis indices are equal? > > 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. -- 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: Parameterized Build and SVN
That parameter is provided by the Subversion plugin.
It simply allows you to select a branch (or tag, or any folder really) from
Subversion as job argument. It doesn't check it out, that's what selecting the
Subversion SCM further down in the job config is for. A bit like the "Choice
Parameter", but with a list initialized from SVN.
What you need do is you rename the parameter to something simpler, like
"RCBranch". Then you configure Subversion SCM to check out the URL
"http://evc.io.comcast.net/chimps/branches/$RCBranch";. Use the same
credentials. If there's a validation error ("$RCBranch" doesn't exist") ignore
it and/or configure Subversion SCM in global config to validate only up to
first '$' character. Done.
On 29.05.2014, at 22:22, Ed Young wrote:
>
>
> I'm trying to build a selectable subversion branch. When I select the branch
> from the dropdown, and kick off the build it fails because it hasn't actually
> pulled the code from svn and so the workspace is empty.
>
> This seems like the simplest use case, so I don't understand why it doesn't
> work.
>
> Jenkins 1.532.1
>
>
> if I check "This build is parameterized" I get options for subversion (and
> other)
>
> The plugin correctly displays the branches in the drop down list, but when I
> kick off the build, it fails because nothing is pulled from SVN and the
> workspace is empty.
>
> Building in workspace /var/lib/jenkins/jobs/chimps-stag-tc-01-deploy/workspace
>
> [workspace] $
> /var/lib/jenkins/jobs/chimps-stag-tc-01-deploy/workspace/grailsw "-DChimps
> release candidate branches=3.5.1-S10-RC"
> -Dgrails.work.dir=/var/lib/jenkins/jobs/chimps-stag-tc-01-deploy/workspace//target
> -Dgrails.project.work.dir=target clean --non-interactive --plain-output
> FATAL: command execution failed
>
> java.io.IOException
> : Cannot run program
> "/var/lib/jenkins/jobs/chimps-stag-tc-01-deploy/workspace/grailsw" (in
> directory "/var/lib/jenkins/jobs/chimps-stag-tc-01-deploy/workspace"):
> error=2, No such file or directory
> at
> java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
>
> at
> hudson.Proc$LocalProc.(Proc.java:244)
>
> at
> hudson.Proc$LocalProc.(Proc.java:216)
>
> at
> hudson.Launcher$LocalLauncher.launch(Launcher.java:773)
>
> at
> hudson.Launcher$ProcStarter.start(Launcher.java:353)
>
> at
> hudson.Launcher$ProcStarter.join(Launcher.java:360)
>
> at
> com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:266)
>
> at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
>
> at
> hudson.model.Build$BuildExecution.build(Build.java:199)
>
> at
> hudson.model.Build$BuildExecution.doRun(Build.java:160)
>
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)
>
> at
> hudson.model.Run.execute(Run.java:1665)
>
> at
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>
> at
> hudson.model.ResourceController.execute(ResourceController.java:88)
>
> at
> hudson.model.Executor.run(Executor.java:246)
>
> Caused by:
> java.io.IOException
> : error=2, No such file or directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.(UNIXProcess.java:135)
> at java.lang.ProcessImpl.start(ProcessImpl.java:130)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
> ... 15 more
> Build step 'Build With Grails' marked build as failure
>
>
> I also have the subversion plugin installed, but I don't believe it's
> necessary since this feature seems to advertise it can pull from SVN.
>
> What am I doing wrong?
>
>
>
>
>
> --
> - Ed
>
> --
> 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.
--
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: a few Jenkins questions
On 29.05.2014, at 13:37, wak...@comcast.net wrote: > would be a build number reset at some point ? Well, it's an int. After build number 2.147.483.647 it wraps around to -2.147.483.648 and Jenkins basically breaks, failing to show these builds on the UI. Not sure this is a relevant limitation though. -- 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 is not Restarted
That's a bug that will be fixed in Jenkins 1.567 or so. https://github.com/jenkinsci/jenkins/pull/1239 On 28.05.2014, at 19:50, srinath0...@gmail.com wrote: > > I'm using java version "1.7.0_45" > > my script is > > export JENKINS_HOME=/home/build/jenkins > export JENKINS_USER="build" > export JAVA_HOME=/tools/java/java170_45 > export CLASSPATH=$JAVA_HOME/lib/tools.jar:./ > export ANT_HOME=/tools/ant/apache-ant-1.8.3 > export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH > export JENKINS_PORT="8080" > export JENKINS_AJP_PORT="8009" > export JENKINS_DEBUG_LEVEL="5" > export JENKINS_ENABLE_ACCESS_LOG="yes" > export JENKINS_HANDLER_MAX="10" > export JENKINS_HANDLER_IDLE="20" > java -Djava.awt.headless=true -DJENKINS_HOME=$JENKINS_HOME -jar > $JENKINS_HOME/jenkins.war > --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger > --simpleAccessLogger.format=combined > --simpleAccessLogger.file=$JENKINS_HOME/logs/access_log > --daemon#!/usr/bin/ksh > > 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. -- 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: Create Dynamic UnprotectedRootURL
Stephen,
That worked thanks a bunch!!
On Tuesday, May 27, 2014 1:20:34 AM UTC-7, Stephen Connolly wrote:
>
> You just want to add either a doDynamic or a getDynamic method (the
> getDynamic is likely more what you want to return an object that has its
> own views)
>
>
> On 27 May 2014 01:29, Daniel Brooks
> > wrote:
>
>> Ok, heres an example of My Class:
>>
>> public class WebHook implements UnprotectedRootAction {
>>
>> public static final String WEBHOOK_URL = "projects";
>>
>> public String getIconFileName() {
>> return null;
>> }
>>
>> public String getDisplayName() {
>> return null;
>> }
>>
>> public String getUrlName() {
>> return WEBHOOK_URL;
>> }
>>
>> //@RequirePOST For some reason the RequirePost is not working right.
>> public void doIndex(StaplerRequest req) {
>> LOGGER.log(Level.FINE, "WebHook called.");
>>
>> String payload = req.getParameter("payload");
>> if (payload == null) {
>> throw new IllegalArgumentException(
>> "Not intended to be browsed interactively (must
>> specify payload parameter)");
>> }
>>
>> //processPayload(payload);
>> }
>>
>>
>>
>> private static final Logger LOGGER = Logger.getLogger(WebHook
>> .class.getName());
>>
>> }
>>
>>
>> Can you provide me an example of what you are talking about. I'm pretty
>> new to Jenkins Plugin development and there doesn't seem to be any
>> decent documentation.
>>
>>
>> On Monday, May 26, 2014 4:47:12 PM UTC-7, Daniel Beck wrote:
>>
>>> DirectoryBrowserSupport (for e.g. AbstractProject.doWs()) does something
>>> similar, so something like the following should work: Have your
>>> UnprotectedRootAction return an object implementing
>>> org.kohsuke.stapler.HttpResponse
>>> from its doProject() method. In that HttpResponse's generateResponse,
>>> access req.getRestOfPath() to get 'xyz' or 'abc'. Pass that into
>>> Jenkins.getInstance().getItemByFullName(...) to process further.
>>>
>>> On 27.05.2014, at 01:27, Daniel Brooks
>>> wrote:
>>>
>>> > HI,
>>> >
>>> > I am trying to create a dynamic UnprotectedRootURL, where it will
>>> process anything like /projects/xyz or /projects/abc. Is there a way to
>>> currently do this with Jenkins.
>>> >
>>> > Thanks,
>>> > Daniel
>>> >
>>> > --
>>> > 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.
>>
>
>
--
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: Why is the LDAP plugin installed?
It's a plugin that can be updated independently from Jenkins itself, or disabled. It used to be a part of Jenkins core, like the 'Execute Shell script' build step or 'freestyle' project type are. Try disabling those! For (I assume) mostly backwards compatibility reasons it still gets bundled in the .war. This means you cannot uninstall it, otherwise Jenkins will just restore the bundled version again, unless you patch the Jenkins .war file to remove it completely. > According to https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin, the > LDAP plugin was split out from the Jenkins core a long time ago. That doesn't > look to be the case. > > I stopped Jenkins, deleted all ldap* from the plugins/ directory, and started > Jenkins (this is 1.564). I see that an old version (1.6) of the ldap plugin > has been expanded into the plugins/ directory, and is listed under Manage > Jenkins --> Plugin Manager. > > I'm not using LDAP for authentication. In Manage Jenkins --> Configure Global > Security, I have CAS authentication selected, and _not_ LDAP. > > Is it possible that, contrary to the documentation, the LDPS plugin _is_ > still bundled with the Jenkins core? > > Thanks > Matthew > > > > > -- > 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/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: Create Dynamic UnprotectedRootURL
Ok, heres an example of My Class:
public class WebHook implements UnprotectedRootAction {
public static final String WEBHOOK_URL = "projects";
public String getIconFileName() {
return null;
}
public String getDisplayName() {
return null;
}
public String getUrlName() {
return WEBHOOK_URL;
}
//@RequirePOST For some reason the RequirePost is not working right.
public void doIndex(StaplerRequest req) {
LOGGER.log(Level.FINE, "WebHook called.");
String payload = req.getParameter("payload");
if (payload == null) {
throw new IllegalArgumentException(
"Not intended to be browsed interactively (must specify
payload parameter)");
}
//processPayload(payload);
}
private static final Logger LOGGER = Logger.getLogger(WebHook
.class.getName());
}
Can you provide me an example of what you are talking about. I'm pretty new
to Jenkins Plugin development and there doesn't seem to be any
decent documentation.
On Monday, May 26, 2014 4:47:12 PM UTC-7, Daniel Beck wrote:
>
> DirectoryBrowserSupport (for e.g. AbstractProject.doWs()) does something
> similar, so something like the following should work: Have your
> UnprotectedRootAction return an object implementing
> org.kohsuke.stapler.HttpResponse from its doProject() method. In that
> HttpResponse's generateResponse, access req.getRestOfPath() to get 'xyz' or
> 'abc'. Pass that into Jenkins.getInstance().getItemByFullName(...) to
> process further.
>
> On 27.05.2014, at 01:27, Daniel Brooks
> >
> wrote:
>
> > HI,
> >
> > I am trying to create a dynamic UnprotectedRootURL, where it will
> process anything like /projects/xyz or /projects/abc. Is there a way to
> currently do this with Jenkins.
> >
> > Thanks,
> > Daniel
> >
> > --
> > 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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Create Dynamic UnprotectedRootURL
DirectoryBrowserSupport (for e.g. AbstractProject.doWs()) does something similar, so something like the following should work: Have your UnprotectedRootAction return an object implementing org.kohsuke.stapler.HttpResponse from its doProject() method. In that HttpResponse's generateResponse, access req.getRestOfPath() to get 'xyz' or 'abc'. Pass that into Jenkins.getInstance().getItemByFullName(...) to process further. On 27.05.2014, at 01:27, Daniel Brooks wrote: > HI, > > I am trying to create a dynamic UnprotectedRootURL, where it will process > anything like /projects/xyz or /projects/abc. Is there a way to currently do > this with Jenkins. > > Thanks, > Daniel > > -- > 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. -- 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.
Create Dynamic UnprotectedRootURL
HI, I am trying to create a dynamic UnprotectedRootURL, where it will process anything like /projects/xyz or /projects/abc. Is there a way to currently do this with Jenkins. Thanks, Daniel -- 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: Build Flow plugin and DSL editor
No. _That_ is the "DSL editor". The entire documentation is only on the wiki page of the plugin as well, last time I checked. On 26.05.2014, at 18:36, j...@introversion.co.uk wrote: > I was taking a look at the Build Flow plugin > https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin and there was a > reference there to a DSL editor: > > "Use the DSL editor to define the flow." > > In the job configuration I see a text box for editing the DSL, but I was > wondering if there was a more interactive / helpful tool for editing > Build-Flow DSL? > > -- > 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. -- 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: How to Triger a Build from java application using REST API
What have you tried? On 26.05.2014, at 12:49, krishna chaitanya wrote: > Hi , > > Any one please help me how to Triger a Build from java application using > REST API. > > -- > 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. -- 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: Failed to fetch from g....@github.com
On 26.05.2014, at 02:49, john.mel...@gmail.com wrote: > I'm attempting to run Jenkins as a Windows Service, so Jenkins is running > under the Local System Account That's just the default. You can configure the service to run as different user. -- 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: Promotion Option Missing Since Upgrade
The action 'Promotion Status' exists in the sidepanel of each build since promotions were defined on the project. If that is missing for you, check whether you have enabled all plugin dependencies of Promoted Builds in Plugin Manager -- they no longer get loaded internally if the admin disabled them even if they're a plugin dependency (that was a bug that was fixed in 1.524): - Primary candidates (declared or transitive dependencies of Promoted Builds): Maven project Plugin, Javadoc, Mailer - In rarer cases, the plugins detached from core since the version declared by the plugin in question are the culprit, in this case: external-monitor-job, ldap, pam-auth, mailer, matrix-auth, windows-slaves, antisamy-markup-formatter, matrix-project Improvements to this issue are essentially tracked as JENKINS-21485 and JENKINS-23150. Other than that, check out the Jenkins log at /log/all, it'll usually contain warnings and errors if things go wrong. Restart Jenkins if necessary to have every loading issue reappear again. On 23.05.2014, at 22:07, Colorado Rob wrote: > I have recently upgraded my Jenkins installation from 1.522 to 1.563 and > along with a number of plugins, including the promoted builds plugin (2.11 -> > 2.17). Since the upgrade, the Promotion Status option is missing from my > builds. My previous jobs have the "Promotion Status" option on the build > screen or in the drop-down menu in build history. And I can still see and > navigate through the earlier builds and their promotions. But none of the > jobs run since the upgrade have this option. > > I only do manual promotions. > > I have tried downgrading and the problem seems to continue. I am rebuilding > a job since the downgrade and will see how that goes. But that is a > temporary solution at best. > > My Google-fu didn't turn up any similar problem reports. Is this a known > issue? > > -- > 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. -- 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 in Winstone vs. Tomcat = poor performance?
On 23.05.2014, at 08:38, Steffen Breitbach wrote: > I guess our installation is quite large, ~1200 jobs, ~10k builds, ~60 views... No idea about Tomcat vs. Winstone, but I'm using Winstone with a patched 1.532.3 that includes fixes to JENKINS-18364 and JENKINS-22720, and it works quite well. The former is only fixed in LTS 1.554.2, and the latter is brand new. But my ~22k jobs are organized into folders, so if that's not the case for you, JENKINS-22720 won't make a difference. -- 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 daemon does not start correctly
On 21.05.2014, at 17:52, Sapientlife wrote: > no matter where we edit the environment variables To explain what I meant by the following: > within Jenkins in the global and node configuration pages Try to set them here if building on the master node: http://jenkins/configure Global properties » Environment variables Or here if building on a slave named foo: http://jenkins/computer/foo/configure Node Properties » Environment variables -- 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 daemon does not start correctly
This is not a bug (and actually might be lead to unexpected behavior on a lot of instances). Set your environment variables elsewhere, e.g. within Jenkins in the global and node configuration pages. On 21.05.2014, at 15:49, Sapientlife wrote: > Hi, > > Jenkins daemon is not starting up correctly. > > Looking at /etc/init.d/jenkins, it calls "daemon" from "/etc/init.d/functions" > > The daemon function does this: > cgroup $nice runuser -s /bin/bash $user -c "$corelimit >/dev/null 2>&1 ; $*" > > If you look at the man page for "runuser": > > -, -l, --login > > make the shell a login shell, uses runuser-l PAM file instead of default > one, clears all envvars except for TERM, initializes HOME, SHELL, > > USER, LOGNAME and PATH > > Note that daemon does not add -login to the command. > > Without the -l runuser is not reading the .bash_profile of the jenkins user. > > Is there a fix for this because it is causing Jenkins to not launch builds > with the correct environment variables. > > > > > > -- > 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. -- 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: Mirror instability. many 503 responses
You could always check the mirrors directly (at least when the first redirected request fails). List and status here: http://mirrors.jenkins-ci.org/status.html Call HttpURLConnection.getURL() after it throws to find out where it was redirected in case you care (e.g. for temporarily blacklisting a mirror). On 19.05.2014, at 16:44, Jim Gumbley wrote: > Seeing identical issues, very disruptive when creating a new environment? > > Surprised this is not causing more disruption? Are the mirrors using a CDN? > > On Tuesday, 8 April 2014 10:49:21 UTC+1, Johannes Wienke wrote: > Hi, > > we are automatic the bootstrapping of our jenkins installations > including plugins through a script that is executed from time to time. > Recently, the installation process fails frequently because either > jenkins itself or some plugins cannot be downloaded: > > jwienke@cinnabar:/tmp/installertests$ wget > http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war > --2014-04-08 11:44:22-- > http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war > Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 > Connecting to mirrors.jenkins-ci.org > (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. > HTTP request sent, awaiting response... 502 Bad Gateway > 2014-04-08 11:44:53 ERROR 502: Bad Gateway > > Or > > Caused by: java.io.IOException: Server returned HTTP response code: 503 > for URL: http://updates.jenkins-ci.org/download/plugins/git/2.2.0/git.hpi > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > > at java.lang.reflect.Constructor.newInstance(Constructor.java:534) > at > sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1458) > > at java.security.AccessController.doPrivileged(Native Method) > at > sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1452) > > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1106) > > at > hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:764) > > ... 8 more > Caused by: java.io.IOException: Server returned HTTP response code: 503 > for URL: http://updates.jenkins-ci.org/download/plugins/git/2.2.0/git.hpi > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403) > > at > sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2214) > > at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:596) > at java.net.URLConnection.getContentLength(URLConnection.java:491) > at > hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) > > ... 8 more > > Can anyone explain what is going on here? This is really a major problem > for us as it became nearly impossible to succeed in generating a > complete installation where everything could be downloaded. > > Cheers, > Johannes > > -- > Johannes Wienke, Researcher at CoR-Lab / CITEC, Bielefeld University > Address: Inspiration 1, D-33619 Bielefeld, Germany (Room 1.307) > Phone: +49 521 106-67277 > > > -- > 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. -- 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: Is there a text/json/parsable form of http://mirrors.jenkins-ci.org/status.html
http://mirrors.jenkins-ci.org/status.html On 19.05.2014, at 13:34, Kevin wrote: > I'm behind a proxied firewall and want to allow all the mirrors via scripting > without trolling through HTML. Is the mirror list somewhere on github > perhaps? > 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/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: Ability to read job config without changing it (re: matrix security)
The plugin is Extended Read Permission Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin It does basically what passing -Dhudson.security.ExtendedReadPermission=true to java would do, documented here: https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties Basically, if you have no idea how to pass arguments to Java, use the plugin. On 19.05.2014, at 17:58, Steve K wrote: > Hello, > > How can I grant a user the ability to see a job configuration without also > granting the ability to modify that configuration? > This question has come up in the past and I'd just like to find out what the > current status is. > Apparently there is a plugin that will help, but then I read that more recent > releases of Jenkins provide this ability. I don't see it though. > > What is the current situation? > > Thanks in advance. > > Steve K. > > -- > 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. -- 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.
