Re: Repeat Build with Parameters
(replies inline) On Wed, 26 Jun 2019, Madhusudan G J wrote: > I am new to jenkins and needs help, how do I build with parameters script till > I pass "No" parameter. > > Currently, I have a script, which will run and complete, when I click on build > with parameters. But I would like to gather the different parameters for > different builds one after the other and build at once. > > How Can I achieve this, please help. > > Example, My script creates a .csv file when I click on build with parameters, > I > would like to get this .csv file appended when I click on click on build > again. > once I am done, I would like to build at once, how can I achieve this. I believe that the Rebuilder plugin would help you here: https://plugins.jenkins.io/rebuild -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2lP_jHbO_LgNcjKoQDHsN-V3faso8eCd9zcgqqV5hSWY571qxDlIr5WP3koDNpMFWC7okyvUUiAX7Jep2vG3CqZQgK6oaqGHCEXvN0lV6Wg%3D%40brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Jenkins git plugin using only Java 7.1
(replies inline) On Mon, 22 Apr 2019, Rich Stephens wrote: > I have a machine that it limited to no higher than Java 7.1. (It's an AIX 6.1 > machine)Â I am running Jenkins 1.6.4.9 for this reason. > > I can get Jenkins running fine, but when I try to install the git plugin, it > installs dependencies that require Java 1.8. > > I cannot find any information on specifically which plugin dependencies are > requiring Java 1.8 or not. > > IS there a version of the git (and, by dependency, git-client) plugin that > will > work with Java 1.7? > > If so, How can I get ahold of it and ONLY those versions of the dependencies > that are java 1.7 compatible? Sounds like you may be running a rather old Jenkins master. Jenkins has entirely moved to JDK8 as of about two years ago: https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/ Trying to dig up older trees of dependency graphs would be a manual process unfortunately. -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190422200306.4lt6qrcvfkcieir5%40grape. For more options, visit https://groups.google.com/d/optout.
Re: Anyone using Jenkins as a job scheduler?
(replies inline) On Tue, 12 Mar 2019, Badarch Nergui wrote: > For that and some other reasons I've been thinking about centralizing the > scheduling of all of our jobs. > > Jenkins isn't really intended for this, but it could work. > > > Enterprise grade job scheduling software is REALLY expensive, but also kind of > overkill. This is one of those areas where technically Jenkins can do it, and you might be able to hack something into place, but it's not its core competency. I have been looking to move some workloads, especially those around the Hadoop ecosystem, to Apache Airflow (https://airflow.apache.org/) which I believe is a bit better suited for general purpose job and dependent task scheduling. Cheers -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/gWtSoav6Ub8nFZvI-VYQ-yd-di-aTZLjUO-mTkv8cnAUq0pdn0J3O0PjZsT2rQri8osSB58tS_93g5DQjgfLbNBGYP1yCHKRPqWIQdw0eXA%3D%40brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Unclear how safe workflow-support 3.0 is for upgrades
(replies inline) On Fri, 04 Jan 2019, Devin Nusbaum wrote: > Good question! > > > ??? I believe this means that only runtime > > persistence for running Pipelines has changed, and none of the previously > > existing on-disk state for Pipeline Runs will change. Would that be correct? > > Yes, the format of build data for completed Pipelines is unchanged, so > you???ll > still be able to access old Pipelines inside of Jenkins after the upgrade. Thanks for the clarifications Devin > To get into the details a bit, the file whose format has changed is > `program.dat`, > which stores the Pipeline program and is used to maintain control flow across > restarts. If you don???t stop a Pipeline during the restart, then after > restarting, > Jenkins won???t be able to deserialize `program.dat` back into the original > Pipeline program, so the build will fail. Once a Pipeline completes, > `program.dat` is deleted, hence the recommendation to wait for running > Pipelines to complete or to stop them manually if having running Pipelines > fail > after the restart would be a problem for your Jenkins installation. > > Hopefully that answers your question, but please let me know if there is > anything else I can clarify in regards to the upgrade. Any suggestions to > improve the changelog warning are also welcome. > > Thanks, > Devin > > > On Jan 4, 2019, at 14:59, R. Tyler Croy wrote: > > > > While considering upgrades for ci.jenkins.io, I see that workflow-support is > > now the first Pipeline-related plugin to arrive at 3.0 > > (https://plugins.jenkins.io/workflow-support). > > Hooray! Thanks for the work dnusbaum :) > > > > From the changelog: > > > >This update involves incompatible changes to the serialized format of > >Pipeline builds. Any Pipelines that are running when Jenkins is restarted > >to apply this upgrade will fail after the restart. Pipelines will be able > >to resume normally after subsequent restarts. > > > >To avoid this one-time issue, please stop all running Pipelines or allow > >them to complete before restarting Jenkins when applying this update. > > > > > > Since there's a marshalling change going on, I wanted to double check my > > understanding of this change. I believe this means that only runtime > > persistence for running Pipelines has changed, and none of the previously > > existing on-disk state for Pipeline Runs will change. Would that be correct? > > > > > > I'm personally a bit weary of seralization changes, which have bitten me in > > the > > past, but if this is just about runtime data and no longer term persisted > > information, then I'll happily upgrade post haste! :) > > > > > > > > Cheers > > -- > > GitHub: https://github.com/rtyler > > > > GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Jenkins Users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to jenkinsci-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/jenkinsci-users/20190104195952.pucqh6wo27xxb7d2%40grape.brokenco.de. > > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/443A7E08-C58E-4B34-A030-23D6620F42F8%40cloudbees.com. > For more options, visit https://groups.google.com/d/optout. -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190105152441.6ayv45nubuoicd6n%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Unclear how safe workflow-support 3.0 is for upgrades
While considering upgrades for ci.jenkins.io, I see that workflow-support is now the first Pipeline-related plugin to arrive at 3.0 (https://plugins.jenkins.io/workflow-support). Hooray! Thanks for the work dnusbaum :) >From the changelog: This update involves incompatible changes to the serialized format of Pipeline builds. Any Pipelines that are running when Jenkins is restarted to apply this upgrade will fail after the restart. Pipelines will be able to resume normally after subsequent restarts. To avoid this one-time issue, please stop all running Pipelines or allow them to complete before restarting Jenkins when applying this update. Since there's a marshalling change going on, I wanted to double check my understanding of this change. I believe this means that only runtime persistence for running Pipelines has changed, and none of the previously existing on-disk state for Pipeline Runs will change. Would that be correct? I'm personally a bit weary of seralization changes, which have bitten me in the past, but if this is just about runtime data and no longer term persisted information, then I'll happily upgrade post haste! :) Cheers -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20190104195952.pucqh6wo27xxb7d2%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Update all plugins automatically
(replies inline) On Thu, 18 Oct 2018, gotviser...@gmail.com wrote: > My Jenkins is not a docker setup. Can I still use this? I found a plugin > and installed it. But getting this error The Evergreen plugin is not useful when installed in a non-Jenkins Evergreen instance. That plugin only exists to support the system bundled in those Jenkins Evergreen containers. -- GitHub: https://github.com/rtyler Twitter: https://twitter.com/agentdero -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20181019152256.GT12208%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Installing Artifactory and Blue Ocean plugins offline
(replies inline) On Tue, 09 Oct 2018, Robert van Gangelen wrote: > Hi All, > > I have installed Jenkins on a Redhat server succesfully. > Now I want to install Artifactory and Blue Ocean plugins but the server is > not able to access the Internet. > So I downloaded the hpi files and tried to import them. The imports fails > because of the dependency error. > I was wondering if there is a other to do this. Or do I have to import a > the depenencies as well? > I downloaded one of the dependencies and during the import I got a lot of > other dependency errors. > > Is there a way to install the hpi file without all the dependency issues? You may find the Juseppe tool to be useful: https://github.com/yandex-qatools/juseppe Cheers -- GitHub: https://github.com/rtyler Twitter: https://twitter.com/agentdero -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20181009211549.GY28842%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: total list of Jenkins plugin
(replies inline) On Mon, 01 Oct 2018, Irfan Sayed wrote: > Hello, > do we have any consolidated list (just total count ) of Jenkins plugins > (irrespective of open source OR cloudbees ) available today ? > not pointing to any specific version but just asking in general The Update Center JSON contains a list of plugins distributed by the Jenkins project: http://updates.jenkins.io/update-center.actual.json We have no idea what other plugins different vendors might be distributing. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20181002004533.GA28842%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Jenkins global metrics
(replies inline) On Wed, 26 Sep 2018, gotviser...@gmail.com wrote: > I'm looking to generate a report, as a job, which will provide the global > metrics of my Jenkins instance. I need details in the report like (1) How > many jobs ran? (2) # of failed and successful jobs and every possible > metrics possible in one report. I need to send this report every week to > my management, so would like to know if it's possible to schedule a job to > run this report every Friday and send the metrics by email to my managers? > I found these two plugins - '*Global Build Status*' and '*Build Metrics*'. > But not able to use these as part of a job, download the report or email a > link to the report or nothing of that sort. Please help. I personally use Datadog and their plugin integration to get such metrics out of our Jenkins instances. You can certainly script such metrics gathering in Jenkins, but there's nothing ready-made out of the box. Cheers -- GitHub: https://github.com/rtyler Twitter: https://twitter.com/agentdero -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180927144554.GA16966%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: structs v1.7 is missing. To fix, install v1.7 or later.
(replies inline) On Sun, 23 Sep 2018, Steve Burrus wrote: > YES UYES Mark I am MOST WILLING to wait at least 3 - 4 days for your help > an d I am very sorry that I seemed to be "pushy" or in any way impatient > for a response from you. Jumping in as mailing list moderator. Many of the folks around here are volunteers and are under no obligation to provide help, and any assistance people are willing to share I very much appreciate. I will not hestitate to bans users for antagonistic behavior, so please be friendly and respectful of each others' time. Cheers -R Tyler Croy -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180924202624.GB12982%40grape.brokenco.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Jenkins Configuration as Code 1.0 is out!
(replies inline) On Wed, 12 Sep 2018, Ewelina Wilkosz wrote: > Hi all! > > Version 1.0 of Jenkins Configuration as Code plugin > <https://github.com/jenkinsci/configuration-as-code-plugin> has just been > released and will be available in update center any time now! > Thanks to all who helped us get there :) Congratulations on all the hard work Ewelina and everybody else who contributed! We've been happily using Configuration as Code for Jenkins Evergreen (https://github.com/jenkins-infra/evergreen) and I'm pleased with how well it's been working out for us. I look forward to a bright future with more immutable Jenkins infrastructure :) Cheers -R Tyler Croy -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180912223424.GP2292%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Regarding plugin installation issue
(replies inline) On Wed, 16 May 2018, kirti.rast...@winvest-global.com wrote: > Hi All, > > While launching jenkins through apache tomcat jenkins doesnt allow me to > install plugins. Now i want to install manualy but while installing i am > getting error through hpi. > Please help me out How are you installing plugins? One (token-macro) wasn't installed correctly and that looks like it's causing the dependency resolution problems. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180516142111.GF3395%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Post commit hook failed with exit code 127: --post-data not found
(replies inline)
On Tue, 15 May 2018, jack wrote:
> Hi everyone,
>
> I'm recently working on this automation solution for my dev team using SVN
> as version control, to run builds and tests automatically when a commit
> occurs.
>
> But each time when I commit my post-commit hook script fails me :/
>
> post-commit hook failed (exit code 127) with output:
> /url/to/our/svnServer/hooks/post-commit: 67: --post-data: not found (which
> is odd : the --post-data line is not at line 67 which is the last line of
> the file)
>
> I'm not able to find the exact same problem on the web so no solution
> found... My script looks like this (the same script from the official doc):
>
>
>
> REPOS="$1"
> REV="$2"
>
> #path to svnlook
> UUID=`svnlook uuid $REPOS`
>
> #notifying jenkins for repository change
> /usr/bin/wget \
> --header `wget -q --output-document - \
>
> 'http://my_jenkins_url/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)'`
> --post-data "`svnlook changed --revision $REV $REPOS`" \
> --timeout=2 \
> http://my_jenkins_url:/subversion/${UUID}/notifyCommit?rev=$REV
While this isn't a Jenkins issue at all, I'll give ya a hand :)
There's a trailing \ character which is missing after the crumbIssuer line in
the script, causing the script interpreter to try to parse the next line as if
it were a new command (`--post-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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20180516141729.GE3395%40grape.lasagna.io.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
Re: Jenkins refuses to queue and run identical consecutive build requests from curl
(replies inline) On Tue, 17 Apr 2018, Martin d'Anjou wrote: > I try to trigger multiple builds rapidly using curl, but Jenkins silently > refuses to launch the builds. It keeps returning the same queue item in the > "Location": >From my understanding this will happen it the "same looking" item goes into the queue and isn't dequeued rapidly enough. So basically if the quiet period is really low, these subsequent calls might queue redundant items once one item is actually dequeued. Anyways, that's my understanding of this behavior. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180418023342.GR1836%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Heads up! Jenkins is on YouTube, with more videos coming soon!
The Jenkins project has been on YouTube for a while, but I recently transitioned our channel to a "Brand Account", which means we can share permissions to post videos _much_ more easily: https://www.youtube.com/c/jenkinscicd I am hoping that we can share access, not only for the Jenkins Online Meetups (https://www.meetup.com/Jenkins-online-meetup/), but also for more project meetings and group meetings (see also: https://groups.google.com/d/msg/jenkinsci-dev/6-1mZoKp4hM/EHz5NaPRBgAJ). Hope you all find more video content helpful! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180411020146.GB1836%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Break init scripts up in to re-usable classes
(replies inline) On Mon, 12 Mar 2018, Edd Grant wrote: > Hi folks, > > I'm using the init hook script mechanism ($JENKINS_HOME/init.groovy.d) to > programmatically configure Jenkins. I'm building up quite a library of code > and want to split it out in to re-usable classes, to keep things > maintainable and make it easier to write well focused tests etc. I have > tried the following with no luck: > > 1: Trying to split classes out in to separate scripts and using Groovy's > 'evaluate' function to load the classes from each script (basically trying > to re-implement some sort of importing behaviour). This doesn't work at all > due to the way Groovy manipulates scripts. > > 2: Putting my classes in a jar file and adding this to WEB-INF/lib in the > Jenkins war. This approach leads to classloader errors, presumably because > the jar classloader that my code belongs to doesn't have access to Jenkins' > PluginManager 'uberClassLoader'? > > 3: Same as [2] but adding the jar to the JVM's classpath rather than adding > it to the jar. Same result as [2]. > > Has anyone tried doing anything similar to this before? I'm really keen to > be able to do things like organise my code in packages and keep it in small > maintainable units. Grateful for any suggestions. I have nothing to suggest that will help you refactor those Groovy scripts. As one who has wielded plenty of init.groovy.d scripts in my day, I can tell you I'm going to refactor mine by just deleting them in favor of: https://github.com/jenkinsci/configuration-as-code-plugin#jenkins-configuration-as-code-plugin I doubt that helps though :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180313021342.kwkigbcbjiws4kzb%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Logs inside BlueOcean do not get updated automatically
(replies inline) On Mon, 05 Mar 2018, Vivek Pandey wrote: > Hi Christian, > > This looks like regression. I have opened > https://issues.jenkins-ci.org/browse/JENKINS-49929, we are going to take a > look at it. Thanks for reporting. Christian, are you using Firefox perhaps? I've noticed that "Karoake mode" seems to stop when I switch away from Blue Ocean tabs for too long of time while a a Pipeline is running. Josh speculated in Gitter that this might be somehow related to recent Firefox features which "quiet" the background tabs. > > On Mon, Mar 5, 2018 at 6:08 AM Christian Ciach <derein...@gmail.com> wrote: > > > Hello, > > > > I wish I could describe this issue better, but I have no idea how to debug > > this. > > > > I am using the current version of Jenkins (2.106) with BlueOcean (1.4.2) > > on CentOS. > > > > Usually, I would expect the logs inside BlueOcean to automatically update > > themself when my build logs new stuff, but this is not the case. I think > > the developers call this the "karaoke mode". > > > > Watching the live log works nicely using the classic view at the URL > > "/job/JOBNAME/JOBNUMBER/console". But with BlueOcean, I have to refresh the > > whole page to see the updated log. > > > > How can I even begin to debug this? > > > > Best regards, > > Christian Ciach > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Jenkins Users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to jenkinsci-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/jenkinsci-users/0120b425-2c72-4abd-8af5-89a9fdacdb96%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/0120b425-2c72-4abd-8af5-89a9fdacdb96%40googlegroups.com?utm_medium=email_source=footer> > > . > > For more options, visit https://groups.google.com/d/optout. > > > -- > Sent from my iPhone > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAKT4V18LBW8%2Bfq_mWmn_UBym87TdfnO_e_8PXpkvbArk%3DfYm8A%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180305201157.53o43x3zg3vrtic2%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
(fwd) Re: Request for participation: Jenkins Security Officer candidates
I was reminded today that I completely forgot to send out an update on this! My apologies, time flies when you're having fun I suppose. I would like to thank the candidates who spoke up and offered their time to act in the capacity as the Jenkins Security Officer. The board has selected Daniel Beck to continue on as the Jenkins project's Security Officer. Since the failure was on the communication part, not the decision making part, I have updated the wiki to reflect that Daniel's term actually started in December. See <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board#Officers> For more information about Jenkins CERT or our responsible disclosure policies, please see: https://jenkins.io/security/ Thanks Daniel for your continued work to make Jenkins more secure \o/ On Fri, 08 Dec 2017, R. Tyler Croy wrote: > Time flies when you're having fun, and or, releasing a whole bunch of security > advisories and patches :) > > I should thank Daniel Beck for leading CERT over the past couple years in his > tenure as the Jenkins Security Officer. Jenkins is more secure than effort > thanks to his, and others', diligent efforts. > > In accordance with our previously agreed upon team lead proposal > (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) > I am now asking, again, on behalf of the Jenkins board[1] for candidates who > are willing to act as the Jenkins Security Officer. > > The responsibilities of the Jenkins Security Officer would be to lead Jenkins > Security (CERT) team, and: > > * Run the Jenkins CERT meeting > * Manage sending gifts to qualifying reporters of resolved security issues [2] > * Coordinate work on, and releases, of security fixes with plugin authors, > Kohsuke and the LTS team lead > * Publish Security Advisories (including CVE IDs and CVSS) and notify the > mailing > list > * Drive security policy definition/changes in the community > * Represent the Jenkins project on security topics with third parties > > > The expected term of the Security Officer would be 12 months. > > > > Contributors interested in being considered for the Jenkins Security Officer > position should email the board: jenkinsci-bo...@googlegroups.com in the *next > seven days* explaining their qualifications for the position. > > In seven days the board will select a candidate to appoint to the position who > will be able to act on behalf of the Governance Board on matters pertaining to > the position described above > > > Thanks! > > > [0] https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CERT+team > [1] The current board: > <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board> > [2] > https://wiki.jenkins-ci.org/display/JENKINS/Rewards+for+reporting+security+issues > > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > -- > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/20171208194139.omtoenz67zlttauo%40blackberry.coupleofllamas.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180217200547.ncmtpgwwi6lajubd%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: github quota limit when scanning with the addition of tags
Sender: jenkinsci-users@googlegroups.com On-Behalf-Of: ty...@monkeypox.org Subject: Re: github quota limit when scanning with the addition of tags Message-Id: <20180106042952.4wlg7enl4dbnn...@blackberry.coupleofllamas.com> Recipient: andrew.h...@nab.com.au The information contained in this email and its attachments may be confidential. If you have received this email in error, please notify the sender by return email, delete this email and destroy any copy. Any advice contained in this email has been prepared without taking into account your objectives, financial situation or needs. Before acting on any advice in this email, National Australia Bank Limited (NAB) recommends that you consider whether it is appropriate for your circumstances. If this email contains reference to any financial products, NAB recommends you consider the Product Disclosure Statement (PDS) or other disclosure document available from NAB, before making any decisions regarding any products. If this email contains any promotional content that you do not wish to receive, please reply to the original sender and write "Don't email promotional material" in the subject. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9633fa14-c91f-4969-b6ab-de03e20cebac%40journal.report.generator. For more options, visit https://groups.google.com/d/optout. --- Begin Message --- (replies inline) On Fri, 05 Jan 2018, Alicia Doblas wrote: > Hi, > > a couple of months ago we had the same problem. After improving the > discover filter of the branch/tag/PR calls, there weren't too much to > do...so we decided to "by-pass" the api of github by using different users. > Looks like the api limit applies to a single user, so the "solution" for us > was to split our jobs into different groups, each of them using a different > user for the api call. > > By changing this configuration we can manage 5000 req/hour x N groups. This is very very much against the GitHub.com terms of service, which states that one legal entity can have one free machine account. https://help.github.com/articles/github-terms-of-service/#b-account-terms - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180106042952.4wlg7enl4dbnnw5i%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature --- End Message ---
Re: github quota limit when scanning with the addition of tags
(replies inline) On Fri, 05 Jan 2018, Alicia Doblas wrote: > Hi, > > a couple of months ago we had the same problem. After improving the > discover filter of the branch/tag/PR calls, there weren't too much to > do...so we decided to "by-pass" the api of github by using different users. > Looks like the api limit applies to a single user, so the "solution" for us > was to split our jobs into different groups, each of them using a different > user for the api call. > > By changing this configuration we can manage 5000 req/hour x N groups. This is very very much against the GitHub.com terms of service, which states that one legal entity can have one free machine account. https://help.github.com/articles/github-terms-of-service/#b-account-terms - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20180106042952.4wlg7enl4dbnnw5i%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Request for participation: Jenkins Security Officer candidates
Time flies when you're having fun, and or, releasing a whole bunch of security advisories and patches :) I should thank Daniel Beck for leading CERT over the past couple years in his tenure as the Jenkins Security Officer. Jenkins is more secure than effort thanks to his, and others', diligent efforts. In accordance with our previously agreed upon team lead proposal (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) I am now asking, again, on behalf of the Jenkins board[1] for candidates who are willing to act as the Jenkins Security Officer. The responsibilities of the Jenkins Security Officer would be to lead Jenkins Security (CERT) team, and: * Run the Jenkins CERT meeting * Manage sending gifts to qualifying reporters of resolved security issues [2] * Coordinate work on, and releases, of security fixes with plugin authors, Kohsuke and the LTS team lead * Publish Security Advisories (including CVE IDs and CVSS) and notify the mailing list * Drive security policy definition/changes in the community * Represent the Jenkins project on security topics with third parties The expected term of the Security Officer would be 12 months. Contributors interested in being considered for the Jenkins Security Officer position should email the board: jenkinsci-bo...@googlegroups.com in the *next seven days* explaining their qualifications for the position. In seven days the board will select a candidate to appoint to the position who will be able to act on behalf of the Governance Board on matters pertaining to the position described above Thanks! [0] https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CERT+team [1] The current board: <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board> [2] https://wiki.jenkins-ci.org/display/JENKINS/Rewards+for+reporting+security+issues - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20171208194829.o4so5ercvgzel6tf%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: LTS support timelines
(replies inline) On Wed, 04 Oct 2017, lv via Jenkins Users wrote: > Hi All, > > I'm one of the people maintaining the public Jenkins installation of the > Apache Impala (Incubating) project, and since it is facing the public > internet we're particularly interested in keeping our installation secure. > We are currently running LTS 2.46.3 and I'm trying to figure out whether > such old LTS releases are still supported, and for how long. > > I looked at the page describing the LTS Release Line and from there it is > not clear to me whether only the latest release line (currently 2.73.X) > will receive security fixes, or whether older lines receive those, too. If > they do, what is the latest LTS line that will receive security update > and/or that is considered when looking at the impact of newly found > security issues? Older LTS releases are in no way supported by the Jenkins project and do not receive backports of any kind. I strongly recommend to always follow the latest LTS versions. ci.jenkins.io (which I maintain) runs 2.73.1 for example, and when we roll new releases, I make sure to upgrade :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20171004183122.dz54bodh3dqvsdqp%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Why do some pipelines not let me view Workspace?
(replies inline) On Fri, 29 Sep 2017, dandeliondodgeball wrote: > Pipeline 1 just runs a script, and has the "Workspace" icon. > > Pipeline 2 runs a Jenkinsfile and doesn't have the "Workspace" icon. > > What I mean by "Workspace" icon. > > <https://lh3.googleusercontent.com/-kYDTubS--cU/Wc6OBN2qUXI/ADY/VGfdrSZYrXMtWsBTL3nV4t3NtCr8aT73gCLcBGAs/s1600/CaptureWS.PNG> Without seeing the actual Jenkinsfile it would be hard to answer your question. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170929195051.tw6ne2m3rhvg22dq%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Debian version of docker image jenkins/jenkins:lts
(replies inline) On Wed, 13 Sep 2017, Jacob Larsen wrote: > What happened to the debian version of the official docker image named > jenkins/jenkins:lts? When I pull that image right now, I get an image built > on alpine. Was there an official decision to switch I could not find any > mention of, or was it overwritten by mistake? There is definitely a bug in our publishing scripts for our Docker images. Currently tracked here: https://github.com/jenkinsci/docker/issues/570 Haven't yet figured out WTF is going on :/ - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170913214638.z446dglwrjhbhclt%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Jenkins crashes with "Illegal character 0x0 for HttpChannelOverHttp" - Why?
(replies inline)
On Fri, 10 Feb 2017, daniel.seeba...@gmail.com wrote:
> Hi,
>
> - Ubuntu 16.04.1
> - Jenkins 2.32.2
>
> Since a few days I see crashes on Jenkins: (/var/log/jenkins/jenkins.log*)*
>
> Feb 10, 2017 12:15:09 AM hudson.security.csrf.CrumbFilter doFilter
> WARNING: No valid crumb was included in request for /azenv.php. Returning
> 403.
For what it's worth, I have been seeing this a bit lately as well. As far as I
can tell (https://bugs.eclipse.org/bugs/show_bug.cgi?id=471081) it's due to
something attempting to speak HTTPs to an HTTP only service.
>
> Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x1 in state=START for buffer
> HeapByteBuffer@6de2eef2[p=1,l=256,c=16384,r=255]={\x01<<<\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01...\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01>>>.com/\r\nContent-Ty...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 2:06:33 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x1 for
> HttpChannelOverHttp@10d1bddb{r=0,c=false,a=IDLE,uri=}
>
> Feb 10, 2017 4:35:15 AM hudson.security.csrf.CrumbFilter doFilter
> WARNING: No valid crumb was included in request for /azenv.php. Returning
> 403.
>
> Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x0 in state=START for buffer
> HeapByteBuffer@5e57ec7c[p=1,l=1,c=16384,r=0]={\x00<<<>>>ET /login
> HTTP/1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:24 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x0 for
> HttpChannelOverHttp@1910d1bc{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x4 in state=START for buffer
> HeapByteBuffer@53c389d4[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>/m.sogou.com/?ran...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x4 for
> HttpChannelOverHttp@3e824b3e{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x4 in state=START for buffer
> HeapByteBuffer@64380bcf[p=1,l=10,c=16384,r=9]={\x04<<<\x01\x00P\xC0c\xF660\x00>>>
>
> HTTP/1.1\r\nUser-A...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x4 for
> HttpChannelOverHttp@605ff7ac{r=0,c=false,a=IDLE,uri=}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: Illegal character 0x5 in state=START for buffer
> HeapByteBuffer@53c389d4[p=1,l=3,c=16384,r=2]={\x05<<<\x01\x00>>>P\xC0c\xF660\x00/m.sogou.c...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
> Feb 10, 2017 5:30:25 AM org.eclipse.jetty.util.log.JavaUtilLog warn
> WARNING: badMessage: 400 Illegal character 0x5 for
> HttpChannelOverHttp@59989f5a{r=0,c=false,a=IDLE,uri=}
>
>
> Anyone can help or have ideas how to solve 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9aacc222-8133-4ca6-bb75-254ba142%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170824061209.u3c5dolrgcytuoff%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
Re: How to restrict access to some shared libraries methods
(replies inline) On Wed, 16 Aug 2017, Cristiano Kliemann wrote: > Hi, > > We are developing pipeline shared libraries to organize common tasks. Some > of the functionality involves deploying files to our binary repository. > We've decided to create small classes and methods to keep things simple and > maintainable. But we have some concerns about what the developer should > have access. Take the example below: On what basis are you intending to restrict the access? You can simply add Pipeline Shared Libraries at a Folder level, and only add the referenced Shared Library to a folder with "trusted" Pipelines. Or the deploy() method could maybe look at `env.JOB_NAME` to select from an inclusion list of Pipelines which execute the rest of the method body? Otherwise, I'm not sure how you might wish to restrict the usage. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170816143854.xmzlca6xwlrpb5x5%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Parameterized build driven by Jenkinsfile
(replies inline) On Wed, 02 Aug 2017, Craig Barr wrote: > In Jenkins you can select "This project is parameterized" and add > parameters. My question is simple: > Can this parameter metadata be populated by an alternative > version-controlled source? > > For example, can I define parameter definitions in my Jenkinsfile so that > when I click Build Now it will populate the parameters from this source? > If this is not possible, are they any other suggestions for addressing such > a requirement? My pal Liam created a screencast on this topic recently: https://www.youtube.com/watch?v=5_tvlaIeQUQ=youtu.be See also: https://jenkins.io/doc/book/pipeline/jenkinsfile/#parameters - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170809212559.4qi4ut3sxo5gbnfz%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Favorite plugin
(replies inline) On Thu, 08 Jun 2017, Christopher Orr wrote: > Hi there, > > On Thu, 8 Jun 2017, at 11:34, Eberhard Beilharz wrote: > > I'm using https://updates.jenkins-ci.org/stable/update-center.json as > > URL for the update site. > > > > When I check the JSON that gets returned from the update site I see that > > it contains the favorite plugin in version 1.16 from 7/2013, so there > > seems to be clearly something wrong. Would be good if that could be > > fixed. > > Yeah, this is unfortunate, but it is at least a known issue; see > https://issues.jenkins-ci.org/browse/INFRA-1215 This has since been fixed FWIW. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170609155035.3ggbaezpbi4rq3kp%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Why can't I put "bat" inside a stage when using Declarative Pipelines
(replies inline)
On Thu, 08 Jun 2017, Marley Kudiabor wrote:
> I'm wondering if I'm doing something wrong the syntax seems radically
> different between Declarative Pipelines and just placing everything inside
> a "node" block.
>
> I was wondering what format I should use to place pipeline steps inside of
> Declarative Pipelines
>
> For example
>
> node {
> stage ("stage") {
> bat ''' echo foo'''
> }
> }
>
> Works but
>
> pipeline {
>
> stage ("stage"){
> bat ''' echo foo
> }
>
> }
>
> Does not
What is the error that Jenkins gives you when you try this?
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170608224115.yixpt53e4qm7jgmd%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
Re: Jenkins pipeline shell set $HOME to /var/www
(replies inline)
On Thu, 08 Jun 2017, Changqin Xie wrote:
> Using the following Jenkinsfile:
> #!/usr/bin/env groovy
>
> pipeline {
> agent any
>
> stages {
> stage('Deploy') {
> steps {
> sh 'echo $HOME'
> }
> }
> }
> }
>
> And I get $HOME == /var/www
> Why isn't it being "/home/www-data"? By the way, I am running Jenkins under
> the user www-data.
I would be willing to bet that the home directory for the www-data user is
actually set to `/var/www` in /etc/passwd.
Most Linux packages set the home-directory for that user to /var/www
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170608165035.a6azgzxiplldv47m%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
Re: [Jenkins-infra] Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC
The wiki is back online, but some users may have difficulty logging in with fresh sessions. Confluence is still syncing user data from LDAP and is likely going to be doing so for the next couple hours. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170607183211.6ijht2y3kfij5hnz%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC
(replies inline) On Tue, 06 Jun 2017, R. Tyler Croy wrote: > > We're planning to perform a Confluence upgrade tomorrow in a maintenance > window > between 15:30 and 17:30 UTC (8:30 - 10:30 PDT). > > The ticket tracking this work is: > https://issues.jenkins-ci.org/browse/INFRA-1201 Just a heads up, this window is taking longer than we had hoped as some migrations timed out when running. I'm optimistic that we'll be wrapping this up in the next 30-45 minutes - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170607173253.dn4kjfukaeelbpqs%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC
We're planning to perform a Confluence upgrade tomorrow in a maintenance window between 15:30 and 17:30 UTC (8:30 - 10:30 PDT). The ticket tracking this work is: https://issues.jenkins-ci.org/browse/INFRA-1201 This is related to, and a continuation of, the work we did previously in April to get Confluence more up to date https://issues.jenkins-ci.org/browse/INFRA-325 Please join #jenkins-infra on Freenode for any questions, and as per usual I will send an all clear once the migration is complete. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170606224813.omyie3qc2fmolqza%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
JIRA downtime tomorrow (2017-06-07) between 16:00-18:00 UTC
The Oregon State University Open Source Lab (OSUOSL), which still hosts some of our infrastructure is moving hardware around in their datacenter tomorrow and will be briefly rebooting the machine which runs JIRA. The outage should be between 10-15 minutes in the 16:00-18:00 window, but we don't have a specific timeslot assigned right now. For any questions, please jump into the #jenkins-infra channel on Freenode and ask away - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170606162658.2zzkn25fyshbsrky%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Interpolating variables in agent's docker parameter
(replies inline)
On Wed, 17 May 2017, Bart??omiej Sacharski wrote:
> Hello.
>
> I'm trying to mount specific directory to a stage-only agent that will use
> docker in a declarative pipeline.
> It looks like this:
>
> > agent {
> > docker {
> > image "myimage:latest"
> > args "-v ${WORKSPACE}/out:/var/www/api/out"
> > }
> > }
> >
>
> However, this results in *No such property: WORKSPACE*. When I'm using
> *env.WORKSPACE* it is interpolated to *null* (also resulting in error).
> Does that mean that interpolation is only available for steps, or is there
> another trick (without resorting to scripted pipeline) to interpolate
> string properly in this case?
I believe interpolationg may work here, but I doubt the workspace or env would
be available since those are heavily agent-dependent. Basically this would be
referencing a variable before it has been created.
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170517192334.z67kdyaotzh2ogod%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
What's Italian for "New-poster moderation for Google Groups has been enabled?"
In response to our on-going battle against spam, we have grown the Google Group moderations teams for jenkinsci-dev@ and jenkinsci-users@. With more moderators, this means that we can enable "New poster" moderation. What this means is that, until further notice, first-time posters to these mailing lists will have their messages filtered to a special moderation queue, and must then be approved before being sent out. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170501201446.nsd5v5m7xf6nwcfa%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Colombian Jenkins users we need your help
Kohsuke posted some details in this blog post: https://jenkins.io/blog/2017/04/27/colombia/ The gist of the issue is that somebody is trying to use/register the Jenkins trademark in Colombia. If you're one of the many Colombian Jenkins users, please take a moment to read the blog post. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170428164347.kac5rda5ruyse3ki%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: BlueOcean: missing visual pipeline editor
(replies inline) On Fri, 21 Apr 2017, Ramanathan Muthaiah wrote: > Hello, > > In the BlueOcean UI, I chose Git and provided the repo name hosted within > organization umbrella. However, with this choice, visual pipeline editor is > not visible. > > Does anyone why is this and what am missing ? Git is not yet fully supported for the editor, only GitHub, see: https://issues.jenkins-ci.org/browse/JENKINS-43148 - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170421163238.4lre6nvdk5xvkjkm%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Jenkins Mirror is down
(replies inline) On Mon, 17 Apr 2017, Devon wrote: > Hi there > > I am trying to update my Jenkins instance but it fails due to the mirror it > is being redirected to being unable to process the request. > > URL I get: http://ftp.icm.edu.pl/packages/jenkins/war/2.55/jenkins.war > > Message being displayed: > > > > ICAP Error (icap_error) > > An error occurred while performing an ICAP operation: Maximum total files > in archive exceeded; File: jenkins.war; Sub File: ; Vendor: Sophos, Plc.; > Engine version: 3.68.1; Pattern version: 5.38.13086169.0; Pattern date: > 2017/04/18 04:33:40 > > There could be a network problem, the ICAP service may be misconfigured, or > the ICAP server may have reported an error. > > > For assistance, contact your network support team. > > > > Currently I am unable to update my Jenkins instance (plugin updating does > work fine). Is there a way to have Jenkins use another mirror? > > FYI: I'm located in Belgium/Netherlands Between this message and https://issues.jenkins-ci.org/browse/INFRA-1154, I think I am going to just disable this mirror until further notice. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170419162422.ljiuc3c7noiktu4i%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Check to see if a Pipeline step exist?
(replies inline) On Mon, 17 Apr 2017, Sam K wrote: > Hi > >You can use this link to keep track of what is already available and > what is not. > https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md This resource is a much more comprehensive reference: https://jenkins.io/doc/pipeline/steps/ A background process searches all plugins which extend Pipeline extension points and generates that page. Unless there has been some failure to generate, which rarely happens, that page will be very up to date. Now to the original poster's original question: > > For example, the "archiveArtifacts" step doesn't exist in Jenkins 1.x. > > Does anyone have a similar problem? https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-archive-code-archive-artifacts As the documentation mentions, archiveArtifacts is only supported on Jenkins 2.x I strongly recommend upgrading to the latest Jenkins 2.46.1 LTS, there are a tremendous number of bugs fixed and security issues addressed which are only available in more current LTS releases. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170417193611.jmtlf4rlkmvdll2n%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Regarding the recent waves of mailing list spam
As you may have noticed, there has been an uptick in spam getting through to the Google Groups run by the Jenkins project. On some lists, these have resulted in Google flagging the group and bouncing emails from those groups. This was discussed during our last project meeting (http://meetings.jenkins-ci.org/jenkins-meeting/2017/jenkins-meeting.2017-04-12-18.00.html), and as promised I wanted to let everybody know where things stand and why. If you receive emails as they're posted (non-digest mode) from Google Groups, if a spamemr gets through, there's nothing we can do for you. While I have added a couple more "Manager" roles to the jenkinsci-users@ list, who can ban authors and delete posts, once something is delivered to your inbox, there's nothing we can do. Some people have suggested first-poster moderation, which is one option, but not one I'm personally willing to turn on until more people are active moderators. Unfortunately I took a weekend off from my morning-routine of banning spammers two weekends ago, which seems to have led to the recent surge and flagging of the group. What we are evaluating between last project meeting and the upcoming one (April 26) is whether Google Groups is still a viable option for the Jenkins project. A number of other projects have moved to groups.io, which would be a likely destination if Google continues to flag our groups. Consider yourselves updated, feel free to ping me on IRC (rtyler) with questions. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170417155333.h7l2ecplmhbcg2ut%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Cannot register, post anonymously on Jenkins Wiki
(replies inline) On Wed, 05 Apr 2017, Anne van der Bom wrote: > Hi there, > > I wanted to post a question regarding the Paremeterized Scheduler Plugin > here: > > https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Scheduler+Plugin > > I don't have a login, but according to the text on the screen, you can post > anonymously. But when I try I get a 403-forbidden. > > So I click on the 'Sign up' > link: https://wiki.jenkins-ci.org/signup.action, which redirects me > to https://accounts.jenkins.io/ But on that page I can not find an option > to register anywhere. > > What am I supposed to do to post on the jenkins wiki? Posting comments to the wiki is not the right place to get help with any particular plugin or feature of Jenkins. Please ask your question on this mailing list. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170405180531.l7xzyb3wevjssmz6%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [Jenkins-infra] Wiki downtime/maintenance window scheduled for 2017-04-01 16-18:00 UTC
(replies inline, dropping jenkinsci-users) On Sun, 02 Apr 2017, JordanGS wrote: > Congrats on the update! There seem to be some issues with the new system > tho. All of my old wiki pages cannot be modified or new edits saved. The > page throws a *Content Encoding Error*. > > See wiki link <https://wiki.jenkins-ci.org/display/JENKINS/zap+plugin>. Were you able to figure this out? I successfully edited this page (https://wiki.jenkins-ci.org/pages/viewpreviousversions.action?pageId=102662470) I'm wondering if you hit the issue orrc filed, which I have since resolved. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170403145848.gde77gsuin32ju57%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [Jenkins-infra] Wiki downtime/maintenance window scheduled for 2017-04-01 16-18:00 UTC
(replies inline) On Sat, 01 Apr 2017, R. Tyler Croy wrote: > (replies inline) > > On Fri, 31 Mar 2017, R. Tyler Croy wrote: > > > > > As promised/threatened a while ago, I am planning to ugprade Confluence on > > April 1st (no joke!). In the process of upgrading Confluence, we will also > > be > > re-sizing the VM it currently lives on for better performance. As such, > > please > > do not expect wiki.jenkins-ci.org to be servicing requests from 16:00 - > > 18:00 > > UTC. > > > > > > The JIRA tracking this work is: > > https://issues.jenkins-ci.org/browse/INFRA-325 > > > > The maintenance window is taking a bit longer, lots of shuffling bits around > on > disk and database migrations are slowing us down. > > We're upgraded to Confluence 5.0.3, and will continue the migration to 6.1.0 > once the re-sizing of the VM completes by the OSUOSL. Things took a *lot* longer than I had hoped during the "embiggen the VM" phase as the legacy VM required a little bit more work to upgrade in the OSUOSL Ganeti cluster. Additionally the backend MySQL DB servers (operated by OSUOSL) are 5.5 and 5.6, the latter which would support Confluence 6.1.0 doesn't have the appropriate innodb settings to support our upgrade right now. While attempting to get us to at least 5.10.8, I discovered that there are additional MySQL library changes which we need to incorporate into our image to make everything happy. What made this whole endeavour complicated was needing to actually perform *three* upgrades rather than one, going from 3.4.7 => 3.5.17, then 3.5.17 => 5.0.3, and finally attempted 5.0.3 => 6.1.0^W5.10.8. The first two required significant data migrations, upgrading from some old tables from MyISAM to InnoDB, and then Confluence's own migrations on top of that. Suffice it to say, *tons* of disk I/O. We saturated disk I/O on the MySQL cluster more than once during this process. As it stands right now, 5.0.3 is up and running, and things appear sane. I'll keep an eye on things and re-evaluate the upgrade path to 6.1.0 once I can discuss with olblak our options a bit more. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170401224249.kp46lmg635ahsdwt%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [Jenkins-infra] Wiki downtime/maintenance window scheduled for 2017-04-01 16-18:00 UTC
(replies inline) On Fri, 31 Mar 2017, R. Tyler Croy wrote: > > As promised/threatened a while ago, I am planning to ugprade Confluence on > April 1st (no joke!). In the process of upgrading Confluence, we will also be > re-sizing the VM it currently lives on for better performance. As such, please > do not expect wiki.jenkins-ci.org to be servicing requests from 16:00 - 18:00 > UTC. > > > The JIRA tracking this work is: > https://issues.jenkins-ci.org/browse/INFRA-325 The maintenance window is taking a bit longer, lots of shuffling bits around on disk and database migrations are slowing us down. We're upgraded to Confluence 5.0.3, and will continue the migration to 6.1.0 once the re-sizing of the VM completes by the OSUOSL. I am hoping to wrap up by 20:00 UTC - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170401190046.4cchobczyyv6lgc4%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Wiki downtime/maintenance window scheduled for 2017-04-01 16-18:00 UTC
As promised/threatened a while ago, I am planning to ugprade Confluence on April 1st (no joke!). In the process of upgrading Confluence, we will also be re-sizing the VM it currently lives on for better performance. As such, please do not expect wiki.jenkins-ci.org to be servicing requests from 16:00 - 18:00 UTC. The JIRA tracking this work is: https://issues.jenkins-ci.org/browse/INFRA-325 Please join #jenkins-infra for any questions, and as per usual I will send an all clear once the migration is complete. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170331172327.xayfb7uqio77yepo%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Interactive input with new DSL
(replies inline) On Mon, 06 Mar 2017, Travis Camechis wrote: > So if you define an agent of none within a stage it will override the > higher level pipeline stage ? Correct, the previously linked documentation has an example of a stage-level "agent" directive. > On Monday, March 6, 2017 at 2:39:42 PM UTC-5, R Tyler Croy wrote: > > > > (replies inline) > > > > On Mon, 06 Mar 2017, Travis Camechis wrote: > > > > > With scripted DSL your not supposed to ask for input inside a node so > > you > > > don't tie up an executor while waiting for user input. How is this same > > > thing accomplished in the new DSL ? It seems like everything runs > > inside a > > > node with the new DSL ? > > > > > > > > > A single stage can use "agent none" > > http://jenkins.io/doc/book/pipeline/syntax/#agent > > > > > > > > - R. Tyler Croy > > > > -- > > Code: <https://github.com/rtyler> > > Chatter: <https://twitter.com/agentdero> > > xmpp: rty...@jabber.org > > > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > > -- > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/c59b475a-35c5-41cd-b7b0-dc2a8b1029c6%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170306222514.j22tdxz6wv552ft4%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [Jenkins-infra] JIRA downtime/maintenance window scheduled for 2017-03-04 16:00 UTC
(replies inline) On Mon, 27 Feb 2017, R. Tyler Croy wrote: > > I'm planning on performing a scheduled upgrade of JIRA (issues.jenkins-ci.org) > this Saturday at 16:00 UTC / 8:00 PST. I don't expect the work to last longer > than 60 minutes, but please expect JIRA to be offline for at least the full > hour. > > The JIRA tracking this (hehe) is: > <https://issues.jenkins-ci.org/browse/INFRA-1010> JIRA has been upgraded, yay. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170304162314.o6iyyphwiihqwzgp%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: downloading files > 1G
(replies inline) On Fri, 03 Mar 2017, Richard Ginga wrote: > I have been struggling all day with a simple problem...I can't download and > archived file of 1.46Gb. That is the size on the slave and the size > reported by Jenkins but when I click to download it, I get 1G. Use the Fingerprint for the file presented in the UI and compare that to an `md5sum` of the file itself. You may be getting the right file, but one place may be reporting with 1000-based versus 1024-based megabytes. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170303214957.dylqj2dqbrqtzs2k%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
JIRA downtime/maintenance window scheduled for 2017-03-04 16:00 UTC
I'm planning on performing a scheduled upgrade of JIRA (issues.jenkins-ci.org) this Saturday at 16:00 UTC / 8:00 PST. I don't expect the work to last longer than 60 minutes, but please expect JIRA to be offline for at least the full hour. The JIRA tracking this (hehe) is: <https://issues.jenkins-ci.org/browse/INFRA-1010> Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170227204615.uozusmypdfmsppsm%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Multi Configuration Job Jenkinsfile
(replies inline) On Thu, 23 Feb 2017, Chris Denneen wrote: > Sathish? What are you referring to here? > This is UI configuration. I've had this for a while. > I'm looking for Jenkinsfile equivalent. There is no such thing as a "Multiconfiguration Pipeline" as such in Pipeline. You might find the use of the parallel() step to be helpful here however: https://jenkins.io/doc/book/pipeline/jenkinsfile/#advanced-scripted-pipeline - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170223204415.jsko7a6zrioa6fsk%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: Problem with docker agent (declarative syntax)
(replies inline)
On Thu, 09 Feb 2017, Bart??omiej Kruczyk wrote:
> Hi, I have problem with setting docker agent type for my pipeline.
>
> Although something like this works:
>
>
> agent {
> docker 'myimage'
>
> }
>
>
> This does not:
>
>
> agent {
> docker {
> image: 'myimage'
>
> registry: 'localhost:5000'
>
> }
> }
As far as I am aware, there is no supported "registry" value inside that
`docker` block.
See also https://jenkins.io/doc/book/pipeline/syntax/#agent
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170210093934.GC26439%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: Unable to use the "when" closure to skip a stage (pipeline-model-definition-plugin)
(replies inline)
On Thu, 09 Feb 2017, Roi Aldaag wrote:
> for a very simple pipeline in the inline pipeline editor (not in an
> external Jenkinsfile):
>
> *node {*
> * stage('1') { // for display purposes*
>
> * }*
> * stage('2') {*
> *when {*
> *//return false*
> *}*
> * }*
> * stage('3') {*
>
> * }*
> *}*
This Jenkinsfile is _not_ a Declarative Pipeline but is instead using the
Scripted Pipeline syntax.
A Declarative Pipeline *must* have a `pipeline { }` outer block, and a number
of other required sections, and `when` is only applicable within Declarative.
Otherwise you can just use normal Groovy conditionals.
See this document for more: https://jenkins.io/doc/book/pipeline/syntax/
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170209101121.GA26439%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: Jenkins2 pipeline - Global methods in shared-library fails when invoked
(replies inline)
On Thu, 02 Feb 2017, Tor Christian Solev?gseide wrote:
> I was finally able to solve this myself. The problem was how I referenced
> the shared library. Apparently, I need to add the underscore character to
> the end if my @Library annotation like this:
> @Library('customized-portal-lib') _
>
> Also, I must make sure to not import my global *acme *variable.
>
> This is documented
> in https://jenkins.io/doc/book/pipeline/shared-libraries/ for those who
> take their time to fine read it (which I didn't at first):
FWIW, the underscore character is kind of a cute little hack. @Library is an
annotation so it must annotate *something*, annotating the underscore is kind
of like annotating a throwaway unused character. Technically you're able to
annotate other statements, as the section in the handbook describes
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20170202112955.GJ26439%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: Japan mirrors unstable
(replies inline) On Thu, 26 Jan 2017, Noam Tamim wrote: > I run my Jenkins server in Israel, and when accessing > http://mirrors.jenkins-ci.org, I get redirected to mirrors in Japan. > However - with those servers, downloads never finish. More often than not, > I get "Connection reset by peer" errors. > > Further, even though Israel and Japan are both technically in Asia - Israel > is closer to Europe and the Internet connections to Europe are much > stronger. > > For those reasons, please redirect Israel requests to one of the European > mirrors. Do you know which japanese mirrors you're hitting, we have a couple. A wget or curl with verbosity turned up would probably help nail it down. Unfortunately, I don't believe I can lock requests from a specific country to a different set of mirrors, but if there is a slow or unstable link, I can tweak the settings for that specific mirror. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20170126210242.GB26439%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Request for participation: Jenkins Security Officer candidates
In this week's Governance Meeting it was announced that the board has appointed Daniel Beck to his second term as the Jenkins Security Officer See <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board#Officers> For more information about Jenkins CERT or our responsible disclosure policies, please see: https://jenkins.io/security/ On Mon, 21 Nov 2016, R. Tyler Croy wrote: > > First, let me thank Daniel Beck for his work as the inaugural Jenkins Security > Officer over the past year. I would also like to thank the numerous members of > the CERT[0] team who have helped Daniel guide the project's security policies, > disclosures and updates. > > In accordance with our previously agreed upon team lead proposal > (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) > I am now asking, again, on behalf of the Jenkins board[1] for candidates who > are willing to act as the Jenkins Security Officer. > > > The responsibilities of the Jenkins Security Officer would be to lead Jenkins > Security (CERT) team, and: > > * Run the Jenkins CERT meeting > * Manage sending gifts to qualifying reporters of resolved security issues [2] > * Coordinate work on, and releases, of security fixes with plugin authors, > Kohsuke and the LTS team lead > * Publish Security Advisories (including CVE IDs and CVSS) and notify the > mailing > list > * Drive security policy definition/changes in the community > * Represent the Jenkins project on security topics with third parties > > > The expected term of the Security Officer would be 12 months. > > > > Contributors interested in being considered for the Jenkins Security Officer > position should email the board: jenkinsci-bo...@googlegroups.com in the *next > seven days* explaining their qualifications for the position. > > In seven days the board will select a candidate to appoint to the position who > will be able to act on behalf of the Governance Board on matters pertaining to > the position described above > > > Thanks! > > > [0] https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CERT+team > [1] The current board: > <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board> > [2] > https://wiki.jenkins-ci.org/display/JENKINS/Rewards+for+reporting+security+issues > > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > -- > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/20161121214738.GA3000%40blackberry.coupleofllamas.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161209212142.GB21965%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Request for participation: Jenkins Security Officer candidates
First, let me thank Daniel Beck for his work as the inaugural Jenkins Security Officer over the past year. I would also like to thank the numerous members of the CERT[0] team who have helped Daniel guide the project's security policies, disclosures and updates. In accordance with our previously agreed upon team lead proposal (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams) I am now asking, again, on behalf of the Jenkins board[1] for candidates who are willing to act as the Jenkins Security Officer. The responsibilities of the Jenkins Security Officer would be to lead Jenkins Security (CERT) team, and: * Run the Jenkins CERT meeting * Manage sending gifts to qualifying reporters of resolved security issues [2] * Coordinate work on, and releases, of security fixes with plugin authors, Kohsuke and the LTS team lead * Publish Security Advisories (including CVE IDs and CVSS) and notify the mailing list * Drive security policy definition/changes in the community * Represent the Jenkins project on security topics with third parties The expected term of the Security Officer would be 12 months. Contributors interested in being considered for the Jenkins Security Officer position should email the board: jenkinsci-bo...@googlegroups.com in the *next seven days* explaining their qualifications for the position. In seven days the board will select a candidate to appoint to the position who will be able to act on behalf of the Governance Board on matters pertaining to the position described above Thanks! [0] https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CERT+team [1] The current board: <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board> [2] https://wiki.jenkins-ci.org/display/JENKINS/Rewards+for+reporting+security+issues - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161121214738.GA3000%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled infrastructure maintenance Oct 27 00:00 UTC
I am pleased to report that the maintenance window has completed, and outside of some Docker annoyances everything went fairly well. I will continue to keep an eye on services for the next couple hours just in case, but please continue your regularly scheduled Jenkins hacking :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161027012225.GO3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Scheduled infrastructure maintenance Oct 27 00:00 UTC
I am scheduling a maintenance window for later today (17:00 PDT / 00:00 UTC) for 60 minutes to apply some new kernel patches to the project's infrastructure. The ticket to track this work can be found here: <https://issues.jenkins-ci.org/browse/INFRA-958> This will be a simple update and reboot so service outages should be minimal. I will update this thread once everything has been completed. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161026171049.GN3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: PermGen issue
(replies inline) On Thu, 13 Oct 2016, vishad alekh wrote: > Hi All, > > I am using Jenkins 2.11. My Jenkins is frequently going down with permGen > issue. > Even if I am not executing any jobs. > My server configuration is pretty good too. > > Can someone please assist with the possible reason for the same. Or any way > in which this can be resolved. > > I have tried increasing the permGen space by passing parameter at the time of > startup but no luck. > > Maven configuration is also done for the same. Out of curiosity are you using Multibranch Pipeline heavily? The fact that you're having a PermGen issue means you're likely running on JDK7, can you tell us anything else about your environment? - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161014011749.GT3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled maintenance for JIRA, Wiki, Accounts, DNS, etc 2016-09-29 22:00-23:00 UTC
(replies inline) On Wed, 28 Sep 2016, R. Tyler Croy wrote: > The ticket this is related to is: > <https://issues.jenkins-ci.org/browse/INFRA-935> > > The services this will affect are: > > * JIRA (https://issues.jenkins-ci.org) > * Confluence (https://wiki.jenkins-ci.org) > * Accounts management (https://accounts.jenkins.io) > * jenkins-admin ircbot > * robobutler ircbot > * DNS services > * demo.jenkins-ci.org > * Docker-capable build agents attached to https://ci.jenkins.io I have completed all the maintenance necessary and am happy to report that our Docker-based services are back online and operational :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160929230948.GB3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Scheduled maintenance for JIRA, Wiki, Accounts, DNS, etc 2016-09-29 22:00-23:00 UTC
Consider this notice that we will be performing scheduled maintenance during a 60 minute window tomorrow September 29th (UTC). I will be taking various services which are deployed via Docker containers temporarily offline as we upgrade the underlying Docker daemons. We will be iterating through machines which host containers one by one, so a total outage should not be experienced. The ticket this is related to is: <https://issues.jenkins-ci.org/browse/INFRA-935> The services this will affect are: * JIRA (https://issues.jenkins-ci.org) * Confluence (https://wiki.jenkins-ci.org) * Accounts management (https://accounts.jenkins.io) * jenkins-admin ircbot * robobutler ircbot * DNS services * demo.jenkins-ci.org * Docker-capable build agents attached to https://ci.jenkins.io I will send an all-clear when the maintenance has completed. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160928200630.GX3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Can't download plugins - HTTP 302 redirect
(replies inline) On Sat, 17 Sep 2016, Corey Wei wrote: > Hi, > > My Jenkins 2.22 is working with Tomcat. There are some errors while I tried > to install plugins like this: > > 18-Sep-2016 11:17:05.590 SEVERE [Update center installer thread [#1]] > hudson.model.UpdateCenter$DownloadJob.run Failed to install GIT server > Plugin > java.io.IOException: Downloaded file > /home/deploy/.jenkins2/plugins/git-server.jpi.tmp does not match expected > SHA-1, expected 'LoG8X55ycVzgPjwTtCA/iKb7lvw=', actual > 'Lbk3pB/mu/UlYJO4o2ttQkZ+mvs=' I recently added a mirror located in China (https://issues.jenkins-ci.org/browse/INFRA-924). Would you mind downloading some files and comparing between the mirror you're hitting and: http://ftp-nyc.osuosl.org/pub/jenkins/ If that mirror is serving corrupted artifacts I will remove it from the rotation immediately. > at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1799) > at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) > at > hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1950) > at > hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194) > at > hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1669) > at > hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1864) > at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) > at java.lang.Thread.run(Thread.java:745) > > $ cat ~/.jenkins2/plugins/git-server.jpi.tmp > > > 302 Found > > Found > The document has moved href="https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/git-server/1.7/git-server.hpi;>here. > > > Looks like it redirects to a mirror update center. > > Any comments would be appreciated. > > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/f1aca3c2-9edb-4c41-addb-042bbb5bae85%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160918065838.GB3357%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: pipeline multi branch, how to continue if error occures
(replies inline)
On Mon, 12 Sep 2016, Klaus Rudolph wrote:
> Hi all,
>
> if I use gtest in pipeline setup and have a unit test which fails the groovy
> script stops.
>
> How can I tell the script that I want to continue so that I am able to see
> the results from xunit/gtest plugin?
>
> From the gui without running Jenkinsfile there I had to write "set +e" in the
> dialog box, but I don't know how to write that in groovy.
If the issue is just a single `sh` command return a non-zero exit code, then
you can avoid that with:
sh './test-runner.sh || true'
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20160913021041.GP18556%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: warnings graph in multibranch pipeline projects
Moin Klaus!
Klaus Rudolph schrieb am Monday, den 12. September 2016:
> I started to migrate some jobs in jenkins to pipeline execution.
>
> Is there any chance to see the warnings graph in pipeline jobs? Within my
> older projects I can configure the graphs with "Configure the trend graph"
> option. These option will crash in the pipeline syntax tool.
This issue might be relevant to your question:
https://issues.jenkins-ci.org/browse/JENKINS-31202
Do you not see graphs on the build specific pages too?
>
> Is there any option to make the graph visible?
>
> I have in my Jenkinsfile:
>
> stage ('Warnings gcc') {
> step([$class: 'WarningsPublisher', canComputeNew: false,
> canResolveRelativePaths: false, defaultEncoding: '', excludePattern: '',
> healthy: '', includePattern: '', messagesPattern: '', parserConfigurations:
> [[parserName: 'GNU Make + GNU C Compiler (gcc)', pattern:
> 'error_and_warnings.txt']], unHealthy: ''])
> }
>
> stage ('Warnings clang') {
> step([$class: 'WarningsPublisher', canComputeNew: false,
> canResolveRelativePaths: false, defaultEncoding: '', excludePattern: '',
> healthy: '', includePattern: '', messagesPattern: '', parserConfigurations:
> [[parserName: 'Clang (LLVM based)', pattern:
> 'error_and_warnings_clang.txt']], unHealthy: ''])
> }
>
> The reports will be generated but no graph is displayed. Any hints?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-860cbe76-3605-4d4b-903e-a3cb43a58741-1473687526354%403capp-gmx-bs24.
> For more options, visit https://groups.google.com/d/optout.
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20160913020902.GO18556%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: Is it possible to aggregate all tests in a pipeline?
(replies inline)
On Fri, 05 Aug 2016, Marc Esher wrote:
> Greetings,
>
> I'm pretty new to pipelines, and I'm coming to them from the perspective of
> replacing Build Flow plugin with Pipelines.
>
> One thing I've found really valuable with Build Flow is the Build Flow Test
> Aggregator plugin, which makes it easy to see all the different test jobs
> (unit, functional, load, security, etc) that comprise a Build Flow in a
> single place.
>
> I'm wondering: If I have a Pipeline that essentially just replicates what
> I'd normally do with a build flow -- building other jobs -- is there a way
> to aggregate all the tests in a single place?
>
> And if not, where would I look for guidance on how to build a plugin to
> integrate into Pipeline to do that?
If you're actually invoking other defined jobs in Jenkins via Pipeline (see the
`build` step), then no I do not believe this is currently feasible.
However, if you're defining a Pipeline which is going to have multiple
steps generating test reports, I believe multiple invocations of `junit` will
cover your nedes. For example:
node {
sh 'bundle exec rake spec'
junit 'spec/reports/*.xml'
sh 'bundle exec rake cucumber'
junit 'features/reports/*.xml'
}
That should meet your needs if I'm understanding correctly.
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20160806011539.GM22427%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Branch Indexing/Poll SCM equivalent with the GitHub Organization Folder
Posting this to the list because I figure the answer might be useful for posterity. With the GitHub Organization Folder there is the "Periodically if not otherwise run" Build Trigger which is set to "1 day" by default. >From my understanding this also means that branch indexing on those repositories in the organization, in effect, are also "running" once a day (since the org is reindexed daily). I'm curious if there is an endpoint to hit with a GitHub Webhook which will ensure that pull requests and new branches are built on-demand? Additionally, if my Jenkins installation is unreachable by GitHub (e.g. behind a firewall), are there any other tunables I can use to ensure that branches and pull requests are discovered in specific repositories in a more timely manner, is ""reindex the entire organization" my only option? Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160804173201.GJ22427%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: How Do You Manage Growth?
(replies inline) On Thu, 28 Jul 2016, rqui wrote: > I am seeking some advice/tips. Our group is experiencing fast growth and > changes and I am trying to architect a solution for managing it. > > We currently have a single master handling various types of jobs: ci, > nightlies, releases, personal dev builds, etc. > > Using OSS, does anyone have experience in handling several masters for > handling the different functions: CI, Releases, DEV? > > Or, do you continue to use a single Jenkins master? > > Any help, advice or tips would be greatly appreciated. I will assume that you are not running jobs on the master, if you are, that's the first step to growing is removing all workloads from the master and delegating them to agents. For most use-cases I have either worked with or seen, delegating work to the agents and then putting a beefy machine in place for the master (fast disk I/O) is sufficient to grow into the many hundreds of jobs/thousands of builds per day. If you're growing past that, I suggest splitting into multiple independent masters based on the workloads associated with them. For example, I might break out the jobs for the "mobile team" to a new master infrastructure since they have Android/iOS build requirements and let the "server" team stick to another master with a number of Linux agents. This has the added benefit of separating concerns, plugins and access control based on logic separations inside your organization. Hope that helps point you in the right direction. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160728193352.GZ22427%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: accounts.jenkins.io problems not able to reset password or sign up
(replies inline) On Tue, 26 Jul 2016, Narahari 'n' Savitha wrote: > Hello: > I tried to reset the password on the accounts.jenkins.io site and here is > what I see. Please try again an issue behind the scenes was preventing the LDAP operations from completing. > > *HTTP ERROR 500* > > Problem accessing /doPasswordReset. Reason: > > Server Error > > > *Caused by:* > > javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error > code 28 - entry update failed]; remaining name > 'cn=savithari,ou=people,dc=jenkins-ci,dc=org' > > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) > > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) > > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) > > at org.kohsuke.stapler.Stapler.service(Stapler.java:238) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837) > > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) > > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174) > > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) > > > Even if I try to signup I get the same > > > *HTTP ERROR 500* > > Problem accessing /doSignup. Reason: > > Server Error > > > *Caused by:* > > javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error > code 80 - Other]; remaining name > 'cn=narahari,ou=people,dc=jenkins-ci,dc=org' > > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) > > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) > > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) > > at org.kohsuke.stapler.Stapler.service(Stapler.java:238) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837) > > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) > > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174) > > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) > > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106) > > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > > at org.eclipse.jetty.server.Server.handle(Server.java:524) > > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319) > > > Can I get some help please ? > > > -Narahari > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/a81fff6d-8353-443d-99e8-8b472529775c%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160727144242.GX22427%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Brief maintenance on (mirrors|updates).jenkins.io June 30 00:00 UTC
This maintenance has been completed On Wed, 29 Jun 2016, R. Tyler Croy wrote: > > I need to perform some maintenance on the machine that powers the mirror > redirector (mirrors.jenkins.io) and the update center (updates.jenkins.io) > tonight at 17:00 PDT or 00:00 UTC. > > This should be brief and entail stopping/starting the host to move it to new > hardware in AWS; that's the best advice I have gotten for addressing the > hidden > cloud goblins that have been affecting our network performance as of late. > > > The downtime should be no more than 30 minutes. > > > > Cheers > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > -- > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/20160629172443.GU9025%40blackberry.coupleofllamas.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160630003356.GV9025%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Brief maintenance on (mirrors|updates).jenkins.io June 30 00:00 UTC
I need to perform some maintenance on the machine that powers the mirror redirector (mirrors.jenkins.io) and the update center (updates.jenkins.io) tonight at 17:00 PDT or 00:00 UTC. This should be brief and entail stopping/starting the host to move it to new hardware in AWS; that's the best advice I have gotten for addressing the hidden cloud goblins that have been affecting our network performance as of late. The downtime should be no more than 30 minutes. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160629172443.GU9025%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Unable to update the Jenkins plugin page
t; org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > at > jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) > > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > > at > hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) > > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > at > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) > > at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) > > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > > at > org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) > > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > > at > hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) > > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > > at > org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) > > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) > > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) > > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) > > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) > > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) > > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) > > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) > > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) > > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) > > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) > > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) > > at org.eclipse.jetty.server.Server.handle(Server.java:370) > > at > org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) > > at > org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) > > at > org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) > > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) > > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) > > at > org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) > > at > org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) > > at > org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) > > at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/089db825-2f9e-40f2-aa8b-405996b5308e%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160628154906.GQ9025%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled infrastructure maintenance window June 14 00:00 UTC
(replies inline) On Mon, 13 Jun 2016, R. Tyler Croy wrote: > Reminder, this will be happening in about 45 minutes issues.jenkins-ci.org is back online with JIRA 7.1.7, wheee! The majority of the maintenance window was actually taking a full backup, once that was completed the upgrade process only took about 10 minutes! I'll be lingering on #jenkins-infra for another hour or two to make sure things are performing as they should. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160614001246.GR6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Scheduled infrastructure maintenance window June 14 00:00 UTC
Reminder, this will be happening in about 45 minutes On Wed, 08 Jun 2016, R. Tyler Croy wrote: > Consider this notice that there will be a scheduled maintenance window June > 14th > 00:00 UTC or June 13th 16:00 PDT for project infrastructure. > > This is a followup window to try to get JIRA upgraded, which we punted during > last week's maintenance window. > > The work is tracked in this ticket > (https://issues.jenkins-ci.org/browse/INFRA-725), and should only affect > availability of issues.jenkins-ci.org for about an hour. > > > Please bear with any service interruptions during this time :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160613221504.GP6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Scheduled infrastructure maintenance window June 14 00:00 UTC
Consider this notice that there will be a scheduled maintenance window June 14th 00:00 UTC or June 13th 16:00 PDT for project infrastructure. This is a followup window to try to get JIRA upgraded, which we punted during last week's maintenance window. The work is tracked in this ticket (https://issues.jenkins-ci.org/browse/INFRA-725), and should only affect availability of issues.jenkins-ci.org for about an hour. Please bear with any service interruptions during this time :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160608232156.GC6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled infrastructure maintenance window June 3 00:00 UTC
Any we're done, closing out INFRA-731 (https://issues.jenkins-ci.org/browse/INFRA-731) Tune in next week for when we, hopefully, roll out that JIRA 7 upgrade. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160603013518.GN6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled infrastructure maintenance window June 3 00:00 UTC
(replies inline) On Thu, 02 Jun 2016, R. Tyler Croy wrote: > (replies inline) > > On Wed, 01 Jun 2016, R. Tyler Croy wrote: > > > > > Consider this notice that there will be a scheduled maintenance window June > > 3rd > > 00:00 UTC or June 2nd 16:00 PDT for project infrastructure. > > > > The work is tracked in this ticket > > (https://issues.jenkins-ci.org/browse/INFRA-731) and should last between 1-2 > > hours. > > > This work is beginning, some services may be periodically on/off-line for the > next couple hours. Work is still on-going. I have had to punt the JIRA upgrade until next week unfortunately, and am slowly working my way through the various security updates in our various datacenters >_< - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160603010613.GM6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-infra] Scheduled infrastructure maintenance window June 3 00:00 UTC
(replies inline) On Wed, 01 Jun 2016, R. Tyler Croy wrote: > > Consider this notice that there will be a scheduled maintenance window June > 3rd > 00:00 UTC or June 2nd 16:00 PDT for project infrastructure. > > The work is tracked in this ticket > (https://issues.jenkins-ci.org/browse/INFRA-731) and should last between 1-2 > hours. This work is beginning, some services may be periodically on/off-line for the next couple hours. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160602231154.GL6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Scheduled infrastructure maintenance window June 3 00:00 UTC
Consider this notice that there will be a scheduled maintenance window June 3rd 00:00 UTC or June 2nd 16:00 PDT for project infrastructure. The work is tracked in this ticket (https://issues.jenkins-ci.org/browse/INFRA-731) and should last between 1-2 hours. Please bear with any service interruptions during this time :) Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160601214344.GG6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins JIRA account access
(replies inline) On Wed, 01 Jun 2016, Robert Simon wrote: > Hi, > > my account (robsimon) for the Jenkins JIRA > (https://issues.jenkins-ci.org/secure/Dashboard.jspa) stopped working. I > tried to reset the password however it appears that I forgot to update my > email address so I cannot access any password update. The reset password > page (https://accounts.jenkins.io/passwordReset) also offers to solve this > by writing to the team and there is no email or online form provided to do > this. > > My questions: > * have the JIRA passwords recently being reset as I store mine in a > password fault and didn't change it > * how can I reach the password reset team to recover my account (robsimon) The account (accounts.jenkins.io) had an old java.net email associated with it. I have changed it to reflect use the notification email that was set in JIRA (which was actually different). You should receive a password reset shortly at the email address that was configured in JIRA. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160601172924.GC6548%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Azure and latency issues
(replies inline) On Wed, 11 May 2016, Jo Shields wrote: > Hi all, > > I'm observing a problem with our new Jenkins master, running on an Ubuntu > VM on a high-spec Azure instance - latency between master and workers is > *crazy* high. Like 30 plus seconds: > https://jenkins.mono-project.com/computer/. The SSH-based workers can > generally survive that, but the JNLP workers time out and kill running jobs > (we're using JNLP for non-cloud workers as it makes our network management > way simpler). And Jenkins does a pretty dreadful job of keeping track of > whether workers are connected or not, so I end up having to restart the > master to kick-start things. It's basically a nightmare. > > It seems we're not the only people running Jenkins on Azure showing obscene > response times, e.g. http://dotnet-ci.cloudapp.net/computer/ - so the > question is whether anyone else on the list has observed this, or (even > better) resolved it. > > The master isn't under high IO, network, memory or CPU load, seems well > supplied with entropy; and the failures don't seem to correlate with Java > GC pauses; so I'm not sure where to point the finger. That is some pretty awful latency. I'm cuhrious whether the master/agents are on different Virtual Networks? Have you also reached out to Azure support about this? Since this is primarily affecting the JNLP agents, I would be skeptical of what software-defined-networking stuff inside Azure might be doing to that traffic that it is not doing to SSH traffic. I would be surprised if the JNLP support in Jenkins were the culprit - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160511180024.GX30995%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: HTTPS Jenkins update site
(replies inline) On Tue, 10 May 2016, Daniel Beck wrote: > > > On 10.05.2016, at 12:23, Mladen Marev <mladen.ma...@gmail.com> wrote: > > > > my proxy and firewall allows download of Java content (e.g. Jenkins war > > file) only from HTTPS protected sites. I have tried manual download of v2.2 > > but it has been rejected because HTTP connection. > > I'm pretty sure we are currently unable to provide full HTTPS for Jenkins and > plugin downloads. Even for metadata it's difficult, see e.g. > https://issues.jenkins-ci.org/browse/INFRA-110?focusedCommentId=210433=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-210433 Moving to end-to-end TLS encryption for the Jenkins distribution site is something that is part of an infrastructure project I'm working towards right now. I don't have many details I can share right now, but my hope is that we have TLS distribution before the end of the calendar year. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160510150102.GK30995%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Possible infrastructure compromise
Last week, the infrastructure team identified the potential compromise of a key infrastructure machine. This compromise could have taken advantage of, what I could be categorized as, an attempt to target contributors with elevated access. Unfortunately, when facing the uncertainty of a potential compromise, the safest option is to treat it as if it were an actual incident, and react accordingly. The machine in question had access to binaries published to our primary and secondary mirrors and contributor account information. Since this machine is not the source of truth for Jenkins binaries, we verified that the files distributed to Jenkins users: plugins, packages, etc, were not tampered with. We cannot, however, verify that contributor account information was not accessed or tampered with and, as a proactive measure, we are issuing a password reset for all contributor accounts. We have also spent significant effort migrating all key services off of the potentially compromised machine to (virtual) hardware so the machine can be re-imaged or decommissioned entirely. WHAT YOU SHOULD DO NOW -- If you have ever filed an issue in JIRA, edited a wiki page, released a plugin or otherwise created an account via the Jenkins website, you have a Jenkins community account. You should be receiving a password reset email shortly, but if you have re-used your Jenkins account password with other services we strongly encourage you to update your passwords with those other services. If you’re not already using one, we also encourage the use of a password manager for generating and managing service-specific passwords. This does not apply to your own Jenkins installation, or any account that you may use to log into it. If you do not have a Jenkins community account, there is no action you need to take. WHAT WE'RE DOING TO PREVENT EVENTS LIKE THIS IN THE FUTURE -- As stated above, the potentially compromised machine is being removed from our infrastructure. That helps address the immediate problem but doesn’t put guarantees in place for the future. To help prevent potential issues in the future we’re taking the following actions: * Incorporating more security policy enforcement into our Puppet-driven infrastructure. Without a configuration management tool enforcing a given state for some legacy services, user error and manual mis-configurations can adversely affect project security. As of right now, all key services are managed by Puppet. * Balkanizing our machine and permissions model more. The machine affected was literally the first independent (outside of Sun) piece of project infrastructure and like many legacy systems, it grew to host a multitude of services. We are rapidly evolving away from that model with increasing levels of user and host separation for project services. * In a similar vein, we have also introduced a trusted zone in our infrastructure which is not routable on the public internet, where sensitive operations, such as generating update center information, can be managed and secured more effectively. * We are performing an infrastructure permissions audit. Some portions of our infrastructure are 6+ years old and have had contributors come and go. Any inactive users with unnecessarily elevated permissions in the project infrastructure will have those permissions revoked. I would like to extend thanks, on behalf of the Jenkins project, to CloudBees for their help in funding and migrating this infrastructure. If you have further questions about the Jenkins project infrastructure, you can join us in the #jenkins-infra channel on Freenode or in an Infrastructure Q session I’ve scheduled for next Wednesday (April 27) at 20:00 UTC (12:00 PST). Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160423000623.GG23033%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Any Changes in the Jenkins Mirrors?
enkins-ci.org -1 (ANY) / > [expiry none] SERVERID Local > Location: http://updates.jenkins.io/update-center.json [following] > Closed fd 3 > --2016-04-21 10:04:22-- http://updates.jenkins.io/update-center.json > Resolving updates.jenkins.io... 52.91.151.148 > Caching updates.jenkins.io => 52.91.151.148 > Connecting to updates.jenkins.io|52.91.151.148|:80... connected. > Created socket 3. > Releasing 0x00c93cb0 (new refcount 1). > ---request begin--- > GET /update-center.json HTTP/1.0 > User-Agent: Wget/1.12 (linux-gnu) > Accept: */* > Host: updates.jenkins.io > Connection: Keep-Alive > ---request end--- > HTTP request sent, awaiting response... > ---response begin--- > HTTP/1.1 503 Service Unavailable > Content-Type: text/html; charset=UTF-8 > Content-Length: 2862 > Connection: close > P3P: CP="CAO PSA OUR" > Expires: Thu, 01 Jan 1970 00:00:00 GMT > Cache-Control: no-store, no-cache, must-revalidate, post-check=0, > pre-check=0 > Pragma: no-cache > ---response end--- > 503 Service Unavailable > Closed fd 3 > 2016-04-21 10:04:22 ERROR 503: Service Unavailable. > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/0dc9df76-f1f4-491f-a3ac-9f8652919970%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160421190319.GF23033%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Scheduled maintenance window April 15th - April 17th
(replies inline) On Wed, 20 Apr 2016, Irfan Sayed wrote: > Hello, > Is this done ? > Please let me know as i was waiting for updates to be happen on the wiki > pages. Sorry for the delayed response, I was finding a lot of gremlins in our previous update center generation process. As of this morning, the update center is being updated and has been properly migrated to a new host. With the migration to newer infrastructure, the generation time has dropped dramatically so I've updated the frequency that the data is generated. Now every 30 minutes we should be generating fresh update-center.json files. (Unfortunately updates may still take some time to propagate to secondary mirrors.) I'll be sending more infra updates out soon - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160420184111.GC23033%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Scheduled maintenance window April 15th - April 17th
(replies inline) On Fri, 15 Apr 2016, R. Tyler Croy wrote: > Howdy folks, starting today I am migrating services from various hosts this > weekend. The services that are primarily going to be affected are: > > * ci.jenkins-ci.org > * mirrors.jenkins-ci.org > * LDAP With a *lot* of effort between Kohsuke and myself (with some help from nibalizer, danielbeck and bwalding) we've migrated a few key services. Most notably ldap which is online at its new home. Our mirror infrastructure is also migrated and I will be performing the final cut-over in the morning. Unfortunately we've run out of weekend time for the migration of ci.jenkins-ci.org, which is going to expand into Monday. Aside from builds not running, this means that update center generation is on-hold until the new hosts are properly online. I apologize for the inconvenience and trust that I'm working as fast as my fingers and machine I/O will let me to get the service migration finished. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160418041839.GU3721%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Scheduled maintenance window April 15th - April 17th
Howdy folks, starting today I am migrating services from various hosts this weekend. The services that are primarily going to be affected are: * ci.jenkins-ci.org * mirrors.jenkins-ci.org * LDAP Plus some other minor services, but frankly I believe that nobody will notice those going down for a few minutes :P I apologize for the late notice, but will work to reduce service interruptions as much as I possibly can. Given my current cadence, I don't expect service interruptions today (April 15), but more over the weekend. I will update this thread as the work progresses, if you wish to have more real-time updates please visit #jenkins-infra on Freenode. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160415151627.GQ3721%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Access to http://jenkins-ci.org/census
(replies inline) On Fri, 08 Apr 2016, Rafael Rezende wrote: > From Usage Statistics Privacy Advisory 2016-03-30 > <https://wiki.jenkins-ci.org/display/JENKINS/Usage+Statistics+Privacy+Advisory+2016-03-30> > : > > As soon as we found out about this bug, we disabled third party access to > > the partially decrypted data at http://jenkins-ci.org/census > > > Is there any plan to open it again in the future? You might be interested in some work that Vivek Pandey has been doing to some for our stats infrastructure (https://issues.jenkins-ci.org/browse/INFRA-623). I believe his work might supercede the old (kind of stupid) /census/ approach while enabling us to have a bit better access control around it. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160408162020.GY15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: jenkins.io blog RSS feed link incorrect?
(replies inline) On Fri, 01 Apr 2016, Brian Ray wrote: > Thanks. Surprised I stumbled across it first. Consider your bubble popped! https://twitter.com/jenkinsci/status/714458268865667072 I didn't realize the actual issue until your email however, so kudos on that :) > On Friday, April 1, 2016 at 9:40:33 AM UTC-7, R Tyler Croy wrote: > > > > (replies inline) > > > > On Fri, 01 Apr 2016, Brian Ray wrote: > > > > > The RSS feed link <https://feeds.feedburner.com/~r/ContinuousBlog/> on > > the > > > new Jenkins blog page <https://jenkins.io/node/> seems to have some > > lint in > > > the URL that causes Feedburner to return an HTTP error 400. However if I > > > remove that bit of lint and use a clean URL for the feed > > > <https://feeds.feedburner.com/ContinuousBlog/>, all is good. > > > > > > Is this a bug in that link? I searched for an issue on > > > issues.jenkins-ci.org but came up with nothing. > > > > > > It does look like that's a bug, I've fixed it and the site is regenerating > > now. > > > > > > > > - R. Tyler Croy > > > > -- > > Code: <https://github.com/rtyler> > > Chatter: <https://twitter.com/agentdero> > > > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > > -- > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/a3d51e0a-dcf9-4737-9028-ad96180e3445%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160402040652.GK15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Request for participation: Jenkins Release Officer candidates
(replies inline)
On Mon, 07 Mar 2016, R. Tyler Croy wrote:
> Based on the team lead structure
> (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams)
> which was previously approved in a project governance meeting, I am asking on
> behalf of the Jenkins board[0], for candidates who are willing to act as the
> Jenkins Release Officer[1].
>
>
> The Jenkins Release Officer would play a key role in driving release processes
> and the release tooling. The Release Officer would not play an exclusive role
> in the Jenkins projects release infrastructure but would be the point person
> to:
>
> * Manage keys for signing and producing official Jenkins releases (e.g. GPG
> signing keys, Windows and Mac OS X certificates)
> * Be responsible for release automation to produce LTS and weekly releases
> * Operate LTS/weekly releases directly, or name specific release managers to
> be
> responsible for those releases (e.g. "this person is responsible for this
> LTS
> series, backporting, etc")
> * Act as a single point of contact for the Security Officer to incorporate
> security fixes/backports into releases (this implies membership to Jenkins
> CERT
> team)
On behalf of the governance board, I'm pleased to announce that Oliver Gondza
has been chosen as the Jenkins Release Officer. If you're a user of Jenkins'
LTS releases, you're already familiar with some of Oliver's work. Personally, I
look forward to Oliver continuing to work with abayer, svanoort and numerous
others to help make Jenkins releases of higher quality and more automated.
For reference on the term of this position and responsibilities, please refer
to the Team Leads page:
<https://wiki.jenkins-ci.org/display/JENKINS/Team+Leads>
Cheers
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20160401201455.GH15060%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: jenkins.io blog RSS feed link incorrect?
(replies inline) On Fri, 01 Apr 2016, Brian Ray wrote: > The RSS feed link <https://feeds.feedburner.com/~r/ContinuousBlog/> on the > new Jenkins blog page <https://jenkins.io/node/> seems to have some lint in > the URL that causes Feedburner to return an HTTP error 400. However if I > remove that bit of lint and use a clean URL for the feed > <https://feeds.feedburner.com/ContinuousBlog/>, all is good. > > Is this a bug in that link? I searched for an issue on > issues.jenkins-ci.org but came up with nothing. It does look like that's a bug, I've fixed it and the site is regenerating now. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160401164022.GF15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins 2.0: Turn off Setup wizard
(replies inline) On Thu, 31 Mar 2016, Richard Bywater wrote: > It sounds to me like there's a good use-case for being able to skip the > setup wizard even in "prod" mode? Is the jenkins.install.runSetupWizard > ignored if development = false? If so would it make sense just to skip that > check? I agree, for stuff like puppet-jenkins the provisioning of the Jenkins master doesn't require the Getting Started wizard. If the system property that Baptiste referenced isn't fully turning the wizard off, then we need to fix that before RCs IMHO. > On Fri, 1 Apr 2016 at 10:10 Baptiste Mathus <m...@batmat.net> wrote: > > > There's a sysprop for that, but normally only for development mode. > > But, NOT FOR KIDS, you can confuse things by forcing it to dev mode. > > > > Probably reasonable for continuously starting from scratch from the docker > > container only, not for prod use obviously (beware that you may trigger > > weird behaviours w/ plugins that would use this property to change things > > for dev). > > > > $ docker run -p 8080:8080 --env JAVA_OPTS="-Dhudson.Main.development=true > > -Djenkins.install.runSetupWizard=false" jenkinsci/jenkins:2.0-beta-1 > > > > 2016-03-31 22:44 GMT+02:00 Curt Bushko <cbus...@gmail.com>: > > > >> Hello, > >> > >> I am building a Docker container based on jenkinsci/jenkins:2.0-beta-1. I > >> am autofilling it in with jobs/pipelines but the annoying thing is that > >> every time I run the image I have to go through the setup wizard. > >> > >> How do disable this wizard so that my container will just be up and > >> running? > >> > >> 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. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/jenkinsci-users/149f107d-59d6-4f74-95bc-1b07742f8239%40googlegroups.com > >> <https://groups.google.com/d/msgid/jenkinsci-users/149f107d-59d6-4f74-95bc-1b07742f8239%40googlegroups.com?utm_medium=email_source=footer> > >> . > >> 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. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS53SUUKuoT4qem%3Dj6sgNJ_X3XjXnOmFrE5-JZzyCjAU-Q%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS53SUUKuoT4qem%3Dj6sgNJ_X3XjXnOmFrE5-JZzyCjAU-Q%40mail.gmail.com?utm_medium=email_source=footer> > > . > > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAMui947kKui-ATTvXoNh7oaAAv0arvKiMxJ8ENL2xSiqbk6SoQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160401002023.GD15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins 2.0 alpha release available
(replies inline) On Tue, 29 Mar 2016, Marcos Mendez wrote: > HI, > > Is there a way to automatically skip/disable that initial setup wizard? > I've got everything already pre-configured and just want to use the new war > file. Use the system property `jenkins.install.runSetupWizard` and set to `false` in your /etc/default/jenkins or wherever your JENKINS_ARGS might be defined - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160329164436.GT15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Meet jenkins.io
I finished up the final work for migration from https://jenkins-ci.org to https://jenkins.io today. The final step of the switchover was to redirect non-mapped URLs from jenkins-ci.org over to jenkins.io. This project has been a tremendous amount of work with Gus Reiber, Baptiste Mathaus, James Dumay, Daniel Beck, Oleg Nenashev and a number of other contributors filling in the new website with CSS, Haml, and most importantly AsciiDoc (for documentation!) Some of the features of jenkins.io that are important to me, I'd like to share: * Visual priority given to the LTS release line (yay) * Built-in support for three layers of documentation: solution pages, getting started guides and the "handbook". * Visual elements to highlight upcoming events * Certificates automated via letsencrypt.org (this is my favorite ;)) The site is statically generated and contributions are welcome here: <https://github.com/jenkins-infra/jenkins.io> As I mentioned in our last project meeting, migration of other properties such as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more time. This is an important first step however! Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160324060209.GB15060%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Bruce Schneier Plugin appears broken
(replies inline) On Fri, 11 Mar 2016, Nicholas Geovanis wrote: > FWIW, for your amusement, on a Friday afternoon: The Bruce Schneier Plugin > for jenkins appears to be broken. No Schneier photos replace the butler > Jenkins. OH NO THE FEDS GOT TO HIM! Will you please file a ticket if you haven't already? Bonus points if you can identify and fix the bug :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160314163136.GR13352%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins 2.0 alpha release available
A follow-up on this thread, we released alpha3 today with the new security setup and some other UI improvements, read more about it here: <https://jenkins-ci.org/blog/2016/03/11/new-jenkins-20-preview/> On Mon, 29 Feb 2016, R. Tyler Croy wrote: > As I mention in this blog post: > https://jenkins-ci.org/blog/2016/02/29/jenkins2-alphas/ > > The first Jenkins 2.0 alpha downloads are available (yay!). You can read more > about it on the 2.0 landing page (https://jenkins-ci.org/2.0/), which also > includes the links the download various native packages of the 2.0 alpha. > > > I'm going to be linking to this thread from the page and blog post for > feedback, so by all means, download it and play around with it! > > > Cheers > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > -- > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/20160229233911.GS13352%40blackberry.coupleofllamas.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160311210425.GN13352%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [Jenkins-events] Request for participation: Jenkins Events Officer candidates
(replies inline) On Wed, 17 Feb 2016, R. Tyler Croy wrote: > The Jenkins Events Officer would have an active role in driving and managing > Jenkins community events. Such events include Jenkins User Conference, Jenkins > Area Meetups, other Jenkins community events (FOSDEM, SCALE), and speaking > opportunities. The Events Officer would be tasked with the following > responsibilities: > > * Process incoming events related requests from users, dev, events mailing > lists > * Point of contact for Jenkins community events (mentioned above) > * Drive communication efforts surrounding Jenkins community events > * Drive content/agenda for the Jenkins User Conference > * Plan and coordinate logistics as needed for Jenkins community events > * Oversee and ensure the success of the overall Jenkins Area Meetups: > * Maintainer/organizer of Jenkins Area Meetup account on meetup.com > * Work with organizers to ensure their success - assist as needed with > speaker, sponsors identification > * Guide new organizers process to start up their local JAM On behalf of the governance board, I'm pleased to announce that Alyssa Tong has been chosen as the Jenkins Events Officer. If you do not already know Alyssa, she's basically been running Jenkins related events since the first Jenkins User Conference 2011 and more recently has helped spearhead the Jenkins Area Meetup (JAM) program <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Area+Meetup> For reference on the term of this position and responsibilities, please refer to the Team Leads page: <https://wiki.jenkins-ci.org/display/JENKINS/Team+Leads> Thanks! - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160302211223.GC13352%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins 2.0 alpha release available
(replies inline) On Wed, 02 Mar 2016, Mike Bayliss wrote: > OK - I've the debian/ubuntu package - it's at > http://pkg.jenkins-ci.org/debian-rc/binary/jenkins_2.0_all.deb. > > The link needs correcting on the 2.0 landing page. I've corrected this (https://github.com/jenkins-infra/jenkins.io/commit/fc6239273692b4f4ecb852d9f47fa1bb1ab6e398) and it will appear on the site shortly. Thanks for the catch. > On Wed, Mar 2, 2016 at 2:59 PM, Mike Bayliss <mike.bayl...@gmail.com> wrote: > > > Is the Ubuntu package supposed to be available yet? The link just gives me: > > > > The requested URL /debian-rc/jenkins_2.0_all.deb was not found on this > > server. > > > > Mike > > > > On Tue, Mar 1, 2016 at 11:16 PM, Daniel Beck <m...@beckweb.net> wrote: > > > >> > >> On 01.03.2016, at 15:59, kondarre...@gmail.com wrote: > >> > >> > I am behind proxy and a blank popup (I guess the registration screen) > >> is blocking me from accessing Jenkins web interface. Can you please suggest > >> a work around. > >> > >> This should actually disappear after a while (30 seconds?) and tell you > >> Jenkins cannot access the internet. Does it remain visible even after a > >> long time? > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Jenkins Users" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to jenkinsci-users+unsubscr...@googlegroups.com. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/jenkinsci-users/50782B7C-B8B6-488E-AD0C-931C10AFB0E4%40beckweb.net > >> . > >> 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAC-P8uuJLgvfVjjMciC6m88D%2Bk%2BYLUGp2oGEYbv46Peis%2BWj5w%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160302161229.GX13352%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: Jenkins chooses incorrect node
(replies inline)
On Thu, 25 Feb 2016, Alex Domoradov wrote:
> Some time ago Jenkins has started run jobs on slave node (win 7).
You have a couple options to consider. One when configuring build nodes,
choosing "Only build jobs with label restrictions matching this node" will
ensure that only when you explicitly "Restrict where this project can be run"
and enter the appropriate label. This will ensure Jenkins doesn't schedule work
on that node unless a job has explicitly requested it.
Additionally/optionally, it's a good practice to label all nodes, including the
master,
with labels that describe its capabilities. In your example I would suggest
labeling all nodes which are intended to perform ant builds with the "ant"
label, then restricting your project to only build on nodes labelled with
"ant". This syntax can be combined to include multiple labels via a label
expression, e.g. "ant && linux"
>
>
> [EnvInject] - Loading node environment variables.
>
> Installing JDK jdk-8u74-oth-JPR
> Downloading JDK from
> http://download.oracle.com/otn-pub/java/jdk/8u74-b02/jdk-8u74-windows-x64.exe
> Downloading 196405336 bytes
>
> Installing D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74\jdk.exe
>
> [jdk-sun-1.8.74] $ D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74\jdk.exe
> /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress
> INSTALLDIR=D:\jenkins\tools\hudson.model.JDK\jdk-sun-1.8.74 /L
> D:\jenkins\tools\hudson.model.JDK\install1182473847874408631log
>
> Building remotely on win7 (WINDOWS) in workspace
> D:\jenkins\workspace\resin-deploy
>
> Cloning the remote Git repository
> ...
> [EnvInject] - Injecting environment variables from a build step.
> [EnvInject] - Injecting as environment variables the properties content
> JAVA_HOME=/var/lib/jenkins/tools/hudson.model.JDK/jdk-sun-1.8.74
>
> [EnvInject] - Variables injected successfully.
> FATAL: Cannot find executable from the chosen Ant installation "ant-1.9.6"
> Build step 'Invoke Ant' marked build as failure
> SSH: Current build result is [FAILURE], not going to run.
> Finished: FAILURE
>
>
> The slave node was connected via
>
>
>
> > java -jar d:\jenkins-slave.jar -jnlpUrl
> > http://jenkins.example.net:8080/computer/win7/slave-agent.jnlp -secret
> > {SECRET}
>
>
>
>
> For example build 10 was built on Master node (linux) and build 11 was
> built on Slave (windows 7). How can I revert the old behavior and tell
> Jenkins build all jobs on master node by default ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/59c9cda5-424b-4ff6-a05c-d602ad07f515%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
- R. Tyler Croy
--
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20160225161344.GE13352%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
Re: [Jenkins-infra] Scheduled maintenance notice: 2016-02-20 17:00-20:00 UTC
(replies inline) On Wed, 17 Feb 2016, R. Tyler Croy wrote: > > Since I'm getting good practice at restarting machines, I'm going to schedule > another maintenance window for this Saturday morning (PST) to take care of > some > long outstanding updates. > > During the window services will be coming and going as I roll upgrades through > the cluster. I will roll through the hosts one by one, so *everything* won't > be > offline for the entire window. If you're interested in participating or > following along, join us in #jenkins-infra on Freenode. > > The primary ticket capturing work that needs to be done is: > <https://issues.jenkins-ci.org/browse/INFRA-514> I'm pleased to report that maintenance has been completed and all services are back online and appear to be functioning correctly. If you notice any issues please let me know by replying to this mail on the infra list. - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160220194707.GK17392%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
